ipro100 causes issues on shared IRQ lines

[gjlgg]

I just installed Beta 3 on a Dell Latitude D500, and I've been having troubles getting it to boot. Originally it would only boot in SafeMode, but I was able to narrow it down to just needed to disable net_server. If I disable net_server, everything (but the network) seems to be exactly as I expect it. If I do not disable net_server, after the Rocket icon the screen goes black and nothing else happens. I did launch KDL and got some information that way, but the system won't boot. I attach a photo of the KDL, the syslog, and the output of listdev.

My D500 has the following networking hardware:

• Intel PRO/100 VE (ethernet)
• Intel PRO/Wireless 2100 3B (wireless)
• Intel 82801DB/DBL/DBM (AC'97 Modem)

Desired outcome: to be able to use Haiku with net_server enabled (and ultimately boot normally and use networking).

Note that this is the x86 version because the Pentium M is 32-bit.

[gjlgg]

Output of listdev

[gjlgg]

Copy of syslog file

[gjlgg]

Photograph of KDL with output from bt and ints

[waddlesplash]

That is quite a lot of interrupts for ipro100. I would imagine the driver is somehow getting stuck.

[gjlgg]

Replying to waddlesplash:

That is quite a lot of interrupts for ipro100. I would imagine the driver is somehow getting stuck.

What is the recommended way to disable/remove the driver? I tried to rename/remove the driver in /system/add-ons/kernel/drivers/bin per the ReportingBugs guide, but the read-only file system stopped me. I also tried booting into a live USB environment, but I guess the /system/add-ons directory doesn't exist yet? (This is essentially my first time using Haiku, so perhaps I'm missing some standard set of steps to modify the /system files.)

[waddlesplash]

You use the "blocklisting" feature, either via the bootloader (temporarily) or via settings file. Described in more detail: ​https://www.haiku-os.org/guides/daily-tasks/disable-package-entries

[waddlesplash]

Most of the directories in /system are read-only because they are a "union mount" of the packages in /system/packages by packagefs, so indeed the data in there is read-only and also not modifiable from another system. You can change the installed packages on a non-running system, boot an older state, or use the blocklisting features to disable individual components.

[waddlesplash]

LOL, the glue interrupt routine for this driver doesn't actually check interrupt statuses: ​https://github.com/haiku/haiku/blob/master/src/add-ons/kernel/drivers/network/ether/ipro100/glue.c#L24

No wonder there are so many interrupts, probably something else on the IRQ line is what is really generating them. I'll see if that TODO can be fixed tomorrow.

[gjlgg]

Replying to waddlesplash:

You use the "blocklisting" feature, either via the bootloader (temporarily) or via settings file. Described in more detail: ​https://www.haiku-os.org/guides/daily-tasks/disable-package-entries

Thanks so much for the quick reply and for apparently figuring out the source of the problem! I did blocklist the driver and can confirm that the system boots normally now when the ipro100 driver is not loaded.

[waddlesplash]

hrev55580 should hopefully fix this. (New nightly builds should be available tomorrow and you can test then. Or if you are feeling intrepid, you can build the driver yourself and see what happens.)

[waddlesplash]

Any chance you have been able to retest this?