Opened 6 years ago

Closed 7 months ago

#10769 closed bug (not reproducible)

PANIC: get_boot_partitions failed

Reported by: AlexeiZavjalov Owned by: nobody
Priority: high Milestone: Unscheduled
Component: Drivers/Disk/ATA Version: R1/Development
Keywords: boot-failure Cc:
Blocked By: Blocking: #11508
Has a Patch: no Platform: All

Description

Haiku revision: hrev47127

Serial dump is attached.

Attachments (4)

haiku_log.txt (64.0 KB ) - added by AlexeiZavjalov 6 years ago.
haiku-nightly-hrev51528-x86_64-anyboot-KDL.JPG (4.2 MB ) - added by rhodes 2 years ago.
chromebook xe500c12 KDL
chromebook-xe500c12-hrev51538.JPG (848.5 KB ) - added by rhodes 2 years ago.
Here's the KDL from hrev51538
ToshibaL35_syslog (150.1 KB ) - added by totish 14 months ago.

Change History (25)

by AlexeiZavjalov, 6 years ago

Attachment: haiku_log.txt added

comment:1 by bonefish, 6 years ago

Component: SystemDrivers/Disk

I'm not particularly familiar with the AHCI module, but the output in the log suggests that something goes wrong there:

1207	ahci: AHCIPort::ScsiTestUnitReady port 0
1208	ahci: AHCIPort::ScsiInquiry port 0
1209	ahci: ExecuteAtaRequest port 0: device is busy
1210	ahci: AHCIPort::ResetPort port 0
1211	ahci: AHCIPort::ResetPort port 0, deviceBusy 1, forceDeviceReset 0
1212	ahci: AHCIPort::PostReset port 0
1213	ahci: device signature 0x00000101 (ATA)
1214	ahci: sata_request::abort called for command 0xec
1215	ahci: identify device failed
1216	ahci: ExecuteAtaRequest port 1: device is busy
1217	ahci: sata_request::abort called for command 0xa0
1218	ahci: ExecuteAtaRequest port 1: device is busy
1219	ahci: AHCIPort::ResetPort port 1
1220	ahci: AHCIPort::ResetPort port 1, deviceBusy 1, forceDeviceReset 0
1221	ahci: AHCIPort::PostReset port 1
1222	ahci: device signature 0xeb140101 (ATAPI)
1223	ahci: sata_request::abort called for command 0xa0

comment:2 by AlexeiZavjalov, 6 years ago

The same problem I have on the R1/Alpha 4.1 release

comment:3 by AlexeiZavjalov, 6 years ago

I found that ATAChannel::_DevicePresent expects SelectedDevice() will return 0, but it returns 1.

The problem has gone after I turned off the SATA mode.

comment:4 by luroh, 6 years ago

Blocking: 7665 added

comment:5 by waddlesplash, 6 years ago

Milestone: R1R1/alpha5
Priority: normalhigh

comment:6 by umccullough, 6 years ago

It seems to me that no x86_64 issues should be a blocker for any R1 related release, since it's totally experimental and unofficial still.

comment:7 by umccullough, 6 years ago

Summary: PANIC: get_boot_partitions failed. Haiku x86_64PANIC: get_boot_partitions failed

Ah, nevermind, the issue is present on Alpha 4.1 it seems, changing the summary.

comment:8 by pulkomandy, 5 years ago

Milestone: R1/alpha5R1/beta1

comment:9 by pulkomandy, 4 years ago

Blocking: 11508 added

comment:10 by waddlesplash, 4 years ago

Related to #12295?

comment:11 by waddlesplash, 3 years ago

There have been a lot of AHCI fixes in the past 3 years, including #12295 from two years ago. Could you please retest?

comment:15 by rhodes, 2 years ago

Dropped into KDL with the same error (PANIC: get_boot_partitions failed!) on a Samsung Chromebook 2 (model xe500c12) booting haiku-nightly-hrev51528-x86_64-anyboot from USB.

The same panic occurs using the haiku-nightly-hrev51536-x86_gcc2_hybrid-anyboot image.

by rhodes, 2 years ago

chromebook xe500c12 KDL

comment:18 by waddlesplash, 2 years ago

Has a Patch: unset

Between hrev51528 and hrev51536 there were some major fixes made to the XHCI bus manager ... so are you sure there are no differences between the two in the KDL message?

by rhodes, 2 years ago

Here's the KDL from hrev51538

comment:19 by waddlesplash, 2 years ago

Has a Patch: unset

Can you enable onscreen debug logging in the bootloader to capture that output, or even use the "dump last syslog" function following a warm reset? (see https://www.haiku-os.org/docs/userguide/en/bootloader.html)

comment:21 by waddlesplash, 2 years ago

Component: Drivers/DiskDrivers/Disk/ATA
ata 0: controller doesn't support DMA, disabling
ata 0: _DevicePresent: device selection failed for device 0
ata 0: _DevicePresent: device 1, presence 0
ata 0: deviceMask 0
ata 0: ignoring device 0
ata 0: ignoring device 1
ata 0 error: target device not present
ata 0 error: target device not present
ata 0 error: invalid target device

Huh, never seen that error before. Interesting.

comment:22 by waddlesplash, 17 months ago

Keywords: boot-failure added

comment:23 by waddlesplash, 17 months ago

Blocking: 7665 removed

comment:24 by waddlesplash, 16 months ago

Milestone: R1/beta1

comment:25 by waddlesplash, 16 months ago

Milestone: Unscheduled

by totish, 14 months ago

Attachment: ToshibaL35_syslog added

comment:26 by waddlesplash, 7 months ago

Resolution: not reproducible
Status: newclosed

The panic in that final syslog is unrelated.

The ATA error I snipped in my comment above is also unrelated, as obviously an ATA error could not prevent a boot from USB, and I've actually seen that error on systems where booting from ATA works just fine.

So, it seems this ticket is actually no longer reproducible.

Note: See TracTickets for help on using tickets.