From: Grant Grundler <grundler@parisc-linux.org>
To: Helge Deller <deller@gmx.de>
Cc: linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: 2.6.28-rcX in pretty bad shape on parisc
Date: Sun, 23 Nov 2008 00:13:48 -0700 [thread overview]
Message-ID: <20081123071348.GA31575@colo.lackof.org> (raw)
In-Reply-To: <49231FD0.9040409@gmx.de>
On Tue, Nov 18, 2008 at 09:04:32PM +0100, Helge Deller wrote:
> Hello PA hackers,
>
> I've tried various -rc candidates in the last few weeks, and sadly the
> parisc kernel is in pretty bad shape.
>
> At the beginning I started to get problems only when I had USB
> keyboard/mouse attached to the PA machine. This lead to bugzilla
> http://bugzilla.kernel.org/show_bug.cgi?id=11913
I don't have any USB devices attached (serial console) on j6000.
Also getting occasional:
Backtrace:
with no other output when a process (usually hppa64-gcc) segfaults "randomly".
This is with kernel builds.
> Now, with -rc4 and -rc5 things got even worse.
I've tried both -rc3 and -rc5. I'm going to try 2.6.27.7 as well.
> Crashes happen often just directly at the beginning.
> I'm sure it's not USB related any more, and I assume we have some strange
> mm-problem somewhere.
I'm inclined to agree though it's just a guess.
> The kernel crashes at various places, and mostly a null-pointer is
> involved.
I haven't crashed the kernel per se, just getting segfaults reminiscent
of when we still had issues with mm not playing well with VIVT caches.
> Right now I'm clueless...
Sorry, I'm not better. :(
All I can do is try to work backwards a bit...but we've been in
pretty bad shape with various types of breakage since 2.6.22 about.
grant
next prev parent reply other threads:[~2008-11-23 7:13 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:04 2.6.28-rcX in pretty bad shape on parisc Helge Deller
2008-11-19 1:33 ` Thibaut VARENE
2008-11-19 15:47 ` Helge Deller
2008-11-19 2:31 ` James Bottomley
2008-11-19 9:13 ` Domenico Andreoli
2008-11-19 14:20 ` James Bottomley
2008-11-19 15:12 ` John David Anglin
2008-11-19 16:25 ` Helge Deller
2008-11-19 18:13 ` Helge Deller
2008-11-20 7:55 ` Helge Deller
2008-11-20 12:57 ` Thibaut VARENE
2008-11-20 15:14 ` John David Anglin
2008-11-20 3:51 ` John David Anglin
2008-11-20 16:57 ` John David Anglin
2008-11-22 5:57 ` Grant Grundler
2008-11-22 6:14 ` Grant Grundler
2008-11-22 19:48 ` John David Anglin
2008-11-22 21:37 ` John David Anglin
2008-11-22 23:01 ` James Bottomley
2008-11-23 16:54 ` John David Anglin
2008-11-22 6:11 ` Grant Grundler
2008-11-23 7:13 ` Grant Grundler [this message]
2008-11-23 16:36 ` John David Anglin
2008-11-23 16:57 ` John David Anglin
2008-11-25 2:54 ` John David Anglin
2008-11-25 13:33 ` Carlos O'Donell
2008-11-25 13:58 ` Guy Martin
2008-11-25 14:07 ` Carlos O'Donell
2008-11-26 17:51 ` Guy Martin
2008-11-30 20:24 ` John David Anglin
2008-11-30 21:03 ` Helge Deller
2008-12-02 0:00 ` John David Anglin
2008-12-01 10:54 ` Thibaut VARENE
2008-12-03 20:41 ` Helge Deller
2008-12-08 5:15 ` Kyle McMartin
2008-12-08 15:23 ` John David Anglin
2008-12-08 15:34 ` Kyle McMartin
2008-12-08 15:57 ` John David Anglin
2008-12-08 16:00 ` Kyle McMartin
2008-12-08 16:00 ` Kyle McMartin
2008-12-09 3:44 ` resource_size_t printk woes Kyle McMartin
2008-12-10 4:05 ` John David Anglin
2009-01-01 13:06 ` Helge Deller
2009-01-01 17:14 ` John David Anglin
2009-01-01 17:32 ` Helge Deller
2009-01-01 19:04 ` John David Anglin
2009-01-01 22:37 ` John David Anglin
2009-01-01 23:39 ` John David Anglin
2009-01-02 9:14 ` Helge Deller
2009-01-02 16:32 ` John David Anglin
2009-01-02 16:43 ` John David Anglin
2009-01-02 19:50 ` Grant Grundler
2008-12-08 4:50 ` 2.6.28-rcX in pretty bad shape on parisc John David Anglin
2008-12-08 7:50 ` Grant Grundler
2008-12-08 15:16 ` John David Anglin
2008-12-09 4:14 ` Kyle McMartin
2008-12-08 12:39 ` Carlos O'Donell
2008-12-08 14:54 ` John David Anglin
2008-12-08 15:02 ` Carlos O'Donell
2008-12-08 15:30 ` John David Anglin
2008-12-08 22:14 ` Carlos O'Donell
2008-12-08 22:39 ` John David Anglin
2008-12-09 0:01 ` Carlos O'Donell
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=20081123071348.GA31575@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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