LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (http://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   3.2.28 Generic Kernel in Slackware (with nvidia optimus, bumblebee) (http://www.linuxquestions.org/questions/linux-kernel-70/3-2-28-generic-kernel-in-slackware-with-nvidia-optimus-bumblebee-4175425199/)

TommyC7 09-01-2012 08:05 PM

3.2.28 Generic Kernel in Slackware (with nvidia optimus, bumblebee)
 
1 Attachment(s)
Hello.

I've been getting this error in Slackware using bumblebee with the generic kernel 3.2.28 (attachment below).

This error doesn't occur on a Slackware machine (same kernel) that doesn't have nvidia optimus.

The log is the end of syslog at the exact moment the crash occurs. I can't quit X, I can't switch to a different tty, it's just a complete freeze. Videos loop about the last millisecond of noise. The mouse also does not move.

Hopefully it's been fixed in a newer kernel version, but I don't keep up with the kernel development.

Didier Spaier 09-03-2012 05:58 AM

I see two worrying lines in the log.

Firts, the last one:
Code:

Sep  1 15:45:55 TomHPdv7 udevd[1817]: could not find module by name='rtc_cmos'
I suppose that you are running Slackware -current as you are using a 3.2.28 kernel.

This is supposed to be fixed since RC3:
Code:

a/udev-182-i486-4.txz: Rebuilt.
      Commented out the entries in /lib/modprobe.d/isapnp.conf to fix
      the error attempting to load rtc_cmos. Thanks to GazL.

Is your Slackware properly uopgraded?

Alse, check the content of /etc/modrobe.d. There should be only two files in it now: README and (possibly) blacklist.nouveau.conf.
If they are others, just remove it. Noticeably, remove isapnp.conf.

Second, this one:
Code:

[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
I don't know if that caused the freeze but I suggest you investigate from there as a Google search on that returns a lot of results.

Anyhow, I see no reason to assume that your problem be kernel related, so I suggest you post it in the Slackware forum instead to get more useful answers (or click the Report button and request a moderator to move the thread there).

TommyC7 09-07-2012 03:10 PM

Hi Didier,

I did a kernel upgrade and it was fixed, and I do properly upgrade Slackware.


All times are GMT -5. The time now is 02:26 AM.