Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35344 - [bumblebee] Kernel warning since update to 3.2.1-3

Attached to Project: Community Packages
Opened by Chris Meyer (caros) - Friday, 17 May 2013, 22:48 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 20 May 2013, 20:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I am getting a kernel warning since bumblebee 3.2.1-1 -> 3.2.1-3. Bumblebee (and bbswitch) still work as expected, though.

Additional info:
*dmesg output


Steps to reproduce:
1.Update bumblebee to 3.2.1-3
2.Boot witch bumblebee enabled.
3.Check dmesg
   dmesg.txt (58.1 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 20 May 2013, 20:00 GMT
Reason for closing:  Upstream
Additional comments about closing:  Has been fixed upstream. This will make it into the next stable release of bbswitch.
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 18 May 2013, 00:07 GMT
Are you quite sure this isn't because of the new kernel? I really didn't change bumblebee in any significant way in the updates you mentioned: https://projects.archlinux.org/svntogit/community.git/log/trunk?h=packages/bumblebee

bbswitch itself was merely rebuilt against different kernel versions.
Comment by Chris Meyer (caros) - Saturday, 18 May 2013, 07:22 GMT
I am sure. I upgraded the kernel on 12 May, the first time this warning showed up was on 17 May, during the first boot after the bumblebee upgrade.

Attachments:
*journalctl |& grep "pci_disable_device" > journal_kwarning.txt
*grep '2013-05-17' /var/log/pacman.log > pacman_2013-05-17.txt
   pacman_2013-05-17.txt (0.6 KiB)
   journal_kwarning.txt (2.9 KiB)
Comment by Chris Meyer (caros) - Saturday, 18 May 2013, 07:33 GMT
I commented out "blacklist nvidia" in /usr/lib/modprobe.d/bumblebee.conf and rebooted without this warning showing in dmesg.
   dmesg.txt (56.6 KiB)
   bumblebee.conf (0 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 18 May 2013, 07:54 GMT
Mh this is rather strange. I will have to talk to upstream about why this would happen.

Loading...