Linux 3.10+ Driver crash
  1 / 12    
I'm having issues with the nvidia Linux driver (both 319 and 325 beta) on my Lenovo IdeaPad Y500 laptop (MBG2BMH with GeForce GT650M GPU) running Arch Linux x64. When starting X, my screen goes black, my fan starts spinning at full speed and after a few seconds, the system dies (turns off, not cleanly). The issue started occurring after a kernel update to Linux 3.10. The nvidia driver for this kernel contains the unofficial patches (see [url]https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/nvidia&id=415c1daa9ccb1ec46c172b304f40929239d87af8[/url] for diff). X output: [code][ 49.888] (**) NVIDIA(0): Enabling 2D acceleration [ 56.164] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [ 56.164] (EE) NVIDIA(0): check your system's kernel log for additional error [ 56.164] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the [ 56.164] (EE) NVIDIA(0): README for additional information. [ 56.164] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! [ 56.164] (EE) NVIDIA(0): Failing initialization of X screen 0 [ 56.164] (II) UnloadModule: "nvidia" [ 56.164] (II) UnloadSubModule: "shadow" [ 56.164] (II) UnloadSubModule: "wfb" [ 56.164] (II) UnloadSubModule: "fb" [ 56.164] (EE) Screen(s) found, but none have a usable configuration.[/code] Kernel output: [code]Jul 25 16:02:20 nwa kernel: NVRM: GPU at 0000:01:00.0 has fallen off the bus. Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context! Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context! Jul 25 16:02:20 nwa kernel: NVRM: GPU at 0000:01:00.0 has fallen off the bus. Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context! Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context! Jul 25 16:02:20 nwa kernel: NVRM: RmInitAdapter failed! (0x25:0x28:1148) Jul 25 16:02:20 nwa kernel: NVRM: rm_init_adapter(0) failed[/code] Relevant topics: [url]https://bbs.archlinux.org/viewtopic.php?pid=1304291[/url] [url]https://bbs.archlinux.org/viewtopic.php?pid=1304141[/url]
I'm having issues with the nvidia Linux driver (both 319 and 325 beta) on my Lenovo IdeaPad Y500 laptop (MBG2BMH with GeForce GT650M GPU) running Arch Linux x64.

When starting X, my screen goes black, my fan starts spinning at full speed and after a few seconds, the system dies (turns off, not cleanly).

The issue started occurring after a kernel update to Linux 3.10.
The nvidia driver for this kernel contains the unofficial patches (see https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/nvidia&id=415c1daa9ccb1ec46c172b304f40929239d87af8 for diff).

X output:
[    49.888] (**) NVIDIA(0): Enabling 2D acceleration
[ 56.164] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
[ 56.164] (EE) NVIDIA(0): check your system's kernel log for additional error
[ 56.164] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
[ 56.164] (EE) NVIDIA(0): README for additional information.
[ 56.164] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
[ 56.164] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 56.164] (II) UnloadModule: "nvidia"
[ 56.164] (II) UnloadSubModule: "shadow"
[ 56.164] (II) UnloadSubModule: "wfb"
[ 56.164] (II) UnloadSubModule: "fb"
[ 56.164] (EE) Screen(s) found, but none have a usable configuration.


Kernel output:
Jul 25 16:02:20 nwa kernel: NVRM: GPU at 0000:01:00.0 has fallen off the bus.
Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context!
Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context!
Jul 25 16:02:20 nwa kernel: NVRM: GPU at 0000:01:00.0 has fallen off the bus.
Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context!
Jul 25 16:02:20 nwa kernel: NVRM: os_pci_init_handle: invalid context!
Jul 25 16:02:20 nwa kernel: NVRM: RmInitAdapter failed! (0x25:0x28:1148)
Jul 25 16:02:20 nwa kernel: NVRM: rm_init_adapter(0) failed


Relevant topics:
https://bbs.archlinux.org/viewtopic.php?pid=1304291
https://bbs.archlinux.org/viewtopic.php?pid=1304141

#1
Posted 07/26/2013 12:09 PM   
Experiencing the exact same issue on my Asus G75VX-T4066H, with GeForce GTX670MX gpu. Also running Arch Linux x64. The only difference for me is that my fans would not start spinning at full speed before my system dies, otherwise I am experiencing the exact same problem.
Experiencing the exact same issue on my Asus G75VX-T4066H, with GeForce GTX670MX gpu. Also running Arch Linux x64. The only difference for me is that my fans would not start spinning at full speed before my system dies, otherwise I am experiencing the exact same problem.

