[SOLVED] Slackware boot using kernel 3.2.45 ends up in black screen
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Slackware boot using kernel 3.2.45 ends up in black screen
I upgraded the kernel-* packages from my Slackware64 14.0 system to version 3.2.45 and tried to boot it, but the system freezes into a black screen after loading the kernel. I was searching the logs and found this:
May 21 01:07:41 sniperwolf kernel: [ 1.897305] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3432!
May 21 01:07:41 sniperwolf kernel: [ 1.897386] invalid opcode: 0000 [#1] PREEMPT SMP
May 21 01:07:41 sniperwolf kernel: [ 1.897594] CPU 0
May 21 01:07:41 sniperwolf kernel: [ 1.897640] Modules linked in: i915(+) video button i2c_a
lgo_bit intel_agp intel_gtt drm_kms_helper drm agpgart thermal_sys hwmon i2c_core uhci_hcd ehci
_hcd usbhid hid
May 21 01:07:41 sniperwolf kernel: [ 1.898001]
May 21 01:07:41 sniperwolf kernel: [ 1.898001] Pid: 961, comm: modprobe Not tainted 3.2.45-s
niperwolf #3 Dell Inc. Inspiron 1525 /0D109D
May 21 01:07:41 sniperwolf kernel: [ 1.898001] RIP: 0010:[<ffffffffa00d3d7b>] [<ffffffffa00
d3d7b>] i915_gem_object_unpin+0xab/0xb0 [i915]
When using i915.modeset=0 on the kernel command line, it boots normaly, but the X server crashes. Then I returned to my custom 3.2.44 kernel and things came back to normal.
I think the i915 driver is just too old and buggy on 3.2.x.
Yes, you're right. I'm using right now the latest stable 3.9.3 kernel without any problems during the system boot.
I think this is an important issue, because even the huge and generic kernels are hanging at the black screen.
I agree, i'm running Slackware 14.0 32b with custom kernel with -rt patch. After upgrading from 3.2.44-rt64 to 3.2.45-rt66, i have blank screen. Unfortunatelly, i can't switch to 3.9, because there is no realtime patch yet. 3.8.11-rt8 is unstable (Oops), so i have to run 3.2.x
Whilst slackpkg is a fantastic utility I don't think people should expect to be able to be totally reliant on it and never have to manage anything more manually. Slackware is not Ubuntu and slackpkg is not apt. A slacker should know how to work around issues like this. Other kernels are available, either the 3.8.x from current or the 3.4.x via the config provided in testing (or you could manually compile any other kernel you like). That is not to say that the problem should not be fixed. If we can get to the bottom of it, it might be nice to have another update.
Last edited by ruario; 05-25-2013 at 03:56 AM.
Reason: added link to other thread
There are updated updated 3.2.45 packages on the primary mirror.
Yes, there's the updated entry on slackware 14.0 Changelog:
Wed May 22 14:11:13 UTC 2013
It appears a bad commit slipped into 3.2.45 and it's causing problems on
systems that use Intel graphics. The commit has been reverted in the kernel
source packages and the kernels and modules have been rebuilt. If you ran
into the black screen problem before, this should fix it up.