The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andreas Mohr <andi@lisas.de>,
	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/7)
Date: Mon, 8 Feb 2010 21:51:05 +0100	[thread overview]
Message-ID: <20100208205105.GA16990@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1002082139360.2811@localhost.localdomain>

Hi,

On Mon, Feb 08, 2010 at 09:40:24PM +0100, Thomas Gleixner wrote:
> On Mon, 8 Feb 2010, Thomas Gleixner wrote:
> > On Mon, 8 Feb 2010, Andreas Mohr wrote:
> > Which compiler version are you using ?
> > 
> > Can you please provide the disassembly of kernel/time/timekeeping.o ?
> 
> Is that NMI watchdog hit fully reproducible ?

Looks like it:
- another bootup also had lockup message
- all /var/log/dmesg* have lockup message, oldest is:
2010-02-07 20:00 dmesg.4.gz

Linux version 2.6.33-rc6 (root@note) (gcc version 4.3.4 (Debian 4.3.4-6)) #3 Sun Jan 31 23:47:51 CET 2010
.
.
.
PM: Adding info for No Bus:cooling_device0
Switching to clocksource acpi_pm
BUG: NMI Watchdog detected LOCKUP on CPU0, ip c1046694, registers:
Modules linked in:

Pid: 266, comm: kwatchdog Not tainted 2.6.33-rc6 #3 Inspiron 8000
/Inspiron 8000
EIP: 0060:[<c1046694>] EFLAGS: 00000082 CPU: 0
EIP is at timekeeping_forward_now+0xf0/0x11d
EAX: 342100fe EBX: f3dcdfc8 ECX: 63826cfb EDX: ffffffff
ESI: 003ffd7b EDI: 00000000 EBP: dfa31f50 ESP: dfa31f28
 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
Process kwatchdog (pid: 266, ti=dfa31000 task=dfa4e0a0 task.ti=dfa31000)
Stack:
 005b9e7e 00000000 6184c590 00000fff 002cb338 4b6f0da7 00000000 c13d8524
<0> c13d8524 dfa31f48 dfa31f60 c10466d2 c13d8524 c13d8524 dfa31f6c
c104725e


IOW, it's NOT gcc 4.4 and it's pretty darn reproducible.

Andreas Mohr

  reply	other threads:[~2010-02-08 20:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06 14:21 clocksource mutex deadlock, cat current_clocksource (2.6.33-rc6) Andreas Mohr
2010-02-06 14:46 ` Thomas Gleixner
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 [this message]
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=20100208205105.GA16990@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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