[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804172140.02311.jdelvare@suse.de>
Date: Thu, 17 Apr 2008 21:40:01 +0200
From: Jean Delvare <jdelvare@...e.de>
To: LKML <linux-kernel@...r.kernel.org>,
linux-pci@...ey.karlin.mff.cuni.cz
Cc: Pavel Machek <pavel@....cz>, Tejun Heo <htejun@...il.com>,
Tom Long Nguyen <tom.l.nguyen@...el.com>,
Randy Dunlap <rdunlap@...otime.net>,
Reuben Farrelly <reuben-lkml@...b.net>,
Jeff Garzik <jgarzik@...ox.com>
Subject: PCI MSI breaks when booting with nosmp
Hi all,
My Thinkpad T60p laptop won't boot any recent kernel with nosmp.
I investigated the issue because many people have been complaining
lately that nosmp was breaking their system, and that's unfortunate
because nosmp is a valuable debugging tool.
The actual problem is that the ahci driver fails during probe.
It's essentially the same problem that has been reported here over
3 years ago:
http://marc.info/?l=linux-ide&m=112729386600155&w=2
The post above gave me the idea to try booting with "nosmp pci=nomsi",
and that worked. This makes me believe that the problem is that PCI MSI
makes expectations that are no longer valid when booting with nomsp.
So, I have come up with the following naive patch:
* * * * *
Booting with "nosmp" doesn't work on my Thinkpad T60p laptop while
booting with "nosmp pci=nomsi" works. Forcibly disabling PCI MSI
when booting with nosmp fixes the problem. I'm not sure if it's the
correct fix though.
Signed-off-by: Jean Delvare <jdelvare@...e.de>
---
drivers/pci/pci.c | 4 ++++
1 file changed, 4 insertions(+)
--- linux-2.6.25-rc9.orig/drivers/pci/pci.c
+++ linux-2.6.25-rc9/drivers/pci/pci.c
@@ -1635,6 +1635,10 @@ static int __devinit pci_init(void)
while ((dev = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
pci_fixup_device(pci_fixup_final, dev);
}
+#ifdef CONFIG_SMP
+ if (setup_max_cpus == 0)
+ pci_no_msi();
+#endif
return 0;
}
* * * * *
I would welcome comments on the patch above. Is it even remotely
correct? Or is the bug more likely in the ahci driver and the PCI MSI
code is innocent?
FWIW, booting with noapic or nolapic without disabling PCI MSI works
fine for me, so it doesn't seem to be an APIC problem (although this was
my first suspect originally.)
Thanks,
--
Jean Delvare
Suse L3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists