From: Jamie Heilman <jamie@audible.transient.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BriQ & Linux 2.6
Date: Tue, 25 May 2004 17:00:41 -0700 [thread overview]
Message-ID: <20040526000040.GY1946@audible.transient.net> (raw)
In-Reply-To: <1085527853.15024.141.camel@gaston>
Benjamin Herrenschmidt wrote:
> Picked this patch somewhere, let me know if it helps for the bogus
> Tx errors. I don't know what's up with the lockup at this point, I
> would expect the machine to be stable. Can you try to exercice it
> using only netbooting instead of the HD or switching the HD down
> to PIO mode (hdparm -d0 /dev/hda) to try to isolate the source of
> the problem ?
Ah cool, thanks I'll give it a try. It'll be a while though, I just
accepted a job out of state, so I'm starting the moving process and
one of the first things I did was stick the briq back in its box.
It'll probably be a month before I'm ready to pull it out again, but
I'll let you know how it goes when I do.
--
Jamie Heilman http://audible.transient.net/~jamie/
"Paranoia is a disease unto itself, and may I add, the person standing
next to you may not be who they appear to be, so take precaution."
-Sathington Willoughby
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-05-26 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 7:40 BriQ & Linux 2.6 Jamie Heilman
2004-05-21 23:10 ` Benjamin Herrenschmidt
2004-05-21 23:35 ` Jamie Heilman
2004-05-22 4:14 ` Benjamin Herrenschmidt
2004-05-22 6:45 ` Jamie Heilman
2004-05-22 7:12 ` Benjamin Herrenschmidt
2004-05-22 19:36 ` Jamie Heilman
2004-05-24 6:47 ` Jamie Heilman
2004-05-25 23:30 ` Benjamin Herrenschmidt
2004-05-26 0:00 ` Jamie Heilman [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=20040526000040.GY1946@audible.transient.net \
--to=jamie@audible.transient.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).