mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Martin Drab <drab@kepler.fjfi.cvut.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: APIC/LAPIC hanging problems on nForce2 system.
Date: Wed, 05 Jan 2005 18:26:43 +0100	[thread overview]
Message-ID: <41DC2353.7010206@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0501051821430.25946@kepler.fjfi.cvut.cz>

[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-05 17:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 15:28 Martin Drab
2005-01-05 16:05 ` Zwane Mwaikambo
2005-01-05 16:56   ` Martin Drab
2005-01-05 16:50 ` Prakash K. Cheemplavam
2005-01-05 17:06   ` Martin Drab
2005-01-05 17:17     ` Prakash K. Cheemplavam
2005-01-05 17:22       ` Martin Drab
2005-01-05 17:26         ` Prakash K. Cheemplavam [this message]
2005-01-05 17:30           ` Martin Drab
2005-01-06  0:14           ` Martin Drab
2005-01-06  9:03             ` Prakash K. Cheemplavam
2005-01-06 13:52               ` Bartlomiej Zolnierkiewicz
2005-01-06 15:04                 ` [PATCH] " Prakash K. Cheemplavam
2005-01-06 23:46                   ` Andrew Morton
2005-01-07  0:28                     ` Prakash K. Cheemplavam
2005-01-07  0:49                       ` Andrew Morton
2005-01-07 11:47                         ` Martin Drab
2005-01-07 13:53                         ` Prakash K. Cheemplavam
2005-01-07 15:34                           ` Bartlomiej Zolnierkiewicz
2005-01-06 14:18               ` Martin Drab

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=41DC2353.7010206@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=drab@kepler.fjfi.cvut.cz \
    --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

Powered by JetHome