sis 672 laptop doesn't shuts down successfully if the charger is plugged in

[Max Payne]

My laptop doesn't shuts down successfully while the charger is plugged in, if I unplug the charger the laptop shuts down successfully, whereas with the charger the image disappears but the power led stays on and I can hear the computer working. "sudo halt" and "sudo shutdown -h now" reproduce this bug. Restart works fine. This bug occurs in Natty, Oneiric and Precise.

WORKAROUND:sudo poweroff

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SIS966 [HDA SIS966], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ana 1386 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SIS966'/'HDA SIS966 at 0xd8100000 irq 18'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,15580801,00100101'
   Controls : 23
   Simple ctrls : 13
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=06efff09-955a-4ceb-9647-c48a702a8a5d
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
MachineType: Phoenix/SiS M7x0S
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-generic root=UUID=05dc832b-2b89-47b2-aba3-3342cfa65e47 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-2-generic N/A
 linux-backports-modules-3.2.0-2-generic N/A
 linux-firmware 1.68
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.2.0-2-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-01-25 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/28/0892
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.asset.tag: 1234567890
dmi.board.name: M7x0S
dmi.board.vendor: SiS
dmi.board.version: Bottom
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SiS
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/28/0892:svnPhoenix/SiS:pnM7x0S:pvrRev.A1:rvnSiS:rnM7x0S:rvrBottom:cvnSiS:ct1:cvrN/A:
dmi.product.name: M7x0S
dmi.product.version: Rev. A1
dmi.sys.vendor: Phoenix/SiS

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 921380

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

apport information

[Max Payne (dj-max-payne)]

I ran the command you asked and authorized the computer to access my launchpad account, don't know if you received the report though.

  BTW: before shutting down successfully or not, my laptop screen flashes alot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

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'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/

[Max Payne (dj-max-payne)]

I installed the file "linux-image-3.2.0-030200-generic_3.2.0-030200.201201042035_amd64.deb" I hope this was what you wanted me to do.

And when I boot grub says Ubunto with linux 3.2.0-030200 or something like that.

The bug stays unchanged, even did a couple of shutdown attempts just to be sure.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Max Payne (dj-max-payne)]

After updating and restarting, the first shutdown attempt went well, the other two I've made after however were not, have no idea why it worked once.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Max Payne (dj-max-payne)]

Sorry for having said nothing lately, I've been really busy with college exams.
How do I report this bug upstream ?

[Khalid Akbar (khalidakbar)]

This also affects my Toshiba Satellite C855-18D running Ubuntu 12.0.4.1.

sudo poweroff does not work for me, but suspend does. The laptop only switches of on shutdown when the ac power cable is detached.

[penalvch (penalvch)]

Max Payne, 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>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc5

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.

[Launchpad Janitor (janitor)]

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