Re: hpt374 / BUG();

[Andre Hedrick]

You have a system where it actually have the PLL already set and in
66-clock base?  You are the first person to ever hit this BUG().
I will need to work with HighPoint to finish the timing table.

If you would have several device of various max transfer rate limits you
could attach without the driver being built it, it would give me a few
data point to verify if the table I have started is even close.

Cheers,

On Tue, 20 Aug 2002, jools wrote:

> Hi
> 
> I'm using a RocketRAID 404 (hpt374) and a Asus A7v266.
> When trying to boot from a 'htp374-enabled' kernel like 2.4.19-ac4 or
> 2.4.20-pre2-ac4, i keep getting kernel panic at hpt366.c:1393.
> Does anyone know why this happens, or what I might do to correct this
> problem? I have tried every patch I can find for the 2.4 kernel.
> 
> hpt366.c line 1392:
> 
> if (hpt_minimum_revision(dev,8))
>         BUG();
> else if (hpt_minimum_revision(dev,5))
>         dev->driver_data = (void *) fifty_base_hpt372;
> else if (hpt_minimum_revision(dev,4))
>         dev->driver_data = (void *) fifty_base_hpt370a;
> else
>         dev->driver_data = (void *) fifty_base_hpt370a;
> printk("HPT37X: using 50MHz internal PLL\n");
> goto init_hpt37X_done;
> 
> 
> Jools
> [e-mail]
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Andre Hedrick
LAD Storage Consulting Group