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/7)
Date: Mon, 8 Feb 2010 22:16:45 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1002082213500.2811@localhost.localdomain> (raw)
In-Reply-To: <20100208210219.GA22039@rhlx01.hs-esslingen.de>
On Mon, 8 Feb 2010, Andreas Mohr wrote:
> On Mon, Feb 08, 2010 at 09:51:05PM +0100, Andreas Mohr wrote:
> > 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
>
> -rc4 and 2.6.32.3 don't show lockup message, instant bootup without any
> visible delay.
>
> Don't tell me I'm now supposed to try -rc5 and also rebuild -rc6 ;)
> If so, do tell early so that I have lots of time to get it built...
Well, we better know, after which point that problem manifested
itself. A bisect would be optimal.
Thanks,
tglx
next prev parent reply other threads:[~2010-02-08 21:17 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
2010-02-08 21:02 ` Andreas Mohr
2010-02-08 21:16 ` Thomas Gleixner [this message]
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.1002082213500.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®