Hi,
I've just installed lenny under VirtualBox as I wanted to try a different Linux distribution.
When I logon to a Gnome session, I often get a popup saying:
"Your system has had a kernel failure"
It most often happens the first time I logon using gnome after a boot.
I don't get this if I select a KDE session.
How do I track this down?
Cheers
Russell Thamm
IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
> I don't get this if I select a KDE session.
>
> How do I track this down?
>
> Cheers
> Russell Thamm
>
> IMPORTANT: This email remains the property of the Australian Defence
> Organisation and is subject to the jurisdiction of section 70 of the CRIMES
> ACT 1914. If you have received this email in error, you are requested to
> contact the sender and delete the email.
>
>
--
My platform is GNU/Linux Debian(sid-amd64, lenny-Intelx86) Gnome GTK.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
I have had the same problem with a Squeeze install. I upgraded to sid
which brought in a newer kernel fixing that error.
It is the package kerneloops.
$ aptitude show kerneloops
Package: kerneloops
[...]
Description: kernel oops tracker
kerneloops is a daemon that collects kernel crash information and then
submits the extracted signature to the kerneloops.org
website for statistical analysis and presentation to the Linux kernel
developers.
> How do I track this down?
Look at /var/log/kernel.log
You should find some logs and a kernel Ooops ! (an error in the kernel or a
module).
I think it will not be very informative.
I also have this at every boot on my Thinkpad T41 running SID.
I think it's related to the wifi chipset having problem with the firmware
ipw2100. It is reloaded very often.
It's a kernel oops. Those usually clear up as the kernel you are using
matures. File a bug. Also, check the settings of the vm again. If
you have hardware virtualization support (CPU), use it. Or if you are
using it, turn it off.
Mark Allums