From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
linux-pci@vger.kernel.org, netdev@vger.kernel.org,
x86@kernel.org, tytso@mit.edu, akpm@linux-foundation.org,
alan@redhat.com, airlied@redhat.com
Subject: Re: Oops/Warning report for the week of December 3rd, 2008
Date: Wed, 3 Dec 2008 20:35:33 -0800 [thread overview]
Message-ID: <20081204043533.GE18027@kroah.com> (raw)
In-Reply-To: <20081203184652.0601b86b@linux.intel.com>
On Wed, Dec 03, 2008 at 06:46:52PM -0800, Arjan van de Ven wrote:
> Rank 1: pci_create_slot (warning)
> Reported 1224 times (1662 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
This will be fixed in 2.6.27.8, so it should go away soon.
> Rank 5: VBoxDrvLinuxIOCtl (warning)
> Reported 756 times (2332 total reports)
> [external] bug in the VirtualBox drivers
> This warning was last seen in version 2.6.28-rc3, and first seen in 2.6.25.11.
> More info: http://www.kerneloops.org/searchweek.php?search=VBoxDrvLinuxIOCtl
Does anyone have a link to the virtualbox linux kernel drivers? I can't
seem to find them poking around on their site. All I found were some
strange C++ files that couldn't possibly be the kernel code...
> Rank 14: sysfs_add_one (oops)
> Reported 195 times (213 total reports)
> Duplicate sysfs registration; mostly in USB audio
> This oops was last seen in version 2.6.27.5, and first seen in 2.6.25.
> More info: http://www.kerneloops.org/searchweek.php?search=sysfs_add_one
Should be resolved in 2.6.27.7, interesting that no one reported it in
.6, perhaps no distro did a release with that kernel version.
thanks,
greg k-h
prev parent reply other threads:[~2008-12-04 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 2:46 Oops/Warning report for the week of December 3rd, 2008 Arjan van de Ven
2008-12-04 4:35 ` Greg KH [this message]
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=20081204043533.GE18027@kroah.com \
--to=greg@kroah.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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