Benjamin Herrenschmidt [off-list ref] writes:
So basically, the kernel tends to die in various locations where things
should be just fine, but I did notice one thing: In most of these cases,
I had softirq around in the backtrace (either running in softirqs, or
having do_softirq() in the backtrace). There is one case where I didn't
have it: it dies inside power_save(), so probably because an interrupt
that happened just before messed things up.
I'm wondering if we might be running into some stack overflow...
Any clue ?
Ben.
Hi,
I haven't observed any problem with recent kernels from your tree with
power supply. When running on battery kernel crashes soon (usually by
15 minutes). This is on my Pismo (March 2000) with 2.4.7-ben0. On the
second thought it might be related to USB as well as I'm not using
battery and USB mouse uncorrelated - IIRC one crash occurred inside
hc_interrupt. I'll rsync and see what's the current status.
cheers,
Jiri
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi,
I haven't observed any problem with recent kernels from your tree with
power supply. When running on battery kernel crashes soon (usually by
15 minutes). This is on my Pismo (March 2000) with 2.4.7-ben0. On the
second thought it might be related to USB as well as I'm not using
battery and USB mouse uncorrelated - IIRC one crash occurred inside
hc_interrupt. I'll rsync and see what's the current status.
Make sure you have the latest yaboot (1.2.3), and add an initrd=<path>
line to your yaboot.conf in order to load the kernel's System.map along
with the kernel image. Also, enable xmon in your kernel. This will give
you some symbols lookup in xmon backtrace which is cool :)
If that crash ever happens again, send me the backtrace (or just copy me
PC, LR and the backtrace values and send along System.map)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Make sure you have the latest yaboot (1.2.3), and add an initrd=<path>
line to your yaboot.conf in order to load the kernel's System.map along
with the kernel image. Also, enable xmon in your kernel. This will give
you some symbols lookup in xmon backtrace which is cool :)
Hrm... I should sleep sometimes... read "sysmap=" and not "initrd=" !
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/