All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Takashi Oe <toe@unlserve.unl.edu>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Occasional crash reports
Date: Tue, 14 Aug 2001 14:03:30 +0100	[thread overview]
Message-ID: <20010814130302.0261BDB9FB@atlas.valhalla.net> (raw)


On Tue, Aug 14, 2001, Takashi Oe wrote:
> On Tue, 14 Aug 2001, Iain Sandoe wrote:
>
>> > I don't really know, but I can confirm that both 2.2.x and 2.4.x kernels
>> > are unstable on a beige g3 and a bmac equipped b/w g3.  I can crash them
>> > rather easily with regular programs, given a day or two.
>>
>> Can you point at which program reliably crashes beige/G3?
>
> It's usually rsync.

hmm.  don't use that as much - but it's consistent with network activity -
does it show up as an illegal instruction?

>> that's what I use as my dev/build machine and it seems to be stable (2.4.x)
>> except under the following circumstance:
>>
>> If I boot using the BootX application - at which point something drops a
>> bomb which almost always ends up in the network stack and shows up as an
>> illegal instruction (usually an FP one).
>
> Ah, yes, we use BootX app here, too.  Version 1.2.2, I think.

try a hard reboot and use the BootX init - that seems to cure the problem
for me.  Finding out what the problem actually is might be more tricky ;-)

I'm on 1.2.2 as well - so that's the same.

ciao,
Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-08-14 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 13:03 Iain Sandoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-18 11:16 Occasional crash reports Iain Sandoe
2001-08-20  2:51 ` Robert E Brose II
2001-08-18  1:28 Robert E Brose II
2001-08-14 16:02 Jiri Masik
2001-08-14 16:28 ` Benjamin Herrenschmidt
2001-08-14 16:45   ` Benjamin Herrenschmidt
2001-08-14  9:45 Iain Sandoe
2001-08-14 12:18 ` Takashi Oe
2001-08-13 16:35 Benjamin Herrenschmidt
2001-08-14  2:59 ` Takashi Oe
2001-08-14 18:15   ` Mike Fedyk

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=20010814130302.0261BDB9FB@atlas.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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.