[Nvidia GF117M] 10de:1140 3D Controller disapear after reboot

Bug #1316095 reported by Yung Shen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
Alberto Milone
nvidia-prime (Ubuntu)
Invalid
Undecided
Alberto Milone

Bug Description

Unable to switch back to nvidia graphic chip after reboot. Switching graphics does not requires reboot, but it does cause issue when user had to reboot for some reason, and will not able to use nvidia graphic until reboot.

Step to reproduce: Switch to intel integrated graphic driver first if you were not,
open nvidia settings from dash or use following command:
sudo prime-select intel && sudo reboot now

Expected result: Able to switch back to nvidia graphic chip using nvidia settings.

Actuall result: unable to swich back to nvidia driver, the 3D controller disapeared in pci list. nvidia-settings will give you empty warning prompt, checking from console gives you unkown result:
sudo prime-select query
unknown

WORKAROUND: Shutdown the system then turn on, the 3D controller will be back.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic]
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1750 F.... pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Mon May 5 07:02:04 2014
HibernationDevice: RESUME=UUID=c19bacd6-a604-4c9b-9a21-5d0a2d9cef5c
InstallationDate: Installed on 2014-04-29 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Vostro 5460
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=15cbb6aa-65e8-4596-be71-2ff7431000be ro rootdelay=60 quiet splash initcall_debug
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: TIE3C2
dmi.board.vendor: Dell Inc.
dmi.board.version: X00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/04/2013:svnDellInc.:pnVostro5460:pvr:rvnDellInc.:rnTIE3C2:rvrX00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Vostro 5460
dmi.sys.vendor: Dell Inc.

Revision history for this message
Yung Shen (kaxing) 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
Yung Shen (kaxing) wrote :
description: updated
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.15 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.15-rc4-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Yung Shen (kaxing)
tags: added: kernel-bug-exists-upstream
Ara Pulido (ara)
tags: added: blocks-hwcert-enablement
Yung Shen (kaxing)
Changed in nvidia-prime (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
Revision history for this message
Alberto Milone (albertomilone) wrote :

This is a regression in the kernel I'm working on (we have a private report about it too)

Changed in linux (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Alberto Milone (albertomilone)
importance: Medium → High
Changed in nvidia-prime (Ubuntu):
status: New → Invalid
penalvch (penalvch)
tags: added: latest-bios-a07 regression-potential
tags: added: needs-bisect regression-release
removed: regression-potential
description: updated
tags: added: kernel-bug-exists-upstream-3.15-rc4
removed: kernel-bug-exists-upstream
Revision history for this message
Alberto Milone (albertomilone) wrote :

Actually, the regression I mentioned turned out to be only a false positive.

I can't reproduce the problem on my system, therefore I'll need your help to debug the problem.

1) Please enable nvidia and reboot.

2) Then switch to intel, reboot, and attach the following files:
a) output of dmesg
b) /var/log/gpu-manager.log

3) Finally switch back to nvidia and log out (to reproduce the issue), and attach the following files:
a) output of dmesg
b) /var/log/gpu-manager.log
c) the output of "update-alternatives --display x86_64-linux-gnu_gl_conf"
d) /var/log/Xorg.0.log

Revision history for this message
Yung Shen (kaxing) wrote :

Hello Alberto,

I cannot follow your steps from 2 to 3, since 3D controller will disappear, it is not able to switch back to nvidia.

In between step 2 and 3, I have to shutdown the system first in order to bring back nvidia controller.

My steps:

1. Enable nvidia driver then reboot

2. Switching to intel then reboot

3. Shutdown the system (because nvidia controller is missing)

4. Switch back to nvidia, prime-select nvidia && logout

Revision history for this message
Alberto Milone (albertomilone) wrote :

I think this is a system specific issue (it depends on the BIOS). Quoting Bbswitch's documentation:

On some machines, turning off the card is permanent and the card does not reappear on subsequents reboots, which can result into the screen staying black all the time, including the BIOS screen. If it occurs, first try to shutdown, unplug power cord, remove battery, wait 30s, then put everything back in and boot. If it's not solved, then the solution is to reset the BIOS to factory settings. Before executing bbswitch for the first time, it is therefore recommended to take note of the full key sequence in the BIOS to do a reset.

source: https://github.com/Bumblebee-Project/bbswitch

On shutdown bbswitch is unloaded and should switch the discrete card back on, but apparently this doesn't work on this specific system.

Changed in linux (Ubuntu):
status: In Progress → Won't Fix
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.