Opened 3 months ago

Last modified 4 weeks ago

#19011 new bug

Haiku hangs (AHCI errors) then panics on ASRock Z170 Pro4S system (only on 32-bit)

Reported by: Illen Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Disk/AHCI Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #19191
Platform: x86

Description

Haiku hangs for about an hour trying to access disk devices and eventually panics on ASRock Z170 Pro4S board. This happens only on 32 bit x86 build, x64 build does boot to desktop.

Attachments (2)

z170.log (90.9 KB ) - added by Illen 3 months ago.
hrev58288 (56.6 KB ) - added by Illen 4 weeks ago.

Download all attachments as: .zip

Change History (9)

by Illen, 3 months ago

Attachment: z170.log added

comment:1 by waddlesplash, 3 months ago

Component: - GeneralDrivers/Disk/AHCI
Summary: Haiku hangs and eventually panics on ASRock Z170 Pro4S system (only on 32 bit x86 build)Haiku hangs (AHCI errors) then panics on ASRock Z170 Pro4S system (only on 32-bit)

Is this a regression from the recent AHCI changes or has it always been this way?

comment:2 by Illen, 3 months ago

I don't remember such problems with 32 bit build on this board in the past. That was a while ago though and the hardware configuration has changed multiple times since then. Will need to try some older builds too.

Also worth a mention that this is USB boot attempt (not booting from any AHCI disk), and I also saw some dprints about nvme fallback to polling instead of using interrupts, so not sure if this problem with just AHCI driver.

comment:3 by Illen, 3 months ago

I can reproduce that even on the beta4, so this probably started happening due to some hardware (or UEFI settings?) change or 32 bit build never really worked on that board.

Version 0, edited 3 months ago by Illen (next)

comment:4 by waddlesplash, 5 weeks ago

Blocking: 19191 added

comment:5 by waddlesplash, 4 weeks ago

Please retest after hrev58277.

comment:6 by Illen, 4 weeks ago

Still happens on hrev28288.

by Illen, 4 weeks ago

Attachment: hrev58288 added

comment:7 by waddlesplash, 4 weeks ago

Looks like interrupts are broken somehow; the NVMe driver switches to polling mode.

Note: See TracTickets for help on using tickets.