[Raring] Laptop gets stuck when plugging in the power connector

[John Swing]

Hello,

I came up recently with a problem on my laptop (Raring amd64 fully updated) : each time I plug in the power connector in order to charge the laptop, it gets stuck and I can't do anything other than reboot. If the connector is already in when I boot there is no problem.

I don't know if reporting a bug against linux is the right thing to do but it seems that my problem had appeared with linux 3.7.0-7.15.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.7.0-7-generic 3.7.0-7.15
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic x86_64
ApportVersion: 2.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lucas 3765 F.... pulseaudio
Date: Tue Dec 18 03:45:12 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ef28e5f8-ea74-41e0-9b7e-0abbb05449da
InstallationDate: Installed on 2012-09-27 (81 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
MachineType: ASUSTeK COMPUTER INC. K55VD
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-7-generic root=UUID=aefd83bc-71cb-4509-8de1-d4ec1e62222e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.7.0-7-generic N/A
 linux-backports-modules-3.7.0-7-generic N/A
 linux-firmware 1.98
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VD.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.305:bd06/13/2012:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Rik Mills (rikmills)]

Similar problem here. Removing and plugging in the power connector causes my machine to lock up.

For me seems to be a regression between the 3.7RC8 and 3.7 final mainline releases, tested with builds from http://kernel.ubuntu.com/~kernel-ppa/mainline/

and equivalent results using raring 3.7.0-5 and 3.7.0-6 kernels, which exhibit regression with the RC8 to final rebase.

[Joseph Salisbury (jsalisbury)]

I will start a kernel bisect between v3.7-rc8 and v3.7 final. This will require testing 7 to 10 kernels. I'll post the first test kernel shortly.

[Joseph Salisbury (jsalisbury)]

I built the first test kernel, which is up to the following commit:
04c5decdc0aecde43bf44860484f26ee0691335f

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1091510

Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results.

Thanks in advance

[Rik Mills (rikmills)]

Further note: In my case, the problem was resolved by uninstalling the Jupiter power panel applet. Was obviously doing something incompatible with the recent kernel changes. I note that the applet did not need to be started or a user logged in, so seemed to be some tweak the install script for the applet had applied to power management on boot.

[John Swing (john-swing)]

Thanks Francis, problem resolved for me to by uninstalling the Jupiter Applet.

[John Swing (john-swing)]

How can I report the bug to the developpers of Jupiter ?

[John Swing (john-swing)]

It seems that they stop the development of Jupiter three days ago : http://www.fewt.com/2012/12/an-important-announcement-about-jupiter.html

[Rik Mills (rikmills)]

Well, it still could be a newly introduced bug in the linux kernel rather than a bug in jupiter that is the root cause here. However, with development on the applet halted it may be a somewhat mute point unless another application also exposes the same behaviour?

For reference, in case this does rear it's head in another form:

From testing the daily builds of the mainline kernel a few days back, my problem started with a commit some time after 27d7c2a006a81c04fab00b8cd81b99af3b32738d (built on 06/12/2012) and had appeared by the next days kernel build (07/12/2012) with commit 18a2f371f5edf41810f6469cb9be39931ef9deb9. So a commit somewhere in the pull requests merged for that intervening day caused my problem to show up.