usb_id errors: "unable to access..."

[tsger]

Binary package hint: usplash

When booting 9.10 Alpha 6, I get several messages starting with "usb_id..." and "unable to access..." then, for example, '/devices/pci0000:00/0000:00:1d.0/usb6/6-1'

Even with no external usb devices connected, i get these messages, although I get fewer than when I do have external devices connected.

ProblemType: Bug
Architecture: amd64
Date: Wed Sep 30 16:59:53 2009
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Studio XPS 1640
NonfreeKernelModules: fglrx
Package: usplash 0.5.39
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=293eb957-0c77-4c1f-a9d0-f988b433c3ae ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: usplash
Uname: Linux 2.6.31-11-generic x86_64
UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1920
 yres=1080
dmi.bios.date: 06/02/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0U785D
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd06/02/2009:svnDellInc.:pnStudioXPS1640:pvrA083:rvnDellInc.:rn0U785D:rvrA08:cvnDellInc.:ct8:cvrA08:
dmi.product.name: Studio XPS 1640
dmi.product.version: A083
dmi.sys.vendor: Dell Inc.

[Wedel (fut2110)]

I can comfirm this bug.

[fumozzo (enri-fuma)]

Me too

[Todd Harris (lalitpatanpur)]

I can also confirm... need any files from me?

[Bossieman (leifsandvik)]

Me2, confirmed.

[tsger (tsgermany)]

I confirmed this as also a problem in the Karmic Beta release. Curiously, when booting the LiveCD I do not see these error messages, just the nice new white Ubuntu logo. But upon booting into the installed system, then I get the above mentioned messages.

[Robbie Williamson (robbiew)]

pretty sure these messages are coming from the kernel

[yassin (yassin)]

usb_id[3130]: unable to access '/devices/pci0000:00/0000:00:1d.1/usb6/6-2'

I have this problem also, please fix this ASAP, my integrated Nvidia graphic card won't work otherwise.

[Scott James Remnant (Canonical) (canonical-scott)]

On Sat, 2009-10-03 at 10:34 +0000, yassin wrote:

> I have this problem also, please fix this ASAP, my integrated Nvidia graphic card won't work otherwise.
>
It's impossibly unlikely that your NVIDIA integrated graphics card is a
USB device.

Seriously.

Scott
--
Scott James Remnant
<email address hidden>

[Tim Besard (maleadt)]

Confirming the behaviour tsger described: the installed version seems to suffer from this bug where the live-cd did not.

[Felix Heinonen (fheinonen)]

I get the same message on a Eeepc 900 except the ending being /usb3/3-2'

[Marcos (deflagmator)]

here the same with last updates today.
?field.comment=here the same with last updates today.

[DominicB (dominic-bartl)]

does anybody can explain to me how i solve this problem?!

[DominicB (dominic-bartl)]

sorry for my englisch "could anybody explain..."

usb_id[433]: unable to access '/devices/pci0000:00/0000:00:1a. 0/usb3/3-2'

usb_id[440]: unable to access '/devices/pci0000:00/0000:00:1d. 0/usb5/5-1'

[pierreblueher (pierre-blueher)]

I can also confirm this bug

[Brian Murray (brian-murray)]

I believe the usb_id messages are from udev.

[Andy Whitcroft (apw)]

Although we are seeing these error messages reported, which we believe are comming from a udev helper application, are we seening any actual problem as a result. As scott indicated it is unlkely they are the cause of a graphics issue as that is not a USB device. Are any other devices affected/missing or not working when booted from the real system, but usable from the live CD ?

[Marcos (deflagmator)]

All the devices work with no problem.
If I I boot the computer with the web camera and usb card reader disconected (both are integrated in my Dell SP2309W screen.) I have no "usb_id" line error.
My question is why I don't see the splash (white ubuntu logo with black background) on boot? . (with and without the usb camera and reader disconected and connected.)
I'm agree the probably is not a really because both (camera and card reader) works perfect.

