From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Report about error: unknown bus]
Date: Thu, 21 Oct 2004 04:15:35 +0000 [thread overview]
Message-ID: <1098332135.5381.11.camel@blaze.homeip.net> (raw)
In-Reply-To: <1098244606.7230.7.camel@blaze.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 2874 bytes --]
On Wed, 2004-10-20 at 20:03 +0200, Kay Sievers wrote:
>
> This should fix the bus error and the /class/net/tun* wait error.
> Greg, please apply.
>
> Thanks,
> Kay
> plain text document attachment (wait-fixes.patch)
> ===== udev_sysfs.c 1.1 vs edited =====
> --- 1.1/udev_sysfs.c 2004-10-19 03:50:52 +02:00
> +++ edited/udev_sysfs.c 2004-10-20 20:02:09 +02:00
> @@ -167,6 +167,7 @@
> { .subsystem = "net", .device = "dummy" },
> { .subsystem = "net", .device = "irda" },
> { .subsystem = "net", .device = "ppp" },
> + { .subsystem = "net", .device = "tun" },
> { .subsystem = "ppp", .device = NULL },
> { .subsystem = "sound", .device = NULL },
> { .subsystem = "printer", .device = "lp" },
> @@ -247,7 +248,8 @@
> { .bus = "pci", .file = "vendor" },
> { .bus = "platform", .file = "detach_state" },
> { .bus = "i2c", .file = "detach_state" },
> - { NULL }
> + { .bus = "ieee1394", .file = "host_id" },
> + { NULL, NULL }
> };
> struct bus_file *busfile;
> int loop;
Kay , i applied the patch to udev-040/wait_for_sysfs.c and it still
shows some errors:
Oct 20 23:58:12 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 (bus specific file
unavailable) or the sysfs-support of your device's driver needs to be
fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 20 23:58:12 blaze ieee1394.agent[4202]: ... no drivers for IEEE1394
product 0x/0x/0x
Oct 20 23:58:14 blaze wait_for_sysfs[2279]: either wait_for_sysfs (udev
040) needs an update to handle the device
'/devices/pci0000:00/0000:00:0d.0/fw-host0/8a1cc7ffff0020ed' properly
(bus specific file unavailable) or the sysfs-support of your device's
driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Oct 20 23:58:14 blaze wait_for_sysfs[2287]: 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 (bus specific file unavailable) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 20 23:58:14 blaze ieee1394.agent[4249]: ... no drivers for IEEE1394
product 0x/0x/0x
Oct 20 23:58:14 blaze ieee1394.agent[4238]: ... no drivers for IEEE1394
product 0x/0x/0x
Oct 20 23:58:14 blaze wait_for_sysfs[2322]: either wait_for_sysfs (udev
040) needs an update to handle the device '/class/net/eth2' properly
(bus specific file unavailable) or the sysfs-support of your device's
driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Oct 20 23:58:14 blaze net.agent[4270]: add event not handled
Thank you,
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-21 4:15 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
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 [this message]
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=1098332135.5381.11.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).