Re: 2.6.12.2 dies after 24 hours

["Rob Mueller" <robm@fastmail.fm>]

> > We recently tried upgrading one of the machines to the latest kernel
> > (2.6.12.2) and it's died after about 24 hours. It seemed to end up in 
> > some
> > weird state where we could ssh into it, and some commands worked (eg 
> > uptime)
> > but process list related commands (ps) would just freeze up into an
> > unkillable state and we'd have to close the seesion and ssh in again.
>
> I experienced the exact same thing on a IBM 335 - in my case I had
> messed up with the ACPI setup. Could you paste the output from
> /proc/interupts also is your kernel running with IRQ balancing ?.

Here's the /proc/interrupts dump:

          CPU0       CPU1       CPU2       CPU3
 0:   11524000          0          0          0    IO-APIC-edge  timer
 1:          8          0          0          0    IO-APIC-edge  i8042
 5:          0          0          0          0   IO-APIC-level  acpi
14:         13          0          0          0    IO-APIC-edge  ide0
16:          2          0          0          0   IO-APIC-level  ibmasm0
20:    2978604          0    2338027          0   IO-APIC-level  eth0
22:    1321957          0          0          0   IO-APIC-level  ips
24:     581291          0          0          0   IO-APIC-level  pci-umem
29:     257154          0          0          0   IO-APIC-level  eth1
NMI:          0          0          0          0
LOC:   11524185   11524201   11524194   11524121
ERR:          0
MIS:          0

I'm not sure about IRQ balancing sorry. How do I tell? The entire boot 
process output is here:

http://robm.fastmail.fm/kernel/t7/bootdmesg.txt

And the config is here:

http://robm.fastmail.fm/kernel/t7/config.txt

Does that help?

Our boot doesn't pass any special parameters, just choosing the deadline 
elevator...

image=/boot/bzImage-2.6.12.2
 label=linux-2.6.12.2
 append="elevator=deadline"
 read-only
 root=/dev/sda2

Thanks for your help!

Rob

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/