public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John R Lenton <john@grulic.org.ar>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	arjanv@redhat.com, "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Axel Thimm" <Axel.Thimm@physik.fu-berlin.de>,
	"Manuel A. McLure" <mmt@unify.com>,
	"Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>,
	"ARND BERGMANN" <std7652@et.fh-osnabrueck.de>,
	"Dunlap, Randy" <randy.dunlap@intel.com>,
	"Martin Diehl" <mdiehlcs@compuserve.de>,
	"Adrian Cox" <adrian@humboldt.co.uk>,
	"Capricelli Thomas" <orzel@kde.org>,
	"Ian Bicking" <ianb@colorstudy.com>
Subject: Re: PATCH 2.4.5.1: Fix Via interrupt routing issues
Date: Mon, 14 May 2001 14:07:53 -0300	[thread overview]
Message-ID: <20010514140752.B19662@grulic.org.ar> (raw)
In-Reply-To: <3AFEC426.50B00B78@mandrakesoft.com>
In-Reply-To: <3AFEC426.50B00B78@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sun, May 13, 2001 at 01:28:06PM -0400

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

On Sun, May 13, 2001 at 01:28:06PM -0400, Jeff Garzik wrote:
> For those of you with Via interrupting routing issues (or
> interrupt-not-being-delivered issues, etc), please try out this patch
> and let me know if it fixes things.  It originates from a tip from
> Adrian Cox... thanks Adrian!

Just to add a little noise: My box (msi 694d pro AI motherboard,
revI, i.e. vt82c686a) been a *lot* stabler since I removed the
Live! and dropped back to the onboard soundcard.

The only time it has frozen has been when checking to see if this
also fixed the X-freezes-on-reentry thing (which I know was
silly, since CVS X has had that fixed for some time and the fix
is on the slow path to 4.1).

I used to get a freeze (that is a lock-up where I have to reset
the box, unable to even alt-sysrq my way out) between one and
five times per day, nearly always in X, nearly always with sound,
nearly always using up a lot of (memtested) memory.

'nearly always' means 'at least once not' -- scientific as hell.


If I could put in words the difference between the Live! and the
via, I would. Alas, I can't, so you're stuck with this inane
rant:

    please please please fix it.

-- 
John Lenton (john@grulic.org.ar) -- Random fortune:
Las palabras, cera; las obras acero.
        -- Luis de Argote y Góngora. (1561-1627) Poeta español. 

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      parent reply	other threads:[~2001-05-15  1:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-13 17:28 PATCH 2.4.5.1: Fix Via interrupt routing issues Jeff Garzik
2001-05-13 18:38 ` Alan Cox
2001-05-13 18:45   ` Jeff Garzik
2001-05-13 18:47     ` Alan Cox
2001-05-14 15:21 ` Axel Thimm
2001-05-14 16:16   ` Jeff Garzik
2001-05-14 19:05     ` Axel Thimm
2001-05-14 19:14       ` Axel Thimm
2001-05-14 17:07 ` John R Lenton [this message]

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=20010514140752.B19662@grulic.org.ar \
    --to=john@grulic.org.ar \
    --cc=Axel.Thimm@physik.fu-berlin.de \
    --cc=adrian@humboldt.co.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=ianb@colorstudy.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdiehlcs@compuserve.de \
    --cc=mmt@unify.com \
    --cc=moffe@amagerkollegiet.dk \
    --cc=orzel@kde.org \
    --cc=randy.dunlap@intel.com \
    --cc=std7652@et.fh-osnabrueck.de \
    /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