LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (http://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   Slackware boot using kernel 3.2.45 ends up in black screen (http://www.linuxquestions.org/questions/linux-kernel-70/slackware-boot-using-kernel-3-2-45-ends-up-in-black-screen-4175462798/)

r41d3n 05-20-2013 11:49 PM

Slackware boot using kernel 3.2.45 ends up in black screen
 
Hi,

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:

Code:

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.

H_TeXMeX_H 05-21-2013 03:15 AM

This might be the answer:

Code:

May 21 01:07:41 sniperwolf kernel: [    1.897305] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3432!
I think the i915 driver is just too old and buggy on 3.2.x.

r41d3n 05-21-2013 06:39 AM

Quote:

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.

pv_ 05-21-2013 07:46 AM

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

It is Slackware-only problem?

Petr

piacentini 05-22-2013 08:19 AM

Same issue here with i915, whole system freezes randomly on X in both KDE and XFCE, with or without OpenGL acceleration. Reverted to the default 14.0 kernels for now.

ruario 05-22-2013 03:13 PM

There are updated updated 3.2.45 packages on the primary mirror.

corstar 05-25-2013 03:09 AM

So, Is this this problem avoidable at all for a newbie slacker who wants to run slackpkg -upgrade-all on a fresh install?
(I also had a borked laptop due to this..acer aspire s3 391 (intelhd-3000))

ruario 05-25-2013 03:49 AM

Depends which problem you are talking about. The issue that started this thread is fixed.

Quote:

Originally Posted by ruario (Post 4956763)
There are updated updated 3.2.45 packages on the primary mirror.

Two of us seem to have another problem, though this appears not to be as widespread. In any case it is possible to work around by using another kernel.

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.

r41d3n 05-25-2013 07:38 PM

Quote:

There are updated updated 3.2.45 packages on the primary mirror.
Yes, there's the updated entry on slackware 14.0 Changelog:

Code:

Wed May 22 14:11:13 UTC 2013
patches/packages/linux-3.2.45/*: Rebuilt.
      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.



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