Subject: Re: Total system freeze (i386)
To: Chavdar Ivanov <ci4ic4@gmail.com>
From: =?ISO-8859-2?Q?Przemys=B3aw_Pawe=B3czyk?= <pp@kv.net.pl>
List: netbsd-users
Date: 06/21/2007 10:16:56
--Signature=_Thu__21_Jun_2007_10_16_56_-0500_cvsd7gJ7=i9JbJ9Y
Content-Type: text/plain; charset=ISO-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

On Mon, 11 Jun 2007 12:21:54 +0100
"Chavdar Ivanov" <ci4ic4@gmail.com> wrote:

> On 11/06/07, Przemys_aw Pawe_czyk <pp@kv.net.pl> wrote:
> >
> > On Tue, 12 Jun 2007 11:28:37 +0200
> > Gilles Gravier <Gilles@Gravier.org> wrote:
> >
> > > Have you looked at the status LEDs on your hard drive?
Hi folks,

I'm back with my problem after several days of testing. I'll recap your
suggestions and my observations.

1) No LED on or blinking.

> > > Could it be that your system's stuck on an IO? Does it stay
> > > completely on?

2) Like dead man.

> I've had this before. My guess is that you are in ddb right now. You
> say that the only option at this moment is to do a RESET.

3) Not true. See the point below (4).

> Have you tried to type blindly
>      reboot 0x104
> and see if you will get a dump on restart (you probably have to wait
> some time before anything happens on screen)?

4) After typing the command the system's dead for a 1-2 s then desktop
rewinds to the left (3 cm of screen picture goes left and reappears on
the right) and then system switches off right away to BIOS level.

*No* dump file is being created.

> > Does it turn off and stay off?
> > System is blocked.

No Ctrl+Alt+Esc (ddb),
No Ctrl+Alt+Backspace (X off),
No Ctrl+Alt+Del (?),
No Ctrl+AltFx (console switching)
No mouse
*Only* plug-out :) or reboot 0x104 (point 4).

> > > How long have you waited when it freezes?
5) 30 min

6) I've put network card in place of audio card and vice versa.
No effect.

7) Dead Man's Syndrome appears during mplayer playings (songs or
internet radio) *AND* (lot of compression/decompression activities *OR*
a lot of web browser openings/closings of html pages).

I can live with it but simultaneously it can be a signal that
something's wrong with the stable/production system of NetBSD.

Of course the culprit can be found everywhere. We can
accuse the mentioned applications or/and to make my old hardware face a
firing squad as well. But for me the true point is how to pinpoint the
vermin?

Regards,
pp

--
Przemysław Pawełczyk (p2o2) - pp_o2@o2.pl
P2O2 - http://pp.kv.net.pl, P2O2 Forum - http://www.p2o2.fora.pl/

--Signature=_Thu__21_Jun_2007_10_16_56_-0500_cvsd7gJ7=i9JbJ9Y
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFGepZoD9+eS/1tsfYRAgIyAJ96Y42PDjiHzB74oFxkPhDA+v2BTQCffQjj
LFILt6mioPjA7BVPUyEUzR0=
=JyTB
-----END PGP SIGNATURE-----

--Signature=_Thu__21_Jun_2007_10_16_56_-0500_cvsd7gJ7=i9JbJ9Y--