Opened 9 years ago

#6996 new bug

ALi M5229 IDE [10b9:5229] IDE Error: "timeout waiting for interrupt"

Reported by: siarzhuk Owned by: marcusoverhagen
Priority: normal Milestone: R1
Component: Drivers/Disk Version: R1/Development
Keywords: ata, timeout, 10b9, 5229, Fujitsu Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

Current Haiku version from trunk (hrev39875) was tested on Fujitsu Lifebook with following IDE controller:

PCI:   vendor 10b9: ALi Corporation
PCI:   device 5229: M5229 IDE
PCI:   info: Mass storage controller (IDE interface)

The system was booted from internal HDD Samsung HM110JC. All icons of the bootscreen were highlighted, system hang for a minute and fall down into following KDL panic:

PANIC: could not write back block 1590524 (Device timeout)

Welcome to Kernel Debugging Land...
Thread 10 "block notifier/writer" running on CPU 0
stack trace for thread 10 "block notifier/writer"
    kernel stack: 0x81073000 to 0x81077000
frame               caller     <image>:function + offset
 0 81076cac (+  32) 800ffb3f   <kernel_x86>:arch_debug_stack_trace + 0x000f
 1 81076ccc (+  12) 80106e7a   <kernel_x86>:arch_debug_call_with_fault_handler + 0x001b
 2 81076cd8 (+  48) 80077a28   <kernel_x86>:debug_call_with_fault_handler + 0x0058
 3 81076d08 (+  80) 80078a92   <kernel_x86> kernel_debugger_loop(char const*: [34m0x0[0m [31m"<NULL>"[0m, char const*: [34m0x80170760[0m [36m"˜mЃ"[0m, char*: [34m0x81076d98[0m, int32: [34m-2146988473[0m) + 0x0162
 4 81076d58 (+  64) 80078d61   <kernel_x86> kernel_debugger_internal(char const*: [34m0x0[0m [31m"<NULL>"[0m, char const*: [34m0x82310684[0m [36m"d1‚"[0m, char*: [34m0x81076db8[0m, int32: [34m-2146988016[0m) + 0x0051
 5 81076d98 (+  32) 80079023   <kernel_x86>:panic + 0x0023
 6 81076db8 (+  80) 8003f768   <kernel_x86> BlockWriter<[32m0x81076e8c[0m>::_WriteBlock(cached_block*: [34m0x822fd480[0m) + 0x00b8
 7 81076e08 (+  64) 80040c4f   <kernel_x86> BlockWriter<[32m0x81076e8c[0m>::Write(hash_iterator*: NULL, [34mtrue[0m) + 0x006f
 8 81076e48 (+ 400) 80042846   <kernel_x86> block_notifier_and_writer(void*: NULL) + 0x00e6
 9 81076fd8 (+  32) 800690e6   <kernel_x86> _create_kernel_thread_kentry() + 0x0016
10 81076ff8 (+2130219016) 8006cf30   <kernel_x86> thread_kthread_exit() + 0x0000

The syslog contains some more data acquired during mentioned hang timeot:

ata 0 error: timeout waiting for interrupt
ata 0 error: RecoverLostInterrupt: device busy, status 0x58
check_sense: Hardware error
ata 0 error: device selection timeout
ata 0-0 error: failed to send transfer request
ata 0 error: device selection timeout
ata 0-0 error: failed to send transfer request
ata 0 error: device selection timeout
ata 0-0 error: failed to send transfer request
ata 0 error: device selection timeout
ata 0-0 error: failed to send transfer request

Any attempts to boot this Notebook in different combinations of safe mode options have no affect.

Note: Haiku was build with all additional tracing options that I have mentioned as ATA-related. This Notebook has onboard RS232 hardware - so feel free to ask me perform some KDL debugging or switch on additional tracing.

Full syslog capture of described above problematic system boot is attached.

Attachments (1)

haiku-cap.log (56.0 KB ) - added by siarzhuk 9 years ago.
Full syslog of booting Haiku hrev39875

Download all attachments as: .zip

Change History (1)

by siarzhuk, 9 years ago

Attachment: haiku-cap.log added

Full syslog of booting Haiku hrev39875

Note: See TracTickets for help on using tickets.