Comment 100 for bug 575333
Revision history for this message
| Johan Prins (johanprins-free) wrote | #100 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Just saw this error the first time today, (it just displays, while boot goes on), and am surprised to see that it is an old, unsolved bug that is ignored by Canonical (they have too much 'real' trouble to fight, I guess).
I 'vote' for the theory that the error is a timing issue at boot time, like other weird errors I have seen that don't affect the final result of boot-up.
Since the boot process includes executing multiple threads that can run into some "not yet!" sort of problems, I presume
we will see this sort of error messages more often in the future, until some timing management of the boot process is added.
Sadly enough, we will go the same way as the Microsoft world, if ever the top brains lose track of what's actually happening inside Linux.