Re: APIC/LAPIC hanging problems on nForce2 system.

From: Prakash K. Cheemplavam (prakashkc_at_gmx.de)
Date: 01/05/05

  • Next message: Martin Drab: "Re: APIC/LAPIC hanging problems on nForce2 system." 
    Date:	Wed, 05 Jan 2005 18:26:43 +0100
To: Martin Drab <drab@kepler.fjfi.cvut.cz>

    Martin Drab schrieb:
    >
    > On Wed, 5 Jan 2005, Prakash K. Cheemplavam wrote:
    >
    >
    >>Martin Drab schrieb:
    >>Just to avoid confusion: If your bios does *not contain the fix, the
    >>kernel should fix it and above line should appear. (It does here with
    >>2.6.10) So if it doesn't in your case (and your bios does not contain
    >>that fix), the detection code probably isn't enough. -> This should be
    >>fixed in kernel.
    >>
    >>When you use a fixed bios though, above line should not appear, and your
    >>system should be stable.
    >
    >
    > Is there some other way to get to know whether BIOS contains the fix
    > allready?

    lspci -xxx

    then check

    0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different
    version?) (rev c1)
    00: de 10 e0 01 06 00 b0 00 c1 00 00 06 00 00 80 00
    10: 08 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 00
    20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 00 1c
    30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00
    40: 02 60 30 00 1b 42 00 1f 02 03 00 00 ff ff ff ff
    50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    60: 08 00 01 20 20 00 88 80 10 00 00 00 01 ff 01 9f <----
    70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    80: 00 01 00 00 ff ff ff 3f 01 00 00 00 01 80 00 00
    90: 14 80 40 a7 14 80 40 a5 00 30 00 00 00 00 00 00
    a0: 40 00 00 00 32 fb 10 00 01 00 00 00 00 00 00 00
    b0: cc ff 07 00 00 00 00 00 00 00 00 00 00 00 00 00
    c0: 33 33 03 00 00 00 00 00 00 00 00 00 00 00 00 00
    d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    e0: d6 01 47 00 16 30 00 10 00 00 00 00 00 00 00 00
    f0: 0f 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00

     From fixup.c:
              * Chip Old value New value
              * C17 0x1F0FFF01 0x1F01FF01
              * C18D 0x9F0FFF01 0x9F01FF01

    If there is old value, it needs to be fixed.

    Prakash

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Martin Drab: "Re: APIC/LAPIC hanging problems on nForce2 system."

    Relevant Pages

    • Re: const versus __attribute__((const))
      ... nice warnign that tells you so, and it will be trivial to fix. ... it wasn't a problem - and the kernel ... tends to be the single most active user of inline asm's of all ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: can device drivers return non-ram via vm_ops->nopage?
      ... Ok, so, how the fsck do we fix the sound drivers? ... providing an architecture dma_coherent_to_pageinterface isn't ... OSS from the kernel because they are abusing existing kernel ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [ACPI] p2b-ds blacklisted?
      ... The kernel started and there were some issues with the interrupt ... I haven't tried to install BIOS 1014beta3 yet. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: can device drivers return non-ram via vm_ops->nopage?
      ... > Well, I've been told to effectively screw my idea by David Woodhouse, ... > also fix the problem. ... > OSS from the kernel because they are abusing existing kernel ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 00/14] ppc32: Remove board ports that are no longer maintained
      ... If the driver had been ... > around to fix it at all and was probably forced to use another OS ... > was updated along the changes to the API in the 2.6 kernel, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)