mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danijel Schiavuzzi <dschiavu@public.srce.hr>
To: linux-kernel@vger.kernel.org
Subject: Screen corruption in 2.4.18
Date: Tue, 19 Mar 2002 22:12:18 +0100	[thread overview]
Message-ID: <200203192112.WAA09721@jagor.srce.hr> (raw)

Hi.

Some two weeks ago I posted here a kernel bug report regarding
a screen corruption issue. You can find it here:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0203.0/1577.html

As I didn't know if it's my hardware that is the cause of corruption,
searched over the Internet and found that Thomas Brehm is also
having the same problem, and he has the same motherboard as me
(MSI MS-6340M, VIA KM133 chipset - VT8365 north + VIA686B south bridge).

Short problem description: 2.4.17 kernel works fine, but any kernel
higher than this makes the screen corrupted in any text or VESA fb
mode. In standard text mode, the screen gets filled with vertical
lines. In vesafb mode, random horizontal lines appear on the screen.

However, I made up the 2.4.18 kernel to boot up properly by 
replacing the file

	./linux/arch/i386/pci-pc.c

with that from the 2.4.17 kernel. The kernel runs fine now.

So, what seems to make the screen corruption?

						-- Danijel

P.S.  Here is a diff between the two pci-pc.c files:

------------------------- begin -------------------------

1112c1112,1113
<  * Nobody seems to know what this does. Damn.
---
>  * Addresses issues with problems in the memory write queue timer in
>  * certain VIA Northbridges.  This bugfix is per VIA's specifications.
1114,1118c1115,1118
<  * But it does seem to fix some unspecified problem
<  * with 'movntq' copies on Athlons.
<  *
<  * VIA 8363 chipset:
<  *  - bit 7 at offset 0x55: Debug (RW)
---
>  * VIA 8363,8622,8361 Northbridges:
>  *  - bits  5, 6, 7 at offset 0x55 need to be turned off
>  * VIA 8367 (KT266x) Northbridges:
>  *  - bits  5, 6, 7 at offset 0x95 need to be turned off
1120c1120
< static void __init pci_fixup_via_athlon_bug(struct pci_dev *d)
---
> static void __init pci_fixup_via_northbridge_bug(struct pci_dev *d)
1123,1127c1123,1134
< 	pci_read_config_byte(d, 0x55, &v);
< 	if (v & 0x80) {
< 		printk("Trying to stomp on Athlon bug...\n");
< 		v &= 0x7f; /* clear bit 55.7 */
< 		pci_write_config_byte(d, 0x55, v);
---
> 	int where = 0x55;
> 
> 	if (d->device == PCI_DEVICE_ID_VIA_8367_0) {
> 		where = 0x95; /* the memory write queue timer register is 
> 				 different for the kt266x's: 0x95 not 0x55 */
> 	}
> 
> 	pci_read_config_byte(d, where, &v);
> 	if (v & 0xe0) {
> 		printk("Disabling VIA memory write queue: [%02x] %02x->%02x\n", where, v, 
v & 0x1f);
> 		v &= 0x1f; /* clear bits 5, 6, 7 */
> 		pci_write_config_byte(d, where, v);
1140c1147,1150
< 	{ PCI_FIXUP_HEADER,	PCI_VENDOR_ID_VIA,	PCI_DEVICE_ID_VIA_8363_0,	
pci_fixup_via_athlon_bug },
---
> 	{ 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 },

------------------------------ end ------------------------------

             reply	other threads:[~2002-03-19 21:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19 21:12 Danijel Schiavuzzi [this message]
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
     [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
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=200203192112.WAA09721@jagor.srce.hr \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®