All boots with bumblebee ends with kernel panic #205

dm4g3 opened this Issue Jul 22, 2012 · 7 comments


None yet

2 participants

dm4g3 commented Jul 22, 2012

After installing Bbee all works fine and switch good.
But after reboot all boots end with KP.
What's wrong with bumblebee? What additional information I must send to developers?

Hardware: lenovo v570a2, i3, GF525, Kingston ValueRAM 8GB, Kingston SSD 60GB.
Software: ubuntu 12.04 LTS 64bit, KDE.

After uninstall bumblebee via aptitude purge, all works fine. So it's bb.


You could try delaying the start of Bumblebee. bbswitch disabled the card during startup, but due to a kernel bug in Precise, you get a Kernel Panic.

dm4g3 commented Jul 23, 2012

Any advice for complete it? I'm not so good with boot delaying.


This is an error that occurs on laptops that have an HDMI port wired to the nvidia card which has an audio output. It occurs on the 3.2 kernel shipped with Ubuntu. I believe that this panic is fixed in later versions of the kernel and as a workaround you can delay the starting process of bumblebeed.

Try the following upstart script in place of /etc/init/bumblebeed.conf:

# Upstart job for Bumblebee daemon

description "Bumblebee supporting nVidia Optimus cards"
author      "Lekensteyn <>"

# XXX: do we need to stop before / after a graphical DE like kdm?
start on    (runlevel [2345])
stop on     (runlevel [016])

# restart in case it crashed for some reason

    # delay startup, increase if you still get a panic
    sleep 2
    # don't use --daemon as Upstart gets confused by that.
    exec /usr/sbin/bumblebeed --use-syslog
end script

The "fixed" upstart script above has been reported to work.

dm4g3 commented Aug 30, 2012

So, completely put this conf-script into head of /etc/bumblebee/bumblebee.conf and reboot the system?
bumblebeed.conf or bumblebee.conf?


@d-mage It is an Upstart script. Put it in /etc/init/bumblebeed.conf

dm4g3 commented Sep 7, 2012

Workaround works properly. No kernel panics.

@dm4g3 dm4g3 closed this Sep 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment