Comment 6 for bug 1203941

As documented in Bug #1184154, I've tried 3.2.45-030245 (the suggested mainline kernel at the time) and found that it booted, but only because the dahdi modules were broken enough that a symbol was missing and so the module wouldn't load.
As with 3.2.0-44, running "sudo dpkg-reconfigure dahdi-dkms" fixed the modules such 3.2.45 would boot and the modules functioned. The issue here isn't the kernel -- it is that the modules aren't being rebuilt properly when a new kernel is installed.