From: Pavel Machek <pavel@suse.cz>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Oleg Nesterov <oleg@tv-sign.ru>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Max Krasnyanskiy <maxk@qualcomm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: latest -git: hibernate: possible circular locking dependency detected
Date: Fri, 22 Aug 2008 11:18:27 +0200 [thread overview]
Message-ID: <20080822091827.GC6542@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <19f34abd0808211059m451f5f7au949217aeecccccaf@mail.gmail.com>
Hi!
> > this path is triggered as a result of "echo disk > /sys/power/state"
>
> Yes. That is what I typed.
>
> >
> > disable_nonboot_cpus() calls cpu_maps_update_being() which takes
> > "cpu_add_remove_lock" (lock-1).
> >
> > If we go down the road cleanup_workqueue_thread() ->
> > flush_cpu_workqueue() will take "cwq->lock" (lock-2).
> > So this should be the second lock.
> >
> >
> [...]
>
> > hmm, did you somehow hit "Sysrq + o"?
> >
> > 'cause I don't see any other places (say, with handle_sysrq(k,...)
> > where "k" migth be 'o') from where do_power_off() might have been
> > triggered...
> >
>
> No. But in my logs I often saw SysRq triggered, even though I didn't
> do it any of these times:
>
> log-20080821-104053.txt:SysRq : SysRq : Show State
> log-20080821-105541.txt:SysRq : Emergency Sync
> log-20080821-105541.txt:SysRq : Emergency Sync
> log-20080821-105541.txt:SysRq : Power Off
> log-20080821-110514.txt:SysRq : Terminate All Tasks
> log-20080821-111650.txt:SysRq : HELP : loglevel0-8 <6>serial 00:0d: activated
> log-20080821-111650.txt:SysRq : Power Off
> log-20080821-111650.txt:SysRq : Terminate All Tasks
> log-20080821-111650.txt:SysRq : SysRq : <6>serial 00:0d: activated
> log-20080821-120628.txt:SysRq : SysRq : HELP : HELP : <6>serial 00:0d: activated
> log-20080821-120628.txt:SysRq : SysRq : HELP : HELP : <6>serial 00:0d: activated
>
> (And it seems to pick a random letter too. It even showed the "HELP:"
> line at one point!)
>
> I have no idea why this happens. Is it possible to trigger SysRq by
> writing data on the other end of the serial console? (Maybe my cable
> is bad or something, but data seems to be going in both directions
> over my serial console.)
Serial break translates to sysrq, IIRC.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-08-22 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 15:04 Vegard Nossum
2008-08-21 17:38 ` Dmitry Adamushko
2008-08-21 17:59 ` Vegard Nossum
2008-08-22 9:18 ` Pavel Machek [this message]
2008-08-21 18:03 ` Oleg Nesterov
2008-08-21 18:22 ` Rafael J. Wysocki
2008-08-21 18:31 ` Vegard Nossum
2008-08-21 18:39 ` Vegard Nossum
2008-08-21 19:07 ` Rafael J. Wysocki
2008-08-21 19:14 ` Vegard Nossum
2008-08-21 19:31 ` Rafael J. Wysocki
2008-08-21 19:41 ` Vegard Nossum
2008-08-21 19:54 ` Rafael J. Wysocki
2008-08-22 8:55 ` Pavel Machek
2008-08-22 19:09 ` Vegard Nossum
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=20080822091827.GC6542@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=a.p.zijlstra@chello.nl \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=oleg@tv-sign.ru \
--cc=rjw@sisk.pl \
--cc=vegard.nossum@gmail.com \
/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
all inboxes | Powered by JetHome®