All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Walter <srwalter@yahoo.com>
To: Danijel Schiavuzzi <dschiavu@public.srce.hr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Screen corruption in 2.4.18
Date: Fri, 22 Mar 2002 17:23:04 -0600	[thread overview]
Message-ID: <20020322232304.GA19579@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <200203192112.WAA09721@jagor.srce.hr> <200203211209.NAA11121@jagor.srce.hr> <20020321172234.GA21274@hapablap.dyn.dhs.org> <200203222204.XAA01121@jagor.srce.hr>

On Fri, Mar 22, 2002 at 08:49:02PM +0100, Danijel Schiavuzzi wrote:
> In 2.4.18, unmodified (with 0x1f value), it shows:
> 	Disabling VIA memory write queue: [55] 38->18
> 
> In 2.4.18, modified (changed 0x1f to 0x7f), it shows:
> 	 Disabling VIA memory write queue: [55] 38->38
> 
> The modified kernel runs *fine*.

Aha.  Excellent.

> lspci tells:
> 
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 81)
                                              ^^^^^^
I think you actually do have an 8363, and so some sort of fix is
probably needed.

> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 
> 40)
> /cut/
> 
> But in fact mine is a *VT8365* (KM133) Northbridge.
> 
> from pci-pc.c:
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_VIA,      
> PCI_DEVICE_ID_VIA_8363_0,       pci_fixup_via_northbridge_bug },
> 		^^^^^^^^
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_VIA,      
> PCI_DEVICE_ID_VIA_8622,         pci_fixup_via_northbridge_bug },
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_VIA,      
> PCI_DEVICE_ID_VIA_8361,         pci_fixup_via_northbridge_bug },
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_VIA,      
> PCI_DEVICE_ID_VIA_8367_0,       pci_fixup_via_northbridge_bug },
>         { 0 }
> 
> Maybe because of this, the kernel thinks mine is a 8363, and applies the fix, 
> but in fact it doesn't need to be applied, or does it? I'm confused %:I

I think your system does need the fix, but only bit 7 needs clearing.
Not all of it.  If memory serves me, clearing bit 7 was the
experimentally-determined fix for the bug, however, VIA said that all 3
bit needed clearing.  Perhaps this should be looked into, as I
experienced the same screen corruption bug on the same chipset.  I have
yet to try my own proposed fix on it, however :-/

I'll do this within the next week or so, and if it works for me, I'll
propose a patch to only clear bit 7, at least on these chips.  Sound
good to you?
-- 
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
			-- George Orwell
He's alive.  He's alive!  Oh, that fellow at RadioShack said I was mad!
Well, who's mad now?
			-- Montgomery C. Burns

  parent reply	other threads:[~2002-03-23  1:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19 21:12 Screen corruption in 2.4.18 Danijel Schiavuzzi
2002-03-20  0:03 ` Steven Walter
     [not found] ` <200203201506.QAA13795@jagor.srce.hr>
     [not found]   ` <20020320172516.GA14024@hapablap.dyn.dhs.org>
     [not found]     ` <200203211209.NAA11121@jagor.srce.hr>
2002-03-21 17:22       ` Steven Walter
     [not found]         ` <200203222204.XAA01121@jagor.srce.hr>
2002-03-22 23:23           ` Steven Walter [this message]
     [not found]             ` <200203231526.QAA09302@jagor.srce.hr>
2002-03-23 16:06               ` Steven Walter
     [not found]                 ` <200203231741.SAA00071@jagor.srce.hr>
2002-03-23 18:26                   ` VIA technical contact [was Screen corruption in 2.4.18] Steven Walter
2002-03-24  7:05                 ` Screen corruption in 2.4.18 Andre Pang
2002-03-24  7:16                   ` [PATCH] " Steven Walter
     [not found]                     ` <200203241231.g2OCV5X18426@Port.imtp.ilyichevsk.odessa.ua>
2002-03-24 15:59                       ` Steven Walter
2002-03-24 16:48                         ` Alan Cox
2002-03-24 18:03                           ` Steven Walter
2002-03-25  2:01                         ` Andre Pang
2002-03-24 15:07                   ` Danijel Schiavuzzi
2002-03-24 16:51                     ` Alan Cox
2002-03-24 17:13                       ` Danijel Schiavuzzi
2002-03-25  1:43                     ` Andre Pang
2002-03-25  2:40                       ` Steven Walter
2002-03-25  3:00                         ` Andre Pang
2002-03-25  8:50                       ` Marc Wilson
2002-03-25 17:07                         ` Daniel Gryniewicz
2002-03-25 21:02                         ` Steven Walter
2002-03-25 21:19                           ` Marc Wilson
2002-03-29  2:06                         ` Andre Pang
2002-03-29  3:16                           ` Marc Wilson
2002-03-25  1:55                     ` Andre Pang
2002-03-25 19:52                       ` Danijel Schiavuzzi
  -- strict thread matches above, loose matches on Subject: below --
2002-03-25 17:59 Petr Vandrovec
2002-03-28 22:46 Bill Hammock
2002-03-29  0:14 ` Danijel Schiavuzzi
2002-03-29  2:05   ` Andre Pang
2002-03-29 12:26 Petr Vandrovec
2002-04-02 21:43 Chris Rankin
2002-04-02 22:33 ` Richard B. Johnson
2002-04-02 22:40   ` Chris Rankin
2002-04-03 14:00     ` Richard B. Johnson
2002-04-03 20:34       ` Chris Rankin
2002-04-02 23:38 ` Erik Ljungström
2002-04-02 22:50 Petr Vandrovec
2002-04-02 22:09 ` Chris Rankin

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=20020322232304.GA19579@hapablap.dyn.dhs.org \
    --to=srwalter@yahoo.com \
    --cc=dschiavu@public.srce.hr \
    --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.