From: Terry Griffin <griffint@pobox.com>
To: linux-hotplug@vger.kernel.org
Subject: Adaptec AUA-1422
Date: Sat, 20 Nov 2004 00:43:52 +0000 [thread overview]
Message-ID: <200411191643.52908.griffint@pobox.com> (raw)
Hi all,
By request of my log file I am posting this information. (Who am I to
argue with my log file?)
I just purchased an Adaptec AUA-1422. This is a CardBus adapter providing
USB 2.0 and Firewire ports. (Yes, nested hot-plugging.) Plugging this in
to my laptop (IBM A20m, Fedora Core 3, kernel 2.6.9-1.678_FC3) generated
these log messages:
Nov 19 16:21:06 nezperce kernel: PCI: Enabling device 0000:02:00.2 (0000 -> 0002)
Nov 19 16:21:06 nezperce kernel: ehci_hcd 0000:02:00.2: EHCI Host Controller
Nov 19 16:21:06 nezperce wait_for_sysfs[3709]: error: unknown bus, please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Nov 19 16:21:06 nezperce wait_for_sysfs[3709]: either wait_for_sysfs (udev 039) needs an update to handle the device '/devices/pci0000:00/0000:00:02.0/0000:02:00.3/fw-host0' properly (unknown bus) or the sysf
s-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Nov 19 16:21:06 nezperce kernel: ehci_hcd 0000:02:00.2: irq 11, pci mem 22aa0800
Nov 19 16:21:06 nezperce hald[2197]: Timed out waiting for hotplug event 277. Rebasing to 278
Nov 19 16:21:07 nezperce ieee1394.agent[3740]: ... no drivers for IEEE1394 product 0x/0x/0x
Nov 19 16:21:07 nezperce kernel: ehci_hcd 0000:02:00.2: new USB bus registered, assigned bus number 2
Nov 19 16:21:07 nezperce kernel: ehci_hcd 0000:02:00.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
Nov 19 16:21:08 nezperce kernel: hub 2-0:1.0: USB hub found
Nov 19 16:21:08 nezperce kernel: hub 2-0:1.0: 3 ports detected
Nov 19 16:21:08 nezperce kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Nov 19 16:21:09 nezperce kernel: ohci_hcd 0000:02:00.0: OHCI Host Controller
Nov 19 16:21:09 nezperce kernel: ohci_hcd 0000:02:00.0: irq 11, pci mem 22ac6000
Nov 19 16:21:09 nezperce kernel: ohci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
Nov 19 16:21:09 nezperce kernel: hub 3-0:1.0: USB hub found
Nov 19 16:21:09 nezperce kernel: hub 3-0:1.0: 2 ports detected
Nov 19 16:21:09 nezperce kernel: PCI: Enabling device 0000:02:00.1 (0000 -> 0002)
Nov 19 16:21:09 nezperce kernel: ohci_hcd 0000:02:00.1: OHCI Host Controller
Nov 19 16:21:09 nezperce kernel: ohci_hcd 0000:02:00.1: irq 11, pci mem 22a7e000
Nov 19 16:21:09 nezperce kernel: ohci_hcd 0000:02:00.1: new USB bus registered, assigned bus number 4
Nov 19 16:21:09 nezperce kernel: hub 4-0:1.0: USB hub found
Nov 19 16:21:09 nezperce kernel: hub 4-0:1.0: 1 port detected
Nov 19 16:21:09 nezperce kernel: ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
Nov 19 16:21:09 nezperce kernel: PCI: Enabling device 0000:02:00.3 (0000 -> 0002)
Nov 19 16:21:11 nezperce kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[20406000-204067ff] Max Packet=[2048]
Nov 19 16:21:13 nezperce wait_for_sysfs[3877]: error: unknown bus, please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Nov 19 16:21:13 nezperce wait_for_sysfs[3877]: either wait_for_sysfs (udev 039) needs an update to handle the device '/devices/pci0000:00/0000:00:02.0/0000:02:00.3/fw-host0/000000000000317b' 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>
Nov 19 16:21:13 nezperce ieee1394.agent[3909]: ... no drivers for IEEE1394 product 0x/0x/0x
Plugging in a USB hard drive did nothing. It wasn't detected. I don't
have any Firewire devices so I don't know if that works or not but
from the messages I'm guessing not. Additional information available on
request (/proc entries, s/w versions, whatever).
Unrelated to this I got a similar complaints about my network devices.
First for my old Addtron Prism-based wireless adapter:
Nov 19 16:03:25 nezperce wait_for_sysfs[4549]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/net/eth0' 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>
And then for my VPN tunnel device:
Nov 19 16:03:33 nezperce wait_for_sysfs[4760]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/net/tun0' 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>
Thanks,
Terry
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-11-20 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 0:43 Terry Griffin [this message]
2004-11-20 14:03 ` Adaptec AUA-1422 Kay Sievers
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=200411191643.52908.griffint@pobox.com \
--to=griffint@pobox.com \
--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).