#2
Posted 07/26/2013 02:48 PM   
Same issue here with Linux 3.10-2, ArchLinux x64, and latest nvidia drivers. The GPU falling off the bus, on a Lenovo ThinkPad W530, every time we try to start X. My system does not overheat and shut down; it just stays on an unworkable black screen. Sometimes I can switch to a different TTY and Ctrl+Alt+Delete for reboot, sometimes I have a hard freeze (haven't tried SysRq yet). I do NOT use Optimus or Bumblebee -- I have set "discrete graphics" as the display option in the BIOS and the nvidia card is the only display exposed to the kernel. Downgrading to Linux 3.9 until this issue is resolved. Sad to see an nvidia release that doesn't support the latest kernel. :(
Same issue here with Linux 3.10-2, ArchLinux x64, and latest nvidia drivers. The GPU falling off the bus, on a Lenovo ThinkPad W530, every time we try to start X. My system does not overheat and shut down; it just stays on an unworkable black screen. Sometimes I can switch to a different TTY and Ctrl+Alt+Delete for reboot, sometimes I have a hard freeze (haven't tried SysRq yet).

I do NOT use Optimus or Bumblebee -- I have set "discrete graphics" as the display option in the BIOS and the nvidia card is the only display exposed to the kernel.

Downgrading to Linux 3.9 until this issue is resolved. Sad to see an nvidia release that doesn't support the latest kernel. :(

#3
Posted 07/26/2013 05:58 PM   
A comment on the Arch forums make me wonder if this is related to the problem experienced by those who use bumblebee. Many laptops now have motherboards that support the Optimus technology, despite not using it. I know that my particular Asus model was originally meant to ship with Optimus technology, although upon release it did not have it. I do assume that the motherboard still has support for it, despite it being deactivated or not used.
A comment on the Arch forums make me wonder if this is related to the problem experienced by those who use bumblebee. Many laptops now have motherboards that support the Optimus technology, despite not using it. I know that my particular Asus model was originally meant to ship with Optimus technology, although upon release it did not have it. I do assume that the motherboard still has support for it, despite it being deactivated or not used.

#4
Posted 07/26/2013 07:03 PM   
I am having the same problems (Lenovo IdeaPad Y500 with GeForce GT650M, Archlinux X86_64). The laptop does not have Optimus enabled. When I boot into a text console, all is fine, but when I start an X session or enable persistence mode using nvidia-smi, the screen goes blank, the fan goes up to full speed, and it automatically powers down after 20-30 seconds. Before it powers down, it is accessible via SSH. My logs are identical to TB's. I tested the nouveau drivers and they work fine.
I am having the same problems (Lenovo IdeaPad Y500 with GeForce GT650M, Archlinux X86_64).
The laptop does not have Optimus enabled. When I boot into a text console, all is fine, but when I start an X session or enable persistence mode using nvidia-smi, the screen goes blank, the fan goes up to full speed, and it automatically powers down after 20-30 seconds.
Before it powers down, it is accessible via SSH. My logs are identical to TB's.
I tested the nouveau drivers and they work fine.

#5
Posted 07/27/2013 10:17 AM   
Same problems, Lenovo Y500, 2x GT650M (SLi), text console working fine, starting X server turns the fan (s) to full speed and power goes down after a while.
Same problems, Lenovo Y500, 2x GT650M (SLi), text console working fine, starting X server turns the fan (s) to full speed and power goes down after a while.

#6
Posted 07/27/2013 10:36 AM   
I have to downgrade my kernel to 3.9.5-301. I got a new 802.11 ac driver. It requires to build driver with kernel source. The issue that 319.32 is incompatible with 3.10 kernel has been spotted for more than a month ago. NVIDIA need to speed up its patch update. I believe they don't get along well with open source society.
I have to downgrade my kernel to 3.9.5-301. I got a new 802.11 ac driver. It requires to build driver with kernel source.

The issue that 319.32 is incompatible with 3.10 kernel has been spotted for more than a month ago. NVIDIA need to speed up its patch update. I believe they don't get along well with open source society.

#7
Posted 07/28/2013 12:39 PM   
I am experiencing the same issue with a Clevo W150ER, NVIDIA GT 650M, linux-ck-ivybridge 3.10.3-1 on Arch. Why hasn't NVIDIA fixed this yet? I began to wonder if it was my fault as it has not been working for over a month. I hope they fix it soon. /twiddles thumbs
I am experiencing the same issue with a Clevo W150ER, NVIDIA GT 650M, linux-ck-ivybridge 3.10.3-1 on Arch. Why hasn't NVIDIA fixed this yet? I began to wonder if it was my fault as it has not been working for over a month. I hope they fix it soon. /twiddles thumbs

#8
Posted 07/29/2013 06:09 AM   
Hi. I have a Sager NP2096 (Based on Compal JHL90), and have a GeForce 9600M GT. Having the same log file in /var/lib/dkms/nvidia/319.32/build/make.log as OP. Haven't had this issue before, and I used to be able to use on 3.9.4 kernel, but that is broke now too. I think this has to do with nVidia driver, not the kernel.
Hi. I have a Sager NP2096 (Based on Compal JHL90), and have a GeForce 9600M GT.

Having the same log file in /var/lib/dkms/nvidia/319.32/build/make.log as OP.

Haven't had this issue before, and I used to be able to use on 3.9.4 kernel, but that is broke now too. I think this has to do with nVidia driver, not the kernel.

#9
Posted 07/30/2013 05:05 PM   
Same issue on ArchLinux x64, kernel 3.10 and nVidia drivers 319.32. It's a MSI GE60 laptop with nVidia GTX660M graphics card.
Same issue on ArchLinux x64, kernel 3.10 and nVidia drivers 319.32. It's a MSI GE60 laptop with nVidia GTX660M graphics card.

#10
Posted 07/30/2013 07:59 PM   
[quote="BonghornLeghorn"]Having the same log file in /var/lib/dkms/nvidia/319.32/build/make.log as OP.[/quote] I think you're mistaken. I did not post a dkms log and building succeeds for me, after applying the (unofficial) 3.10 patches that are going around.
BonghornLeghorn said:Having the same log file in /var/lib/dkms/nvidia/319.32/build/make.log as OP.


I think you're mistaken. I did not post a dkms log and building succeeds for me, after applying the (unofficial) 3.10 patches that are going around.

#11
Posted 08/01/2013 11:00 AM   
We internally file bug to track this issue for Y500 notebook bug id 1341332 .
We internally file bug to track this issue for Y500 notebook bug id 1341332 .

Thanks,
Sandip.

#12
Posted 08/01/2013 02:57 PM   
The issue is also present on Lenovo ThinkPad W530, although I don't think it's hardware-specific. The GPU "falls off bus" whenever trying to run anything with Bumblebee. It is also reported to be in switched off state by BBSwitch and I wasn't able to turn it on, not even through direct ACPI-call. Presumably this is caused by the patch, which allows drivers to be compiled for kernel 3.10.
The issue is also present on Lenovo ThinkPad W530, although I don't think it's hardware-specific. The GPU "falls off bus" whenever trying to run anything with Bumblebee. It is also reported to be in switched off state by BBSwitch and I wasn't able to turn it on, not even through direct ACPI-call.

Presumably this is caused by the patch, which allows drivers to be compiled for kernel 3.10.

#13
Posted 08/02/2013 01:21 AM   
Problem also had on Lenovo IdeaPad Y510P with GT 750M. I have tried the available patches for 325.08, 319.32 and 319.17, and have also tried downgrading to 3.9.9-1 kernel, and each combination of those, with no success. The patches allowed the module to compile but startx fails to execute, with the PCI:1:0:0 output referenced elsewhere. I have just invested HEAVILY in a full blown NVIDIA dual-card laptop JUST to avoid having video problems with Radeon, this is all much like the disappointment when I bought an Optimus/ION-containing laptop around 2010 and could never use Linux on it. Imagine buying a state of the art laptop, expecting it to run Linux games beautifully, and then not even being able to open X! Twice now, almost $2000 down the drain! NVIDIA, please consider open sourcing your drivers - you are a hardware vendor, not a software vendor!
Problem also had on Lenovo IdeaPad Y510P with GT 750M. I have tried the available patches for 325.08, 319.32 and 319.17, and have also tried downgrading to 3.9.9-1 kernel, and each combination of those, with no success. The patches allowed the module to compile but startx fails to execute, with the PCI:1:0:0 output referenced elsewhere.

I have just invested HEAVILY in a full blown NVIDIA dual-card laptop JUST to avoid having video problems with Radeon, this is all much like the disappointment when I bought an Optimus/ION-containing laptop around 2010 and could never use Linux on it. Imagine buying a state of the art laptop, expecting it to run Linux games beautifully, and then not even being able to open X! Twice now, almost $2000 down the drain!

NVIDIA, please consider open sourcing your drivers - you are a hardware vendor, not a software vendor!

#14
Posted 08/02/2013 04:07 AM   
[quote="sandipt"]We internally file bug to track this issue for Y500 notebook bug id 1341332 . [/quote] So does that mean we're going to get a reply when it's implemented, a status on it, or in some obscure update list?
sandipt said:We internally file bug to track this issue for Y500 notebook bug id 1341332 .


So does that mean we're going to get a reply when it's implemented, a status on it, or in some obscure update list?

#15
Posted 08/03/2013 09:26 PM   
  1 / 12    
Scroll To Top