Hello,
we are using a Promise SuperTrak RAID controller together with the
integrated i2o-drivers in the linux kernel 2.4.18. Everything works fine
so far.
Now we wanted to upgrade to kernel 2.4.20. Configuration was unchanged.
But now the system hangs at boot time:
When the IDE driver is loaded, it finds the system disk /dev/hda just
like before. But with 2.4.20 the IDE driver also finds disks /dev/hde,
/dev/hdf and so on which belong to the raid system. At this point many
"interrupt lost" messages appear on the screen and the system hangs. It
never gets far enough to load i2o.
Any ideas?
Thanks,
Sebastian
It shouldn't find /dev/hde ... /dev/hdj (there's some problem with the
detection mechanism), as these are I2O devices, and thus it's
/dev/i2o/hd?. You have to stop the discovery process by adding
hde=noprobe hdf=noprobe hdg=noprobe hdh=noprobe hdi=noprobe hdj=noprobe
to the lilo append variable.
BTW, I'm using 2.4.20-pre10-ac1 and it runs rock solid (despite some
1-10s stalls that seem to be controller related).
On Thu, 2003-01-16 at 11:27, Sebastian Zimmermann wrote:
> Hello,
>
> we are using a Promise SuperTrak RAID controller together with the
> integrated i2o-drivers in the linux kernel 2.4.18. Everything works fine
> so far.
>
> Now we wanted to upgrade to kernel 2.4.20. Configuration was unchanged.
> But now the system hangs at boot time:
>
> When the IDE driver is loaded, it finds the system disk /dev/hda just
> like before. But with 2.4.20 the IDE driver also finds disks /dev/hde,
> /dev/hdf and so on which belong to the raid system. At this point many
> "interrupt lost" messages appear on the screen and the system hangs. It
> never gets far enough to load i2o.
>
> Any ideas?
>
> Thanks,
>
> Sebastian
>
> -
> 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/
--
Juergen "George" Sawinski | Phone: +49-6221-486-308
Max-Planck Institute for Medical Research | Fax: +49-6221-486-325
Dept. of Biomedical Optics | Mobile: +49-171-532 5302
Jahnstr. 29 |
D-69120 Heidelberg |
Germany |
GPG Key/Fingerprint: 9A5F7A31/86F2E5D5EDF4D9983BDD3F23986F154F9A5F7A31
Am Don, 2003-01-16 um 12.23 schrieb Juergen "George" Sawinski:
> It shouldn't find /dev/hde ... /dev/hdj (there's some problem with the
> detection mechanism), as these are I2O devices, and thus it's
> /dev/i2o/hd?. You have to stop the discovery process by adding
>
> hde=noprobe hdf=noprobe hdg=noprobe hdh=noprobe hdi=noprobe hdj=noprobe
>
> to the lilo append variable.
Yes, thank you. Now I can boot. (I also had to add /dev/hdm and /dev/hdo
though.)
Nonetheless, I still consider this a kernel bug. The kernel should boot
without the workaround as it did with version 2.4.18.
Sebastian
Try the Alan Cox patch set.
I should have fixed the mess introduced in 2.4.19 by the OEM vendor.
On 20 Jan 2003, Sebastian Zimmermann wrote:
> Am Don, 2003-01-16 um 12.23 schrieb Juergen "George" Sawinski:
> > It shouldn't find /dev/hde ... /dev/hdj (there's some problem with the
> > detection mechanism), as these are I2O devices, and thus it's
> > /dev/i2o/hd?. You have to stop the discovery process by adding
> >
> > hde=noprobe hdf=noprobe hdg=noprobe hdh=noprobe hdi=noprobe hdj=noprobe
> >
> > to the lilo append variable.
>
> Yes, thank you. Now I can boot. (I also had to add /dev/hdm and /dev/hdo
> though.)
>
> Nonetheless, I still consider this a kernel bug. The kernel should boot
> without the workaround as it did with version 2.4.18.
>
> Sebastian
>
>
> -
> 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