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 17:50:31 +0100 [thread overview]
Message-ID: <41DC1AD7.7000705@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0501051604200.24191@kepler.fjfi.cvut.cz>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Martin Drab schrieb:
> Hi,
>
> I'm witnessing a total freeze on my system when the APIC and LAPIC are
> enabled in kernel 2.6.10-bk7.
Do you know whether your bios already contains the C1 halt disconnect
fix? I couldn't find this line in your dmesg:
PCI: nForce2 C1 Halt Disconnect fixup
Did it occur with earlier kernels? If yes, this is a regression.
Try as workaround if
athcool off
makes your system stable. If yes, you need above fix activated.
Cheers,
Prakash
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-05 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 15:28 APIC/LAPIC hanging problems on nForce2 system Martin Drab
2005-01-05 16:05 ` Zwane Mwaikambo
2005-01-05 16:56 ` Martin Drab
2005-01-05 16:50 ` Prakash K. Cheemplavam [this message]
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
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=41DC1AD7.7000705@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.