public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Bernat <bernat@free.fr>
To: Kurt Garloff <garloff@suse.de>
Cc: Steve Kieu <haiquy@yahoo.com>, kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround
Date: Fri, 19 Apr 2002 12:18:03 +0200	[thread overview]
Message-ID: <m3zo00yotg.fsf@neo.loria> (raw)
In-Reply-To: <20020415174059.E2345@nbkurt.etpnet.phys.tue.nl> <20020416064306.91089.qmail@web10407.mail.yahoo.com> <20020416095703.A12012@nbkurt.etpnet.phys.tue.nl>

OoO En cette matinée ensoleillée du mardi 16 avril 2002, vers 09:57,
Kurt Garloff <garloff@suse.de> disait:

>> > and claiming that not clearing bit 5 did make the
>> > problem go away.
>> > (IOW: Replace v &= 0x1f; /* clear bits 5, 6, 7 */
>> >            by v &= 0x3f; /* clear bits 6, 7 */
>> >  and see whether this helps.)

> It would be intersting to know. Maybe just clearing bits 6 and 7
> would make everybody happy? 

Another related hack is to modify latency of this northbridge to 0 and
to increase latency of "bandwidth eating" components. On
french-speaking newsgroup fr.comp.os.linux.moderated, we have several
reports that complete freeze of the system with TV cards can be
postponed (at least ; in my case, they disappeared) by this
tweak. Since, this is TV card related, I have already submitted this
to bttv maintainer (I haven't checked if latest revisions of bttv
include an option for this) but maybe decreasing to 0 the northbridge
latency could help some people too (with or without TV card).
-- 
BOFH excuse #5:
static from plastic slide rules

      reply	other threads:[~2002-04-19 10:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13  8:58 2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround Steve Kieu
2002-04-15 15:40 ` Kurt Garloff
2002-04-16  6:43   ` Steve Kieu
2002-04-16  7:57     ` Kurt Garloff
2002-04-19 10:18       ` Vincent Bernat [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=m3zo00yotg.fsf@neo.loria \
    --to=bernat@free.fr \
    --cc=garloff@suse.de \
    --cc=haiquy@yahoo.com \
    --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