well, since i couldn't find any useful log i can take, and since i can't copy any log after the system get stuck, i searched in the kernel source the place it prints those messages and indeed find it in dumpstack.c, in kernel __die.
i removed the memory and registers prints, so when the error occurred again - i could see the first error prints on the screen (before kernel dies).
so now i have this output:
BUG: unable to handle kernel NULL pointer derefrence at 000000e0
IP: [<c03bdb4e>] 0xc03bdb4e
*pde = 00000000
Oops: 0002 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8.5/1-8.5:1.0/net/eth4/address
EIP: [<c03bdb4e>] SS:ESP 0068:c049be7c
CR2: 00000000000000e0
---[ end trace 0b55e72310c9d136 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Pid: 0, comm: swapper Tainted: G D 2.6.33.3-tinycore #2
Call Trace:
thats it.
in eth4 i had a usb-eth adapter (asix chip)
what's the "last sysfs file" means? does this mean that the problem is somewhere with the eth4 adapter?
if i couldn't fix it, i'd rather reboot the system when this bug happens. what can i add to the end of the "__die" (dumpstack.c) function in order to reboot safely?
thanks.