Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already 
done so (pay attention to lspci's additional options), as required by the 
Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. 
It should be one, long line of text which includes the exact kernel version 
you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the 
resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the 
resulting file "lspci-vvnn.log" to this bug report.
4. Please attach your /var/log/kern.log and /var/log/kern.log.0 files to this 
bug report.
5. Please run Memory test as described at 
https://help.ubuntu.com/community/MemoryTest.

Also, your two call traces look like two separate issues. If your memory
test comes back ok, it would probably be best to open a separate bug
report for the second oops.

For your reference, the full description of procedures for kernel-
related bug reports is available at
https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Chris Coulson (chrisccoulson)
       Status: New => Incomplete

-- 
OOPS: "Unable to handle kernel NULL pointer dereference"
https://bugs.launchpad.net/bugs/258450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to