You are not logged in.

#1 2009-09-08 09:01:30

pie86
Member
Registered: 2009-09-06
Posts: 78

Sudden kernel panic!

Hi everybody,
is there a way to find out what caused a kernel panic on my pc yesterday night?! I had a look at kernel.log, messages.log and errors.log but I couldn't find anything suspicious.

thanks in advances
pietro

Offline

#2 2009-09-10 11:23:45

Preacher
Member
From: UK
Registered: 2006-09-26
Posts: 46

Re: Sudden kernel panic!

Try everything.log as well.  Assume this happened when you were booting up?


To be a preacher requires two apparently contradictory qualities: confidence and humility.

Offline

#3 2009-09-10 11:54:02

pie86
Member
Registered: 2009-09-06
Posts: 78

Re: Sudden kernel panic!

No, I don't know exactly when it happened: my laptop was downloading with transmission, screen was black, when I saw bloch-maiusc and bloch-num flashing I had no doubt sad

I've tried to find something in everything.log but nothing within the time interval it should have happened.

Hope it was an caused by a particulary strong cosmic ray! big_smile

thanks
pietro

Offline

#4 2009-09-30 20:49:20

pie86
Member
Registered: 2009-09-06
Posts: 78

Re: Sudden kernel panic!

It happened again. I think that conditions were the same: lid closed and transmission running.

Anyway this time I've been as sly as a fox: I've started the pc with a live cd and backuped all log files!

My problem now is that my messages.log ends like this:

Sep 30 19:27:32 xps kernel: tg3 0000:09:00.0: PME# disabled
Sep 30 19:27:32 xps kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 30 19:27:34 xps kernel: tg3 0000:09:00.0: PME# disabled
Sep 30 19:27:34 xps kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 30 19:27:48 xps dhcpcd: version 5.1.0 starting
Sep 30 19:27:48 xps dhcpcd: eth1: rebinding lease of 192.168.10.101
Sep 30 19:27:48 xps dhcpcd: eth1: acknowledged 192.168.10.101 from 192.168.10.1
Sep 30 19:27:48 xps dhcpcd: eth1: checking for 192.168.10.101
Sep 30 19:27:53 xps dhcpcd: eth1: leased 192.168.10.101 for 43200 seconds
Sep 30 19:27:53 xps dhcpcd: forking to background
Sep 30 19:35:26 xps kernel: CE: hpet increasing min_delta_ns to 15000 nsec
Sep 30 19:47:19 xps acpid: client 3604[0:0] has disconnected
Sep 30 19:47:19 xps acpid: client connected from 4775[0:0]
Sep 30 19:47:19 xps acpid: 1 client rule loaded
Sep 30 19:50:02 xps kernel: Clocksource tsc unstable (delta = -132553038 ns)
Sep 30 19:54:14 xps logger: ACPI group/action undefined: video / VID1
Sep 30 19:54:14 xps laptop-mode: Laptop mode 
Sep 30 19:54:14 xps laptop-mode: enabled, 
Sep 30 19:54:14 xps laptop-mode: not active [unchanged]
Sep 30 20:14:15 xps -- MARK --

and I think that it's not telling us anything. hmm

messages.log is the last file modified before the kernel panic however I have the whole /var/log folder backuped.

Any suggestions?
Thanks in advances,
pietro

Offline

Board footer

Powered by FluxBB