10de:0a3c shutdown command does not power off the machine Quadro FX 880M

[Unseen]

While using nvidia-current, If I try to shutdown the machine, it goes to a black screen, backlight still on and nothing happens anymore. The before suggested acpi=force did not help unfortunately.
The problem started after the update from 12.04 -> 12.10

Ok, so I uninstalled nvidia-current and virtual box, and installed the mainline
uname -r
3.7.0-030700rc1-generic

With the mainline shutdown seemed to work ok.

WORKAROUND: Use nouveau. I then uninstalled the mainline and reinstalled the ubuntu default kernel (without nvidia-current):
uname -r
3.5.0-17-generic

With this, the shutdown worked as well.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: unseen 2183 F.... pulseaudio
 /dev/snd/controlC0: unseen 2183 F.... pulseaudio
 /dev/snd/pcmC0D0p: unseen 2183 F...m pulseaudio
Date: Sun Oct 21 23:33:50 2012
HibernationDevice: RESUME=UUID=2ded6111-76a4-427c-ae8d-9946bee15ed3
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: LENOVO 4389W1B
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=d9c6a793-9462-4a60-8afb-07b11c9a72a6 ro quiet splash acpi=force
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-10-20 (1 days ago)
dmi.bios.date: 02/24/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET76WW (1.37 )
dmi.board.name: 4389W1B
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6NET76WW(1.37):bd02/24/2011:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4389W1B
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO

[penalvch (penalvch)]

Unseen, thank you for reporting this and helping make Ubuntu better. 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 kernel in the mainline kernels archive directory daily 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.7-rc1-quantal

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Unseen (unseen-mail)]

I tried installing the mainline kernel, but received an error from the nvidia current driver module:

unseen@shodan-mobile:~/Downloads$ ll *.deb
-rw-rw-r-- 1 unseen unseen 918062 Oct 22 11:42 linux-headers-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210161007_amd64.deb
-rw-rw-r-- 1 unseen unseen 12333938 Oct 22 11:42 linux-image-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210161007_amd64.deb
-rw-rw-r-- 1 unseen unseen 25303150 Oct 22 11:43 linux-image-extra-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210161007_amd64.deb
unseen@shodan-mobile:~/Downloads$ sudo dpkg -i *.deb
[sudo] password for unseen:
Selecting previously unselected package linux-headers-3.7.0-030700rc1-generic.
(Reading database ... 199917 files and directories currently installed.)
Unpacking linux-headers-3.7.0-030700rc1-generic (from linux-headers-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210161007_amd64.deb) ...
Selecting previously unselected package linux-image-3.7.0-030700rc1-generic.
Unpacking linux-image-3.7.0-030700rc1-generic (from linux-image-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210161007_amd64.deb) ...
Done.
Selecting previously unselected package linux-image-extra-3.7.0-030700rc1-generic.
Unpacking linux-image-extra-3.7.0-030700rc1-generic (from linux-image-extra-3.7.0-030700rc1-generic_3.7.0-030700rc1.201210161007_amd64.deb) ...
dpkg: dependency problems prevent configuration of linux-headers-3.7.0-030700rc1-generic:
 linux-headers-3.7.0-030700rc1-generic depends on linux-headers-3.7.0-030700rc1; however:
  Package linux-headers-3.7.0-030700rc1 is not installed.

dpkg: error processing linux-headers-3.7.0-030700rc1-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-3.7.0-030700rc1-generic (3.7.0-030700rc1.201210161007) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.7.0-030700rc1-generic /boot/vmlinuz-3.7.0-030700rc1-generic
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
    import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.7.0-030700rc1-generic (x86_64)
Consult /var/lib/dkms/nvidia-current/304.43/build/make.log for more information.
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
    import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.7.0-030700rc1-generic (x86_64)
Consult /var/lib/dkms/vboxhost/4.2.2/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.7.0-030700rc1-generic /boot/vmlinuz-3.7.0-030700rc1-generic
update-initramfs: Generating /boot/initrd.img-3.7.0-030700rc1-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.7.0-030700rc1-generic /boot/vmlinuz-3.7.0-030700rc1-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.7.0-030700rc1-generic /boot/vmlinuz-3.7.0-030700rc1-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.7.0-030700rc1-generic /boot/vmlinuz-3.7.0-030...

[Unseen (unseen-mail)]

Add on to the above post: this is the content of the /var/lib/dkms/vboxhost/4.2.2/build/make.log :

DKMS make.log for nvidia-current-304.43 for kernel 3.7.0-030700rc1-generic (x86_64)
Mon Oct 22 19:43:48 CEST 2012
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1

[Unseen (unseen-mail)]

Arg sry, was too fast, the above one was from the nvidia, and the virtual box one it this:

DKMS make.log for vboxhost-4.2.2 for kernel 3.7.0-030700rc1-generic (x86_64)
Mon Oct 22 19:43:48 CEST 2012
make: Entering directory `/usr/src/linux-headers-3.7.0-030700rc1-generic'
make: Makefile: No such file or directory
make: *** No rule to make target `Makefile'. Stop.
make: Leaving directory `/usr/src/linux-headers-3.7.0-030700rc1-generic'

[penalvch (penalvch)]

Unseen, could you please uninstall virtualbox and nvidia drivers, and then try the mainline?

[Unseen (unseen-mail)]

Ok, so I uninstalled nvidia-current and virtual box and installed the mainline.

Version:

unseen@shodan-mobile:~$ uname -r
3.7.0-030700rc1-generic

With the mainline shutdown seemed to work ok.

I then uninstalled the mainline and reinstalled the ubuntu default kernel (without nvidia-current):

Current Version:

unseen@shodan-mobile:~$ uname -r
3.5.0-17-generic

With this, the shutdown worked as well.

I then reinstalled the nvidia-current driver, and shutdown was immidiatly broken again.

[Unseen (unseen-mail)]

Hi, I saw you updated the description with a workaround. This may work for most people, but it doesnt for the Lenovo W510 it seems ...

Using the nouveau breaks other things, e.g. CUDA and dual-monitoring. I can mirror the screen with the nouveau, but expanding the desktop to the second screen freezes the system. This works just fine with the nvidia driver. So it seems to be an issue with nouveau.

[penalvch (penalvch)]

Unseen, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1069551/comments/8 :
>"Using the nouveau breaks other things, e.g. CUDA and dual-monitoring. I can mirror the screen with the nouveau, but expanding the desktop to the second screen freezes the system. This works just fine with the nvidia driver. So it seems to be an issue with nouveau."

It is understood that nouveau is not a WORKAROUND for the other problems you mentioned. However, this bug report is only focused on the one problem of how the shutdown command does not power off the machine using nvidia-current.

Each of your other problems would require a separate report, one report per problem:
1) I can mirror the screen with the nouveau, but expanding the desktop to the second screen freezes the system.
2) Using nouveau, CUDA does not work.

You are welcome to file each one via a terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thank you for your understanding.

[penalvch (penalvch)]

Due to how this issue is reproducible with nvidia-current, and not without/using nouveau, moving package to nvidia-current. Please send back if deemed a kernel issue.

Thank you for your understanding.

[penalvch (penalvch)]

Unseen, instead of using nvidia-current, does nvidia-current-updates also have the same problem?

[Unseen (unseen-mail)]

This is more related to the nvidia driver, so switching over from kernel makes sense...

The nvidia-current-updates unfortunately behaves exactly as nvidia-current, so it doesn't work.

Current version at the moment of writing: 304.51-0ubuntu1

Anything else I can provide? :-)

About the issues with nouveau: I think someone who acually uses it should report it, since I need this computer alot, alos for work stuff and I don't want to switch drivers all the time. Besides I think its a general thing that CUDA needs nvidia drivers ;-) Sry.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joni-Pekka Kurronen (joni-kurronen)]

3.2.0-38-generic + nvidia from NVIDIA directly and build
processor FX8150
AsRock FX990me mainboard

I have tried lot experiments but:

a) sudo shutdown -P now
b) computer goes down but start's immediately power off

I supposed problem is somwhere ACPI and "wakenLan" , wake by device,...
  and diabled all :
joni@mpi1:/mpi3$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PC02 S4 *disabled pci:0000:00:02.0
PC04 S4 *disabled
PC05 S4 *disabled pci:0000:00:05.0
PC06 S4 *disabled
PC09 S4 *disabled
PC0A S4 *disabled pci:0000:00:0a.0
PC0B S4 *disabled
PC0D S4 *disabled
SBAZ S4 *disabled pci:0000:00:14.2
UAR1 S4 *disabled pnp:00:0c
P0PC S4 *disabled pci:0000:00:14.4
UHC1 S4 *disabled pci:0000:00:12.0
UHC2 S4 *disabled pci:0000:00:12.2
USB3 S4 *disabled pci:0000:00:13.0
UHC4 S4 *disabled pci:0000:00:13.2
USB5 S4 *disabled pci:0000:00:16.0
UHC6 S4 *disabled pci:0000:00:16.2
UHC7 S4 *disabled pci:0000:00:14.5
PE20 S4 *disabled
PE21 S4 *disabled
joni@mpi1:/mpi3$

AND IT DO NOT HELP,...

could it realted whit this change ??? ,... http://www.spinics.net/lists/linux-usb/msg53661.html

[penalvch (penalvch)]

Joni-Pekka Kurronen, if you have a bug in Ubuntu, the Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the Ubuntu X.Org team (maintainers of nvidia-graphics-drivers), Ubuntu Bug Control team, and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[dino99 (9d9)]

That version is no more supported; please open a new bug report if the actual archive found version also has the same issue.