[Bug 605667] Re: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP: 0010:[<ffffffff81365730>] [<ffffffff81365730>] fb_release+0x30/0x70

[Andy Whitcroft]

This bug seems to be related to a race condition between console
initialisation and plymouthd.  Note: if your crash does not include
plymouthd as the trigger you likely have a different issue.  In my case
I get several different possible outcomes.  Sometimes I just get a black
screen, sometimes I get much flashing and dropped to 'low resolution'
mode, sometimes I get logged in apparently fine but there is a crash
waiting in apport.  These are all basically variants of this bug.  The
trigger is that the drm frambuffer ejects the vesafb framebuffer as it
starts.  If the vesa framebuffer is opened by plymouthd before this
occurs then we trigger a panic when plymouthd tries to exit.  Bad.

** Tags added: kernel-candidate kernel-reviewed
** Tags removed: kernel-needs-review

** Changed in: linux (Ubuntu)
       Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Andy Whitcroft (apw)

-- 
Kernel Oops - unable to handle kernel NULL pointer dereference; RIP: 0010:[<ffffffff81365730>]  [<ffffffff81365730>] fb_release+0x30/0x70
https://bugs.launchpad.net/bugs/605667
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.