System hangs after the power cord is plugged/unplugged

[Serghei Zagorinyak]

When I plug / unplug the power cord on my hp6735b the screen goes white and the system hangs.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: svz 1528 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0x96500000 irq 16'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30ee,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 18
   Simple ctrls : 11
Date: Sun May 2 16:05:04 2010
HibernationDevice: RESUME=UUID=55f01cdb-3b92-4dbc-bb29-07b9f6308986
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 pan0 no wireless extensions.
MachineType: Hewlett-Packard HP Compaq 6735b
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=2caa93a1-6045-4418-9db2-de963bb88c3f ro quiet splash
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 06/27/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GTT Ver. F.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30E3
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.1C
dmi.chassis.asset.tag: CNU8352JLT
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68GTTVer.F.05:bd06/27/2008:svnHewlett-Packard:pnHPCompaq6735b:pvrF.05:rvnHewlett-Packard:rn30E3:rvrKBCVersion96.1C:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6735b
dmi.product.version: F.05
dmi.sys.vendor: Hewlett-Packard

[Jeremy Foshee (jeremyfoshee)]

Hi Serghei,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Serghei Zagorinyak (serghei-zag)]

I`ve switched to i386 kernel. No such problem there. In amd-64 the problem was gone after the activation of ATI proprietary driver, though it still can't adjust screen brightness. Unfortunately, I can't test the upstream kernels right away.

[u2ix (u2ix)]

I have the same laptop and sadly I get the same problem.
As Jeremy advices I installed the daily build of the kernel (linux-image-2.6.35-999-generic_2.6.35-999.201007211008_amd64.deb 21-Jul-2010).
So that resolved the problem.

But It seams that there are less modules so my Wlan stopped working now.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]