From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82711] After update to kernel soft lockup (oops) and incomplete boot and shutdown fail
Date: Fri, 05 Sep 2014 16:58:17 +0000 [thread overview]
Message-ID: <bug-82711-2300-Ity8VYhDGd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82711-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82711
EmanueL Czirai <somelinuxbugs@riseup.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |somelinuxbugs@riseup.net
--- Comment #9 from EmanueL Czirai <somelinuxbugs@riseup.net> ---
This may or may not apply but maybe you could check if your video driver
(nouveau?) is (re)compiled for the new kernel? I got a similar NULL pointer
deref. when I recompiled the kernel and my fglrx(not nouveau for me) driver
failed to compile and thus kept the previous module.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-09-05 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 9:51 [Bug 82711] New: After update to kernel soft lockup and incomplete boot bugzilla-daemon
2014-08-18 10:26 ` [Bug 82711] " bugzilla-daemon
2014-08-18 18:58 ` bugzilla-daemon
2014-08-18 18:59 ` bugzilla-daemon
2014-08-18 19:01 ` bugzilla-daemon
2014-08-18 19:01 ` [Bug 82711] After update to kernel soft lockup and incomplete boot and shutdown fail bugzilla-daemon
2014-08-18 19:08 ` bugzilla-daemon
2014-08-18 19:29 ` bugzilla-daemon
2014-08-18 19:30 ` bugzilla-daemon
2014-08-18 19:31 ` bugzilla-daemon
2014-08-18 19:55 ` [Bug 82711] After update to kernel soft lockup (oops) " bugzilla-daemon
2014-08-20 9:25 ` bugzilla-daemon
2014-09-05 16:58 ` bugzilla-daemon [this message]
2014-09-05 19:42 ` bugzilla-daemon
2014-10-07 9:47 ` bugzilla-daemon
2014-10-09 16:53 ` bugzilla-daemon
2014-10-22 11:05 ` 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-82711-2300-Ity8VYhDGd@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.