Same thing hasppend to me below are the specs
96 MEG RAM
Dual P133
Adaptec 2940UW
2x 4 GIG Barracudas
Dual Ethernet cards
no soundcard
Matrox Mystique 4 meg
Kernel: 2.2.1
I came home one day to find the system complete locked at a black screen.
It's
port on the hub was inactive, couldn't ping, etc, It was completely dead. I
haven't had it since. So I'm not sure if it was just a freak accident or
what
have you.
______________________________ Reply Separator
_________________________________
Subject: Re: [SuSE Linux] Total Crash! 2.2.1 unstable maybe?
Author: "Rachel Greenham" [SMTP:[EMAIL PROTECTED]] at BCEEXCH
Date: 2/19/99 1:00 PM
[EMAIL PROTECTED] wrote:
>
> On 17-Feb-99 Rachel Greenham wrote:
> >
> > One of the major nice things about Linux, of course, is that this isn't
> > supposed to happen. So I thought the fact that it has was worth
> > reporting.
> >
> > My machine just crashed on me. Total stiff. Pointer froze, A window
> > froze unfinished (xmcd), no keyboard activity (including alt-ctrl-Fkey
> > to another console), no network activity, no response to ping.
> >
> > I didn't think I was provoking it very hard. But I thought it might be
> > worth mentioning as a possible instability between SuSE 6.0 and kernel
> > 2.2.1. Other possibilities include a successful attack, or failing
> > hardware.
> >
> > If anyone wants any details information to help figure out why this
> > happened, I'll be glad to co-operate.
> >
> > Brief snapshot though:
> >
> > SuSE 6.0 kernel 2.2.1
> > Simple vanilla PC hardware: AT SOYO motherboard, AMD K6-2 300MHz, 64Mb
> > RAM, 8Gb EIDE,
> > Matrox Productiva G100 graphics.
> > No sound card.
> >
> > At the time I was in a KDE 1.0 desktop with nedit, Netscape, xmcd, and a
> > couple of kvts running. One of them was doing a big wget in the
> > background. Behind the scenes I was running - well, the usual stuff,
> > including postgres (not actually doing much), Apache, JRunPro, Samba,
> > but only as a client...
> >
> > --
> > Rachel Greenham
> > Epinet Communications plc
> > -
>
> My first guess for any such instability would be Netscape. Depends of
course
> on what you were using it for. I've personally locked up KDE by
back-stepping
> pages while Netscape was loading in a Macromedia Shockwave file.
Fortunately
I
> could kill the process, but I still had to back KDE out by doing a
system-wide
> init 2.
Netscape is unstable. It does crash every now and then, but I've never
seen it take the system down with it. Nothing a killall netscape can't
get me out of.
No, this time it was *completely* unresponsive to any IO.
--
Rachel Greenham
Epinet Communications plc
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
