From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>
Cc: nando@ccrma.Stanford.EDU, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.21.5-rt17 on lenovo t61, some BUG's (lukewarm IQ?)
Date: Sat, 30 Jun 2007 12:42:10 -0700 [thread overview]
Message-ID: <1183232530.14071.17.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <20070630192403.GE3720@elte.hu>
On Sat, 2007-06-30 at 21:24 +0200, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
>
> > Hi Ingo, this is happening in a brand new laptop, a Lenovo t61 with a
> > 7700 processor and the Santa Rosa chipset.
> >
> > Lukewarm IQ detected in hotplug locking
> > BUG: at kernel/cpu.c:44 lock_cpu_hotplug()
>
> hm, that's an upstream kernel message. Cpu-hotplug locking is ... a bit
> messy still. Does it otherwise work? (it should only affect sw-suspend
> on SMP)
It seems to work (I'm typing this on that machine running rt17). But I'm
still testing things and I have certainly not gotten to the point of
really trying suspend. It is a brand new laptop with new'ish chipset and
stuff so lotsa small details to fix :-)
> > [BTW, I tried to unsuccessfully boot rt18 today in one of my CCRMA
> > machines but the boot hung when trying to start the acpi daemon - this
> > was on FC6, I'll try to find out more tomorrow. We are seeing some
> > hungs with rt17 that I have not tried to diagnose yet]
>
> do you still see this?
Yes I do. My previous report was not very precise.
Trying to boot rt18 - this is on fc6 - seems more slugish than rt17
(very subjective), eventually it gets to "starting udev" and it hangs
there. I presume it is trying to start a device driver unsuccessfully
but I don't get any more information and can't get to single user to
find out more.
Yesterday I noticed that _sometimes_ "starting udev" in rt17 takes some
time. So this may be something that got worse in rt18 as opposed to
something completely new in rt18.
Sorry for the vageness and let me know if there's something I can do to
try to find out what's going on (looking at rc.sysinit I found there's
some kernel boot options that allow for more debugging but I did not
have time to try that).
As for the hangs in rt17 I have not been able to find anything out. They
are very sporadic (surprise!) and so far I have found no clues or
commonality in what was happening when the hang occurs.
-- Fernando
prev parent reply other threads:[~2007-06-30 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 3:20 Fernando Lopez-Lezcano
2007-06-30 19:24 ` Ingo Molnar
2007-06-30 19:42 ` Fernando Lopez-Lezcano [this message]
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=1183232530.14071.17.camel@cmn3.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®