Dma Timeout Error Status=0xd8 Busy
posts View posts from last 24 hours Gentoo Forums Forum Index Kernel & Hardware View previous topic :: View next topic Author Message mpooln00bJoined: 16 Dec 2002Posts: 26 Posted: Sat Nov 20, 2004 12:25 am Post subject: temporary lock up with hda DMA and IRQ timeout errors I've been having periodic lockups with clicking noises from my harddrive. These last a few seconds to a few minutes then everything goes back to normal. Under Windows, everything is stable. Here is part of dmesg that only occurs during a lockup: Code: spurious 8259A interrupt: IRQ7. hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd8 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success The number of times the triplets are repeated is related to the length of the lock up (i.e. longer lockup means more repeats). I have read somewhere else that this could be possibly fixed by turning APIC or PCI IRQ sharing off in the kernel. I can't find either of these options in menuconfig but they are on: C
titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches Recent Posts Menu Forums Forums Quick Links Search Forums Recent Posts Members Members Quick Links Notable Members Current Visitors Recent Activity New Profile Posts Menu Log in Sign up Proxmox Support Forum Forums > Retired and read only forums > Proxmox VE 1.x: Installation and configuration > This site uses cookies. By continuing https://forums.gentoo.org/viewtopic-t-254573-start-0.html to use this site, you are agreeing to our use of cookies. Learn More. Problem on debian with KVM / Disks Discussion in 'Proxmox VE 1.x: Installation and configuration' started by aureld, Apr 9, 2009. aureld New Member Joined: Apr 9, 2009 Messages: 3 Likes Received: 0 Hi all ! I'm new on this forum, but i'm using proxmoxVE https://forum.proxmox.com/threads/problem-on-debian-with-kvm-disks.1294/ since 6 or 7 months ago ! But now we have a little problem with one server : It's a debian etch on KVM. kernel on the vm' : 2.6.24-etchnhalf.1-686 kernel proxmox :2.6.24-2-pve (the last i think) And we have problem with disk , for example this morning : Apr 9 06:42:48 z kernel: hda: dma_timer_expiry: dma status == 0x21 Apr 9 06:44:14 z kernel: hda: dma_timer_expiry: dma status == 0x21 Apr 9 06:44:14 z kernel: hda: DMA timeout error Apr 9 06:44:14 z kernel: hda: dma timeout error: status=0xd8 { Busy } Apr 9 06:44:14 z kernel: ide: failed opcode was: unknown Apr 9 06:44:14 z kernel: hda: DMA disabled Apr 9 06:44:14 z kernel: ide0: reset: success Apr 9 06:48:21 z kernel: hda: dma_timer_expiry: dma status == 0x21 Apr 9 06:49:05 z kernel: Clocksource tsc unstable (delta = 100606509 ns) Apr 9 06:49:05 z kernel: Time: acpi_pm clocksource has been installed. Apr 9 07:02:32 z kernel: hda: dma_timer_expiry: dma status == 0x21 Apr 9 07:02:32 z kernel: hda: DMA timeout error Apr 9 07:02:
Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug134453 - Processes hang https://bugzilla.redhat.com/show_bug.cgi?id=134453 in uninterruptible state when trying to access CD/DVD drive Summary: Processes hang in uninterruptible state when trying to access CD/DVD drive Status: CLOSED CANTFIX Aliases: None Product: Fedora Classification: Fedora Component: kernel (Show other bugs) https://github.com/tapper/Tapper-TAP-Harness/blob/master/t/tap_archive_kernbench3.tap Sub Component: --- Version: 4 Hardware: i686 Linux Priority medium Severity high TargetMilestone: --- TargetRelease: --- Assigned To: Dave Jones QA Contact: Brian Brock Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency dma timeout tree /graph Reported: 2004-10-02 18:13 EDT by Matt Dainty Modified: 2015-01-04 17:10 EST (History) CC List: 2 users (show) pfrields wtogami See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2005-12-27 21:10:25 EST Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments dma timeout error (Terms of Use) Kernel boot log (20.92 KB, text/plain) 2004-10-02 18:15 EDT, Matt Dainty no flags Details Output of "lspci -v" (4.98 KB, text/plain) 2004-10-02 18:16 EDT, Matt Dainty no flags Details Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Matt Dainty 2004-10-02 18:13:38 EDT From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: I've noticed processes hang in the uninterruptible state 'D' when trying to access my CD/DVD drive, which is a Pioneer DVD-120S on the secondary channel of the AMD IDE controller on a Gigabyte GA-7DPXDW-P (which also has a Promise controller, for reference). The process to nearly always go first is magicdev as it polls the various removable media devices periodically. Once one process gets stuck, any further commands that try and access the same device also get stuck. While a reboot will clear this out every time, the processes are unkillable and so I can never unmount my /usr and /home partitions cleanly, nor even exit my X session cleanly as I suspect its waiting for magicdev to exit. The only output I get from the kernel is usually the following: hdc: request sense failure: status=0x51 { DriveReady SeekComplete Error } hdc: request sense failure: error=0x04Aborte
Sign in Pricing Blog Support Search GitHub This repository Watch 3 Star 0 Fork 3 tapper/Tapper-TAP-Harness Code Pull requests 1 Projects 0 Pulse Graphs Permalink Branch: master Switch branches/tags Branches Tags master v4.1.1-hotfixes v5 Nothing to show v5.0.7 v5.0.6 v5.0.5 v5.0.4 v5.0.3 v5.0.2 v5.0.1 v5.0.0 v4.1.2 v4.1.1 v4.1.0 v4.0.2 v4.0.1 3.000010 3.000004 3.000002 3.000001 Nothing to show Find file Copy path Tapper-TAP-Harness/t/tap_archive_kernbench3.tap Fetching contributors… Cannot retrieve contributors at this time Raw Blame History 392 lines (390 sloc) 9.4 KB 1..1 # Tapper-suite-version: 0.020016 # Tapper-starttime-test-program: 19330511T155947 # Tapper-machine-name: sles10-32bit # Tapper-suite-name: KernBench # Tapper-reportgroup-arbitrary: # Tapper-section: tapper-meta-information # Tapper-reportgroup-testrun: ok 1 - tapper-meta-data 1..1 # Tapper-Section: stats-proc-interrupts-before ok 1 - /proc/interrupts --- 0: CPU0: 26512 CPU1: 0 CPU2: 0 linetail: IO-APIC-edge timer 1: CPU0: 0 CPU1: 0 CPU2: 8 linetail: IO-APIC-edge i8042 4: CPU0: 391 CPU1: 0 CPU2: 0 linetail: IO-APIC-edge serial 7: CPU0: 0 CPU1: 0 CPU2: 0 linetail: IO-APIC-edge parport0 8: CPU0: 0 CPU1: 2 CPU2: 0 linetail: IO-APIC-edge rtc 9: CPU0: 0 CPU1: 0 CPU2: 0 linetail: IO-APIC-level acpi 12: CPU0: 102 CPU1: 0 CPU2: 0 linetail: IO-APIC-edge i8042 14: CPU0: 0 CPU1: 0 CPU2: 3233 linetail: IO-APIC-edge ide0 169: CPU0: 0 CPU1: 327 CPU2: 104 linetail: IO-APIC-level xen-platform-pci 177: CPU0: 25 CPU1: 0 CPU2: 0 linetail: IO-APIC-level uhci_hcd:usb1 NMI: CPU0: 0 CPU1: 0 CPU2: 0 linetail: ~ LOC: CPU0: 26113 CPU1: 25976 CPU2: 25975 linetail: ~ ERR: CPU0: 0 CPU1: ~ CPU2: ~ linetail: ~ MIS: CPU0: 0 CPU1: ~ CPU2: ~ linetail: ~ ... 1..1 # Tapper-section: kernel-untar ok 1 - untar of kernel succeeded. 1..1 # Tapper-section: kernbench-untar ok 1 - untar of testsuite succeeded. 1..1 # Tapper-section: kernbench-testrun ok 1 - Run took ntp: 1688s, system: 2195s 1..1 ok 1 - KernBench --- Thu May 11 16:13:41 CET 1933 2.6.16.60-0.27-smp Average Optimal load -j 12 Run (std deviation): Elapsed Time 261.57 (30.8727) User Time 226.59 (1.33692) System Time 301.29 (8.735) Percent CPU 203 (19.5448) Context Switches 26313.2 (314.936) Sleeps 25000.2 (263.972) ... 1..1 # Tapper-section: kernbench-results ok 1 - KernBench --- Thu May 11 16:13:41 CET 1933 2.6.16.60-0.27-smp Average Optimal load -j 12 Run (std deviation): Elapsed Time 261.57 (30.8727) User Time 226.59 (1.33692) System Time 301.29 (8.735) Percent CPU 203 (19.5448) Context Switches 26313.2 (314.936) Sleeps 25000.2 (263.972) ... 1..1 # Tapper-sec