From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
NetDev <netdev@vger.kernel.org>,
x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: oops/warning report for the week of November 26, 2008
Date: Wed, 26 Nov 2008 16:05:37 -0800 [thread overview]
Message-ID: <200811261605.43099.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <492DD792.6080302@linux.intel.com>
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...
Jesse
next prev parent reply other threads:[~2008-11-27 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 23:11 Arjan van de Ven
2008-11-27 0:05 ` Jesse Barnes [this message]
2008-11-27 11:48 ` Ingo Molnar
2008-11-27 19:42 ` Alex Chiang
2008-11-27 19:49 ` Arjan van de Ven
2008-11-27 11:52 ` Ingo Molnar
2008-11-27 17:02 ` Jesse Barnes
2008-11-27 18:01 ` Arjan van de Ven
2008-11-27 20:18 ` Ingo Molnar
2008-11-27 20:28 ` Arjan van de Ven
2008-11-27 20:47 ` Ingo Molnar
2008-11-27 20:53 ` Arjan van de Ven
2008-11-28 8:34 ` Ingo Molnar
2008-11-27 21:18 ` H. Peter Anvin
2008-11-27 21:18 ` Yinghai Lu
2008-11-27 21:42 ` H. Peter Anvin
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=200811261605.43099.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=x86@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
all inboxes | Powered by JetHome®