UEVENT not generated when removing PCMCIA pc card

Bug #162402 reported by Frank on 2007-11-13
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

On (K)ubuntu 7.10 a UEVENT is not generated by the kernel when a PCMCIA PC card is removed from the system:

$ sudo udevmonitor
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent

UEVENT[1194953228.779786] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953228.959397] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953230.598672] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953233.415975] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953233.508582] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953234.972943] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953237.759973] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953237.867551] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953239.028915] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953241.624024] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953241.753107] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953243.323935] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953243.326690] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953246.291972] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953246.443285] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953247.602263] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953249.891969] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953250.035555] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953251.129067] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UEVENT[1194953253.427974] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953253.579552] add /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)
UDEV [1194953254.633208] remove /devices/pci0000:00/0000:00:1e.0/0000:02:00.0/0.0 (pcmcia)

Actually, from the code above you can see that one of the removals did in fact trigger the proper UEVENT, but usually this does not happen and this behaviour breaks programs which depend on D-BUS for HW detection.

I've checked this behaviour against (K)ubuntu 6.10 LTS, and it correctly generates a UEVENT for each removal. So this is definately a problem with the 2.6.22 kernel used in (K)ubuntu 7.10.

Frank (frank-aune) wrote :

This is the same activity performed on Kubuntu 6.10 LTS:

udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]

UEVENT[1194955803.201066] add@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UDEV [1194955803.235275] add@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UEVENT[1194955804.801254] remove@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UDEV [1194955804.802018] remove@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UEVENT[1194955807.657327] add@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UDEV [1194955807.691431] add@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UEVENT[1194955808.583364] remove@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UDEV [1194955808.584129] remove@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UEVENT[1194955811.209548] add@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UDEV [1194955811.244305] add@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UEVENT[1194955811.764918] remove@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0
UDEV [1194955811.765911] remove@/devices/pci0000:00/0000:00:1e.0/0000:05:04.1/1.0

Michael Nagel (nailor) wrote :

is this still an issue?

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.


2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Michael Nagel (nailor) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers