Dma Timeout Error Status=0x50 Driveready Seekcomplete

hours Gentoo Forums Forum Index Kernel & Hardware View previous topic :: View next topic Author Message gourangaTux's lil' helperJoined: 05 Aug 2005Posts: 113 Posted: Wed Feb 22, 2006 12:35 pm Post subject: Harddisk Problem Dmesg sais this (see code) Anyone any id what it means? DMA works sometimes, but now its off. It's very strange, something kills DMA. Code: ide: failed opcode was: unknown hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0x50 { DriveReady SeekComplete } ide: failed opcode was: unknown hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x04 { DriveStatusError } ide: failed opcode was: unknown hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x04 { DriveStatusError } ide: failed opcode was: unknown hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x04 { DriveStatusError } ide: failed opcode was: unknown hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x04 { DriveStatusError } ide: failed opcode was: unknown ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } ide: failed opcode was: unknown hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } ide: failed opcode was: unknown hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } Code: root@genserv everything # hdparm -d /dev/hda4 /dev/hda4: using_dma = 0 (off) root@genserv everything # hdparm -d1 /dev/hda4 /dev/hda4: setting using_dma to 1 (on) HDIO_SET_DMA failed: Invalid argument using_dma = 0 (off) Back to top JeliJamiVeteranJoined: 17 Jan 2006Posts: 1086Location: Belgium Posted: Wed Feb 22, 2006 1:01 pm Post subject: those error messages may indicate a dying hard drive_________________Unanswered Post Initiative | Search | FAQ Former username: davjel Back to top

XPi CD P150ST ... dma timeout error: status=0x50 { DriveReady SeekComplete } ... dma timeout error: status=0x50 { DriveReady ... - read more ... linux-hardware-18/hda-errors-in-dmesg ... dma timeout error: status=0x50 { DriveReady ... hda: status error: status=0x50 { DriveReady SeekComplete } - read more Tweet Please vote if the answer you were given helped you or not, thats the best way to improve our algorithm. You can https://forums.gentoo.org/viewtopic-t-436479-start-0.html also submit an answer or search documents about dma timeout error status 0x50 driveready seekcomplete. Share your answer: dma timeout error status 0x50 driveready seekcomplete? dma timeout error status 0x50 driveready seekcomplete resources Linux-Kernel Archive: Re: "hde: timeout waiting...... timeout waiting for DMA": message gone, same behaviour From: ... > Older https://www.askiven.com/dma-timeout-error-status-0x50-driveready-seekcomplete.html trees take one DMA timeout ... irq timeout: status=0x50 { DriveReady SeekComplete } Sep ... Linux-Kernel: Re: DMA timeout error... dma timeout error: status=0x58 { DriveReady ... status error: status=0x58 { DriveReady SeekComplete ... send the line "unsubscribe linux-kernel" in the ... LinuxQuestions.org - DMA Problem.DMA Problem. I have installed ... hdb: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } ... hda: status error: status=0x50 { DriveReady ... Xen - Dev - DMA in HVM guest on x86_64DMA in HVM guest on x86_64. ... dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } ... dma timeout error: status=0x58 { DriveReady SeekComplete ... SATA Disk Problems with suggested solutions |...... status=0x51 { DriveReady SeekComplete Error } ... SATA Disk Problems with suggested solutions. ... dma timeout retry: status=0x50 { DriveReady SeekComplete } Bug 132584 – hdc: dma_timer_expiry: dma status ==...... hda: dma_timer_expiry: dma status == 0x21 ... dma timeout error: status=0x5

This bug is not in your last search results. Bug2494 - PDC20265 crashes when DMA is enabled Summary: PDC20265 crashes when DMA is enabled Status: REJECTED https://bugzilla.kernel.org/show_bug.cgi?id=2494 INSUFFICIENT_DATA Product: IO/Storage Classification: Unclassified Component: IDE Hardware: i386 Linux Importance: P2 normal Assigned To: Bartlomiej Zolnierkiewicz URL: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: 2004-04-11 13:23 UTC by peter mutsaers Modified: 2007-06-18 07:42 UTC (History) CC List: 3 users (show) drescher0110-lists hhielscher sumbach See Also: Kernel Version: 2.6.5 and 2.6.5-mm4, not in 2.4.x Tree: Mainline Regression: --- Attachments pdc20267 (465 bytes, patch) 2004-10-17 09:46 dma timeout UTC, Krzysztof Chmielewski Details | Diff View All Add an attachment (proposed patch, testcase, etc.) Description peter mutsaers 2004-04-11 13:23:36 UTC Distribution: slackware Hardware Environment: A7V, with normal (VIA) IDE controller and on-board PDC20265 Software Environment: the "old" promise IDE driver Problem Description: When DMA is enabled and two disks are connected (one to each channel) and used heavily a crash follows soon. At first random programs start crashing an dma timeout error starting new programs results in complaints that required shared libraries cannot be found/loaded, this even when the executables and shared libraries reside on other disks not connected to the PDC20265. As soon as a 2.4.x kernel is used, DMA is disabled or the disks are moved to the normal VIA controller no problem happens. Steps to reproduce: Start badblocks -n on both disks, it happens within a few seconds. Start badblocks -n or large copies on just one disk the same happens but much later and less predictable. Comment 1 Frank Elis 2004-05-12 18:23:55 UTC Can confirm the problem also exists in 2.6.6. Have seen this problem occur with vanilla 2.6.6 kernels as well as with redhat FC 2 test kernels. Any heavy activity on any drive attached to a PDC20265 controller will cause this bug to manifest (such as RAID activity, filesystem rsyncs, etc.). The system generally becomes unusable and will not reboot without a power cycle. Comment 2 Frank Elis 2004-05-12 18:27:55 UTC Here are some kernel logs of the timeout occuring: hde: dma_timer_expiry: dma status == 0x60 hde: DMA timeout retry PDC202XX: Primary channel reset PDC202XX: Secondary channel reset hde: timeout waiting for DMA hde: dma_timer_expiry: dma status == 0x61 hde: DMA timeout error Con