| 2009-01-22 20:37:31 |
Scott James Remnant (Canonical) |
bug |
|
|
added bug |
| 2009-01-22 20:43:58 |
Scott James Remnant (Canonical) |
dkms: status |
New |
Confirmed |
|
| 2009-01-22 20:43:58 |
Scott James Remnant (Canonical) |
dkms: importance |
Undecided |
Critical |
|
| 2009-01-22 20:43:58 |
Scott James Remnant (Canonical) |
dkms: statusexplanation |
|
|
|
| 2009-01-22 20:54:52 |
Mario Limonciello |
dkms: status |
New |
Confirmed |
|
| 2009-01-22 20:54:52 |
Mario Limonciello |
dkms: importance |
Undecided |
Critical |
|
| 2009-01-22 20:54:52 |
Mario Limonciello |
dkms: statusexplanation |
|
|
|
| 2009-01-22 21:06:07 |
Mario Limonciello |
dkms: status |
Confirmed |
Fix Committed |
|
| 2009-01-22 21:06:07 |
Mario Limonciello |
dkms: assignee |
|
superm1 |
|
| 2009-01-22 21:06:07 |
Mario Limonciello |
dkms: statusexplanation |
|
http://linux.dell.com/git/?p=dkms.git;a=commit;h=72c7412fe6125d635e40a7eead6f040acab71001 |
|
| 2009-01-22 21:10:51 |
Mario Limonciello |
bug |
|
|
added attachment 'udev_trigger.diff' (udev_trigger.diff) |
| 2009-01-22 21:25:06 |
Launchpad Janitor |
dkms: status |
Fix Committed |
Fix Released |
|
| 2009-01-22 21:27:01 |
Mario Limonciello |
description |
Binary package hint: dkms
DKMS must *NOT* call udevadm trigger.
This will have utterly dire consequences for the installed machine.
Minor bugs will be things like Network Manager and GNOME Power Manager reporting multiple copies of network cards, or batteries.
Major bugs will be apparent corruption of mounted filesystems (e.g. "/usr: data error") until a reboot.
And critical bugs include the entire /dev changing to root:root/660 on upgrade.
If you want to find out whether the module can claim a device, why not just modprobe it? If it doesn't claim a device, it should error out and not be loaded. |
IMPACT:
DKMS must *NOT* call udevadm trigger.
This will have utterly dire consequences for the installed machine.
Minor bugs will be things like Network Manager and GNOME Power Manager reporting multiple copies of network cards, or batteries.
Major bugs will be apparent corruption of mounted filesystems (e.g. "/usr: data error") until a reboot.
And critical bugs include the entire /dev changing to root:root/660 on upgrade.
ADDRESSING BUG:
This has been fixed in git HEAD, as well as in jaunty.
TEST CASE:
On a system that is using DKMS, try to remove an installed module and reinstall it. When DKMS is using udevadm trigger, you will see your network device duplicated in Network Manager. You will also disconnect and reconnect from the network.
For a specified MODULE and VERSION, the following should be a good test case.
dkms remove -m MODULE -v VERSION --all
/etc/init.d/dkms_autoinstaller start
REGRESSION POTENTIAL:
Anyone that was relying on this behavior of DKMS will have to add the optional UDEV_TRIGGER flag to the dkms.conf included with their driver package. The worst behavior expected from this is that the user will have to modprobe the module themselves initially rather that having udev replay the entire database. Also, a reboot would resolve this behavior. |
|
| 2009-01-22 21:27:53 |
Mario Limonciello |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2009-01-23 00:20:05 |
Scott James Remnant (Canonical) |
dkms: status |
Fix Released |
Confirmed |
|
| 2009-01-23 00:20:05 |
Scott James Remnant (Canonical) |
dkms: statusexplanation |
http://linux.dell.com/git/?p=dkms.git;a=commit;h=72c7412fe6125d635e40a7eead6f040acab71001 |
|
|
| 2009-02-06 22:25:06 |
Launchpad Janitor |
dkms: status |
Confirmed |
Fix Released |
|
| 2009-02-06 22:29:53 |
Mario Limonciello |
description |
IMPACT:
DKMS must *NOT* call udevadm trigger.
This will have utterly dire consequences for the installed machine.
Minor bugs will be things like Network Manager and GNOME Power Manager reporting multiple copies of network cards, or batteries.
Major bugs will be apparent corruption of mounted filesystems (e.g. "/usr: data error") until a reboot.
And critical bugs include the entire /dev changing to root:root/660 on upgrade.
ADDRESSING BUG:
This has been fixed in git HEAD, as well as in jaunty.
TEST CASE:
On a system that is using DKMS, try to remove an installed module and reinstall it. When DKMS is using udevadm trigger, you will see your network device duplicated in Network Manager. You will also disconnect and reconnect from the network.
For a specified MODULE and VERSION, the following should be a good test case.
dkms remove -m MODULE -v VERSION --all
/etc/init.d/dkms_autoinstaller start
REGRESSION POTENTIAL:
Anyone that was relying on this behavior of DKMS will have to add the optional UDEV_TRIGGER flag to the dkms.conf included with their driver package. The worst behavior expected from this is that the user will have to modprobe the module themselves initially rather that having udev replay the entire database. Also, a reboot would resolve this behavior. |
IMPACT:
DKMS must *NOT* call udevadm trigger.
This will have utterly dire consequences for the installed machine.
Minor bugs will be things like Network Manager and GNOME Power Manager reporting multiple copies of network cards, or batteries.
Major bugs will be apparent corruption of mounted filesystems (e.g. "/usr: data error") until a reboot.
And critical bugs include the entire /dev changing to root:root/660 on upgrade.
ADDRESSING BUG:
This has been fixed in git HEAD, as well as in jaunty.
TEST CASE:
On a system that is using DKMS, try to remove an installed module and reinstall it. When DKMS is using udevadm trigger, you will see your network device duplicated in Network Manager. You will also disconnect and reconnect from the network.
For a specified MODULE and VERSION, the following should be a good test case.
dkms remove -m MODULE -v VERSION --all
/etc/init.d/dkms_autoinstaller start
REGRESSION POTENTIAL:
Anyone that was relying on this behavior of DKMS will have to manually modprobe the module that was just built themselves or in a postinstall. Also, a reboot would resolve this behavior. |
|
| 2009-02-19 19:23:53 |
Martin Pitt |
dkms: status |
Confirmed |
Fix Committed |
|
| 2009-03-13 17:37:54 |
Launchpad Janitor |
dkms: status |
Fix Committed |
Fix Released |
|
| 2009-12-05 11:29:20 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/dkms |
|
| 2009-12-05 11:35:51 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/intrepid-proposed/dkms |
|
