From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86-64 sporadic hang in 2.6.23rc7 and 2.6.22
Date: Sat, 29 Sep 2007 16:09:28 +0200 [thread overview]
Message-ID: <46FE5C98.1030507@aitel.hist.no> (raw)
In-Reply-To: <1190669351.4035.254.camel@chaos>
Thomas Gleixner wrote:
> On Mon, 2007-09-24 at 23:08 +0200, Helge Hafting wrote:
>
>> The two kernels mentioned hangs occationally.
>> Typically when I compile something and pass the time
>> by surfing the web.
>>
>> A few minutes and then I notice that the mouse (and everything else in X)
>> stops. kbd LEDs does not react to numlock/capslock.
>> The only thing that still works is sysrq+B
>> So far this has happened while running X, so no messages.
>>
>> I have gone back to 2.6.22rc4, which seems to work.
>>
>> This is a single opteron, although on a dual-slot board.
>>
>
> Can you switch to serial console, so we can get some information out of
> that box? Sysrq-B is working, so we can get info from other sysrq
> functions as well.
>
I didn't need the serial - it crashes during console work too.
I think a "make clean" was in progress at the time. There must be work
going on
in order to crash.
This time 2.6.22rc4 died on me with a general protection fault
I got two reports, the first one scrolled partially off screen but
the whole trace was there:
shrink_dcache_memory
shrink_slab
kswapd
autoremove_wake_function
thread_return
trace_hardirqs_on
kswapd
kswapd
kthtread
child_rip
restore_args
kthread
child_rip
Then I got:
spinlock lockup on cpu #0, kswapd 0/212
_raw_spin_lock
shrink_dcache_parent
shrink_dcache_parent
proc_flush_task
release_task
do_exit
die
error_exit
prune_dcache
[From here on, it continues exactly like the first report:]
shrink_dcache_memory
shrink_slab
kswapd
autoremove_wake_function
thread_return
trace_hardirqs_on
kswapd
kswapd
kthtread
child_rip
restore_args
kthread
child_rip
sysrq P says:
cpu 0
pid 212 comm: kswapd0 not tainted 2.6.22-rc4 #18
RIP: __delay
I took a picture of the screen, in case the register dumps are interesting.
Wonder what this is - dcache trouble? swap trouble?
Helge Hafting
next prev parent reply other threads:[~2007-09-29 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 21:08 x86-64 sporadic hang in 2.6.23rc7 and 2.6.22 Helge Hafting
2007-09-24 21:29 ` Thomas Gleixner
2007-09-29 14:09 ` Helge Hafting [this message]
2007-09-30 15:58 ` Thomas Gleixner
2007-09-30 20:57 ` Helge Hafting
2007-10-08 22:35 ` Helge Hafting
2007-09-30 21:44 ` Andi Kleen
2007-10-01 8:41 ` Helge Hafting
2007-10-05 12:11 ` Helge Hafting
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=46FE5C98.1030507@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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