From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91091] New: 3.19 kernels hang during boot for an NV28 based card
Date: Sat, 10 Jan 2015 09:25:34 +0000 [thread overview]
Message-ID: <bug-91091-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=91091
Bug ID: 91091
Summary: 3.19 kernels hang during boot for an NV28 based card
Product: Drivers
Version: 2.5
Kernel Version: 3.19-rc3+
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: bruno@wolff.to
Regression: Yes
Created attachment 163071
--> https://bugzilla.kernel.org/attachment.cgi?id=163071&action=edit
dmesg output from a successful 3.18 boot
3.19 kernels having been hanging for me during boot for one of my machines.
This is still happening as of commit dc9319f5a3e1f67d2a2fbf190e30f6d03f569fed
(post rc3). The problem first happens with commit
ad4a362635353f7ceb66f4038269770fee1025fa. I tried reverting
ad4a362635353f7ceb66f4038269770fee1025fa from
dc9319f5a3e1f67d2a2fbf190e30f6d03f569fed, but there were conflicts and I don't
know enough to properly resolve them.
The hang is early enough that I can't get logging output from the boot.
I have filed a bug at freedesktop.org for this as well:
https://bugs.freedesktop.org/show_bug.cgi?id=88262
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-01-10 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 9:25 bugzilla-daemon [this message]
2015-01-10 16:09 ` [Bug 91091] 3.19 kernels hang during boot for an NV28 based card bugzilla-daemon
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=bug-91091-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.