From: Justin Madru <jdm64@gawab.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [regression bisected] HR-timers bug >=2.6.25
Date: Fri, 16 May 2008 10:26:10 -0700 [thread overview]
Message-ID: <482DC3B2.3040907@gawab.com> (raw)
In-Reply-To: <1210922458.7886.14.camel@twins>
Peter Zijlstra wrote:
> The kernel doesn't hang, right? My reading of the description tells me
> the splash just doesn't work.
>
> If it does hang the kernel, an NMI trace collected over serial or
> netconsole (regular console being out of the question since its
> graphical stuff :/) would be most helpful.
I've seen it blank out in 2 different ways.
1) Usplash completely finishes. Then screen goes blank for the usual mode change/screen refreshing,
doing several refreshes of a blank screen. But, the screen then stays black.
I do still hear the gdm sound, and can switch to a console.
Pressing ctrl+alt+f1 makes the screen "refresh" again, but stay blank/black. I can still login but blindly.
2) More rarely. Usplash hasn't finished (but near the end). The usplash screen fades out to black.
It's like a screen burn in, or after image; the screen slowly fades out to black.
After this the computer is _seemingly_unresponsive_ - Only alt+sysrq+b seems to work. (I have to hard reset)
After I reboot the backlight is at the lowest level.
Anyways, I think I can figure out how to set up a netconsole, but
is there something more to setup a NMI trace? I found Documentation/networking/netconsole.txt
But, it doesn't say anything about a NMI trace.
Justin
next prev parent reply other threads:[~2008-05-16 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 19:32 [regression bisected] HR-timers bug >=2.6.25 Justin Madru
2008-05-16 7:15 ` Thomas Gleixner
2008-05-16 7:20 ` Peter Zijlstra
2008-05-16 17:26 ` Justin Madru [this message]
2008-05-16 17:31 ` Peter Zijlstra
2008-05-18 22:15 ` Justin Madru
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=482DC3B2.3040907@gawab.com \
--to=jdm64@gawab.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--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