Opened 11 months ago

Last modified 10 months ago

#14820 new bug

regression: won't boot until iprowifi2100 blacklisted

Reported by: taos Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/iprowifi2100 Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

hrev52748 gcc2hybrid

It's no longer possible to boot Haiku on an Acer Travelmate 800 (Centrino, ca. 2003) without blacklisting the iprowifi2100 driver. Without blacklisting, booting stops after the last boot icon (rocket?) lights up. Most of the time my wifi LED starts blinking, then emits continuously, but booting never gets to the desktop.

It was once possible to actually connect wirelessly to a network on this computer.

The attached syslog contains several boot attempts:

Last - booted to desktop with blacklisted iprowifi2100.

Second to last - boot attempt without blacklisting, wifi LED did not light up.

Third to last (and others before) - boot attempt without blacklisting, wifi LED lighted up.

Attachments (14)

syslog (389.2 KB ) - added by taos 11 months ago.
syslog with several boot attempts
listdev (2.7 KB ) - added by taos 11 months ago.
listdev output
bt_kernel_daemon_net_server.jpg (2.6 MB ) - added by taos 11 months ago.
bt for net_server and kernel daemon
bt_ipw_intr_handler.jpg (1.5 MB ) - added by taos 11 months ago.
bt for ipw intr handler
bt_iprowifi.jpg (2.1 MB ) - added by taos 11 months ago.
bt for other iprowifi2100 related threads
syslog_tail_50.jpg (1.8 MB ) - added by taos 11 months ago.
last 50 lines of syslog
syslog.2 (306.6 KB ) - added by taos 10 months ago.
hrev52502 syslog
syslog.3 (306.5 KB ) - added by taos 10 months ago.
hrev52533 syslog
syslog.4 (306.5 KB ) - added by taos 10 months ago.
hrev52539 syslog
syslog.5 (309.5 KB ) - added by taos 10 months ago.
hrev52853 syslog
syslog.6 (312.5 KB ) - added by taos 10 months ago.
hrev52860 syslog
syslog.7 (306.4 KB ) - added by taos 10 months ago.
hrev52843 syslog
syslog.8 (306.4 KB ) - added by taos 10 months ago.
hrev52859 syslog
syslog.9 (306.2 KB ) - added by taos 10 months ago.
hrev52849 syslog

Change History (29)

by taos, 11 months ago

Attachment: syslog added

syslog with several boot attempts

by taos, 11 months ago

Attachment: listdev added

listdev output

comment:1 by waddlesplash, 11 months ago

iprowifi2100 is not mentioned in the syslog at all, so that will be pretty hard to debug.

Try blacklisting your ethernet driver instead and see if that also fixes the problem. There was a similar issue that "solved itself" in which one had to blacklist one driver or the other and then things worked.

in reply to:  1 comment:2 by taos, 11 months ago

Replying to waddlesplash:

Try blacklisting your ethernet driver instead and see if that also fixes the problem. There was a similar issue that "solved itself" in which one had to blacklist one driver or the other and then things worked.

Do you think of #14667? As I've already written there, blacklisting my ethernet driver does not let me boot. And the problem didn't resolve itself for me. #14667 also contains a syslog from hrev52547 that still mentions iprowifi2100, the newer syslog only refers to "device 1043: PRO/Wireless LAN 2100 3B Mini PCI Adapter (MIM2000/Centrino)".

comment:3 by waddlesplash, 11 months ago

Could you please drop into KDL after the hang begins (via Alt+PrntScrn+D) and then get backtraces of the net_server and kernel_daemon threads (you can find their IDs by running threads | grep daemon and threads | grep net_server, and then run bt NUM). That should give more insight into what's going wrong.

comment:4 by taos, 11 months ago

I'll try this as soon as I get my hands on the Acer TM 800 again, probably next weekend or the weekend after.

comment:5 by taos, 11 months ago

I've attached the backtraces for kernel daemon, net_server, ipw intr handler, and other iprowifi related threads (hrev52798).

Last edited 11 months ago by taos (previous) (diff)

by taos, 11 months ago

bt for net_server and kernel daemon

