dahdi-dkms modules not updating properly with kernel updates, can cause soft lockup

[Andre Paquette]

This was originally reported in bug #1184154, which was closed because the originator could no longer contribute.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184154

From a starting point of 3.2.0-43-generic, dahdi and asterisk are running and working as expected.
Updating to a more recent kernel (e.g., 3.2.0-44 or 3.2.0-48), via update manager or manually, results in a system that will not boot. Running the recovery mode version of the kernel from grub shows that shortly after the dahdi module is loaded it gets "soft lockup" on the cores and the system stops booting. I can't enclose logs for this because it doesn't get far enough to write anything out.

If I fall back to 3.2.0-43 and add module blacklisting and temporarily remove init.d/dadhi and init.d/asterisk, I can then get 3.2.0-44 to boot since the dadhi module is no longer loaded.
From that point, I can run "sudo dpkg-reconfigure dahdi-dkms", which appears to purge the dadhi dkms modules and rebuild them, which is similar to what it appeared to do when installing the new kernel. If I then undo the hack to prevent dadhi from loading and reboot into 3.2.0-44, dadhi loads fine without lockups and asterisk runs as expected.

An objdump compare of modules generated after the kernel install and after the dpkg-reconfigure show that they're fairly different -- symbols are moved around and of different sizes.

This is easy to reproduce and several people using dadhi have reported the issue (in the earlier bug report) with kernel versions 3.2.0-44 or later. I can purge 3.2.0-44 and then re-update to that version and show that the dadhi modules are causing soft lockups until I do a "dpkg-reconfigure dadhi-dkms".

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-44-generic 3.2.0-44.69
ProcVersionSignature: Ubuntu 3.2.0-44.69-generic 3.2.44
Uname: Linux 3.2.0-44-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andre 1838 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8ff8000 irq 45'
   Mixer name : 'Analog Devices AD1988B'
   Components : 'HDA:11d4198b,104381f6,00100200'
   Controls : 49
   Simple ctrls : 26
Date: Mon Jul 22 22:47:20 2013
HibernationDevice: RESUME=UUID=5ff6e571-5a9f-4503-b785-11d535246217
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-44-generic root=UUID=8a71ba4a-d8d9-4fc8-9dc3-3df31bed8057 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-44-generic N/A
 linux-backports-modules-3.2.0-44-generic N/A
 linux-firmware 1.79.4
RfKill:

SourcePackage: linux
StagingDrivers: echo
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1238
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[John Hopkinson (john-hopkinson)]

Thank you for including me one this Report, and Yes I still have the problem.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

[Joseph Salisbury (jsalisbury)]

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/

[Andre Paquette (l-andre)]

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.

[Oseias (ferreira-oseias)]

I opened another bug report. Sorry if it is duplicate…
dkms.conf are passing incorrect variable to Makefile kernel version.
Details:
https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1257160