From: Jeff Garzik <jgarzik@pobox.com>
To: Mihai RUSU <dizzy@roedu.net>
Cc: Jon Smirl <jonsmirl@yahoo.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: libata patch
Date: Sun, 15 Feb 2004 15:27:47 -0500 [thread overview]
Message-ID: <402FD643.4040307@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58L0.0402151138140.7324@ahriman.bucharest.roedu.net>
Mihai RUSU wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi
>
> Hmm, I hit the same problem (only once so far) on 2.6.2 vanilla. While I
> was installing one of my first SATA systems, on ICH5, I hit the same thing
> (some error in kernel log regardning DMA and the SATA hdd seemed frozen,
> the only commands working were those cached in RAM already). Hope this
> helps :) (sorry I couldnt do more, it only happened once so far).
Can you try 2.6.3-rc3? The questionable patch is not in 2.6.2 vanilla,
FWIW.
If you could fill out a bug report at http://bugzilla.kernel.org/ and
include "lspci -vvv" and "dmesg" output, that would be useful.
Jeff
prev parent reply other threads:[~2004-02-15 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 16:02 libata patch Jon Smirl
2004-02-14 18:58 ` Jeff Garzik
2004-02-15 9:41 ` Mihai RUSU
2004-02-15 20:27 ` Jeff Garzik [this message]
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=402FD643.4040307@pobox.com \
--to=jgarzik@pobox.com \
--cc=dizzy@roedu.net \
--cc=jonsmirl@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox