This is real hardware, it is a always on desktop MB machine, nothing too weird,
right now I am putting 2.6.24.4 on it, and we will see in a few weeks if it does
it again.
I am getting it fairly consistently, so any ideas of what to turn on, or watch
for in the next event would be useful. I did try collect several samples of
information from /proc of things that looked useful, the most telling thing I
found was that it appeared that in /proc/timer_list
now at 7300171087468 nsecs (number was different).
was actually looping similar to the time/date and not rising as it should have
been, this is a 32 bit on an AMD Sempron(tm) Processor 3400+, it is 64bit
capable. I did have files that containing several samples of /proc/timer_list,
but apparently the alt-sysrq-s then u before the b failed to save the
information or the general state of the machine was just so bad that it did not
get written out to disk, the last 2 times I have had this happen, it completely
failed to shutdown gracefully and s-u-b at least enabled me to force a reboot
without having to go to the machine and power cycle it.
From previous data, the shortest time is 14 days 11 hours, and the longest is
about 23 days.
Roger
--
