Is there a place other than bugzilla.kernel.org where I can report the
kernel bug?, I can't enter that site. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879059
Title:
Random kernel panic
Since an update to kernel 3.0.0-14-generic I haven't had any problems.
Perhaps it has been fixed it that version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879059
Title:
Random kernel panic
To
Public bug reported:
So far I have experienced random kernel panic with the new kernel 3
which did't happen using kernel 2.6, I'm under the impression it happens
when the laptop is not plugged in, the main symptom is that any sound
being playing at the time of the kernel panic gets stuck on a part
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879059
Title:
Random kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879059/+subscriptio
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879059
Title:
Random kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
I just tested against kernel
3.1.0-999-generic_3.1.0-999.201110200416_i386, bug remains, kernel panic
occurred while on battery power, I attach the output from the
installation of that kernel since it gave an error.
** Attachment added: "The output of the installation of kernel
3.1.0-999-generic_
Is there a tool to get the screen shot of the kernel panic, or is it
sufficient with a cell phone photo?, It all happens so quickly even I
panic, but I see some text about a trace in console mode that I have no
idea how to copy other that on paper. Thanks in advance.
--
You received this bug not
