Opened 9 years ago

Closed 8 years ago

#6238 closed bug (fixed)

Kernel panic on Lenovo W510

Reported by: Tux Owned by: mmlr
Priority: normal Milestone: R1
Component: Drivers/USB Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

When I moved my Haiku disk to an Lenovo W510 I get the following Panic message (attached image)

Attachments (4)

panic.jpg (111.7 KB) - added by Tux 9 years ago.
Picure of panic message
panic2.jpg (119.4 KB) - added by Tux 9 years ago.
Retry with the haiku-nightly-hrev37268-x86gcc4hybrid-anyboot image.
lsusb.txt (486 bytes) - added by Tux 9 years ago.
dump of lsusb from ubuntu on same hardware.
lspci.txt (5.3 KB) - added by Tux 9 years ago.
dump of lspci -nn from ubuntu on same hardware.

Download all attachments as: .zip

Change History (7)

Changed 9 years ago by Tux

Attachment: panic.jpg added

Picure of panic message

comment:1 Changed 9 years ago by Tux

This message appears right after the third icon get colorized in the boot sequence.

Changed 9 years ago by Tux

Attachment: panic2.jpg added

Retry with the haiku-nightly-hrev37268-x86gcc4hybrid-anyboot image.

Changed 9 years ago by Tux

Attachment: lsusb.txt added

dump of lsusb from ubuntu on same hardware.

Changed 9 years ago by Tux

Attachment: lspci.txt added

dump of lspci -nn from ubuntu on same hardware.

comment:2 Changed 9 years ago by luroh

Component: - GeneralDrivers/USB
Owner: changed from nobody to mmlr
Platform: x86-64All
Version: R1/alpha2R1/Development

Guessing this has something to do with the USB 3.0 hub present in that machine.

comment:3 in reply to:  2 Changed 8 years ago by mmlr

Resolution: fixed
Status: newclosed

Replying to luroh:

Guessing this has something to do with the USB 3.0 hub present in that machine.

No, this merely is the virtual USB 3.0 root hub, so apparently there's an XHCI controller in that device. This won't be seen by Haiku at all.

This is almost for sure the same thing as fixed in hrev37409 (from a few days later). Given that that laptop has the same Gobi chip in it, there probably is the same broken USB descriptor. Basically the descriptor points to an inexistent index that was previsouly unchecked. The fix is valid as it should absolutely be checked, how to eventually make the device usable is another question though. I'll close this one, please reopen if this specific problem still persists.

Note: See TracTickets for help on using tickets.