View previous topic :: View next topic |
Author |
Message |
johny007 n00b
Joined: 13 Aug 2006 Posts: 26
|
Posted: Sun Dec 16, 2007 5:22 pm Post subject: Strange kernel panic |
|
|
I've got my kernel for about 5 months on a laptop (asus barebone, santa rossa etc., quite a new one), everything has always been working fine. I had a kernel panic about two weeks ago, and a day later I had another one. Rebooting helped in both cases, but I'm just curious what could have been a reason for those 2 kernel panics? Any ideas?
I haven't had it since then, but I'm afraid it may happen one day when I'm really in hurry and need to do something important. |
|
Back to top |
|
|
mahdi1234 Guru
Joined: 19 Feb 2005 Posts: 559 Location: Being There
|
Posted: Sun Dec 16, 2007 6:11 pm Post subject: |
|
|
Had similar problem several months ago, one of my memory modules went corrupted. That would be the first thing to check, run the memory test ... |
|
Back to top |
|
|
johny007 n00b
Joined: 13 Aug 2006 Posts: 26
|
Posted: Tue Dec 18, 2007 11:54 am Post subject: |
|
|
I've tested memory with memtest86, no errors, so that's probably not the case :/
What else can be wrong? |
|
Back to top |
|
|
djinnZ Advocate
Joined: 02 Nov 2006 Posts: 4831 Location: somewhere in L.O.S.
|
Posted: Tue Dec 18, 2007 5:10 pm Post subject: |
|
|
Some errors in disk acces (much for swap access) seems to be equal to a memory error.
As discussed in another thread some hardware errors can be due for a damaged/old/under measure power unit or because there is an elettrical incompatibility between battery backup and power unit. The old ata power connectors (as normal used for cd-rom, pata discs etc.) need to be revised every 2 or 3 years for oxidation or deformation of the internal connector, otherwise can be a problem in the data cable.
note: memtest must run ripetitive (10 try can be good) to be sure to nor have memory iussues. _________________ scita et risus abundant in ore stultorum sed etiam semper severi insani sunt
mala tempora currunt...mater stultorum semper pregna est
Murpy'sLaw:If anything can go wrong, it will - O'Toole's Corollary:Murphy was an optimist |
|
Back to top |
|
|
ToeiRei Veteran
Joined: 03 Jan 2005 Posts: 1191 Location: Austria
|
Posted: Tue Dec 18, 2007 6:17 pm Post subject: |
|
|
you should post some info about the kernel panic so we might see what happened...
Rei _________________ Please stand by - The mailer daemon is busy burning your messages in hell... |
|
Back to top |
|
|
johny007 n00b
Joined: 13 Aug 2006 Posts: 26
|
Posted: Tue Dec 18, 2007 7:37 pm Post subject: |
|
|
Yeah, but what can I do now when those 2 kernel panics where about 3 weeks ago,
now I don't remember anything what the messages said, or is there still something in logs? |
|
Back to top |
|
|
ToeiRei Veteran
Joined: 03 Jan 2005 Posts: 1191 Location: Austria
|
Posted: Tue Dec 18, 2007 10:05 pm Post subject: |
|
|
Kernel panics usually look that way on a 2.6:
Code: | Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
d083a064
Oops: 0002 [#1]
SMP
CPU: 0
EIP: 0060:[<d083a064>] Not tainted
EFLAGS: 00010246 (2.6.6)
EIP is at faulty_write+0x4/0x10 [faulty]
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
esi: cf8b2460 edi: cf8b2480 ebp: 00000005 esp: c31c5f74
ds: 007b es: 007b ss: 0068
Process bash (pid: 2086, threadinfo=c31c4000 task=cfa0a6c0)
Stack: c0150558 cf8b2460 080e9408 00000005 cf8b2480 00000000 cf8b2460 cf8b2460
fffffff7 080e9408 c31c4000 c0150682 cf8b2460 080e9408 00000005 cf8b2480
00000000 00000001 00000005 c0103f8f 00000001 080e9408 00000005 00000005
Call Trace:
[<c0150558>] vfs_write+0xb8/0x130
[<c0150682>] sys_write+0x42/0x70
[<c0103f8f>] syscall_call+0x7/0xb
Code: 89 15 00 00 00 00 c3 90 8d 74 26 00 83 ec 0c b8 00 a6 83 d0 |
and those would be damn helpful on debugging...
Rei _________________ Please stand by - The mailer daemon is busy burning your messages in hell... |
|
Back to top |
|
|
|