#15141 closed bug (fixed)
Haiku hangs while booting off usb disk
| Reported by: | BeRUS | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Drivers/USB/XHCI | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #15092 | |
| Platform: | All |
Description (last modified by )
Attachments (12)
Change History (30)
comment:1 by , 5 years ago
| Component: | - General → System |
|---|---|
| Description: | modified (diff) |
| Summary: | Hangs here → Haiku hangs at boot periodically |
comment:2 by , 5 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 5 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Haiku hangs at boot periodically → Haiku hangs while booting off usb2 disk |
by , 5 years ago
| Attachment: | IMG_20190707_200132.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20190707_200414.jpg added |
|---|
comment:4 by , 5 years ago
| Component: | System → Drivers/USB/XHCI |
|---|---|
| Description: | modified (diff) |
| Owner: | changed from to |
| Platform: | x86-64 → All |
| Summary: | Haiku hangs while booting off usb2 disk → Haiku hangs while booting off usb disk |
comment:5 by , 5 years ago
comment:6 by , 5 years ago
According to BeRUS on Telegram this (or something similar) also happened on beta1. He managed to install it earlier (he doesn't recall the exact hrev) by letting it sit there for some time and eventually it booted to the Desktop.
comment:7 by , 5 years ago
My guess is that in some revision xhci was slightly less broken on his hardware.
comment:8 by , 5 years ago
In his other ticket, he lists XHCI-attached mice as being "laggy" following recent changes; so it's very possible his controller is broken in some strange way. Can I get a syslog including the PCI ID of the XHCI controller?
by , 5 years ago
| Attachment: | syslog.old added |
|---|
by , 5 years ago
| Attachment: | syslog.null added |
|---|
comment:9 by , 5 years ago
These syslogs are filled with XHCI error messages and contain no real useful data that was not already in the ticket.
by , 5 years ago
| Attachment: | IMG_20190712_123639.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20190712_123749.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20190712_124107.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20190712_124339.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20190712_124556.jpg added |
|---|
comment:10 by , 5 years ago
| Blocking: | 15092 added |
|---|
comment:12 by , 5 years ago
Actually, please retest after hrev53855, as that may also change things.
comment:13 by , 5 years ago
According to original author it boots further now and KDLs at intel_cstates driver.
by , 5 years ago
| Attachment: | IMG_20200225_221109.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20200225_221128.jpg added |
|---|
by , 5 years ago
| Attachment: | IMG_20200225_221148.jpg added |
|---|
comment:16 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
It seems this is fixed if it got all the way to intel_cstates, anyway. A new ticket should be opened for the cstates issue (and the graphics driver issue, it looks like.)
comment:17 by , 5 years ago
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
comment:18 by , 5 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
When did this start occurring?