[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-12 Thread Sayantan Das
Hi Christopher,

I have tried the follwowing Nvidia drivers

nvidia-304, nvida-331, nvidia-334 and nvidia-337. All of them fail.
Yesterday I tried  setting nouveau in the bumblebee.conf
the moment i restart bumblebee, I get a call trace in the log and the system 
crashes after sometime.


** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-12 Thread Christopher M. Penalver
Sayantan Das, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked.

Thank you for your understanding.

** Changed in: linux (Ubuntu)
   Status: Confirmed = Triaged

** Summary changed:

- running bumblebee in Ubuntu 14.04 results in call trace in logs
+ [Dell Vostro 3300] running bumblebee in Ubuntu 14.04 results in call trace in 
logs

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  [Dell Vostro 3300] running bumblebee in Ubuntu 14.04 results in call
  trace in logs

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
  

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-10 Thread Sayantan Das
Hi Christopher,

I have tested this with upstream kernel version 3.14.1. I get the same
error. Do I need to test with 3.15rc2?

kernel version tested : 3.14.1-031401

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.14.1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-10 Thread Christopher M. Penalver
Sayantan Das, the latest mainline kernel is the one all the way at the
top (3.15).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 07JC8T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-10 Thread Sayantan Das
Hi Christopher,

Tested with  3.15.0-031500-generic #201406081435. I get the same error.
Attached is the dmesg


** Attachment added: -1224143649
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4129178/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/25/2010
  

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-10 Thread Christopher M. Penalver
Sayantan Das, as a potential WORKAROUND, would using either nouveau, or
a different version of the nvidia drivers as noted in
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia change
anything?

As well, did this problem not occur in a release prior to Trusty?

** Tags removed: kernel-bug-exists-upstream-3.14.1
** Tags added: kernel-bug-exists-upstream-3.15

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-09 Thread Christopher M. Penalver
** Attachment removed: AlsaInfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127260/+files/AlsaInfo.txt

** Attachment removed: CRDA.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127262/+files/CRDA.txt

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127261/+files/BootDmesg.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127263/+files/CurrentDmesg.txt

** Attachment removed: IwConfig.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127264/+files/IwConfig.txt

** Attachment removed: Lspci.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127265/+files/Lspci.txt

** Attachment removed: Lsusb.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127266/+files/Lsusb.txt

** Attachment removed: ProcCpuinfo.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127267/+files/ProcCpuinfo.txt

** Attachment removed: ProcEnviron.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127268/+files/ProcEnviron.txt

** Attachment removed: ProcModules.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127270/+files/ProcModules.txt

** Attachment removed: ProcInterrupts.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127269/+files/ProcInterrupts.txt

** Attachment removed: PulseList.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127271/+files/PulseList.txt

** Attachment removed: RfKill.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127272/+files/RfKill.txt

** Attachment removed: UdevLog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127274/+files/UdevLog.txt

** Attachment removed: UdevDb.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127273/+files/UdevDb.txt

** Description changed:

  I tried installing bumblebee with nvidia-337 graphics  driver. Bumblebee
  does not work.
  
  # Configuration file for Bumblebee. Values should **not** be put between
  quotes
  
  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d
  
  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false
  
- 
  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
  
  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-09 Thread Christopher M. Penalver
Sayantan Das, thank you for reporting this and helping make Ubuntu
better. Could you please capture the call trace following
https://help.ubuntu.com/community/DebuggingSystemCrash ?

** Description changed:

  I tried installing bumblebee with nvidia-337 graphics  driver. Bumblebee
  does not work.
+ 
+ WORKAROUND: Don't install bumblebee.
  
  # Configuration file for Bumblebee. Values should **not** be put between
  quotes
  
  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d
  
  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false
  
  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
  
  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
  
  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
  
  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 07JC8T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn07JC8T:rvrA10:cvnDellInc.:ct8:cvrA10:
  

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-09 Thread Sayantan Das
memory test went fine. All pass.

Trying to run bumblebee ends with the following message in the syslog:

Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.445420] bbswitch: version 
0.8
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.445434] bbswitch: Found 
integrated VGA device :00:02.0: \_SB_.PCI0.GFX0
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.445446] bbswitch: Found 
discrete VGA device :01:00.0: \_SB_.PCI0.P0P1.PEGP
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.445468] ACPI Warning: 
\_SB_.PCI0.P0P1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20131115/nsarguments-95)
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.445844] ACPI Warning: 
\_SB_.PCI0.P0P1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20131115/nsarguments-95)
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.446213] bbswitch: detected 
a nVidia _DSM function
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.446326] pci :01:00.0: 
enabling device ( - 0003)
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.446479] bbswitch: 
Succesfully loaded. Discrete card :01:00.0 is on
Jun  9 23:07:02 sayantan-Vostro-3300 bumblebeed[28797]: /usr/sbin/bumblebeed 
3.2.1 started
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.451481] bbswitch: disabling 
discrete graphics
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.467150] ACPI Warning: 
\_SB_.PCI0.P0P1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20131115/nsarguments-95)
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.474302] vgaarb: device 
changed decodes: PCI::00:02.0,olddecodes=none,decodes=io+mem:owns=none
Jun  9 23:07:02 sayantan-Vostro-3300 acpid: input device has been disconnected, 
fd 8
Jun  9 23:07:02 sayantan-Vostro-3300 acpid: input device has been disconnected, 
fd 9
Jun  9 23:07:02 sayantan-Vostro-3300 acpid: input device has been disconnected, 
fd 10
Jun  9 23:07:02 sayantan-Vostro-3300 acpid: input device has been disconnected, 
fd 11
Jun  9 23:07:02 sayantan-Vostro-3300 acpid: input device has been disconnected, 
fd 16
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579399] [ cut 
here ]
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579417] WARNING: CPU: 0 
PID: 4 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214 
sysfs_remove_group+0xc6/0xd0()
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579421] sysfs group 
81cab9c0 not found for kobject 'acpi_video0'
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579424] Modules linked in: 
bbswitch(OF) pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) ctr 
ccm bnep rfcomm bluetooth binfmt_misc snd_hda_codec_hdmi snd_hda_codec_idt arc4 
brcmsmac cordic brcmutil b43 mac80211 uvcvideo cfg80211 ssb videobuf2_vmalloc 
videobuf2_memops dell_wmi sparse_keymap videobuf2_core mxm_wmi intel_powerclamp 
videodev snd_hda_intel snd_hda_codec snd_hwdep coretemp i915 snd_pcm 
snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_intel snd_seq 
snd_seq_device kvm drm_kms_helper drm snd_timer dell_laptop joydev dcdbas 
i2c_algo_bit serio_raw lpc_ich bcma snd mei_me intel_ips soundcore mei wmi 
video mac_hid parport_pc ppdev lp parport psmouse ahci r8169 libahci mii
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579537] CPU: 0 PID: 4 Comm: 
kworker/0:0 Tainted: GF  O 3.13.0-29-generic #53-Ubuntu
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579541] Hardware name: Dell 
Inc. Vostro 3300/07JC8T, BIOS A10 10/25/2010
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579551] Workqueue: 
kacpi_hotplug acpi_hotplug_work_fn
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579555]  0009 
880240175ac8 8171a214 880240175b10
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579564]  880240175b00 
810676bd  81cab9c0
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579571]  88023c04b4a8 
88023fd58098 8802402afc08 880240175b60
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579579] Call Trace:
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579592]  
[8171a214] dump_stack+0x45/0x56
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579599]  
[810676bd] warn_slowpath_common+0x7d/0xa0
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579604]  
[8106772c] warn_slowpath_fmt+0x4c/0x50
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579610]  
[8123407e] ? sysfs_get_dirent_ns+0x4e/0x70
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579614]  
[81235366] sysfs_remove_group+0xc6/0xd0
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579623]  
[81498783] dpm_sysfs_remove+0x43/0x50
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579629]  
[8148e1b5] device_del+0x45/0x1c0
Jun  9 23:07:02 sayantan-Vostro-3300 kernel: [ 1795.579633]  
[8148e34e] 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-09 Thread Sayantan Das
attaching kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 07JC8T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-09 Thread Christopher M. Penalver
Sayantan Das, could you please test the latest upstream kernel available (the 
one all the way at the top, and 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-3.15

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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  WORKAROUND: Don't install bumblebee.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  attached is the dmesg log
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-08 Thread Sayantan Das
Also, 
I have a fedora 20 installation on a different partition. Bumblebee works 
perfectly fine there. 

[sdas@localhost ~]$ optirun glxgears
4763 frames in 5.0 seconds = 952.527 FPS
4822 frames in 5.0 seconds = 964.383 FPS
4658 frames in 5.0 seconds = 931.459 FPS
4724 frames in 5.0 seconds = 944.760 FPS
4679 frames in 5.0 seconds = 935.701 FPS
4677 frames in 5.0 seconds = 935.380 FPS
4620 frames in 5.0 seconds = 923.967 FPS
4623 frames in 5.0 seconds = 924.578 FPS
4542 frames in 5.0 seconds = 908.211 FPS
4572 frames in 5.0 seconds = 914.304 FPS
4504 frames in 5.0 seconds = 900.764 FPS
4487 frames in 5.0 seconds = 897.251 FPS
4471 frames in 5.0 seconds = 894.154 FPS
4469 frames in 5.0 seconds = 893.614 FPS
 frames in 5.0 seconds = 888.729 FPS
4554 frames in 5.0 seconds = 910.636 FPS
4582 frames in 5.0 seconds = 916.344 FPS
4533 frames in 5.0 seconds = 906.416 FPS
^C[  593.535907] [WARN]Received Interrupt signal.
[sdas@localhost ~]$ uname -a
Linux localhost.localdomain 3.14.4-200.fc20.x86_64 #1 SMP Tue May 13 13:51:08 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  
  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  
  attached is the dmesg log
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-07 Thread Sayantan Das
apport information

** Tags added: apport-collected

** Description changed:

  I tried installing bumblebee with nvidia-337 graphics  driver. Bumblebee
  does not work.
  
  # Configuration file for Bumblebee. Values should **not** be put between
  quotes
  
  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d
  
  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false
  
  
  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
  
  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
  
  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
  
  
  attached is the dmesg log
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  sayantan   2374 F pulseaudio
+  /dev/snd/controlC0:  sayantan   2374 F pulseaudio
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
+ InstallationDate: Installed on 2014-06-01 (6 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
+ MachineType: Dell Inc. Vostro 3300
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
+ ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-27-generic N/A
+  linux-backports-modules-3.13.0-27-generic  N/A
+  linux-firmware 1.127.2
+ Tags:  trusty
+ Uname: Linux 3.13.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/25/2010
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A10
+ dmi.board.name: 07JC8T
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A10
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: A10
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn07JC8T:rvrA10:cvnDellInc.:ct8:cvrA10:
+ dmi.product.name: Vostro 3300
+ dmi.product.version: A10
+ dmi.sys.vendor: Dell Inc.

** Attachment added: AlsaInfo.txt
   

[Kernel-packages] [Bug 1327598] Re: running bumblebee in Ubuntu 14.04 results in call trace in logs

2014-06-07 Thread Sayantan Das
Sorry I think I ran the command twice . Hope thats not a problem

** Attachment removed: WifiSyslog.txt
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327598/+attachment/4127275/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327598

Title:
  running bumblebee in Ubuntu 14.04 results in call trace in logs

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I tried installing bumblebee with nvidia-337 graphics  driver.
  Bumblebee does not work.

  # Configuration file for Bumblebee. Values should **not** be put
  between quotes

  ## Server options. Any change made in this section will need a server restart
  # to take effect.
  [bumblebeed]
  # The secondary Xorg server DISPLAY number
  VirtualDisplay=:8
  # Should the unused Xorg server be kept running? Set this to true if waiting
  # for X to be ready is too long and don't need power management at all.
  KeepUnusedXServer=false
  # The name of the Bumbleblee server group name (GID name)
  ServerGroup=bumblebee
  # Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
  # server exits.
  TurnCardOffAtExit=false
  # The default behavior of '-f' option on optirun. If set to true, '-f' will
  # be ignored.
  NoEcoModeOverride=false
  # The Driver used by Bumblebee server. If this value is not set (or empty),
  # auto-detection is performed. The available drivers are nvidia and nouveau
  # (See also the driver-specific sections below)
  Driver=nvidia-337
  # Directory with a dummy config file to pass as a -configdir to secondary X
  XorgConfDir=/etc/bumblebee/xorg.conf.d

  ## Client options. Will take effect on the next optirun executed.
  [optirun]
  # Acceleration/ rendering bridge, possible values are auto, virtualgl and
  # primus.
  Bridge=auto
  # The method used for VirtualGL to transport frames between X servers.
  # Possible values are proxy, jpeg, rgb, xv and yuv.
  VGLTransport=proxy
  # List of paths which are searched for the primus libGL.so.1 when using
  # the primus bridge
  
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
  # Should the program run under optirun even if Bumblebee server or nvidia card
  # is not available?
  AllowFallbackToIGC=false

  
  # Driver-specific settings are grouped under [driver-NAME]. The sections are
  # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
  # detection resolves to NAME).
  # PMMethod: method to use for saving power by disabling the nvidia card, valid
  # values are: auto - automatically detect which PM method to use
  # bbswitch - new in BB 3, recommended if available
  #   switcheroo - vga_switcheroo method, use at your own risk
  # none - disable PM completely
  # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

  ## Section with nvidia driver specific options, only parsed if Driver=nvidia
  [driver-nvidia]
  # Module name to load, defaults to Driver if empty or unset
  KernelDriver=nvidia-337
  PMMethod=auto
  # colon-separated path to the nvidia libraries
  LibraryPath=/usr/lib/nvidia-337:/usr/lib32/nvidia-337
  # comma-separated path of the directory containing nvidia_drv.so and the
  # default Xorg modules path
  XorgModulePath=/usr/lib/nvidia-337/xorg,/usr/lib/xorg/modules
  XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

  ## Section with nouveau driver specific options, only parsed if Driver=nouveau
  [driver-nouveau]
  KernelDriver=nouveau
  PMMethod=auto
  XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  
  attached is the dmesg log
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sayantan   2374 F pulseaudio
   /dev/snd/controlC0:  sayantan   2374 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bf97d424-fc0a-40d8-a799-ee28fc70d432
  InstallationDate: Installed on 2014-06-01 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Vostro 3300
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=0cdd0302-af0e-41f3-9d3c-5992d54b61c8 ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.