From: Stephen Waterbury <golux@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: IEEE 1394 "unknown bus" messages
Date: Fri, 19 Nov 2004 19:03:28 +0000 [thread overview]
Message-ID: <419E4380.3020509@comcast.net> (raw)
I'm not on the list, so please cc me if I need to send
more info. Some system info:
$ uname -a
Linux bigboote 2.6.9-1.678_FC3 #1 Mon Nov 15 18:28:07 EST 2004 i686 i686 i386 GNU/Linux
I'm using the Adaptec AFW-4300 firewire card and the DiskGo! Edge
portable 120 GB hard drive, which has 1 USB and 2 1394 ports.
It worked okay yesterday, but something's weird today.
Anyway, I'm reporting this to the list because the following
appeared in /var/log/messages, which requested that I report
it to the list:
Nov 19 13:40:44 localhost kernel: ieee1394: Error parsing configrom for node 0-00:1023
Nov 19 13:40:45 localhost wait_for_sysfs[3603]: error: unknown bus, please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Nov 19 13:40:45 localhost wait_for_sysfs[3603]: either wait_for_sysfs (udev 039) needs an update to handle the device '/devices/pci0000:00/0000:00:1e.0/0000:02:0c.0/fw-host0/0050770e205d1518' 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 13:40:45 localhost ieee1394.agent[3619]: ... no drivers for IEEE1394 product 0x/0x/0x
Nov 19 13:40:45 localhost kernel: scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
Nov 19 13:40:46 localhost kernel: ieee1394: sbp2: Logged into SBP-2 device
Nov 19 13:40:46 localhost kernel: Vendor: Maxtor 6 Model: Y120L0 Rev:
Nov 19 13:40:46 localhost kernel: Type: Direct-Access ANSI SCSI revision: 06
Nov 19 13:40:46 localhost wait_for_sysfs[3613]: error: unknown bus, please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Nov 19 13:40:46 localhost wait_for_sysfs[3613]: either wait_for_sysfs (udev 039) needs an update to handle the device '/devices/pci0000:00/0000:00:1e.0/0000:02:0c.0/fw-host0/0050770e205d1518/0050770e205d1518-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>
Nov 19 13:40:46 localhost ieee1394.agent[3671]: ... no drivers for IEEE1394 product 0x/0x/0x
Nov 19 13:40:46 localhost scsi.agent[3665]: disk at /devices/pci0000:00/0000:00:1e.0/0000:02:0c.0/fw-host0/0050770e205d1518/0050770e205d1518-0/host0/0:0:0:0
Nov 19 13:40:46 localhost kernel: SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB)
Nov 19 13:40:46 localhost kernel: SCSI device sda: drive cache: write through
Nov 19 13:40:46 localhost kernel: sda: unknown partition table
Nov 19 13:40:46 localhost kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
-------------------------------------------------------
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-19 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 19:03 Stephen Waterbury [this message]
2004-11-19 20:54 ` IEEE 1394 "unknown bus" messages 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=419E4380.3020509@comcast.net \
--to=golux@comcast.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.