From: Bob Martin <bmartin@ayrix.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Via chipset
Date: Thu, 16 Aug 2001 10:35:41 -0500 [thread overview]
Message-ID: <3B7BE84D.117212FE@ayrix.net> (raw)
In-Reply-To: <E15X75K-0003vl-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Someone should be able to forward failure cases to some AMD contacts. A
> > day or so with a bus analyzer should pin things down, AMD certainly has
> > the hardware to check this.
>
> It doesnt happen with AMD chipsets. Although if anyone from AMD is
> interested I'd be happy to know
>
> Alan
I have a MSI-6195 slot-A , AMD chipset with a visiontek nvidia vanta 32mb agp
card, RH 7.1 installed. I have experienced complete system lockups with random
uptimes < 1 day to 4 days, no mouse, keyboard, VCs, can't even telnet in or
ping. I finally made the connection it was happening when I was away from the
box and not using it interactively, which lead me to xscreensaver and sure
enough after I disabled it, no more lockups, up 30 days now. But I haven't
figured what in xscreensaver is doing this, don't know if it might be kernel
related or not, probably not. I suspect xscreensaver is triggering something in
the xserver that is not normally getting hit in normal use.
--
Bob Martin
next prev parent reply other threads:[~2001-08-16 15:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 23:10 Via chipset Øystein Haare
2001-08-07 18:46 ` Bobby D. Bryant
2001-08-07 23:16 ` Dan Hollis
2001-08-07 23:36 ` Alan Cox
2001-08-07 23:47 ` Larry McVoy
2001-08-08 9:16 ` Janne Pänkälä
2001-08-08 16:09 ` Marco Colombo
2001-08-15 3:25 ` Maxwell Spangler
2001-08-15 11:48 ` Alan Cox
2001-08-15 12:28 ` Bobby D. Bryant
2001-08-15 19:59 ` Dan Hollis
2001-08-15 20:16 ` Alan Cox
2001-08-15 20:27 ` Dan Hollis
2001-08-15 20:32 ` Alan Cox
2001-08-15 21:50 ` Bryan O'Sullivan
2001-08-16 15:35 ` Bob Martin [this message]
2001-08-16 21:09 ` Dan Hollis
2001-08-17 3:04 ` Adrian V. Bono
2001-08-20 22:52 ` Bob Martin
2001-08-08 1:54 ` Ignacio Vazquez-Abrams
[not found] <no.id>
2001-08-15 16:09 ` Alan Cox
2001-08-16 16:02 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 16:46 Ryan C. Bonham
2001-09-12 18:49 VIA chipset Marco Colombo
2001-09-12 19:22 ` Alan Cox
2001-09-12 20:06 ` Jussi Laako
2001-09-12 20:13 ` Marco Colombo
2001-09-12 20:55 ` Anders Peter Fugmann
2001-09-14 17:29 ` Jussi Laako
2001-10-05 10:20 amit yajurvedi
2001-10-15 11:09 grouch
[not found] <Pine.LNX.4.10.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
[not found] <Pine.LNX.4.10.10110151554040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 20:31 ` grouch
[not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` grouch
2001-10-17 11:45 grouch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B7BE84D.117212FE@ayrix.net \
--to=bmartin@ayrix.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.