Comment 57 for bug 6367

No, those have nothing to do with it.

The culprit is the scan_block_tree() and recurse_tree() functions in udevplug.c

A half-fixed version is in the edgy source archive at the moment, it uses the symlinks in /sys/bus/pci/devices, however does not yet sort them so is effectively in a random order.

If I'm being hostile, it's only because of the attitude of people such as yourself on this bug. For example this bug has been reported exactly twice, not "1,000,000 times", and it took four months before a user was willing to perform the necessary tests to help us locate the bug. It certainly has not been confirmed "10,000,000 times" (your words, again) because I doubt we have that many users!

As you can see from the log, I've been perfectly fluffy until the point people starting throwing their toys out of their pram and threatening things if the bug was not fixed now, Now, NOW! WAAAH BIKKIT!

I've iterated many times that until we have performed mass-scale testing of the fix for this bug, there is no way to know whether it will break other people or not -- the chances are that it will. We were only a few weeks from release when this bug was finally identified as a problem in udevplug, and the fix identified -- that is not a time you fundamentally change the way hardware enumeration works.

I've also iterated that the fix has been around for some time now, and that it would go into edgy when it opened (it's already partially there, awaiting builds) -- and that if we have no adverse effects in edgy, it could be backported to either dapper-updates or at least dapper-proposed or dapper-backports.