[Zachary Dunn (zach4618-deactivatedaccount)]

I am also experiencing this problem:

usb_id[442]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb7/7-2'
Starting up ...
usb_id[445]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2.1'

usb_id[453]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2.2'

usb_id[459]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2.3'

though I do not have any problem using USB devices after the boot.

[Scott James Remnant (Canonical) (canonical-scott)]

While the error messages are coming from a udev helper, I think that they are indicative of a kernel issue - downgrading the kernel makes them go away again.

It looks like the kernel is announcing a sysfs object that it never creates or something?

[Diogo Ferreira (diogo-underdev)]

I can confirm this, this is the reason why the ubuntu boot logo doesn't come up I think.

I can confirm it on 3 x86_64 machines, my laptop and two desktop pcs. If there's some additional info I can provide please tell me so, I'd love to see this go away before the final release.

[Marcos (deflagmator)]

25@
I thought the same but if i follow this
http://ubuntuforums.org/showpost.php?p=8063596&postcount=8
the usplash appears.

May be in this beta stage this is disabled to see system messages.

[tsger (tsgermany)]

Hey, Marcos, That worked for me as well. So much nicer to see usplash instead of text, even if it doesn't speed up the boot time at all. Thanks for the link.

[Andy Whitcroft (apw)]

@Keybuk -- ok so I assume that the udev logs will show us what event the kernel triggered. Perhaps we can tie that to the dmesg.

Could those seeing these messages please attach a dmesg output and the contents of /var/adm/udev to the bug. Thanks.

[Jens Cornelis (mail-jenscornelis)]

I guess you meant /var/log/udev?

[Laurent Simonneau (l-simonneau)]

Isn't it /var/log/udev instead of /var/adm/udev ?

[Laurent Simonneau (l-simonneau)]

In my case (atachement of #32) it's the Broadcom_BCM2045B2 (bluethooth) and my Logitech wireless mouse and keyboard USB receiver that produce error message at boot time.

[Laurent Simonneau (l-simonneau)]

No more message after my last update. Sorry for the flood ...

[Kzin (wmkzin)]

I can confirm comment #33 by Laurent Simonneau.
If I unplug my Logitech Bluetooth dongle this error goes away.
With the last Kernel update my bluetooth stopped working, now the dongle only operates in USB compatibility mode. This means I cannot pair other devices with the dongle, only the Keyboard/Mouse.
The Bluez applet says "No bluetooth devices connected"

[Kzin (wmkzin)]

Er, I suppose I should mention OS;
Linux version 2.6.31-12-generic (buildd@vernadsky) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu7) ) #41-Ubuntu SMP Wed Oct 7 18:42:46 UTC 2009
As an aside, my bluetooth was working fine in 9.04, until last weeks Kernel update. I went to 9.10 today in the hopes that my bluetooth issue would be resolved... Does anyone else use a bluetooth dongle in this thread? If you unplug and reboot, do you still get the error?

[Nicholas Coltharp (coltharpnicholas)]

I am seeing the same problem, and should add that I also have a bluetooth dongle--but in my case, it's built into the computer, so there's not much I can do about that.

[Nicholas Coltharp (coltharpnicholas)]

And just after I posted that I remembered that I could unplug it by disabling my wireless. I did so and lo and behold, no error on reboot.

[Kzin (wmkzin)]

Are you able to sync bluetooth devices s/a headphones/smartphones etc? Or does System > Preferences > Bluetooth say "Your computer does not have any Bluetooth adapters plugged in."

[DominicB (dominic-bartl)]

Yuhu =) I think I know how to solve it...

just update your ubuntu and then the massage wont will come again
my laptop dosent write this massage any more

[Kzin (wmkzin)]

Confirmed comment #40 by DominicB
A sudo apt-get update sudo apt-get upgrade has at least made the errors go away on boot.
My bluetooth still doesn't work, but I guess that'd be out of the scope of this thread?

[Marcos (deflagmator)]

