From: Dave Jones <davej@codemonkey.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nick Urbanik <nicku@vtc.edu.hk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Debugging hard lockups (hardware?)
Date: Sun, 6 Apr 2003 21:31:45 +0100 [thread overview]
Message-ID: <20030406203145.GA5783@suse.de> (raw)
In-Reply-To: <1049654048.1600.11.camel@dhcp22.swansea.linux.org.uk>
On Sun, Apr 06, 2003 at 07:34:09PM +0100, Alan Cox wrote:
> > 02:0a.0 RAID bus controller: CMD Technology Inc PCI0680 (rev 01)
> > 02:0b.0 RAID bus controller: CMD Technology Inc PCI0680 (rev 01)
> ...
> Your choice of components looks fine, its all stuff I trust, even if the
> ethernet card is not good for performance it ought to be fine in
> general. If it is a faulty part most likely its a one off fault.
Note the IDE controller, and 2.5 bugzilla #123
That controller has been nothing but trouble for me.
Dave
next prev parent reply other threads:[~2003-04-06 20:20 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 [this message]
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
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=20030406203145.GA5783@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--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.