From: Mike Galbraith <efault@gmx.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Frederik Himpe <fhimpe@telenet.be>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24 regression: pan hanging unkilleable and un-straceable
Date: Mon, 04 Feb 2008 15:49:18 +0100 [thread overview]
Message-ID: <1202136558.7282.18.camel@homer.simson.net> (raw)
In-Reply-To: <1200980828.4643.11.camel@homer.simson.net>
On Tue, 2008-01-22 at 06:47 +0100, Mike Galbraith wrote:
> On Tue, 2008-01-22 at 16:25 +1100, Nick Piggin wrote:
> > On Tuesday 22 January 2008 16:03, Mike Galbraith wrote:
>
> > > I've hit same twice recently (not pan, and not repeatable).
> >
> > Nasty. The attached patch is something really simple that can sometimes help.
> > sysrq+p is also an option, if you're on a UP system.
>
> SMP (P4/HT imitating real cores)
>
> > Any luck getting traces?
>
> We'll see. Armed.
Hm. ld just went loopy (but killable) in v2.6.24-6928-g9135f19. During
kbuild, modpost segfaulted, restart build, ld goes gaga. Third attempt,
build finished. Not what I hit before, but mentionable.
[ 674.589134] modpost[18588]: segfault at 3e8dc42c ip 0804a96d sp af982920 error 5 in modpost[8048000+9000]
[ 674.589211] mm/memory.c:115: bad pgd 3e081163.
[ 674.589214] mm/memory.c:115: bad pgd 3e0d2163.
[ 674.589217] mm/memory.c:115: bad pgd 3eb01163.
[ 1407.322144] =======================
[ 1407.322144] ld R running 0 21963 21962
[ 1407.322144] db9d7f1c 00200086 c75f9020 b1814300 b0428300 b0428300 b0428300 c75f9280
[ 1407.322144] b1814300 00000001 db9d7000 00000000 d08c2f90 dba4f300 00000002 00000000
[ 1407.322144] b1810120 dba4f334 00200046 ffffffff db9d7000 c75f9020 db9d7f30 b02f333f
[ 1407.322144] Call Trace:
[ 1407.322144] [<b02f333f>] preempt_schedule_irq+0x45/0x5b
[ 1407.322144] [<b0117a10>] ? do_page_fault+0x0/0x470
[ 1407.322144] [<b0104d6e>] need_resched+0x1f/0x21
[ 1407.322144] [<b0117a10>] ? do_page_fault+0x0/0x470
[ 1407.322144] [<b0117a5c>] ? do_page_fault+0x4c/0x470
[ 1407.322144] [<b0117a10>] ? do_page_fault+0x0/0x470
[ 1407.322144] [<b02f4a3a>] ? error_code+0x72/0x78
[ 1407.322144] [<b02f0000>] ? init_transmeta+0xcf/0x22f <== zzt P4
next prev parent reply other threads:[~2008-02-04 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 20:58 2.6.24 regression: pan hanging unkilleable and un-straceable Frederik Himpe
2008-01-22 0:05 ` Nick Piggin
2008-01-22 5:03 ` Mike Galbraith
2008-01-22 5:25 ` Nick Piggin
2008-01-22 5:47 ` Mike Galbraith
2008-02-04 14:49 ` Mike Galbraith [this message]
2008-02-04 23:02 ` Nick Piggin
2008-01-22 10:38 ` Ingo Molnar
2008-01-24 5:30 ` Valdis.Kletnieks
2008-01-26 13:29 ` Frederik Himpe
2008-01-26 13:46 ` Nick Piggin
2008-01-26 14:27 ` Pascal Terjan
2008-01-28 1:49 ` Nick Piggin
2008-01-28 1:46 ` Nick Piggin
2008-01-28 18:05 ` Frederik Himpe
2008-01-31 22:45 ` Frederik Himpe
2008-02-02 0:53 ` Nick Piggin
2008-01-22 10:37 ` Ingo Molnar
2008-01-22 23:00 ` Nick Piggin
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=1202136558.7282.18.camel@homer.simson.net \
--to=efault@gmx.de \
--cc=fhimpe@telenet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.