Opened 3 years ago

Closed 2 years ago

#17276 closed bug (fixed)

[usb_hid] crash in usb_hid_device_added

Reported by: Animortis0 Owned by: waddlesplash
Priority: normal Milestone: R1/beta4
Component: Drivers/USB Version: R1/Development
Keywords: Cc: bga
Blocked By: Blocking: #17846
Platform: All

Description

Getting the attached kernel panic on booting from USB with the latest nightly (55443). The stable version does not boot at all, either. Seems to be related to USB. Without USB, I can't get to the boot menu to blacklist this stuff, so idk what to do. Attached.

Attachments (4)

haiku-kernel-panic-55443.jpg (1.5 MB ) - added by Animortis0 3 years ago.
Screenshot of kernel panic
Haiku-Error-55768.jpg (4.5 MB ) - added by Animortis0 3 years ago.
55768
55772.jpg (3.5 MB ) - added by Animortis0 3 years ago.
Nightly 55772 error message
error-haiku-master-hrev55961-x86_64-anyboot.jpg (3.6 MB ) - added by Animortis0 3 years ago.
hrev55961 error March232022

Change History (25)

by Animortis0, 3 years ago

Screenshot of kernel panic

comment:1 by waddlesplash, 3 years ago

Component: - GeneralDrivers/USB
Owner: changed from nobody to waddlesplash
Status: newassigned

comment:2 by diver, 3 years ago

Summary: Kernel panic on boot -- related to USB?[usb_hid] crash in usb_hid_device_added

comment:3 by diver, 3 years ago

You can blacklist it using the bootloader.

comment:4 by Animortis0, 3 years ago

I think it isn't detecting my USB keyboard due to this error, so I haven't been able to get the boot menu up.

comment:5 by diver, 3 years ago

The bootloader starts before the kernel and drivers. Sometimes it's tricky to get there. Try to smash spacebar early in the boot process before the icons show up.

comment:6 by waddlesplash, 3 years ago

Does this occur on prior nightlies or any stable version?

comment:7 by Animortis0, 3 years ago

I used it on two other prior nightlies and got a similar error. I can’t get the stable version to boot past the load splash, so I’m not sure if it’s a similar error.

comment:8 by Animortis0, 3 years ago

Update: Blacklisting the component (/boot/system/add-ons/kernel/drivers/dev/input/usb_hid) did allow me to boot, but then I can't use my mouse or keyboard. Nightly 55481.

comment:9 by Animortis0, 3 years ago

I suspect I have failing hardware that's causing this. Other OS's are reporting an error with the USB hub, too. Their ability to boot depends on how well they bypass the error. A potential fix might be to ignore the hub if it doesn't work?

comment:10 by bga, 3 years ago

FWIIW, I have exactly the same issue on an Alienware keyboard and it is definitely not failing hardware (it is brand new and other OSs have no issues with it).

comment:11 by bga, 3 years ago

Some information that might be helpful:

Booting without the keyboard and connecting it after boot results in exactly the same crash.

I tried with a different USB keyboard and was able to boot, but then. connecting my mouse stalled usb_hid (I guess and keyboard and mouse did not work).

comment:12 by bga, 3 years ago

Cc: bga added

comment:13 by waddlesplash, 3 years ago

Does using USB Passthrough with these devices in a VM cause the same KDLs?

comment:14 by Animortis0, 3 years ago

I can pass through a USB of the Haiku nightly installer in a Virt Manager instance, but I don't get any errors. It loads it fine.

comment:15 by waddlesplash, 3 years ago

I meant with one of the crashing HID devices.

comment:16 by Animortis0, 3 years ago

I'm not sure quite how to do that.

Attaching the latest crash as of 55768.

by Animortis0, 3 years ago

Attachment: Haiku-Error-55768.jpg added

55768

comment:17 by korli, 3 years ago

Could you check at least with hrev55771

by Animortis0, 3 years ago

Attachment: 55772.jpg added

Nightly 55772 error message

comment:18 by waddlesplash, 3 years ago

Please retest with a recent nightly.

by Animortis0, 3 years ago

hrev55961 error March232022

comment:19 by waddlesplash, 3 years ago

This is still not the original problem. It seems your system cannot (anymore?) boot from USB. That needs a separate ticket.

comment:20 by waddlesplash, 2 years ago

Blocking: 17846 added

comment:21 by waddlesplash, 2 years ago

Milestone: UnscheduledR1/beta4
Resolution: fixed
Status: assignedclosed

Should be fixed by hrev56432.

Note: See TracTickets for help on using tickets.