The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Marco Berizzi" <pupilla@hotmail.com>
To: "VDA" <VDA@port.imtp.ilyichevsk.odessa.ua>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] again: Re: Athlon kernel crash (i686 works)
Date: Tue, 9 Oct 2001 13:04:39 +0200	[thread overview]
Message-ID: <LAW2-OE29ilTmbtQVi0000079ef@hotmail.com> (raw)
In-Reply-To: <LAW2-OE3760Ov0Hvk1w000079df@hotmail.com> <140103605516.20011009134517@port.imtp.ilyichevsk.odessa.ua>

ohhh thanks for the real time response. It's the first time I'm posting
to this mailing list.
Could I try to patch also 2.4.10 kernel? This patch will be included in
kernel 2.4.11?

----- Original Message -----
From: "VDA" <VDA@port.imtp.ilyichevsk.odessa.ua>
To: "Marco Berizzi" <pupilla@hotmail.com>;
<linux-kernel@vger.kernel.org>
Sent: Tuesday, October 09, 2001 1:45 PM
Subject: [PATCH] again: Re: Athlon kernel crash (i686 works)


> Oh no.
>
> Anybody still insist that 'Athlon bug' patch is not to be
> included into mainstream kernel?
> If someone doesn't like it, feel free to make it a config
> option (enabled by default!) and submit an updated patch.
> My original patch against 2.4.9 is at the end.
>
> Tuesday, October 09, 2001, 11:32:24 AM,
> "Marco Berizzi" <pupilla@hotmail.com> wrote:
> MB> I updated my motherboard from ASUS A7V to ABIT KT7A (VIA Apollo
KT133A
> MB> chipset). The kernel I had (2.4.10) started crashing on boot
usually
> MB> right after starting init. I tryed a i686 kernel and noticed it
works
> MB> OK, so I recompiled my crashy kernel only switching the processor
type
> MB> and it also worked. Changed it back to Athlon/K7/Duron and it
starts
> MB> crashing.
>
> MB> I also search the mailing list. My mother board is KT7A series
v1.3 with
> MB> bios revision 4T (I also try with 3N, same results). K7 at
1333MHz. BIOS
> MB> settings are default (except I have disabled all BIOS/video
shadow).
> MB> After flash I also reset CMOS via hardware jumper.
>
> MB> Is there any solution to this (except compiling kernel for 6x86)?
> --
> Best regards, VDA
> mailto:VDA@port.imtp.ilyichevsk.odessa.ua
>
> --- pci-pc.c.orig       Sun Aug 12 15:54:07 2001
> +++ pci-pc.c    Tue Sep 18 16:45:21 2001
> @@ -948,6 +948,26 @@
>         d->irq = 9;
>  }
>
> +/* Fixes some oopses on Athlon optimized
> + * fast_copy_page when it uses 'movntq's
> + * instead of 'movq's on Athlon/Duron optimized kernels.
> + * Bit 7 at offset 0x55 seems to be responsible:
> + * > Device 0 Offset 55 - Debug (RW)
> + * >   Bits 7-0: Reserved (do not program). default = 0
> + * ABIT KT7A 3R BIOS: 0x89 (oopses)
> + * ABIT KT7A YH BIOS: 0x00 (works)
> + */
> +static void __init pci_fixup_athlon_bug(struct pci_dev *d)
> +{
> +       u8 v;
> +        pci_read_config_byte(d, 0x55, &v);
> +        if(v & 0x80) {
> +                printk(KERN_NOTICE "Stomping on Athlon bug.\n");
> +                v &= 0x7f; /* clear bit 55.7 */
> +                pci_write_config_byte(d, 0x55, v);
> +        }
> +}
> +
>  struct pci_fixup pcibios_fixups[] = {
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_INTEL_82451NX,    pci_fixup_i450nx },
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_INTEL,
> PCI_DEVICE_ID_INTEL_82454GX,    pci_fixup_i450gx },
> @@ -961,6 +981,7 @@
>  /* Our bus code shouldnt need this fixup any more. Delete once
> verified */
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_COMPAQ,
> PCI_DEVICE_ID_COMPAQ_6010,      pci_fixup_compaq },
>  #endif
> +       { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_VIA,
> PCI_DEVICE_ID_VIA_8363_0,       pci_fixup_athlon_bug },
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_UMC,
> PCI_DEVICE_ID_UMC_UM8886BF,     pci_fixup_umc_ide },
>         { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SI,
> PCI_DEVICE_ID_SI_5513,          pci_fixup_ide_trash },
>         { PCI_FIXUP_HEADER,     PCI_ANY_ID,             PCI_ANY_ID,
> pci_fixup_ide_bases },
>
>
>

  reply	other threads:[~2001-10-09 11:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09  9:32 Athlon kernel crash (i686 works) Marco Berizzi
2001-10-09 11:45 ` [PATCH] again: " VDA
2001-10-09 11:04   ` Marco Berizzi [this message]
2001-10-09 11:55     ` Gergely Tamas
2001-10-09 13:59       ` Alejandro Conty
2001-10-09 14:19         ` Brian Gerst
     [not found]         ` <Pine.LNX.4.33.0110091611050.20120-100000@falka.mfa.kfki.hu>
2001-10-09 14:52           ` Alejandro Conty
2001-10-09 14:52             ` Gergely Tamas
2001-10-09 21:12               ` Dan Hollis
2001-10-09 22:22       ` Luigi Genoni
2001-10-09 14:27   ` Fabio Coatti
2001-10-09 21:11   ` Dan Hollis
2001-10-09 22:19   ` Luigi Genoni
2001-10-09 17:37 ` Roberto Jung Drebes
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09 13:00 [PATCH] again: " Bryan Mayland
2001-10-09 14:28 ` Bill Davidsen
     [not found] <fa.efssf0v.146031s@ifi.uio.no>
2001-10-10  4:06 ` Dan Maas
2001-10-10  8:09   ` VDA

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=LAW2-OE29ilTmbtQVi0000079ef@hotmail.com \
    --to=pupilla@hotmail.com \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --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