From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>,
<linuxppc-dev@lists.linuxppc.org>, Michel Lanners <mlan@cpu.lu>
Subject: Re: Crash on BenH's latest rsync (2.4.6-pre3)
Date: Tue, 26 Jun 2001 22:51:47 +0200 [thread overview]
Message-ID: <20010626205147.26310@smtp.wanadoo.fr> (raw)
In-Reply-To: <20010626121003.D31231@opus.bloom.county>
>Not this one in particular, but I'm tracking 2 different oopses w/
>the tree on a new iBook right now. 2.4.5-pre3 is rock solid too :)
>
>How did you get that oops? There seems to be a problem w/ inserting
>power to a sleeping 'book. Or at least w/ this one.
The biggest difference between 2.4.5-pre3 and my current tree is
(except from linux maintstream changes) the new MM layer and
merging of all the linuxppc_2_4_devel work.
It would be helpful for me if you could both try out the current
_2_4_devel tree and tell me if it exhibit the same symtoms. Well,
I beleive sleep won't work on the iBook, so that cannot be tested,
but at least Michel can try it out and tell me.
I currently fail to see what in my recent changes could explain
such weird/random crashes. As far as the iBook is concerned, it
may well be yet another HW issue with a device playing mad
tricks to memory, but I still doubt it.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-06-26 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 20:29 Crash on BenH's latest rsync (2.4.6-pre3) Michel Lanners
2001-06-26 19:10 ` Tom Rini
2001-06-26 20:38 ` Michel Lanners
2001-06-26 20:51 ` Benjamin Herrenschmidt [this message]
2001-06-26 21:29 ` Takashi Oe
2001-06-26 22:13 ` Tom Rini
2001-06-26 22:31 ` Takashi Oe
2001-06-26 22:43 ` Tom Rini
2001-06-27 16:25 ` Stephen R Marenka
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=20010626205147.26310@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=trini@kernel.crashing.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).