** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968906
Title:
general protection fault: [#1] SMP
To manage notifications
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968906
Title:
general protection fault: [#1] SMP
To manage notifications about this bug go to:
apport information
** Tags added: apport-collected staging
** Description changed:
Just starting the machine after updating.
ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic
Uname: Linux 3.2.0-20-generic x86_64
Annotation: Your system
Do you have a way to reproduce the bug, or was this a one time event?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: queue-work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I will restart a few time to see what happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968906
Title:
general protection fault: [#1] SMP
To manage notifications about this bug go to:
Every time I get tree other errors:
- ColorD -- bug is confirmed
- two times Xorg crashed with SIGSEGV in signal handler called() -- flaged
as nvidia-graphics-drivers bug.
Command ubuntu-bug nvidia-graphics-drivers gives a pop-up that
nvidia-graphic-drivers does not exist.
So to answer your
Did this just start happening after your last update?
Since this bug does happen multiple times, would it be possible for you
to test the previous kernel to see if it is a new regression?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
