From: Thomas Gleixner <tglx@linutronix.de>
To: Andreas Mohr <andi@lisas.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
John Stultz <johnstul@us.ibm.com>
Subject: Re: clocksource mutex deadlock, cat current_clocksource (2.6.33-rc6)
Date: Sat, 6 Feb 2010 15:46:50 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1002061534020.2811@localhost.localdomain> (raw)
In-Reply-To: <20100206142141.GA12871@rhlx01.hs-esslingen.de>
On Sat, 6 Feb 2010, Andreas Mohr wrote:
> echo t > /proc/sysrq-trigger shows (full output on request):
At least the state of "kwatchdog" would be interesting.
> cat D 00000000 0 19361 2959 0x00000000
> de215ef8 00000046 00000000 00000000 c13b0294 dd45c380 dd45c5fc df9c6ef0
> de215f28 de215f08 c13b0260 00000202 de215f28 c124fcae dd45c380 c13b0280
> c13b0280 c13b0280 dd45c380 de215f08 ffffffff d9de1000 c13b0338 df9c6ef0
> Call Trace:
> [<c124fcae>] mutex_lock_nested+0x157/0x23d
> [<c104873e>] sysfs_show_current_clocksources+0x17/0x41
>
> INFO: lockdep is turned off.
Why is lockdep turned off ?
Thanks,
tglx
next prev parent reply other threads:[~2010-02-06 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 14:21 Andreas Mohr
2010-02-06 14:46 ` Thomas Gleixner [this message]
2010-02-07 19:19 ` Andreas Mohr
2010-02-08 5:38 ` clocksource mutex deadlock, cat current_clocksource (2.6.33-rc6/7) Andreas Mohr
2010-02-08 9:13 ` Thomas Gleixner
2010-02-08 9:37 ` Andreas Mohr
2010-02-08 10:06 ` Thomas Gleixner
2010-02-08 19:47 ` Andreas Mohr
2010-02-08 20:28 ` Thomas Gleixner
2010-02-08 20:40 ` Thomas Gleixner
2010-02-08 20:51 ` Andreas Mohr
2010-02-08 21:02 ` Andreas Mohr
2010-02-08 21:16 ` Thomas Gleixner
2010-02-09 10:02 ` Thomas Gleixner
2010-02-09 22:13 ` Andreas Mohr
2010-02-14 18:27 ` Andreas Mohr
2010-02-15 6:21 ` Andreas Mohr
2010-02-08 20:43 ` Andreas Mohr
2010-02-08 20:39 ` Andreas Mohr
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=alpine.LFD.2.00.1002061534020.2811@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=andi@lisas.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®