[Optimus] - Bumblebee problem after upgrade

ksolsim · 2013-06-29 19:28:38

After today's upgrade (bbswitch-0.7-4 cups-filters-1.0.35-1 linux-3.9.8-1 linux-headers-3.9.8-1 lirc-utils-1:0.9.0-49 man-db-2.6.5-1 nvidia-319.32-2 nvidia-utils-319.32-1) seems that bumblebee has some problems.

[ksolsim@arch ~]$ optirun --status
Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.

and if I try an application, e.g. kate (or any other application):

[ksolsim@arch ~]$ optirun kate

application starts, but if I do "optirun --status" again I get:

[ksolsim@arch ~]$ optirun --status
Bumblebee status: Error (3.2.1): [XORG] (EE) Server terminated successfully (0). Closing log file.

And the only way to return to normality is:

[root@arch ksolsim]$ systemctl restart bumblebeed.service

Does anyone have any ideas on how to overcome this?

Last edited by ksolsim (2013-06-29 19:52:21)

ksolsim · 2013-07-25 15:42:27

Problem still exists. Am I the only one with this problem?

Cthulhu82 · 2013-07-26 10:50:26

I can reproduce your problem, but it doesn't seem to prevent bumblebee from running correctly, as I obtain this after closing an application started with optirun or primusrun :

$ cat /proc/acpi/bbswitch
0000:01:00.0 OFF

and it was ON when the application was running.

Cthulhu82 · 2013-07-26 10:54:07

I saw on Bumblebee launchpad that it has been reported as a bug (by you, I imagine ), so let's see what they say.

Faither · 2013-07-26 14:20:02

I have the exact same problem here after the update.

dmesg during boot:
[    0.258300] pci 0000:01:00.0: [10de:0fd1] type 00 class 0x030000
[    0.258311] pci 0000:01:00.0: reg 10: [mem 0xd2000000-0xd2ffffff]
[    0.258321] pci 0000:01:00.0: reg 14: [mem 0xa0000000-0xafffffff 64bit pref]
[    0.258331] pci 0000:01:00.0: reg 1c: [mem 0xb0000000-0xb1ffffff 64bit pref]
[    0.258338] pci 0000:01:00.0: reg 24: [io  0x4000-0x407f]
[    0.258345] pci 0000:01:00.0: reg 30: [mem 0xfff80000-0xffffffff pref]
[    0.258394] pci 0000:01:00.0: System wakeup disabled by ACPI
[    0.285051] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
[    0.285053] vgaarb: bridge control possible 0000:01:00.0
[    0.304359] pci 0000:01:00.0: no compatible bridge window for [mem 0xfff80000-0xffffffff pref]
[    0.304398] pci 0000:01:00.0: BAR 6: assigned [mem 0xb2000000-0xb207ffff pref]
[    1.007250] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[    1.007618] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x0e7110a2
[    1.007620] nouveau  [  DEVICE][0000:01:00.0] Chipset: GK107 (NVE7)
[    1.007621] nouveau  [  DEVICE][0000:01:00.0] Family : NVE0
[    1.009056] nouveau  [   VBIOS][0000:01:00.0] checking PRAMIN for image...
[    1.057249] nouveau  [   VBIOS][0000:01:00.0] ... signature not found
[    1.057251] nouveau  [   VBIOS][0000:01:00.0] checking PROM for image...
[    1.057333] nouveau  [   VBIOS][0000:01:00.0] ... signature not found
[    1.057334] nouveau  [   VBIOS][0000:01:00.0] checking ACPI for image...
[    5.847131] nouveau  [   VBIOS][0000:01:00.0] ... appears to be valid
[    5.847136] nouveau  [   VBIOS][0000:01:00.0] using image from ACPI
[    5.847349] nouveau  [   VBIOS][0000:01:00.0] BIT signature found
[    5.847352] nouveau  [   VBIOS][0000:01:00.0] version 80.07.24.00.70
[    5.847762] nouveau  [ DEVINIT][0000:01:00.0] adaptor not initialised
[    5.847766] nouveau  [   VBIOS][0000:01:00.0] running init tables
[    5.971527] nouveau  [     PFB][0000:01:00.0] RAM type: DDR3
[    5.971529] nouveau  [     PFB][0000:01:00.0] RAM size: 2048 MiB
[    5.971530] nouveau  [     PFB][0000:01:00.0]    ZCOMP: 0 tags
[    5.999162] nouveau  [  PTHERM][0000:01:00.0] FAN control: none / external
[    5.999167] nouveau  [  PTHERM][0000:01:00.0] fan management: disabled
[    5.999178] nouveau  [  PTHERM][0000:01:00.0] internal sensor: yes
[   21.305455] vgaarb: transferring owner from PCI:0000:00:02.0 to PCI:0000:01:00.0
[   26.120572] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[   26.120704] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[   26.147966] pci 0000:01:00.0: power state changed by ACPI to D3cold

dmesg after I try to start something on the discrete card:

[  157.432383] bbswitch: enabling discrete graphics
[  157.849342] pci 0000:01:00.0: power state changed by ACPI to D0
[  157.916183] nvidia: module license 'NVIDIA' taints kernel.
[  157.916187] Disabling lock debugging due to kernel taint
[  157.921102] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[  157.921267] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
[  157.921272] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  319.32  Wed Jun 19 15:51:20 PDT 2013
[  163.245099] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[  163.245109] NVRM: os_pci_init_handle: invalid context!
[  163.245112] NVRM: os_pci_init_handle: invalid context!
[  163.245117] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
[  163.245122] NVRM: os_pci_init_handle: invalid context!
[  163.245123] NVRM: os_pci_init_handle: invalid context!
[  163.265202] NVRM: RmInitAdapter failed! (0x25:0x28:1148)
[  163.265209] NVRM: rm_init_adapter(0) failed

 
Xorg.8.log
[   163.076] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
[   163.076] (EE) NVIDIA(0):     check your system's kernel log for additional error
[   163.076] (EE) NVIDIA(0):     messages and refer to Chapter 8: Common Problems in the
[   163.076] (EE) NVIDIA(0):     README for additional information.
[   163.076] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
[   163.076] (EE) NVIDIA(0): Failing initialization of X screen 0

Works/ed fine on 3.9.9

Malstrond · 2013-07-26 17:27:23

Same problem struck me too today after upgrading the following:

upgraded linux (3.9.9-1 -> 3.10.2-1)
upgraded bbswitch (0.7-4 -> 0.7-6)
upgraded git (1.8.3.3-1 -> 1.8.3.4-1)
upgraded harfbuzz (0.9.18-1 -> 0.9.19-1)
upgraded lirc-utils (1:0.9.0-49 -> 1:0.9.0-52)
upgraded nvidia (319.32-2 -> 319.32-4)

gsgleason · 2013-08-04 23:21:44

My bumblebee stopped working as well recently. I'm not sure which update did it, but it certainly was working before.

I have a Thinkpad W530 with 3rd gen i7

$ lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1000M] (rev ff)

$ optirun -vvv glxinfo
[   30.953455] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[   30.953870] [DEBUG]optirun version 3.2.1 starting...
[   30.953891] [DEBUG]Active configuration:
[   30.953896] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[   30.953900] [DEBUG] X display: :8
[   30.953903] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
[   30.953906] [DEBUG] Socket path: /var/run/bumblebee.socket
[   30.953909] [DEBUG] Accel/display bridge: auto
[   30.953913] [DEBUG] VGL Compression: proxy
[   30.953916] [DEBUG] VGLrun extra options: 
[   30.953919] [DEBUG] Primus LD Path: /usr/lib/primus:/usr/lib32/primus
[   30.953994] [DEBUG]Using auto-detected bridge virtualgl
[   38.860391] [INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
[   38.860405] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
[   38.860409] [DEBUG]Socket closed.
[   38.860422] [ERROR]Aborting because fallback start is disabled.
[   38.860426] [DEBUG]Killing all remaining processes.

bumblebee 3.2.1-3
intel-dri 9.1.6-1
lib32-mesa 9.1.6-1
lib32-mesa-libgl 9.1.6-1
mesa 9.1.6-1
mesa-demos 8.1.0-1
mesa-libgl 9.1.6-1
nvidia 319.32-4
nvidia-utils 319.32-1
xf86-video-intel 2.21.13-1

Last edited by gsgleason (2013-08-04 23:22:52)

Faither · 2013-08-13 12:22:56

Problem still present with all 3.10.x Kernels and Nvidia 325 rebuilds

Also tried a fresh install to see if I somehow messed up the configuration files.

lspci -nn

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev ff)

Selo · 2013-08-13 18:04:36

This is nVidia's f*ck up, we have to downgrade or wailt for a fix. Same issue is discussed here

https://bbs.archlinux.org/viewtopic.php?id=167195

and here

https://devtalk.nvidia.com/default/topi … ver-crash/

Arch Linux

#1 2013-06-29 19:28:38

[Optimus] - Bumblebee problem after upgrade

#2 2013-07-25 15:42:27

Re: [Optimus] - Bumblebee problem after upgrade

#3 2013-07-26 10:50:26

Re: [Optimus] - Bumblebee problem after upgrade

#4 2013-07-26 10:54:07

Re: [Optimus] - Bumblebee problem after upgrade

#5 2013-07-26 14:20:02

Re: [Optimus] - Bumblebee problem after upgrade

#6 2013-07-26 17:27:23

Re: [Optimus] - Bumblebee problem after upgrade

#7 2013-08-04 23:21:44

Re: [Optimus] - Bumblebee problem after upgrade

#8 2013-08-13 12:22:56

Re: [Optimus] - Bumblebee problem after upgrade

#9 2013-08-13 18:04:36

Re: [Optimus] - Bumblebee problem after upgrade

Board footer