Just to make this issue more intriguing, I thought I should note that in researching the problem I came across cases of three separate Ubuntu users whose system was hosed when they updated to 2.6.24-18-generic, and who reported that they solved the problem by (are you sitting down?) deleting the older kernel images!
http://ubuntuforums.org/showthread.php?t=818241 http://ubuntuforums.org/showthread.php?t=818608 Now, I'm having a hard time understanding how just having the bytes for the images sitting there in the file system could possibly cause a computer to freeze up so consistently. At first I conjured up far- fetched theories like corrupted file systems with garbled cross links between the blocks for the image files. But as wildly improbable as that would be for a single case, the odds against that happening to three separate users are beyond astronomical. I should point out that for at least one (perhaps all) of these three cases the users got no better results with the solution I used, which was to just pick the older kernel from the grub menu, so I'm not really sure how much commonality there is between the bug(s) I ran into and their situations. I would be *very* interested in any light anyone can shed explaining (rationally, not "it's just voodoo") how the presence of older kernel images could possibly affect the behavior of the computer in any way. -- Heron freezing with latest kernel (2.6.24-18) https://bugs.launchpad.net/bugs/237612 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
