From: Chuck <chunkeey@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: How's the nforce4 support in Linux?
Date: Sat, 26 Mar 2005 17:01:08 +0100 [thread overview]
Message-ID: <200503261701.08774.chunkeey@web.de> (raw)
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
(something) like the same problem here:
I get lots of:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
The disk (WDC WD800JB) is about 1/2 year old.
I've checked the drive in my old system... nothing!
Also WD's diagnostic kit doesn't report any problems like bad sectors,
or other troubles...
(Please CC me, I'm not on the list)
next reply other threads:[~2005-03-26 15:01 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 16:01 Chuck [this message]
2005-03-26 15:19 ` How's the nforce4 support in Linux? Arjan van de Ven
2005-03-26 17:32 ` Marcin Dalecki
2005-03-27 12:26 ` Chuck
2005-04-02 23:55 ` Julien Wajsberg
-- strict thread matches above, loose matches on Subject: below --
2005-03-25 22:59 Julien Wajsberg
2005-03-25 23:14 ` Lee Revell
2005-03-26 0:38 ` Julien Wajsberg
2005-03-26 0:48 ` Lee Revell
2005-03-29 18:58 ` Tomasz Torcz
2005-03-29 20:40 ` Lee Revell
2005-03-30 15:00 ` Tomasz Torcz
2005-03-30 16:45 ` Lennart Sorensen
2005-03-30 19:19 ` Martin Schlemmer
2005-03-30 21:01 ` Lee Revell
2005-03-31 5:58 ` Martin Schlemmer
2005-03-25 23:20 ` Lee Revell
2005-03-26 0:17 ` Julien Wajsberg
2005-03-26 14:13 ` Michal Schmidt
2005-03-29 6:47 ` Julien Wajsberg
2005-03-25 23:21 ` Lee Revell
2005-03-25 23:41 ` Julien Wajsberg
2005-04-05 13:42 ` Julien Wajsberg
2005-04-05 14:10 ` Richard B. Johnson
2005-04-05 22:58 ` Julien Wajsberg
2005-04-06 11:41 ` Richard B. Johnson
2005-04-06 16:02 ` Bartlomiej Zolnierkiewicz
2005-04-10 23:43 ` Julien Wajsberg
2005-04-10 23:27 ` Julien Wajsberg
2005-03-25 9:37 Chuck Ebbert
[not found] <3LwFC-4Ko-15@gated-at.bofh.it>
[not found] ` <3LwYW-4Xx-11@gated-at.bofh.it>
[not found] ` <3LwYZ-4Xx-25@gated-at.bofh.it>
2005-03-24 10:00 ` Asfand Yar Qazi
2005-03-24 10:11 ` Arjan van de Ven
2005-03-24 16:29 ` Lennart Sorensen
2005-03-24 16:41 ` Raphael Jacquot
2005-03-24 20:41 ` Jeff Garzik
2005-03-25 2:15 ` Robert Hancock
2005-03-25 2:40 ` Lee Revell
[not found] <3Lxis-5a0-29@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-31@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-33@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-27@gated-at.bofh.it>
2005-03-24 10:11 ` Asfand Yar Qazi
2005-03-24 9:20 Asfand Yar Qazi
2005-03-24 9:30 ` Jeff Garzik
2005-03-24 9:34 ` Arjan van de Ven
2005-03-24 10:03 ` Tupshin Harper
2005-03-24 16:27 ` Lennart Sorensen
2005-03-24 21:01 ` Jeff Garzik
2005-03-28 15:31 ` Andi Kleen
2005-03-30 19:42 ` Jeff Garzik
2005-03-30 20:17 ` Indrek Kruusa
2005-03-30 20:25 ` Jeff Garzik
2005-03-30 20:48 ` Indrek Kruusa
2005-03-30 21:06 ` Francois Romieu
2005-03-30 21:47 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200503261701.08774.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox