From: Hannes Reinecke <Hannes.Reinecke@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Dumb question: BKL on reboot ?
Date: Thu, 21 Aug 2003 17:55:49 +0200 [thread overview]
Message-ID: <3F44EB85.5000108@suse.de> (raw)
In-Reply-To: <20030821154113.GE29612@dualathlon.random>
Andrea Arcangeli wrote:
> On Thu, Aug 21, 2003 at 10:05:20AM +0200, Hannes Reinecke wrote:
[ .. ]
>>
>>Exactly what happened here. CPU#1 entered sys_reboot, got BKL and
>>prepared to stop. It will never release BKL, leaving a nice big window
>>for CPU#0 to deadlock.
>
>
> if that was really the case it shouldn't deadlock, because CPU0
> shouldn't depend on a big kernel lock to be able to re-enable the irqs,
> and to receive the IPI. Nor any IPI handler could ever be allowed to
> take the big kernel lock.
>
> Unless you can demonstrate a dependency on the big kernel lock for CPU0
> to re-enable the irqs eventually, I can't see how the above could
> deadlock.
>
What happened was this:
================================================================
TASK HAS CPU (0): 0x904000 (kupdated):
LOWCORE INFO:
-psw : 0x400100180000000 0x0000000007aa22
-function : sync_old_buffers+58
-prefix : 0x009c8000
-cpu timer: 0xfffffa77 0x33465f80
-clock cmp: 0x00b9e503 0x235324f4
-general registers:
0000000000000000 0x000000002e1000
0x0000000007aa22 0x0000000004919e
0x00000000907f28 0x0000000022b428
0000000000000000 0000000000000000
0x00000000224340 0000000000000000
0x00000000970000 0x00000000233b00
0x00000000904000 0x000000001deb60
0x00000000907e78 0x00000000907dd8
[ .. ]
STACK:
0 kupdate+424 [0x7af4c]
1 arch_kernel_thread+70 [0x18d72]
================================================================
TASK HAS CPU (1): 0x3318000 (reboot):
LOWCORE INFO:
-psw : 0x700100180000000 0x0000007ffe0d8e
-function : not found in System map
-prefix : 0x009c2000
-cpu timer: 0xfff79e2d 0x014244c0
-clock cmp: 0x00b9e503 0x3a5d9504
-general registers:
0x00000000000001 0000000000000000
0000000000000000 0000000000000000
0x0000000001f268 0000000000000000
0x00000000000003 0x000000000002c0
0x000000000490f0 0x00000003318000
0x00000000016422 0000000000000000
0x00000000000001 0x000000001da280
0x0000000001f268 0x0000000331bae0
[ .. ]
STACK:
0 machine_restart_smp+62 [0x1f5f2]
1 machine_restart+48 [0x19884]
2 sys_reboot+306 [0x49222]
3 sysc_noemu+16 [0x16242]
Not sure why CPU#0 wanted to execute kupdate(), but hey ...
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Deutschherrnstr. 15-19 +49 911 74053 688
90429 Nürnberg http://www.suse.de
next prev parent reply other threads:[~2003-08-21 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 10:22 Dumb question: BKL on reboot ? Hannes Reinecke
2003-08-20 18:29 ` Andrew Morton
2003-08-20 18:35 ` David S. Miller
2003-08-20 20:23 ` Dave Hansen
2003-08-21 8:05 ` Hannes Reinecke
2003-08-21 15:41 ` Andrea Arcangeli
2003-08-21 15:55 ` Hannes Reinecke [this message]
2003-08-21 16:39 ` Andrea Arcangeli
2003-08-21 16:58 ` Andrea Arcangeli
2003-08-22 6:39 ` Hannes Reinecke
2003-08-22 13:57 ` Andrea Arcangeli
2003-08-24 21:43 ` Andrea Arcangeli
2003-08-21 15:33 ` Andrea Arcangeli
[not found] <3F434BD1.9050704@suse.de.suse.lists.linux.kernel>
2003-08-20 10:49 ` Andi Kleen
2003-08-20 11:51 ` Hannes Reinecke
2003-08-20 12:03 ` Andi Kleen
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=3F44EB85.5000108@suse.de \
--to=hannes.reinecke@suse.de \
--cc=andrea@suse.de \
--cc=haveblue@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).