[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#425997: marked as done (eth1394 in 2.6.21 breaks udev)

Your message dated Sun, 29 Jul 2007 02:11:56 +0200
with message-id <20070729001156.GF31608@stro.at>
and subject line eth1394 in 2.6.21 breaks udev
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: udev
Version: 0.105-4
Severity: normal

Since booting up with linux 2.6.21, I have:

        1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
            link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
            link/ether 00:0a:e4:e0:35:57 brd ff:ff:ff:ff:ff:ff
        3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
            link/ieee1394 12:34:56:78:12:34:56:78 brd ff:ff:ff:ff:ff:ff:ff:ff
        4: eth2_rename: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 10 00
            link/ether 00:0e:9b:b9:54:63 brd ff:ff:ff:ff:ff:ff

With 2.6.20, eth1 was my wlan interface and eth2 was the firewire
interface.

/etc/udev/rules.d/z25_persistent-net.rules contains:

        # PCI device 0x10ec:0x8169 (r8169)
        SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0a:e4:e0:35:57", NAME="eth0"
        # PCI device 0x14e4:0x4318 (bcm43xx)
        SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0e:9b:b9:54:63", NAME="eth1"
        # Firewire device 1234567812345678 (ohci1394)
        SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="12:34:56:78:12:34:56:78", NAME="eth2"

There was also a delay during boot, I *think* it was during the 'waiting
for /dev to be fully populated' stage, but I am not sure.

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.21-1-k7

Debian Release: 4.0
  540 stable          security.debian.org 
  540 stable          ftp.uk.debian.org 
  530 etch-backports  backports.org 
  520 testing         ftp.uk.debian.org 
  510 unstable        ftp.uk.debian.org 

--- Package information. ---
Depends              (Version) | Installed
==============================-+-=============
libc6             (>= 2.3.6-6) | 2.5-9
libselinux1          (>= 1.32) | 1.32-3
libvolume-id0     (>= 0.103-1) | 0.105-4
debconf              (>= 0.5)  | 1.5.11
 OR debconf-2.0                | 
lsb-base            (>= 3.0-6) | 3.1-23.1

--- End Message ---
--- Begin Message --- 
Version: 2.6.22-1

fixed upstream

-- 
maks

--- End Message ---
Reply to: