Auto Update to Linux 2.6.32.25.27 broke Digitemp

Bug #650731 reported by NDLunchbox
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
digitemp (Ubuntu)
Fix Released
Undecided
NDLunchbox

Bug Description

I have a custom Munin script that monitors several temps, including ambient temperature via a 1-Wire network. I noticed my graphs started reading '-nan' and the last update was 6:25a this morning. I checked my mail to see if updates were performed and found the following:

----------
Date: Tue, 28 Sep 2010 06:28:37 -0400 (EDT)
From: root <root@xxx>
To: xxx@localhost
Subject: unattended-upgrades result for 'xxx'

Unattended upgrade returned: True

Packages that are upgraded:
 linux-server linux-headers-server linux-image-server

Package installation log:
Selecting previously deselected package linux-image-2.6.32-25-server.
(Reading database ... 75672 files and directories currently installed.)
Unpacking linux-image-2.6.32-25-server (from .../linux-image-2.6.32-25-server_2.6.32-25.44_amd64.deb) ...
Done.
Selecting previously deselected package linux-headers-2.6.32-25.
Unpacking linux-headers-2.6.32-25 (from .../linux-headers-2.6.32-25_2.6.32-25.44_all.deb) ...
Selecting previously deselected package linux-headers-2.6.32-25-server.
Unpacking linux-headers-2.6.32-25-server (from .../linux-headers-2.6.32-25-server_2.6.32-25.44_amd64.deb) ...
Preparing to replace linux-headers-server 2.6.32.24.25 (using .../linux-headers-server_2.6.32.25.27_amd64.deb) ...
Unpacking replacement linux-headers-server ...
Preparing to replace linux-server 2.6.32.24.25 (using .../linux-server_2.6.32.25.27_amd64.deb) ...
Unpacking replacement linux-server ...
Preparing to replace linux-image-server 2.6.32.24.25 (using .../linux-image-server_2.6.32.25.27_amd64.deb) ...
Unpacking replacement linux-image-server ...
Setting up linux-image-2.6.32-25-server (2.6.32-25.44) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-25-server
Running postinst hook script /usr/sbin/update-grub.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-25-server
Found initrd image: /boot/initrd.img-2.6.32-25-server
Found linux image: /boot/vmlinuz-2.6.32-24-server
Found initrd image: /boot/initrd.img-2.6.32-24-server
Found linux image: /boot/vmlinuz-2.6.32-23-server
Found initrd image: /boot/initrd.img-2.6.32-23-server
Found linux image: /boot/vmlinuz-2.6.32-21-server
Found initrd image: /boot/initrd.img-2.6.32-21-server
Found memtest86+ image: /memtest86+.bin
done

Setting up linux-headers-2.6.32-25 (2.6.32-25.44) ...
Setting up linux-headers-2.6.32-25-server (2.6.32-25.44) ...

Setting up linux-headers-server (2.6.32.25.27) ...
Setting up linux-image-server (2.6.32.25.27) ...
Setting up linux-server (2.6.32.25.27) ...

Unattended-upgrades log:
Initial blacklisted packages: munin munin-common munin-node munin-plugins-extra
Starting unattended upgrades script
Allowed origins are: ["['Ubuntu', 'lucid-security']", "['Ubuntu', 'lucid-updates']"]
Packages that are auto removed: ''
Packages that are upgraded: linux-server linux-headers-server linux-image-server
Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2010-09-28_06:27:47.787943.log'
All upgrades installed
----------

When I run digitemp, I get the following output:
$ digitemp_DS9097U -i -a -o"%F" -q -s /dev/ttyUSB0
Error 5: DS2480B Adapter Not Detected
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed

Here is the system info:
Ubuntu 10.04.1 LTS
Linux 2.6.32-25-server #44-Ubuntu SMP x86_64 GNU/Linux

digitemp:
  Installed: 3.5.0ds1-1
  Candidate: 3.5.0ds1-1
  Version table:
 *** 3.5.0ds1-1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message
NDLunchbox (ndlunchbox) wrote :

I removed digitemp via aptitude, it removed the old headers as un-needed...

$ sudo aptitude
(Reading database ... 97163 files and directories currently installed.)
Removing digitemp ...
Removing linux-headers-2.6.32-24-server ...
Removing linux-headers-2.6.32-24 ...
Processing triggers for man-db ...
Press return to continue.

I then reinstalled digitemp using apt-get but same problem exists.

affects: ubuntu → digitemp (Ubuntu)
Revision history for this message
NDLunchbox (ndlunchbox) wrote :

I've started a tread over at digitemp's support forum. They seem to think it is an issue with the serial port. Found here: http://groups.google.com/group/digitemp/browse_thread/thread/4e5d813877e9b62

Revision history for this message
NDLunchbox (ndlunchbox) wrote :

A few other users of digitemp on their support forum seem to confirm it no longer works on newer kernels. Based on when it broke, I think the change that killed it is somewhere in here: https://launchpad.net/ubuntu/+source/linux/2.6.32-25.44

This no longer seems to be platform related and likely the digitemp developers will need to fix this.

Should this bug be closed since it's really not Ubuntu or should we leave it open in case a fix is found and a new version needs to be uploaded to the repository?

Revision history for this message
NDLunchbox (ndlunchbox) wrote :

This appears to be a Debian related problem... somehow Digitemp can't talk to the COM port anymore...

Revision history for this message
Vince McIntyre (vmcintyr) wrote :

I am seeing exactly the same issue, on i386. I have the same version of digitemp, 3.5.0ds1-1.

I found a kernel commit which I think causes this, see LP#655868.

It's unclear if the kernel was wrong before and got fixed (so digitemp needs to be changed too)
or if the kernel change was wrong somehow.

These two bugs may be the same issue.

Revision history for this message
NDLunchbox (ndlunchbox) wrote :

Vince,
There are a few people working on this over on the digitemp google group linked above - including a small monetary reward for getting this sorted out. May be worth a look but I think you're onto what the problem is.

You question is the big one though - does the kernel need to be fixed or does digitemp (and other USB to Serial devices) need to be altered to conform to the new kernel...

Revision history for this message
NDLunchbox (ndlunchbox) wrote :

PS - I heard one report that it's working again on Ubuntu 10.10's kernel but cannot confirm since I want to keep my server on a LTS release.

Revision history for this message
NDLunchbox (ndlunchbox) wrote :

Fixed - latest kernel update (2.6.32-28) resolved the issue.

Changed in digitemp (Ubuntu):
status: New → Fix Released
assignee: nobody → NDLunchbox (ndlunchbox)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.