Re: EISA & sysfs.

Dave Jones
2004-02-18T15:42:55Z

On Wed, Feb 18, 2004 at 04:24:15PM +0100, Marc Zyngier wrote:

> It looks like hp100 is at least broken wrt probing, since it lacks a
> EISA-ID table terminator. What about changing it to :
>
> static struct eisa_device_id hp100_eisa_tbl[] = {
> { "HWPF180" }, /* HP J2577 rev A */
> { "HWP1920" }, /* HP 27248B */
> { "HWP1940" }, /* HP J2577 */
> { "HWP1990" }, /* HP J2577 */
> { "CPX0301" }, /* ReadyLink ENET100-VG4 */
> { "CPX0401" }, /* FreedomLine 100/VG */
> { "" }, /* THIS ENTRY IS MANDATORY !!! */
> };

I'll give it a try in a few minutes..

> Dave> I've seen same exactly the same behaviour with quite a few other
> Dave> modules. For my 'modprobe/rmmod script-o-death', I just ended
> Dave> up disabling EISA in that test tree, as it was too painful to
> Dave> hit this issue over and over, but its a real situation that
> Dave> could bite users of for eg, vendor kernels.
>
> What are the other modules ?

See the 'modprobe script-o-doom' I posted last night. Just loading and
unloading various modules causes crashes.

> I'd like to reproduce the problem (I have
> no PCI hp100 to check if the above fixes the problem).

Me either. This is the case that crashes. I'll bet it works fine
if you actually have hardware, as that was the case that got tested
when the driver got changed last.

Dave