2.6.23-rc4, now on third reboot

2.6.23-rc4, now on third reboot

[Gene Heskett]

Greetings;

About 8 hours uptime, firefox/kmail & a bunch of tails running on logs, an 
amanda session running in the background, reading groklaw with FF.  click, 
blank screen, reboot, nothing in the logs.

10 minutes later, everything locks up about 2 minutes after I start an amflush 
session to cleanup after the last crash.  The log, according to the tail I 
had running on it at the time of the freeze, has this, and it just crashed & 
self rebooted again, so I'm back on -rc3:
==========
Aug 29 01:06:52 coyote kernel: hdd: dma_timer_expiry: dma status == 0x61
==========

The 2nd time I go into bios and reset some things to default.

The third time I rebooted to 2.6.23-rc3, which had been running stable for 15 
days worth of uptime.

On the 2nd crash, the kpanel clock was frozen, no response from any key 
combo.

Third time, just a click and a black screen as it posted again.

Has anyone else encountered this or do I have hardware on the way out?

Now, lets see if I can cleanup the spillage from amanda.  And it reset again.

This time I turned the VCore 1 voltage down about .05 volts in the bios, to 
around 1.62 volts.  Just for effects, like a little rum in the morning 
coffee.  Its an athlon XP-2800 that has always run a little warm, showing 
145F now, but has hit 161F a couple times with no ill effects that I know of.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
<kira> Ada, the only language written to milspec.
<Mikster> <shudder>

Re: 2.6.23-rc4, now on third reboot

[Michal Piotrowski]

Hi Gene,

On 29/08/2007, Gene Heskett <gene.heskett@gmail.com> wrote:
> Greetings;
>
> About 8 hours uptime, firefox/kmail & a bunch of tails running on logs, an
> amanda session running in the background, reading groklaw with FF.  click,
> blank screen, reboot, nothing in the logs.
>
> 10 minutes later, everything locks up about 2 minutes after I start an amflush
> session to cleanup after the last crash.  The log, according to the tail I
> had running on it at the time of the freeze, has this, and it just crashed &
> self rebooted again, so I'm back on -rc3:
> ==========
> Aug 29 01:06:52 coyote kernel: hdd: dma_timer_expiry: dma status == 0x61
> ==========
>
> The 2nd time I go into bios and reset some things to default.
>
> The third time I rebooted to 2.6.23-rc3, which had been running stable for 15
> days worth of uptime.
>
> On the 2nd crash, the kpanel clock was frozen, no response from any key
> combo.
>
> Third time, just a click and a black screen as it posted again.
>
> Has anyone else encountered this or do I have hardware on the way out?
>
> Now, lets see if I can cleanup the spillage from amanda.  And it reset again.
>
> This time I turned the VCore 1 voltage down about .05 volts in the bios, to
> around 1.62 volts.  Just for effects, like a little rum in the morning
> coffee.  Its an athlon XP-2800 that has always run a little warm, showing
> 145F now, but has hit 161F a couple times with no ill effects that I know of.

Please try to capture this bug. Net or serial console would be useful.

Chapter 3 "Collecting kernel messages"
http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf

Regards,
Michal

-- 
LOG
http://www.stardust.webpages.pl/log/