From: Dave Jones <davej@codemonkey.org.uk>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Nick Urbanik <nicku@vtc.edu.hk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Debugging hard lockups (hardware?)
Date: Tue, 8 Apr 2003 13:35:08 +0100 [thread overview]
Message-ID: <20030408123501.GA30244@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10304072032350.6320-100000@master.linux-ide.org>
On Mon, Apr 07, 2003 at 08:33:12PM -0700, Andre Hedrick wrote:
> That controller is perfectly fine, give it a swing in 2.4 and it rocks.
> 2.5 is the problem not the hardware.
Exactly the same problem in 2.4. Your words on this subject previously..
"Get over it, you have a hardware problem period! I have drives that do this every time."
So which is it ?
It does this with every drive I've tried with it, so I'm incredibly
sceptical theres a problem with the drives, especially when they
work 100% fine on other controllers.
Dave
next prev parent reply other threads:[~2003-04-08 12:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 6:32 Debugging hard lockups (hardware?) Nick Urbanik
2003-04-06 6:39 ` Nick Urbanik
2003-04-06 9:27 ` John Bradford
2003-04-06 10:55 ` Bruce Harada
2003-04-06 18:34 ` Alan Cox
2003-04-06 20:29 ` Arador
2003-04-06 21:04 ` Alan Cox
2003-04-17 16:12 ` Arador
2003-04-06 20:31 ` Dave Jones
2003-04-06 22:02 ` Nick Urbanik
2003-04-06 23:15 ` Dave Jones
2003-04-08 3:33 ` Andre Hedrick
2003-04-08 12:35 ` Dave Jones [this message]
2003-09-15 8:49 ` Debugging hard lockups (hardware?): Power Supply! Nick Urbanik
2003-09-15 19:57 ` Resident Boxholder
-- strict thread matches above, loose matches on Subject: below --
2003-04-06 10:12 Debugging hard lockups (hardware?) mikpe
2003-04-06 16:01 ` Nick Urbanik
2003-04-07 23:24 Richard J Moore
2003-04-09 1:24 ` Nick Urbanik
2003-04-08 18:36 Scott Lee
2003-04-11 18:08 Scott Lee
2003-04-11 19:22 ` Bernd Eckenfels
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=20030408123501.GA30244@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicku@vtc.edu.hk \
/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.