#10769 closed bug (not reproducible)
PANIC: get_boot_partitions failed
Reported by: | AlexeiZavjalov | Owned by: | nobody |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Drivers/Disk/ATA | Version: | R1/Development |
Keywords: | boot-failure | Cc: | |
Blocked By: | Blocking: | #11508 | |
Platform: | All |
Description
Haiku revision: hrev47127
Serial dump is attached.
Attachments (4)
Change History (26)
by , 11 years ago
Attachment: | haiku_log.txt added |
---|
comment:1 by , 11 years ago
Component: | System → Drivers/Disk |
---|
comment:3 by , 11 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 , 10 years ago
Blocking: | 7665 added |
---|
comment:5 by , 10 years ago
Milestone: | R1 → R1/alpha5 |
---|---|
Priority: | normal → high |
comment:6 by , 10 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 , 10 years ago
Summary: | PANIC: get_boot_partitions failed. Haiku x86_64 → PANIC: get_boot_partitions failed |
---|
Ah, nevermind, the issue is present on Alpha 4.1 it seems, changing the summary.
comment:8 by , 10 years ago
Milestone: | R1/alpha5 → R1/beta1 |
---|
comment:9 by , 9 years ago
Blocking: | 11508 added |
---|
comment:11 by , 7 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 , 7 years ago
by , 7 years ago
Attachment: | haiku-nightly-hrev51528-x86_64-anyboot-KDL.JPG added |
---|
chromebook xe500c12 KDL
comment:18 by , 7 years ago
patch: | 0 |
---|
comment:19 by , 7 years ago
patch: | → 0 |
---|
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 , 7 years ago
Component: | Drivers/Disk → Drivers/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 , 6 years ago
Keywords: | boot-failure added |
---|
comment:23 by , 6 years ago
Blocking: | 7665 removed |
---|
comment:24 by , 6 years ago
Milestone: | R1/beta1 |
---|
comment:25 by , 6 years ago
Milestone: | → Unscheduled |
---|
by , 6 years ago
Attachment: | ToshibaL35_syslog added |
---|
comment:26 by , 6 years ago
Resolution: | → not reproducible |
---|---|
Status: | new → closed |
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.
comment:27 by , 5 years ago
Milestone: | Unscheduled |
---|
Remove milestone for tickets with status = closed and resolution != fixed
I'm not particularly familiar with the AHCI module, but the output in the log suggests that something goes wrong there: