Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754035AbYK0Tma (ORCPT ); Thu, 27 Nov 2008 14:42:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752619AbYK0TmR (ORCPT ); Thu, 27 Nov 2008 14:42:17 -0500 Received: from g1t0027.austin.hp.com ([15.216.28.34]:14529 "EHLO g1t0027.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752523AbYK0TmQ (ORCPT ); Thu, 27 Nov 2008 14:42:16 -0500 Date: Thu, 27 Nov 2008 12:42:10 -0700 From: Alex Chiang To: Jesse Barnes Cc: Arjan van de Ven , Linux Kernel Mailing List , Linus Torvalds , NetDev , x86@kernel.org, Andrew Morton , "Theodore Ts'o" , Alan Cox Subject: Re: oops/warning report for the week of November 26, 2008 Message-ID: <20081127194210.GB28870@ldl.fc.hp.com> Mail-Followup-To: Alex Chiang , Jesse Barnes , Arjan van de Ven , Linux Kernel Mailing List , Linus Torvalds , NetDev , x86@kernel.org, Andrew Morton , Theodore Ts'o , Alan Cox References: <492DD792.6080302@linux.intel.com> <200811261605.43099.jbarnes@virtuousgeek.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200811261605.43099.jbarnes@virtuousgeek.org> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1412 Lines: 34 * Jesse Barnes : > On Wednesday, November 26, 2008 3:11 pm Arjan van de Ven wrote: > > Rank 2: pci_create_slot (warning) > > Reported 603 times (639 total reports) > > BIOS provided duplicated slot names, the PCI layer blindly passes to sysfs > > This warning was last seen in version 2.6.27.5, and first seen in > > 2.6.27-rc7-git1. More info: > > http://www.kerneloops.org/searchweek.php?search=pci_create_slot > > IIRC we fixed this one post-2.6.27. I didn't send the patches back to -stable > because they were a bit big, but if someone were sufficiently motiviated I'm > sure the backport wouldn't be that hard... I can do this backport. A few questions though... We're seeing a proliferation of this one presumably because Fedora10 uses 2.6.27.5 as a starting point? If I just backport the fixes against Greg's latest tree, do I have to do anything special to make sure they get into the Fedora kernel? Also, does kerneloops capture any of the machine information, like DMI output, etc. or does it just get the oops? It would be nice to see which machines out there have the broken BIOS that causes this oops. Thanks. /ac -- 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/