kernel-packages team mailing list archive

[Quinn Balazs <qtbalazs@xxxxxxxxx>]

Additional logs cannot be captured as the panic is triggered on boot. As is stated in the title from the stack trace it seems that the issue stems from an issue with clock scheduling. RIP points to handle_cmd_completion+0x25c/0xba0, cmd, being a python script. 
And the kernel is tainted, with PID reading GF     I. With all modules running under GPL, one or more modules having been force loaded using "insmod -f", and lastly that there was a severe bug in the firmware (either BIOS or other).

Just wanted to put a bit more out to attempt to come close to the kernel
team's policies.

Quinn Balazs

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1215371

Title:
  [Kernel-Oops] Kernel NULL pointer dereference at interrupt when doing
  Centrino clock stuff (drm_kms_helper)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I booted up Ubuntu 13.04 which I updated completely as of yesterday,
  logged on, and then I got the following black screen, which I took a
  picture of with my camera because this happens every time I try to use
  Ubuntu, so I can't access the logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215371/+subscriptions