Then the problem has been solved?

[Kzin (wmkzin)]

For me yes. Confirmed solved.

[Jonenst (jon-harper87)]

I can also confirm the problem is solved for me

[Zachary Dunn (zach4618-deactivatedaccount)]

Problem has been solved for me as well.

[Andy Whitcroft (apw)]

As per previous 4 comments these messages are no longer present following the kernel update. Closing Fix Released.

[tsger (tsgermany)]

I no linger see the messages, but I do see the white ubuntu logo. How do I confirm that the messages are no longer there? Could it be that they are just hidden by the logo?

[glepore70 (greg-rhobard)]

I am still seeing this message with the latest kernel:
usb_id[423]: unable to access '/devices/pci0000:00/0000:00:02.0/usb2/2-3'

kernel info:
Linux upstairs 2.6.31-14-generic #46-Ubuntu SMP Tue Oct 13 16:47:28 UTC 2009 x86_64 GNU/Linux

[Kzin (wmkzin)]

@ #47 tsger
If you see the white Ubuntu logo, all should be good.
The logo goes away when there are messages from the Kernel or early boot, s/a "Disc needs to be checked" or "unable to access '/devices/pci0000:00/0000:00:02.0/usb2/2-3'"

@ #48 glepore
I am not getting this message anymore for sure, and there is now a new Kernel. Try doing a dist-upgrade and see if that sorts you out.

sudo apt-get update
sudo apt-get dist-upgrade

Dylan.

[glepore70 (greg-rhobard)]

Still seeing the message.
Linux upstairs 2.6.31-14-generic #47-Ubuntu SMP Thu Oct 15 03:42:30 UTC 2009 x86_64 GNU/Linux
the 2.6.31-14 kernel is the latest that I get, I think it's the latest there is, and I'm still getting the error.
I don't use any splash screens at all, maybe that's related?

[Andrew C. Oliver (acoliver)]

I have this on the latest kernel, etc. It seems to occur intermittently and seems like some kind of timing issue. It has a strong correlation with when a check disk auto-runs or updates that require a reboot happen.

[Erkan Ozgur Yilmaz (eoyilmaz)]

in 2.6.31-16-generic I have this messages too... and my laptop (HP HDX-18) boots around in 5-6 minutes. Another thing I found, while booting, if I press Ctrl+Alt+Del for once while getting the "unable to access" messages, it immediately passes the messages by saying "* Asking all the remaining processes to terminate" and boots in normal time...

[bidwej (bidwej)]

I still see a similar message. "usb_id[394]: unable to access 'devices/pci0000:00/0000:00: id.1/usb3/3-1" running Karmic 9.10 fully updated. I also ran dist-upgrade and encounter the same results.

The problem started ~2 months ago, ~50% of the time my machine does not boot up on the first try. The computer powers on but the monitor does not become active. I suspect this problem is interfering with my PCI-Express Nvidia Quadro FX 4000 card.

[Mario (mariosaleiro)]

I'm running linux ubuntu 2.6.31.19 on a 64 bit system and since I updated to this version I started getting this problem. Now the computer takes too much time on startup, but always boots ok after some minutes.

[Holger (bug-holger-kinkelin)]

I can confirm this issue on 2.6.31.19 (server) on 64 machine.

[Simon Harris (haruki-zaemon)]

I'm having the same issue with any USB decice, Keyboard, mouse, you name it. The devices work but the error message appears. If I disconnect all USB devices, the message no longer appears.

2.6.31-20-server #58-Ubuntu SMP Fri Mar 12 05:40:05 UTC 2010 x86_64 GNU/Linux

[kokonobs (kokonobs)]

Might i add to this. I'm having the same issue. And for me it goes further. I suspect its the source of my regular once a day Ubuntu hanging (freezing), Only able to reboot from using Alt+SysR+ (r,s,e,i,u,b) in turn... I see the error when i do Alt+SysR+e.

Dell Inspiron 1564, Lucid Lynx 64bit.