by taos, 11 months ago

Attachment: bt_ipw_intr_handler.jpg added

bt for ipw intr handler

by taos, 11 months ago

Attachment: bt_iprowifi.jpg added

bt for other iprowifi2100 related threads

by taos, 11 months ago

Attachment: syslog_tail_50.jpg added

last 50 lines of syslog

comment:6 by waddlesplash, 11 months ago

Unfortunately all of those things look relatively normal; so I'm not sure what the problem could be.

comment:7 by taos, 10 months ago

I'm checking a few nightlies to find out when the problem started (I'll add the syslogs and update this comment):

hrev52502 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)

hrev52533 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)

hrev52539 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)

hrev52547 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED blinking

Last edited 10 months ago by taos (previous) (diff)

by taos, 10 months ago

Attachment: syslog.2 added

hrev52502 syslog

by taos, 10 months ago

Attachment: syslog.3 added

hrev52533 syslog

by taos, 10 months ago

Attachment: syslog.4 added

hrev52539 syslog

comment:8 by waddlesplash, 10 months ago

hrev52539 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present, but can't see any wireless networks)

hrev52547 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED blinking

Now that is extremely interesting, because there are no changes to the iprowifi2100 driver in that range, and so I think hrev52546 is the only changeset of any potential relevance.

Within that range, this is the only commit which might be suspect, and all error paths added in that commit will print to syslog, save the _user_set_memory_protection one, which is rarely (if ever?) called.

If you can do a custom build, reverting that individual commit and seeing if it fixes something would be very interesting.

comment:9 by taos, 10 months ago

Where will this change end up? In haiku.hpkg? As far as I remember I haven't been able to successfully build a complete image for quite a long time in haiku. Individual files or (some) packages on the other hand should build fine. However, I won't have time until Friday to start a custom build and check if reverting the mentioned commit solves the issue.

I'll also try to find out when the iprowifi2100 stopped seeing wireless networks (not related to the boot issue).

comment:10 by humdinger, 10 months ago

You can just do "jam -q iprowifi2100" and copy the resulting binary to /boot/system/non-packaged/add-ons/kernel/drivers/bin/iprowifi2100 . Not sure if you need to blacklist the original system driver...

comment:11 by waddlesplash, 10 months ago

No, the relevant changes affect only the kernel and not this driver. haiku.hpkg will have to be rebuilt.

comment:12 by humdinger, 10 months ago

Sorry for the misinformation...

comment:13 by taos, 10 months ago

Just wanted to update haiku before starting to build haiku.hpkg with the reverted commit. I'm on hrev52874 now (updated from hrev52833) and the boot problem is gone. In addition, iprowifi2100 can see a number of wireless networks (except mine, of course). Was there a commit this week that could have fixed something related to the boot issue?

comment:14 by waddlesplash, 10 months ago

I don't think so, but there were a few kernel changes that could be relevant, though that would imply there was some deeper issue they just prevented. Could you try to narrow down that range a bit by bisecting?

by taos, 10 months ago

Attachment: syslog.5 added

hrev52853 syslog

by taos, 10 months ago

Attachment: syslog.6 added

hrev52860 syslog

by taos, 10 months ago

Attachment: syslog.7 added

hrev52843 syslog

by taos, 10 months ago

Attachment: syslog.8 added

hrev52859 syslog

by taos, 10 months ago

Attachment: syslog.9 added

hrev52849 syslog

comment:15 by taos, 10 months ago

Okay, now I'm a little puzzled:

hrev52833 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED blinking

hrev52843 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, but can't see any wireless networks

hrev52849 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, but can't see any wireless networks

hrev52853 - no problem during first boot (but no /dev/net/iprowifi2100/0), can't boot to desktop after installing the firmwares, stops at blue background, wifi indicator LED off

hrev52859 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, can see some but not all wireless networks

hrev52860 - no problem during first boot (but no /dev/net/iprowifi2100/0), boots to desktop after installing the firmwares (/dev/net/iprowifi2100/0 present), wifi indicator LED off, can see some but not all wireless networks

Note: See TracTickets for help on using tickets.