Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750853AbWCIU1v (ORCPT ); Thu, 9 Mar 2006 15:27:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751392AbWCIU1v (ORCPT ); Thu, 9 Mar 2006 15:27:51 -0500 Received: from smtp.osdl.org ([65.172.181.4]:38796 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1750853AbWCIU1v (ORCPT ); Thu, 9 Mar 2006 15:27:51 -0500 Date: Thu, 9 Mar 2006 12:24:13 -0800 (PST) From: Linus Torvalds To: Ben Collins cc: Tomasz Torcz , Greg KH , Adrian Bunk , Andrew Morton , Linux Kernel Mailing List , linux-pci@atrey.karlin.mff.cuni.cz, pcihpd-discuss@lists.sourceforge.net Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 In-Reply-To: <1141935002.6072.40.camel@grayson> Message-ID: References: <20060306223545.GA20885@kroah.com> <20060308222652.GR4006@stusta.de> <20060308225029.GA26117@suse.de> <20060308231851.GA26666@suse.de> <20060309184010.GA4639@irc.pl> <1141935002.6072.40.camel@grayson> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 918 Lines: 26 On Thu, 9 Mar 2006, Ben Collins wrote: > > The difference between our 2.6.15 386 and 686 kernels is actually pretty > huge. The 386 is M486, and UP, while our 686 kernel is M686, and SMP. Ok, that's actually better than a _real_ M386. At least M486 has most of the new instructions statically. But the SMP thing obviously makes a big difference. Can you get your tester to try "ctrl + scroll-lock" to see if it outputs anything? > So the problem would seem to be narrowed down to between M486 and M686. Well, SMP ends up being a big issue, and adds tons of things. It would be very interesting to hear whether a M686 _UP_ kernel shows the same problem. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/