From: Randy Dunlap <rdunlap@xenotime.net>
To: "Justin M. Forbes" <jforbes@redhat.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@fedoraproject.org,
dri-devel@lists.freedesktop.org
Subject: Re: 3.5.x boot hang after conflicting fb hw usage <driver> vs VESA VGA - removing generic driver
Date: Fri, 17 Aug 2012 15:28:54 -0700 [thread overview]
Message-ID: <502EC5A6.7040502@xenotime.net> (raw)
In-Reply-To: <1345242330.3841.8.camel@fedora64.linuxtx.org>
On 08/17/2012 03:25 PM, Justin M. Forbes wrote:
> for <driver>, we have verified cases on inteldrmfb, radeondrmfb, and
> cirrusdrmfb.
>
> This is the last message displayed before the system hangs. This seems
> to be hitting a large number of users in Fedora, though certainly not
> everyone. This started happening with the 3.5 updates, and is still an
> issue. It appears to be a race condition, because various things have
> allowed boot to continue for some users, though there is no clear work
> around. Has anyone else run across this? Any ideas. For more
> background we have the following bugs:
>
> inteldrmfb:
> https://bugzilla.redhat.com/show_bug.cgi?id=843826
>
> radeondrmfb:
> https://bugzilla.redhat.com/show_bug.cgi?id=845745
>
> cirrusdrmfb <kvm>:
> https://bugzilla.redhat.com/show_bug.cgi?id=843860
>
> It should be noted that the conflicting fb hw usage message is not new,
> it has been around for a while, but this is the last message seen before
> the hang.
Hi, (adding dri-devel mailing list)
I started seeing this problem on 3.5-rc6.
AFAICT, the system is not actually hung, it's just that no output
is showing up on the real (physical) output device (display) -- it's
going somewhere else (or to the bit bucket).
--
~Randy
next prev parent reply other threads:[~2012-08-17 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 22:25 3.5.x boot hang after conflicting fb hw usage <driver> vs VESA VGA - removing generic driver Justin M. Forbes
2012-08-17 22:28 ` Randy Dunlap [this message]
2012-08-17 22:54 ` Dave Airlie
2012-08-17 22:55 ` Dave Airlie
2012-08-17 23:05 ` Randy Dunlap
2012-08-20 5:13 ` Randy Dunlap
2012-08-20 5:22 ` Dave Airlie
2012-08-20 22:45 ` Randy Dunlap
2012-08-21 0:23 ` Dave Airlie
2012-08-21 0:58 ` Randy Dunlap
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=502EC5A6.7040502@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=jforbes@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).