From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Report about error: unknown bus]
Date: Wed, 20 Oct 2004 05:33:45 +0000 [thread overview]
Message-ID: <1098250425.4907.16.camel@blaze.homeip.net> (raw)
In-Reply-To: <1098244606.7230.7.camel@blaze.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 3421 bytes --]
On Wed, 2004-10-20 at 06:27 +0200, Kay Sievers wrote:
> A lot of these errors are already fixed. If possible, please update to a
> newer version of udev. If you still get errors, please report it again.
> We've added some more detailed information to the log, to see what exactly
> failed.
>
> Thanks,
> Kay
>
Kay, thanks for suggestion.
I did upgrade to 040 and it still spits some errors such as:
Oct 20 01:09:44 blaze logger: /etc/rc.d/rc.hotplug start (entering
script)
Oct 20 01:09:44 blaze kernel: ohci1394: $Rev: 1223 $ Ben Collins
<bcollins@debian.org>
Oct 20 01:09:44 blaze kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI
22 (level, high) -> IRQ 22
Oct 20 01:09:44 blaze wait_for_sysfs[2039]: error: unknown bus, please
report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Oct 20 01:09:44 blaze wait_for_sysfs[2039]: either wait_for_sysfs (udev
040) needs an update to handle the device
'/devices/pci0000:00/0000:00:0d.0/fw-host0' properly (unknown bus) or
the sysfs-support of your device's driver needs to be fixed, please
report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 20 01:09:44 blaze ieee1394.agent[2051]: ... no drivers for IEEE1394
product 0x/0x/0x
Oct 20 01:09:44 blaze kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI):
IRQ=[22] MMIO=[ee084000-ee0847ff] Max Packet=[2048]
Oct 20 01:09:46 blaze wait_for_sysfs[2431]: error: unknown bus, please
report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Oct 20 01:09:46 blaze wait_for_sysfs[2431]: either wait_for_sysfs (udev
040) needs an update to handle the device
'/devices/pci0000:00/0000:00:0d.0/fw-host0/8a1cc7ffff0020ed' properly
(unknown bus) or the sysfs-support of your device's driver needs to be
fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 20 01:09:46 blaze ieee1394.agent[2467]: ... no drivers for IEEE1394
product 0x/0x/0x
Oct 20 01:09:46 blaze wait_for_sysfs[2442]: error: unknown bus, please
report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Oct 20 01:09:46 blaze wait_for_sysfs[2442]: either wait_for_sysfs (udev
040) needs an update to handle the device
'/devices/pci0000:00/0000:00:0d.0/fw-host0/8a1cc7ffff0020ed/8a1cc7ffff0020ed-0' properly (unknown bus) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 20 01:09:46 blaze ieee1394.agent[2480]: ... no drivers for IEEE1394
product 0x/0x/0x
Oct 20 01:09:46 blaze kernel: eth1394: $Rev: 1224 $ Ben Collins
<bcollins@debian.org>
Oct 20 01:09:48 blaze kernel: usb 3-1: new full speed USB device using
address 2
Oct 20 01:09:48 blaze usb.agent[3424]: ... no modules for USB product
46d/840/100
Oct 20 01:09:49 blaze kernel: USB Universal Host Controller Interface
driver v2.2
Oct 20 01:09:52 blaze wait_for_sysfs[2505]: either wait_for_sysfs (udev
040) needs an update to handle the device '/class/net/eth1' properly (no
device symlink) or the sysfs-support of your device's driver needs to be
fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 20 01:10:12 blaze usb.agent[4314]: ... no modules for USB product
0/0/0
Oct 20 01:10:12 blaze logger: /etc/rc.d/rc.hotplug start (exiting
script)
If you need more info such as full dmesg or /proc/pci or lspci please
let me know.
Thanks again,
Paul
--
FreeBSD -- The Power to Serve!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-20 5:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 3:56 [Report about error: unknown bus] Paul Blazejowski
2004-10-20 4:27 ` Kay Sievers
2004-10-20 5:33 ` Paul Blazejowski [this message]
2004-10-20 13:17 ` Kay Sievers
2004-10-20 17:05 ` Kay Sievers
2004-10-20 17:44 ` Paul Blazejowski
2004-10-20 17:48 ` Paul Blazejowski
2004-10-20 18:03 ` Kay Sievers
2004-10-20 20:44 ` Kay Sievers
2004-10-21 4:15 ` Paul Blazejowski
2004-10-21 8:11 ` Kay Sievers
2004-10-21 18:40 ` Paul Blazejowski
2004-10-21 19:58 ` Kay Sievers
2004-10-21 20:28 ` Paul Blazejowski
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=1098250425.4907.16.camel@blaze.homeip.net \
--to=paulb@blazebox.homeip.net \
--cc=linux-hotplug@vger.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;
as well as URLs for NNTP newsgroup(s).