From: Thomas Gleixner <tglx@linutronix.de>
To: Justin Madru <jdm64@gawab.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
David Airlie <airlied@linux.ie>,
Sylvain Meyer <sylvain.meyer@worldonline.fr>,
Antonino Daplas <adaplas@gmail.com>,
Roman Zippel <zippel@linux-m68k.org>, Greg KH <gregkh@suse.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [regression bisected] HR-timers bug >=2.6.25
Date: Fri, 16 May 2008 09:15:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0805160909450.3255@apollo.tec.linutronix.de> (raw)
In-Reply-To: <482C8FD6.10808@gawab.com>
On Thu, 15 May 2008, Justin Madru wrote:
> I've reported this problem previously:
> http://lkml.org/lkml/2008/3/12/290
> http://bugzilla.kernel.org/show_bug.cgi?id=10235
> https://bugs.freedesktop.org/show_bug.cgi?id=15602
>
> This bug is still in mainline as of 2.6.26-rc1. (affected versions 2.6.25-rc0
> - 2.6.26-rc1)
>
> Ever since 2.6.25-rc3 (the first rc I tested), my screen would blank out when
> mode switching from the Ubuntu uplash to the gdm login. Normally after the
> boot splash, the screen goes black and "refreshes" to select the correct
> resolution. But when using a kernel newer than 2.6.24 the screen doesn't come
> back on - it stays blank. This doesn't happen every time, but a good majority
> of the time. The workaround is to disable the splash, and that fixes the
> problem almost completely.
>
> I did a git bisect. Rebooting 3 times if the problem didn't occur just to make
> sure.
> The git bisect reports that it's timing related - which is what Jesse Barnes
> said it could be.
Well, it's a timing problem related to splash which is exposed by the
scheduler timing changes. This is neither a hrtimer nor a scheduler
bug. Something in the splash / video driver switchover relies on some
obscure timing which is nowhere guaranteed.
Thanks,
tglx
next prev parent reply other threads:[~2008-05-16 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 19:32 Justin Madru
2008-05-16 7:15 ` Thomas Gleixner [this message]
2008-05-16 7:20 ` Peter Zijlstra
2008-05-16 17:26 ` Justin Madru
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=alpine.LFD.1.10.0805160909450.3255@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=adaplas@gmail.com \
--cc=airlied@linux.ie \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=jdm64@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=sylvain.meyer@worldonline.fr \
--cc=zippel@linux-m68k.org \
/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®