linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Toscano <pete.lkml@toscano.org>
To: Francois Romieu <romieu@cogenit.fr>
Cc: PinkFreud <pf-kernel@mirkwood.net>, linux-kernel@vger.kernel.org
Subject: Re: Are we going too fast?
Date: Tue, 14 Aug 2001 00:21:31 -0400	[thread overview]
Message-ID: <20010814002131.A26321@bubba.toscano.org> (raw)
In-Reply-To: <Pine.LNX.4.20.0108130303120.1037-100000@eriador.mirkwood.net> <20010813105554.A8387@se1.cogenit.fr>
In-Reply-To: <20010813105554.A8387@se1.cogenit.fr>

I'm running a SMP (2xPIII 600) on a Tyan Tiger mobo (Via Apollo Pro 133a
chipset) with a G400 and it runs fine, when I do the following:

	- disable APIC ("noapic" as a boot parameter).  Then again, the
	  system won't boot without APIC disabled.
	- use the ALSA drivers for my SoundBlaster Live.  (I haven't
	  tried the kernel-based drivers for a few version now, so this
	  situation might have changes, but up until I switched to ALSA,
	  I had crashes all the time during medium to high I/O.
	- use the uhci USB driver when I'm using a USB printer.  If I
	  use the usb-uhci driver with my USB printer, the whole system
	  locks.  This has been reported a few times on LKML,
	  linux-usb-users, and linux-usb-developers and nobody helped,
	  but a few people wrote back with "me too"s.  It was broken in
	  the trasnition from 2.4.3 to 2.4.4 and only seems to affect
	  SMP systems.  I just gave up on USB printing and went back to
	  my parallel port.

Finally, I'm using RedHat 7.1.  This system has no stability problems
now (after a long series of all kinds of stability problems).  Maybe
it's a load thing, I don't know, but it now runs stable.  

pete

On Mon, 13 Aug 2001, Francois Romieu wrote:

> I'm not convinced that gaining stability on a VIA + G400 + X + smp 
> combo is an easy task anyway.

  reply	other threads:[~2001-08-14  4:21 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  7:43 Are we going too fast? PinkFreud
2001-08-13  8:52 ` Brian
2001-08-13  8:55 ` Francois Romieu
2001-08-14  4:21   ` Pete Toscano [this message]
2001-08-14 12:48     ` Alan Cox
2001-08-14 13:03       ` usb-uhci + SMP -> bad Andre Pang
2001-08-14 16:01         ` Russell Cattelan
2001-08-14 22:30       ` Are we going too fast? Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29   ` Justin Guyett
2001-08-13 12:56     ` Andrzej Krzysztofowicz
2001-08-13 16:54     ` Gérard Roudier
2001-08-13 10:09 ` Chris Wilson
2001-08-13 11:09   ` szonyi calin
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51   ` Anders Larsen
2001-08-14 20:29     ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov
2001-08-13 17:16 ` Stephen Satchell
2001-08-13 21:01 ` A warning (was: Re: Are we going too fast?) Nico Schottelius
2001-08-13 17:53 Are we going too fast? PinkFreud
2001-08-13 20:27 ` Gérard Roudier
2001-08-13 18:46 Per Jessen
2001-08-14 13:58 ` Andrew Scott
2001-08-14 19:54 ` David Ford
2001-08-13 18:53 Petr Vandrovec
     [not found] <fa.l9dq0tv.7gqnhh@ifi.uio.no>
     [not found] ` <fa.g70as7v.1722ipv@ifi.uio.no>
2001-08-13 19:14   ` John Weber
     [not found] <no.id>
2001-08-13 20:24 ` Alan Cox
2001-08-13 21:06   ` Anthony Barbachan
2001-08-14 20:47 ` Alan Cox
2001-08-15  0:07   ` PinkFreud
2001-08-13 21:07 PinkFreud
2001-08-13 21:20 ` Alan Cox
2001-08-13 21:41   ` Rog�rio Brito
2001-08-14  0:56   ` Ben Ford
2001-08-14  7:34   ` Peter Wächtler
2001-08-14  2:24 ` David Ford
2001-08-14  4:19   ` Nicholas Knight
2001-08-14 12:49     ` Alan Cox
2001-08-14 22:27       ` Paul G. Allen
2001-08-13 21:36 PinkFreud
2001-08-14  7:57 ` Helge Hafting
2001-08-13 21:44 PinkFreud
2001-08-14  0:04 ` PinkFreud
2001-08-14  7:24   ` Francois Romieu
2001-08-15 23:24   ` Dr. Kelsey Hudson
2001-08-14 16:25 PinkFreud
2001-08-14 16:32 PinkFreud
2001-08-14 19:47 Per Jessen
2001-08-14 20:07 Per Jessen
2001-08-14 20:20 Per Jessen
2001-08-15 20:13 Roy Murphy
2001-08-16 21:42 PinkFreud

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=20010814002131.A26321@bubba.toscano.org \
    --to=pete.lkml@toscano.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pf-kernel@mirkwood.net \
    --cc=romieu@cogenit.fr \
    /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).