Attachments (3)
Change History (15)
by , 6 years ago
Attachment: | iprowifi2200_panic.log added |
---|
comment:1 by , 6 years ago
Also similar fixed issue where driverfailed gracefully (regression maybe?): #10891
by , 6 years ago
Attachment: | iprowifi2200_panic_long.log added |
---|
comment:3 by , 6 years ago
After 3 panics there is another panic message three times (thread 'daemon") and after that panics start oscillating between thread "daemon" and thread "a:392:x-vnd.Haiku-FirstBootProm" (with slight changes, first part of panic is the same in except first three)
comment:4 by , 6 years ago
Same problem here...
I have an old 32bit Notebook with an Intel Pentium M Processor, and an Intel PRO/Wireless 2200BG card.
I've tried to install the latest Haiku OS (haiku-nightly-hrev52249-x86_gcc2_hybrid-anyboot), but as soon as the graphical boot-up finishes, and before the installer or desktop could start, I get a kernel panic that blames iprowifi2200. :-(
I've attached a "screenshot" made with my smartphone...
@halamix2: How did you get the message in a pure text log file? And how the long version?
by , 6 years ago
Attachment: | Haiku_Kernel_Panic_iprowifi2200.jpg added |
---|
comment:5 by , 6 years ago
I should mention that I have Pentium M as well (the laptop is Fujitsu Lifebook s7020) (and another error in intel_extreme but I hope it doesn't interfere with this one)
@Nuke: As for the log I connected through rs-232 cable
comment:6 by , 6 years ago
The other KDLs are probably timing issues caused by this one; for the beta branch at least the KDEBUG_LEVEL will be turned down a bit so these should be gone.
For now you can just blacklist the driver.
comment:7 by , 6 years ago
@halamix2: OK, thank you! :-) I'll give it a try, still having some RS-232 cables here... somewhere... ;-)
comment:8 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This was fixed by changes to the compat layer.
comment:9 by , 6 years ago
I have to say, using hrev52527 my R50e ThinkPad gives me the same first for iprowifi2200, then ipro1000 too.
comment:10 by , 6 years ago
I have encountered this bug in nightly build hrev52815 on my Thinkpad X41.
comment:11 by , 6 years ago
It is almost certainly not the same bug, as the one described in this ticket was pretty definitively fixed, and the code in question hasn't changed since then. So, please open a new ticket and attach a picture.
comment:12 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
log file