[Dell Studio 1537] No sensors and fan control if there is no battery present on wakeup from suspend

Bug #575030 reported by Filip Milivojevic
54
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Sensors and fan control don't work when this laptop wakes up from suspend if there is no battery inserted.
When there is battery present, everything works normally.

After resume with battery:
$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +46.0°C (crit = +100.0°C)
temp2: +44.0°C (crit = +100.0°C)
temp3: +0.0°C (crit = +100.0°C)

After resume with no battery:
$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +0.0°C (crit = +100.0°C)
temp2: +0.0°C (crit = +100.0°C)
temp3: +0.0°C (crit = +100.0°C)

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic-pae 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: slobodan 9900 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc700000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:111d7675,1028029f,00100103 HDA:80862802,80860101,00100000'
   Controls : 20
   Simple ctrls : 11
Date: Tue May 4 12:02:49 2010
HibernationDevice: RESUME=UUID=79a9e06f-a05f-43df-8d7c-d30198690c33
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
MachineType: Dell Inc. Studio 1537
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=0169a1e6-b426-410c-ae0f-ee0916b59827 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: dell-wifi: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 05/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0P173H
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A09
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/27/2009:svnDellInc.:pnStudio1537:pvrA09:rvnDellInc.:rn0P173H:rvrA09:cvnDellInc.:ct8:cvrA09:
dmi.product.name: Studio 1537
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.

Revision history for this message
Filip Milivojevic (zekica) wrote :
Revision history for this message
Pfanne (pfannenwender) wrote :

Can confirm this bug on the dell studio 1555.

Revision history for this message
Andy Whitcroft (apw) wrote :

I can confirm that this affects my Dell 1537 also. I would note that if you suspend/remove battery/resume sensors (and presuably fan control) are broken. If you then reinsert the battery live, the sensors are restored.

Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Andy Whitcroft (apw) wrote :

@Filip, @Pfanne, could you confirm that reinserting and removing the battery while the machine is awake restores your sensors too. Marking this Low as there seems to be a pretty simple, safe work around.

Revision history for this message
Andy Whitcroft (apw) wrote :

Ok further testing seems to indicate that remove battery/suspend/resume will also trigger this. That is a resume with no battery present leads to this issue, and reinserting it is enough to restore functionality (removing it again does not re-break sensors). If those who are affected could confirm that removing the battery live and then s/r breaks things too and that re-inserting and even removing it leaves them restored. If they (and I strongly suspect they will) then I at least have a good handle on the symptoms.

Revision history for this message
Filip Milivojevic (zekica) wrote :

Yes, if I reinsert the battery after wakeup, sesors/fan control is restored.

Revision history for this message
Filip Milivojevic (zekica) wrote :

Also, it doesn't matter if I remove battery before or after suspend, exactly as you have described.

Revision history for this message
Andy Whitcroft (apw) wrote :

I have just tested the same machine with a karmic kernel, userspace unchanged and this does not appear to occur. Marking a release regression.

Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
Revision history for this message
Jose Martin (jose.martin) wrote :

Same behavior with the Studio XPS 1640, also, the battery workaround works.

Revision history for this message
Slobodan Milivojevic (poglavica) wrote :

Is there any progress on resolving this issue? It has been almost two months since this bug was reported, and there haven't been any updates on this.

Revision history for this message
Ward (wpoely86) wrote :

With the an up to date system and the 10.6 ati drivers, everything works fine on my studio 1537.

Revision history for this message
jpph (jpprudhomme) wrote :

With Maverick and kernel "2.6.35-24-generic #42-Ubuntu SMP", I have the same issue on a studio 1737.
After resume when battery unplugged, the fan doesn't work and sensors report 0°c

Revision history for this message
penalvch (penalvch) wrote :

Filip Milivojevic, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
assignee: Andy Whitcroft (apw) → nobody
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.