Perhaps some useful info: I updated to 3.2.45-030245 and it booted successfully, but DAHDI didn't come up because of a symbol mismatch. I ran "sudo dpkg-reconfigure dahdi-dkms" and rebooted back into 3.2.45 and DAHDI came up fine. So the upstream kernel is working for me.
And so I went back to 3.2.0-44, which booted fine because of the symbol mismatch in DAHDI (which was reconfigured for 3.2.45). And re-ran dpkg- reconfigure on dahdi-dkms for that kernel, and now I can boot into 3.2.0-44 just fine. It seems like the issue here is a dependency problem between dahdi and the kernel. The difference between 3.2.0-43 and 3.2.0-44 was small enough that it didn't fail to load because of a symbol mismatch but large enough that it caused some serious system issues that prevented booting. Juergen, perhaps you should boot to 3.2.0-43 and add dahdi to the module blacklist. Then upgrade to the kernel of your choice and hopefully it will boot. Then reconfigure the dadhi package so it gets rebuilt for that kernel. Then remove dadhi from the module blacklist and reboot. And pray. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184154 Title: After last Kernel Update (3.2.0-44) system hangs on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184154/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
