E5420 Laptop freezes whilst charging and below 90% battery (approx) 13.04 12.04 10.04

Bug #1217367 reported by Karl Hunt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

My Dell Latitude E5420 hangs when the power cord is in and the battery is charging and below 90%. This bug has existed in 10.04 and every version since. There used to be a work around:

echo N> /sys/module/drm_kms_helper/parameters/poll

but this no longer works in raring ringtail. Also before 13.04 I was able to still barely use the system and perform the above command but now the system locks up entirely until the batter is removed.

I am currently using an up to date ringtail installation.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: karlhunt 2195 F.... pulseaudio
CRDA:
 country GB:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Tue Aug 27 14:29:46 2013
HibernationDevice: RESUME=UUID=8e3061b3-2966-432b-afcc-f8e5b61c4dde
InstallationDate: Installed on 2013-06-21 (67 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
Lsusb:
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
MachineType: Dell Inc. Latitude E5420
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=e2a067db-5091-4705-b366-5010191aa820 ro persistent quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-29-generic N/A
 linux-backports-modules-3.8.0-29-generic N/A
 linux-firmware 1.106
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0H5TG2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd04/20/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Karl Hunt (karlgeorgehunt-7) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Karl Hunt (karlgeorgehunt-7) wrote :

I noticed that during boot I get the message "Disabling IRQ 16" so checked out debugging IRQ porblems.

https://help.ubuntu.com/community/DebuggingIRQProblems

I tried all of the examples and none had any effect except irqpoll which allowed the mouse to move but the rest of the system still locked up.

I did however notice that in 13.04 the lock up does not start until login. If I leave the machine at the login screen it is ok (mouse and keyboard input is ok and menus work fine with no lag). Shortly after logging in however the machine completely locks up and needs either the battery or power cord taking out to "fix"

Revision history for this message
Karl Hunt (karlgeorgehunt-7) wrote :

To add to my previous comment:

However if I log out again without the battery or cord then plug it back in whilst on the login screen it locks up immediately.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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".

Thanks in advance.

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Karl Hunt (karlgeorgehunt-7) wrote :

Firstly.....
Oh My God! this bug has plagued me for 2 years!

But now I can confirm that it is fixed upstream.

I installed 3.11.0-031100rc7-generic and now the issue is completely resolved!

The only issues I have now are related to kernel modules not being compatible with this kernel for example vritualbox but I will tackle this in the virtualbox forums.

Will this be the first kernel available in saucy?

Plus how to I add the tag 'kernel-fixed-upstream' to this bug?

Thanks again.

description: updated
Revision history for this message
Karl Hunt (karlgeorgehunt-7) wrote :

I have now added the tag 'kernel-fixed-upstream'

tags: added: kernel-fixed-upstream
Revision history for this message
penalvch (penalvch) wrote :

Karl Hunt, as per http://www.dell.com/support/troubleshooting/us/en/19/Product/latitude-e5420 an update is available for your BIOS (A13). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Thank you for your understanding.

tags: added: bios-outdated-a13 lucid precise
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.