From: Andrew Morton <akpm@osdl.org>
To: Jason Stubbs <jstubbs@work-at.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Consistent lock up on >=2.6.8
Date: Mon, 4 Oct 2004 01:35:48 -0700 [thread overview]
Message-ID: <20041004013548.26e853fc.akpm@osdl.org> (raw)
In-Reply-To: <200410041611.17000.jstubbs@work-at.co.jp>
Jason Stubbs <jstubbs@work-at.co.jp> wrote:
>
> I'm getting consistent hangs under heavy load on 2.6.8.1, 2.6.9-rc2 and
> 2.6.9-rc3. I have tested on 2.6.7 and have no problems at all. I can
> reproduce the problem in less than 10 minutes by repeatedly running a cpu
> intensive process such as openssl while the system performs its regular
> tasks.
>
> SysRq works and I was able to pull the registers (which are always very
> similar) and the last 50 lines of the task list. If more of the task list is
> necessary, I'll go out and buy a serial cable to get it. All information
> provided is from 2.6.9-rc3.
>
> ...
>
> Pid: 22433, comm: openssl
> EIP: 0060:[<c02d5082>] CPU: 0
> EIP is at _spin_lock+0xa/0x13
> EFLAGS: 00000286 Not tainted (2.6.9-rc3)
> EAX: c03b2500 EBX: 00000000 ECX: x031ca80 EDX: 00000000
> ESI: f8b9c926 EDI: ffffffff EBP: c03e1f44 DS: 007b ES: 007b
> CR0: 8005003b CR2: b7df91df CR3: 3705c000 CR4: 000006d0
Looks like a locking bug.
> Stack pointer is garbage, not printing trace
Sigh. That's exactly the info we wanted. Please try 2.6.9-rc3-mm1 which
should have that fixed. Or wait 15 minutes for 2.6.9-rc3-mm2.
Then do the sysrq-P trace again. You may need to type it a few times. If
you manage to get a backtrace of the process which is stuck in spin_lock,
that's the info we want.
You may find that all CPUs are stuck in spin_lock(). If so, please send
each CPU's backtrace. If you have to type it all in, don't worry about the
eight-digit hex numbers.
next prev parent reply other threads:[~2004-10-04 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 7:11 PROBLEM: Consistent lock up on >=2.6.8 Jason Stubbs
2004-10-04 8:35 ` Andrew Morton [this message]
2004-10-04 10:31 ` Jason Stubbs
2004-10-04 19:05 ` Andrew Morton
2004-10-05 1:53 ` Jason Stubbs
2004-10-05 1:58 ` Andrew Morton
2004-10-05 4:17 ` Jason Stubbs
2004-10-29 15:08 ` RESEND: Consistent lock up 2.6.8-1.521 (and 2.6.8.1 w/ high-res-timers/skas/sysemu) Andrew A.
2004-10-29 15:22 ` Andrew A.
2004-10-29 15:23 ` Andrew A.
2004-10-05 2:03 ` PROBLEM: Consistent lock up on >=2.6.8 Roland Dreier
2004-10-05 3:51 ` Andrew Morton
2004-10-05 4:05 ` Roland Dreier
2004-11-25 1:03 ` Jason Stubbs
-- strict thread matches above, loose matches on Subject: below --
2004-12-06 8:30 Chris Caputo
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=20041004013548.26e853fc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jstubbs@work-at.co.jp \
--cc=linux-kernel@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 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.