From: arno@natisbad.org (Arnaud Ebalard)
To: linuxppc-dev@ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Random crashes with 2.6.27-rc3 on PPC
Date: Sat, 23 Aug 2008 18:58:02 +0200 [thread overview]
Message-ID: <874p5bekit.fsf@natisbad.org> (raw)
In-Reply-To: 200808231610.46473.mb@bu3sch.de
Hi,
Michael Buesch <mb@bu3sch.de> writes:
> I am seeing random kernel and userland application
> crashes on a Powerbook running a 2.6.27-rc3 based kernel
> (wireless-testing.git).
>
> The crashes did recently appear. It might be the case that they were
> introduced with the merge of 2.6.27-rc1 into wireless-testing.
> I'm not sure on that one, however. Just a guess. I still need to
> do more testing (also on vanilla upstream kernels).
>
> The crashes are completely random and they look like bad hardware.
> However I cannot reproduce on 2.6.25.9 (That's a kernel I still had
> installed, so I tried that one). So it most likely is _not_ caused
> by faulty hardware.
>
> The crashes are hard to reproduce, and happen about every 20 minutes
> when compiling a kernel tree. (gcc segfaults). Sometimes the kernel
> oopses in random places with pointer dereference faults.
Exact same thing here on a PB 12" (not a ppc64, but ppc32). It was not
on a wireless-testing.git but on a recent net-2.6 or 2.6.27-rc3 (I do
not remember precisely). I thought it was a thermal issue and did not
spend time on it because of another regression I bisected (sysctl+IPv6)
that version useless for me.
> Is this a known issue?
Now it is ;-)
> I'm going to bisect this one, but it will take a lot of time, as
> reproducing takes about 20 minutes. So that's about an hour for one
> test round.
Thanks for doing that.
Cheers,
a+
WARNING: multiple messages have this Message-ID (diff)
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-kernel@vger.kernel.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Random crashes with 2.6.27-rc3 on PPC
Date: Sat, 23 Aug 2008 18:58:02 +0200 [thread overview]
Message-ID: <874p5bekit.fsf@natisbad.org> (raw)
In-Reply-To: 200808231610.46473.mb@bu3sch.de
Hi,
Michael Buesch <mb@bu3sch.de> writes:
> I am seeing random kernel and userland application
> crashes on a Powerbook running a 2.6.27-rc3 based kernel
> (wireless-testing.git).
>
> The crashes did recently appear. It might be the case that they were
> introduced with the merge of 2.6.27-rc1 into wireless-testing.
> I'm not sure on that one, however. Just a guess. I still need to
> do more testing (also on vanilla upstream kernels).
>
> The crashes are completely random and they look like bad hardware.
> However I cannot reproduce on 2.6.25.9 (That's a kernel I still had
> installed, so I tried that one). So it most likely is _not_ caused
> by faulty hardware.
>
> The crashes are hard to reproduce, and happen about every 20 minutes
> when compiling a kernel tree. (gcc segfaults). Sometimes the kernel
> oopses in random places with pointer dereference faults.
Exact same thing here on a PB 12" (not a ppc64, but ppc32). It was not
on a wireless-testing.git but on a recent net-2.6 or 2.6.27-rc3 (I do
not remember precisely). I thought it was a thermal issue and did not
spend time on it because of another regression I bisected (sysctl+IPv6)
that version useless for me.
> Is this a known issue?
Now it is ;-)
> I'm going to bisect this one, but it will take a lot of time, as
> reproducing takes about 20 minutes. So that's about an hour for one
> test round.
Thanks for doing that.
Cheers,
a+
next prev parent reply other threads:[~2008-08-23 18:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 14:10 Random crashes with 2.6.27-rc3 on PPC Michael Buesch
2008-08-23 16:58 ` Arnaud Ebalard [this message]
2008-08-23 16:58 ` Arnaud Ebalard
2008-08-23 22:52 ` Benjamin Herrenschmidt
2008-08-24 7:23 ` Michael Buesch
2008-08-24 13:44 ` Michael Buesch
2008-08-24 13:44 ` Michael Buesch
2008-08-24 14:46 ` Andreas Schwab
2008-08-24 14:46 ` Andreas Schwab
2008-08-24 15:00 ` Michael Buesch
2008-08-24 15:00 ` Michael Buesch
2008-08-24 22:39 ` Benjamin Herrenschmidt
2008-08-24 22:39 ` Benjamin Herrenschmidt
2008-08-24 22:37 ` Benjamin Herrenschmidt
2008-08-24 22:37 ` Benjamin Herrenschmidt
2008-09-02 6:50 ` [PATCH 1/1] Work around the fomit-frame-pointer bug Tony Breeds
2008-09-02 6:50 ` Tony Breeds
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=874p5bekit.fsf@natisbad.org \
--to=arno@natisbad.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 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.