From: Jamie Heilman <jamie@audible.transient.net>
To: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BriQ & Linux 2.6
Date: Sun, 23 May 2004 23:47:04 -0700 [thread overview]
Message-ID: <20040524064703.GI1946@audible.transient.net> (raw)
In-Reply-To: <20040522193639.GO8520@audible.transient.net>
Well played around with the pcnet32 driver, reverting some of the
changes since 1.27a, and it didn't help at all, so I gave up on that
problem and focused on the spontaneous rebooting. SMART tests on the
disk revealed nothing, acording to the selftests everything is fine.
On a whim I removed the gargoyle expansion board from the briq, and lo
and behold - stability improved dramatically. Its hard to know why it
helped. But more disturbing is that it didn't solve the issue by a
long shot. So I ran bonnie++ for a few itterations ... and it worked
flawlessly (in 2.6.6-bk8). Then I ran:
while :; do tar jxf linux-2.6.6-bk8.tar.bz2; echo -n .; done
The second time through the machine spontaneously rebooted. :-(
So I booted up 2.4.24-2004021601briq from TI's site, reran the above
test, and it got through about 4 itterations before it locked up hard,
and VFD went dark (didn't reboot). So then I stepped back to
2.4.23-2004012801briq also from TI... ran the test again, got maybe 1
itteration further and locked up again. So, swearing up a storm, I
booted up 2.2.19 and ran the test again, this got through quite a few
itterations (like around 11 or 12) but in the end the machine still
locked up and the VFD went dark.
Frustrating; I'm starting to wonder if the software is the real issue
though.
--
Jamie Heilman http://audible.transient.net/~jamie/
"I was in love once -- a Sinclair ZX-81. People said, "No, Holly,
she's not for you." She was cheap, she was stupid and she wouldn't
load -- well, not for me, anyway." -Holly
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-24 6:47 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 [this message]
2004-05-25 23:30 ` Benjamin Herrenschmidt
2004-05-26 0:00 ` Jamie Heilman
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=20040524064703.GI1946@audible.transient.net \
--to=jamie@audible.transient.net \
--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).