Subject : 2.6.39-rc7-git1 boot error message (no crash) Submitter : "werner" <w.landgraf@ru.ru> Date : 2011-05-11 4:58 Message-ID : web-520830057@zbackend1.aha.ru References : http://marc.info/?l=linux-kernel&m=130512952706444&w=2 This entry is being used for tracking a regression from 2.6.38. Please don't close it until the problem is fixed in the mainline.
Has this issue been fixed?
On Monday, June 13, 2011, werner wrote: > This problem continues with 3.0-rc2. > wl > ===== > On Sun, 12 Jun 2011 23:12:08 +0200 (CEST) > "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > This message has been generated automatically as a part > >of a report > > of regressions introduced between 2.6.38 and 2.6.39. > > > > The following bug entry is on the current list of known > >regressions > > introduced between 2.6.38 and 2.6.39. Please verify if > >it still should > > be listed and let the tracking team know (either way). > > > > > > Bug-Entry : > >http://bugzilla.kernel.org/show_bug.cgi?id=35142 > > Subject : 2.6.39-rc7-git1 boot error message (no crash) > > Submitter : werner <w.landgraf@ru.ru> > > Date : 2011-05-11 4:58 (33 days old)
Error message: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:1e.0/0000:02:0b.4/microamps_requested_vmmc' Rafael, does this mean anything to you? I think we should close this out unless we can do something about it.
Per Mark Brown, this is "probably a bug in whatever driver is requesting the supply twice." The backtrace below (from the original report) suggests that this is the sdhci driver. WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0x83/0x95() Hardware name: Qosmio E10 sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:1e.0/0000:02:0b.4/microamps_requested_vmmc' Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.39-rc7-git1-i486-1sys #1 Call Trace: [<c112d5e2>] ? sysfs_add_one+0x83/0x95 [<c1040e25>] warn_slowpath_common+0x7a/0x8f [<c112d5e2>] ? sysfs_add_one+0x83/0x95 [<c1040ec5>] warn_slowpath_fmt+0x33/0x35 [<c112d5e2>] sysfs_add_one+0x83/0x95 [<c112cfd8>] sysfs_add_file_mode+0x4a/0x72 [<c112d018>] sysfs_add_file+0x18/0x1c [<c112d0b3>] sysfs_create_file+0x25/0x27 [<c1792ac8>] device_create_file+0x18/0x1a [<c1693b3a>] create_regulator+0xd8/0x21d [<c1693dde>] _regulator_get+0x15f/0x1ba [<c1693e5c>] regulator_get+0xf/0x11 [<c1cd492d>] sdhci_add_host+0x586/0x6d1 [<c15945ab>] ? pci_ioremap_bar+0x5b/0x60 [<c1eb3c28>] sdhci_pci_probe_slot+0x1c1/0x204 [<c1eb3d71>] ? sdhci_pci_probe+0x106/0x1cd [<c1eb3dd9>] sdhci_pci_probe+0x16e/0x1cd [<c15947dd>] local_pci_probe+0x41/0x85 [<c1595352>] pci_device_probe+0x48/0x6b ... create_regulator: dummy: could not add regulator_dev requested microamps sysfs entry _regulator_get: 0000:02:0b.4 supply vmmc not found, using dummy regulator
Created attachment 84031 [details] Kernel bluetooth oops
Hi guys, I see a very similar error with a bluetooth devices on my system: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/bluetooth/hci0/hci0:21' I'm running 3.5.0-17-generic #28-Ubuntu version. It doesn't seem like a driver specific bug, but rather the kernel does not detect and remove the directories fast enough. In my case I can trigger this error by switching the bluetooth keyboard off and back on again within a minute or so. Should I report it as a separate bug? I've attached a full trace, just in case.
Also another guy seems to have the same problem but with different kernel version, here: http://ubuntuforums.org/showthread.php?t=2007814