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
[email protected]
On Tue, 2002-08-20 at 15:10, jools wrote:
> 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.
Its hitting a setup check for later chips when it finds them on a 66MHz
PCI bus slot. At that point the current code aborts because the 66MHz
tables for the HPT374 haven't been verified yet.
The status on that bit is an Andre question
On Tue, 2002-08-20 at 15:10, 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.
Please try the next -ac when it appears. I've changed the bugs to error
back more intelligently so hopefully you'll get a sensible response even
though you want get UDMA
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
> [email protected]
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> 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
> 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.
My HPT374 controller works with the new 2.4.20-pre2-ac6 patch, running at
ATA-66.
/proc/ide/hpt366 shows only primary and secondary channel, so I guess thats
why the hard drives on channel 3 and 4 is not working?
-
UAG
I just got a reply from HighPoint and they claim they do not have support
for a 66MHz base PLL for hpt374/hpt372.
So that make is more interesting.
On Thu, 22 Aug 2002, Ulf-Andre Gramstad wrote:
> > 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.
>
> My HPT374 controller works with the new 2.4.20-pre2-ac6 patch, running at
> ATA-66.
> /proc/ide/hpt366 shows only primary and secondary channel, so I guess thats
> why the hard drives on channel 3 and 4 is not working?
>
>
> -
> UAG
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> 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
> I just got a reply from HighPoint and they claim they do not have support
> for a 66MHz base PLL for hpt374/hpt372.
>
> So that make is more interesting.
The kernel works fine when all my HD's are connected to IDE1 and IDE2 on the
raid controller, but only one raid drive is enabled by hptraid.c.
Some of my info:
hde: 241254720 sectors (123522 MB) w/1863KiB Cache, CHS=239340/16/63,
UDMA(100)
hdf: 241254720 sectors (123522 MB) w/1863KiB Cache, CHS=239340/16/63,
UDMA(100)
hdg: 156250000 sectors (80000 MB) w/2048KiB Cache, CHS=155009/16/63,
UDMA(100)
hdh: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63,
UDMA(100)
hde/hdf = raid0 (240gb)
hdg/dhd = raid0 (160gb)
My /proc/partitions:
114 0 156249984 ataraid/d0
114 1 156248158 ataraid/d0p1
34 0 78125000 hdg
34 64 78150744 hdh
33 0 120627360 hde
33 64 120627360 hdf
3 0 40209120 hda
3 1 265072 hda1
3 2 39937590 hda2
messages:
Aug 25 21:40:04 fantasy kernel: ataraid/d0: ataraid/d0p1
Aug 25 21:40:04 fantasy kernel: Highpoint HPT370 Softwareraid driver for
linux version 0.01
Aug 25 21:40:04 fantasy kernel: Drive 0 is 76293 Mb
Aug 25 21:40:04 fantasy kernel: Drive 1 is 76319 Mb
Aug 25 21:40:04 fantasy kernel: Raid array consists of 2 drives.
Shouldn't hptraid.c also create ataraid/d1 and ataraid/d1p1?
Mvh
Ulf-Andre Gramstad