An update on the reports of similar lockups with the latest kernel: one of the three users described above as having solved the problem by eliminating the older kernel images did some additional experimenting and reported the following sequence.
First he re-installed 2.6.24-17 kernel image and headers and rebooted into that kernel. His system was hosed. Next he removed the kernel image for 2.6.24-18 and rebooted back into 2.6.24-17. System still didn't work. Then he removed the kernel headers for 2.6.24-18 and rebooted back into 2.6.24-17. System working perfectly. I post this information not because I understand how the presence of older header files could affect system behavior (I don't), but in the hopes that the maintainers who know more about the kernel and the package management system than I do will find useful clues in it. In contrast with the issue tracking systems used for the software I write myself, where the users of the software have adequate means for communicating the severity of a problem, it doesn't appear that I have any way of setting the "Importance" value for bugs that I file against Ubuntu. It seems like a broken kernel that freezes the whole system for a bunch of users would merit more urgent attention than (for example) cosmetic flaws. What can I as a mere mortal do differently when I file a bug report for a serious show-stopper like this in order to get the attention of those doing triage on the incoming reports? Thanks! -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
