From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 955] New: Nvidia Nforce2 interrupt handling problems
Date: Fri, 18 Jul 2003 09:45:29 -0700 [thread overview]
Message-ID: <10010000.1058546729@[10.10.2.4]> (raw)
http://bugme.osdl.org/show_bug.cgi?id=955
Summary: Nvidia Nforce2 interrupt handling problems
Kernel Version: 2.6.0-test1
Status: NEW
Severity: normal
Owner: greg@kroah.com
Submitter: andy-kernel.388488@dustman.net
Distribution: Gentoo
Hardware Environment: Athlon-XP, Nvidia Nforce2 chipset, Radeon 8500 (r200) AGP,
3com 3c920
Software Environment:
AWARD BIOS
gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)
GNU ld version 2.14.90.0.2 20030515 <-- binutils
XFree-4.3.0
Problem Description:
PCI interrupt assignments get weird. With certain boot parameters, you can get
from mostly non-functional to mostly functional. dmesg from several combinations
of parmeters will be attached, but in a nutshell, with local APIC and IO-APIC
and ACPI enabled in the kernel, a lot of strange things happen, even if you use
noapic and pci=noacpi. Disabling the APIC helps a little, but to be functional
at all, pci=noacpi must be used.
Steps to reproduce:
Will be detailed in the following attachments.
reply other threads:[~2003-07-18 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='10010000.1058546729@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--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;
as well as URLs for NNTP newsgroup(s).