linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ryan C. Bonham" <Ryan@srfarms.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: RE: Via chipset
Date: Wed, 15 Aug 2001 12:46:19 -0400	[thread overview]
Message-ID: <19AB8F9FA07FB0409732402B4817D75A038A6A@FILESERVER.SRF.srfarms.com> (raw)

Alan,

Is anyone keeping a list of which boards with VIA chipsets are having
problems, and which aren't.. Or is the problem more random then that, like
some Abit board work and some don't??  If there is a list, would someone
send it to me.. I am interested in trying to help debug this problem, and I
need to know what boards I should test this out on.. 

Thanks

Ryan

> -----Original Message-----
> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> Sent: Wednesday, August 15, 2001 12:10 PM
> To: bdbryant@mail.utexas.edu
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Via chipset
> 
> 
> > Alan Cox wrote:
> > > We know it happens on some boards that apparently cant 
> keep up. We dont know
> > > why, there is no time estimate for a cure. That 
> unfortunately is about it
> > 
> > FWIW (qualitative data point), my EPoX system with the VIA 
> chipset seems to run a
> > few *hours* without an oops when I boot a PIII kernel and 
> run it with X, but a few
> > *days* on the same kernel when I don't start X.
> > 
> > Sometimes it barfs early even without X, but there seems to 
> be a significant
> > difference in the expected uptime between using X and not using X.
> 
> If you are running XFree servers then provide info on the 
> card, the machine
> configuration and XFree version, whether you use DRI or not. 
> Also send the
> same info to XFree86 themselves. It's entirely possible the Xserver is
> the trigger some of the bugs, and getting the info to both 
> parties will
> really help
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

             reply	other threads:[~2001-08-15 16:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15 16:46 Ryan C. Bonham [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-17 11:45 VIA chipset grouch
     [not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` 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.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
2001-10-15 11:09 grouch
2001-10-05 10:20 amit yajurvedi
2001-09-12 18:49 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
     [not found] <no.id>
2001-08-15 16:09 ` Via chipset Alan Cox
2001-08-16 16:02 ` Alan Cox
2001-08-07 23:10 Ø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
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

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=19AB8F9FA07FB0409732402B4817D75A038A6A@FILESERVER.SRF.srfarms.com \
    --to=ryan@srfarms.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).