Reviewing that log showed the problem: Mar 4 10:23:22 SERVER1 udevd[313]: seq 1210 queued, 'remove' 'module' Mar 4 10:23:22 SERVER1 udevd[313]: passed 107 bytes to monitor 0x21c081f0 Mar 4 10:23:22 SERVER1 udevd-work[9630]: seq 1210 running Mar 4 10:23:22 SERVER1 udevd-work[9630]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Mar 4 10:23:22 SERVER1 udevd-work[9630]: passed 95 bytes to monitor 0x21c081f0 Mar 4 10:23:22 SERVER1 udevd-work[9630]: passed -1 bytes to monitor 0x21c10250 Mar 4 10:23:22 SERVER1 udevd-work[9630]: seq 1210 processed with 0 Mar 4 10:23:22 SERVER1 udevd[313]: seq 1210 done with 0 Mar 4 10:23:22 SERVER1 kernel: [148426.666522] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI Mar 4 10:23:22 SERVER1 kernel: [148426.666532] e100: Copyright(c) 1999-2006 Intel Corporation Mar 4 10:23:22 SERVER1 kernel: [148426.666638] e100 0000:00:07.0: PCI->APIC IRQ transform: INT A -> IRQ 23 Mar 4 10:23:22 SERVER1 udevd[313]: seq 1211 queued, 'add' 'module' Mar 4 10:23:22 SERVER1 udevd[313]: passed 104 bytes to monitor 0x21c081f0 Mar 4 10:23:22 SERVER1 udevd-work[9630]: seq 1211 running Mar 4 10:23:22 SERVER1 udevd-work[9630]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Mar 4 10:23:22 SERVER1 udevd-work[9630]: RUN '/usr/local/bin/backup %k%n drive1' /etc/udev/rules.d/usb-backup.rules:34 Mar 4 10:23:22 SERVER1 udevd-work[9630]: '/usr/local/bin/backup e100 drive1' started
The /etc/udev/rules/usb-backup.rules file runs a rsync backup of the computer when a certain usb drive is plugged in. The rule is: ID_SERIAL_SHORT=="9QM42EXK", ACTION=="add", RUN="/usr/local/bin/backup %k%n drive1" For some reason, udev is matching the ethernet port to that hard drive, even though the rule doesn't match (ID_SERIAL_SHORT is not the same, or even present). The network card's info: r...@server1:~# udevadm info --query all --path=/devices/pci0000:00/0000:00:07.0 P: /devices/pci0000:00/0000:00:07.0 E: UDEV_LOG=3 E: DEVPATH=/devices/pci0000:00/0000:00:07.0 E: DRIVER=e100 E: PCI_CLASS=20000 E: PCI_ID=8086:1229 E: PCI_SUBSYS_ID=8086:100C E: PCI_SLOT_NAME=0000:00:07.0 E: MODALIAS=pci:v00008086d00001229sv00008086sd0000100Cbc02sc00i00 E: SUBSYSTEM=pci I'm also attaching udev.log.?field.comment=Reviewing that log showed the problem: Mar 4 10:23:22 SERVER1 udevd[313]: seq 1210 queued, 'remove' 'module' Mar 4 10:23:22 SERVER1 udevd[313]: passed 107 bytes to monitor 0x21c081f0 Mar 4 10:23:22 SERVER1 udevd-work[9630]: seq 1210 running Mar 4 10:23:22 SERVER1 udevd-work[9630]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Mar 4 10:23:22 SERVER1 udevd-work[9630]: passed 95 bytes to monitor 0x21c081f0 Mar 4 10:23:22 SERVER1 udevd-work[9630]: passed -1 bytes to monitor 0x21c10250 Mar 4 10:23:22 SERVER1 udevd-work[9630]: seq 1210 processed with 0 Mar 4 10:23:22 SERVER1 udevd[313]: seq 1210 done with 0 Mar 4 10:23:22 SERVER1 kernel: [148426.666522] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI Mar 4 10:23:22 SERVER1 kernel: [148426.666532] e100: Copyright(c) 1999-2006 Intel Corporation Mar 4 10:23:22 SERVER1 kernel: [148426.666638] e100 0000:00:07.0: PCI->APIC IRQ transform: INT A -> IRQ 23 Mar 4 10:23:22 SERVER1 udevd[313]: seq 1211 queued, 'add' 'module' Mar 4 10:23:22 SERVER1 udevd[313]: passed 104 bytes to monitor 0x21c081f0 Mar 4 10:23:22 SERVER1 udevd-work[9630]: seq 1211 running Mar 4 10:23:22 SERVER1 udevd-work[9630]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Mar 4 10:23:22 SERVER1 udevd-work[9630]: RUN '/usr/local/bin/backup %k%n drive1' /etc/udev/rules.d/usb-backup.rules:34 Mar 4 10:23:22 SERVER1 udevd-work[9630]: '/usr/local/bin/backup e100 drive1' started The /etc/udev/rules/usb-backup.rules file runs a rsync backup of the computer when a certain usb drive is plugged in. The rule is: ID_SERIAL_SHORT=="9QM42EXK", ACTION=="add", RUN="/usr/local/bin/backup %k%n drive1" For some reason, udev is matching the ethernet port to that hard drive, even though the rule doesn't match (ID_SERIAL_SHORT is not the same, or even present). The network card's info: r...@server1:~# udevadm info --query all --path=/devices/pci0000:00/0000:00:07.0 P: /devices/pci0000:00/0000:00:07.0 E: UDEV_LOG=3 E: DEVPATH=/devices/pci0000:00/0000:00:07.0 E: DRIVER=e100 E: PCI_CLASS=20000 E: PCI_ID=8086:1229 E: PCI_SUBSYS_ID=8086:100C E: PCI_SLOT_NAME=0000:00:07.0 E: MODALIAS=pci:v00008086d00001229sv00008086sd0000100Cbc02sc00i00 E: SUBSYSTEM=pci I'm also attaching udev.log. ** Attachment added: "udev.log" http://launchpadlibrarian.net/40176098/udev.log -- e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin https://bugs.launchpad.net/bugs/530348 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
