public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <brice@myri.com>
To: Brandon Philips <brandon@ifup.org>
Cc: Andrew Morton <akpm@osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	Robert Love <rml@novell.com>
Subject: Re: 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s
Date: Sat, 09 Sep 2006 02:14:41 -0400	[thread overview]
Message-ID: <45025BD1.9020106@myri.com> (raw)
In-Reply-To: <20060909060106.GB6364@plankton.ifup.org>

Brandon Philips wrote:
> On 01:47 Sat 09 Sep 2006, Brice Goglin wrote:
>> Do we have Brandon lspci so that I can see if any of the MSI quirks is
>> involved?
>
> 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
> 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
> 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode])
> 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) (prog-if 00 [Normal decode])
> 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) (prog-if 00 [Normal decode])
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode])
>   

There is no MSI quirk for these chipsets, MSI work fine on Intel.

Let me know if your dichotomy leads to one of the following patches:

1) gregkh-pci-msi-cleanup-existing-msi-quirks.patch
2) gregkh-pci-msi-factorize-common-code-in-pci_msi_supported.patch
3) gregkh-pci-msi-export-the-pci_bus_flags_no_msi-flag-in-sysfs.patch
4)
gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capability.patch
5)
fix-gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capability.patch

(only (1) and (2) should be relevant here)

thanks,
Brice


  reply	other threads:[~2006-09-09  6:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 17:44 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s Brandon Philips
2006-09-08 19:13 ` Andrew Morton
2006-09-08 19:43   ` Brandon Philips
2006-09-08 19:50     ` Andrew Morton
2006-09-09  2:22       ` Benoit Boissinot
2006-09-09  3:27       ` Eric W. Biederman
2006-09-09  5:21         ` Andrew Morton
2006-09-09  5:47           ` Brice Goglin
2006-09-09  6:01             ` Brandon Philips
2006-09-09  6:14               ` Brice Goglin [this message]
2006-09-11  2:14       ` Brandon Philips
2006-09-11 16:51         ` Andrew Morton
2006-09-11 17:55           ` Eric W. Biederman
2006-09-12  6:20           ` Eric W. Biederman
2006-09-12  7:50             ` [patch] genirq/MSI: restore __do_IRQ() compat logic temporarily Ingo Molnar
2006-09-12 12:44               ` Brandon Philips
2006-09-12 14:37               ` Eric W. Biederman

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=45025BD1.9020106@myri.com \
    --to=brice@myri.com \
    --cc=akpm@osdl.org \
    --cc=brandon@ifup.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@novell.com \
    --cc=tglx@linutronix.de \
    /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