From: "ismail dönmez" <ismail.donmez@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NForce4 ide problems?
Date: Wed, 20 Apr 2005 21:36:59 +0300 [thread overview]
Message-ID: <2a4f155d05042011361234531d@mail.gmail.com> (raw)
In-Reply-To: <2a4f155d050420081220b3f801@mail.gmail.com>
FWIW problem happens way before any driver is loaded ( i.e nVidia ) so
this is not a such problem.
On 4/20/05, ismail dönmez <ismail.donmez@gmail.com> wrote:
> Hi all,
>
> I recently bought an Asus A8N-SLI mobo and an AMD 3500+ CPU for my
> system but my ide drive seems to have some problems with them. Here is
> what I get at boot :
>
> <snip>
> hda: 156368016 sectors (80060 MB) w/2048KiB Cache, CHS=16383/255/63,
> UDMA(100)
> hda: cache flushes supported
> /dev/ide/host0/bus0/target0/lun0: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
> </snip>
>
> First I thought it was bad ide cable ( because I wasn't using the one
> that came with mobo ) so I tried with the brand new cable coming with
> mobo and same error happened. Also trying to do something like :
>
> hdparm -m16 -c -u1 -d1 -Xudma2 /dev/hda
>
> results in a cpu exception thrown and a kernel panic after that. Full
> dmesg log is attached. I appreciate any help/comments.
>
> P.S: I tried with kernel 2.6.10 and 2.6.12-rc2 and same problems happen
>
> Regards,
> ismail
>
>
> --
> Time is what you make of it
>
>
--
Time is what you make of it
next prev parent reply other threads:[~2005-04-20 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 15:12 NForce4 ide problems? ismail dönmez
2005-04-20 18:36 ` ismail dönmez [this message]
2005-04-20 19:45 ` Jesper Juhl
2005-04-21 5:57 ` ismail dönmez
2005-04-21 18:14 ` ismail dönmez
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=2a4f155d05042011361234531d@mail.gmail.com \
--to=ismail.donmez@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.