2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

Post by Steve Kie » Sun, 14 Apr 2002 18:10:05



Hi,

This is a known problem I know, the screen problem
with some athlon computer due to some PCI optimization
code  etc..; but how can I work around this. For
2.4.19-pre2 I remember to go somewhere to find pci.c
and comment out the code related, but in
2.4.19-pre6aa1 I got stuck..

Is there an official way to overcome/fix this problem
? (kernel build option?) Or just anyone interested in
doing such job?

Please help and copy your reply to my email address.

Thanks a lot

=====
Steve Kieu

http://messenger.yahoo.com.au - Yahoo! Messenger
- A great way to communicate long-distance for FREE!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

Post by Kurt Garlof » Wed, 17 Apr 2002 00:50:08


Hi,


> This is a known problem I know, the screen problem
> with some athlon computer due to some PCI optimization
> code  etc..; but how can I work around this. For
> 2.4.19-pre2 I remember to go somewhere to find pci.c
> and comment out the code related, but in
> 2.4.19-pre6aa1 I got stuck..

> Is there an official way to overcome/fix this problem
> ? (kernel build option?) Or just anyone interested in
> doing such job?

I don't know of an "official way".
There were a number of postings refering to
arch/i386/kernel/pci-pc.c: pci_fixup_via_northbridge_bug()
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.)

Regards,
--

GPG key: See mail header, key servers         Linux kernel development
SuSE Linux AG, Nuernberg, DE                            SCSI, Security

  application_pgp-signature_part
< 1K Download

 
 
 

2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

Post by Steve Kie » Wed, 17 Apr 2002 15:50:08


Quote:

> I don't know of an "official way".

I think this is a known problem but it is strange that
no one bother to implement something to make it easier
for the end user to compile their own kernel rather
than seraching the file and edit it . Of course I
believe my box is not the only one suffering such
problem.

Quote:> There were a number of postings refering to
> arch/i386/kernel/pci-pc.c:
> pci_fixup_via_northbridge_bug()

Just after posting my first email, I found the file,
yes it is in arch/i386/kernel/pci-pc.c and I just
comment out all lines in struct pci_fixup
pcibios_fixups[] related to VIA; that is
PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA  etc...

I have no idea if this affects the system, but it
seemed that the problem is solved and no thing wierd
happened yet :-). May be if I got some trouble I will
set the bit as you said.

Quote:> 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.)

> Regards,

Thanks for your reply

=====
Steve Kieu

http://messenger.yahoo.com.au - Yahoo! Messenger
- A great way to communicate long-distance for FREE!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

Post by Kurt Garlof » Wed, 17 Apr 2002 17:10:05


Hi Steven,


> I think this is a known problem but it is strange that
> no one bother to implement something to make it easier
> for the end user to compile their own kernel rather
> than seraching the file and edit it.

The reason for the code there was that people had problems without it.
Somebody found some docu from VIA and came up with the patch that is now
in the kernel. And it helped those people.

So, it's not that nobody bothers, it's just that we don't want to break
those people's computers.

Quote:> Of course I believe my box is not the only one suffering such
> problem.

No, there have been a few reports on LKML.

Quote:> > arch/i386/kernel/pci-pc.c:

> Just after posting my first email, I found the file,
> yes it is in arch/i386/kernel/pci-pc.c and I just
> comment out all lines in struct pci_fixup
> pcibios_fixups[] related to VIA; that is
> PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA  etc...

> I have no idea if this affects the system, but it
> seemed that the problem is solved and no thing wierd
> happened yet :-). May be if I got some trouble I will
> set the bit as you said.

You complain that no one bothers. The opposite is true:
Hacking solutions that work for some and not for others is just not
acceptable. But that's what you did now.
(Nothing wrong with it, if it helps you. But you don't help finding a
solution that works for everybody.)

Quote:> > 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?
But the docu seems to indicate otherwise and there have not yet been
enough reports to be sure.

Regards,
--

GPG key: See mail header, key servers         Linux kernel development
SuSE Linux AG, Nuernberg, DE                            SCSI, Security

  application_pgp-signature_part
< 1K Download
 
 
 

2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

Post by Vincent Berna » Sat, 20 Apr 2002 19:30:09


OoO En cette matine ensoleille du mardi 16 avril 2002, vers 09:57,

Quote:>> > 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

1. Kernel panic 2.4.19-pre6 AND 2.4.19-pre5-ac3 - More info - ksymoops

Code: 8b 40 20 c7 40 24 00 00 00 00 a1 a0 3e 2d c0 59 89 15 c4 cf
Using defaults from ksymoops -t elf32-i386 -a i386

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   8b 40 20                  mov    0x20(%eax),%eax
Code;  00000003 Before first symbol
   3:   c7 40 24 00 00 00 00      movl   $0x0,0x24(%eax)
Code;  0000000a Before first symbol
   a:   a1 a0 3e 2d c0            mov    0xc02d3ea0,%eax
Code;  0000000f Before first symbol
   f:   59                        pop    %ecx
Code;  00000010 Before first symbol
  10:   89 15 c4 cf 00 00         mov    %edx,0xcfc4

--
Shawn Starr
Developer Support Engineer
Datawire Communication Networks Inc.
10 Carlson Court, Suite 300
Toronto, ON, M9W 6L2
T: 416-213-2001 ext 179  F: 416-213-2008

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. 3.0 stability in a production firewall

3. 2.4.19-rc2 -> 2.4.19-rc3 : no more eth (fwd)

4. HP 4L info again please

5. 3Ware ok 2.4.19, dies 2.4.19-ac4

6. Linux Today: ZDNet: How Microsoft Jilted Developers [re MS DNA announcements]

7. Promise 20267 hangs with 2.4.19-pre3 and 2.4.19-pre3-ac3

8. PPTP on RH 7.2

9. kbuild25 version 3.0 for 2.4.19-pre9 and 2.4.19-pre9-ac3

10. Kernel 2.4.19-pre6aa1 problem report (VM related)

11. Kernel patching 2.4.19pre1 -> 2.4.19pre2

12. KERN_INFO 2.4.19-pre2 PCI related messages

13. Kernel 2.4.19-pre2