[SOLVED] Upgrading Slackware 14 to Kernel 3.2.45 resulted in black screen on boot.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been pointed to another suspicious commit and might be forced to do a third build. Giving much credit to whether a kernel series is designated LTS isn't looking like it matters as much as we may have thought. If 3.2.x had been dead, we'd have patched the CVE and had it right the first time.
I'm still seeing crashes with the second build, on an Intel DQ67SW with Core i7 2600 (HD 2000 Graphics) unless I append nomodeset.
I'm considering doing a third build. If anyone who is running into problems still could revert this patch and rebuild to see if it fixes the issue, then I'd do it for sure. The only Intel graphics I have here are the trusty GM945, and there's no problem there.
# lspci -v -s $(lspci | awk '/VGA/{print $1}')
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Samsung Electronics Co Ltd Device c0b3
Flags: bus master, fast devsel, latency 0, IRQ 49
Memory at c0000000 (64-bit, non-prefetchable) [size=4M]
Memory at b0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
and I was having issues with X freezing when using 3.2.45 (both the first and the second package), prior to switching to the 3.8.13 kernel from -current. However to help out with confirmation I'll revert this patch and compile 3.2.45 locally and try again.
Might be a few hours delay in giving you a response though. It is almost midnight here and I need to get some sleep as I expect my 1 year old to wake me during the night (my wife is away so it is just me looking after the little one). Let's see how long it takes to compile. If it is quick I'll let you know soon. Otherwise in the morning my local time.
Last edited by ruario; 05-30-2013 at 05:16 PM.
Reason: Clarified my wording
Ok, well I am done compiling (I actually started compilation some time before I submitted my previous message). I have now rebooted and am now using 3.2.45 with that patch reverted. So far so good. No hangs at all. It has only been a few minutes but then that is all it took previously before the issue showed up. It was very consistent.
I will leave the machine running overnight and have a look at it again tomorrow if you want a longer test. Anyway, thanks for the effort in tracking this down. Your hard work is very much appreciated (even though I am likely to go back to 3.8.13 when all is said and done. ).
Last edited by ruario; 05-30-2013 at 05:55 PM.
Reason: s/ ery/ very/
I'm considering doing a third build. If anyone who is running into problems still could revert this patch and rebuild to see if it fixes the issue, then I'd do it for sure. The only Intel graphics I have here are the trusty GM945, and there's no problem there.
Same as ruario here. I reverted the patch, rebuilt the kernel, reinstalled modules, rebuilt initrd, run lilo. After rebooting I didn't have any issues so far, so you probably fixed it. I didn't use the patch command to revert, but I tracked the lines below in drivers/gpu/drm/i915/intel_ringbuffer.c and deleted them manually.
Code:
/* Required for the hardware to program scanline values for waiting */
if (INTEL_INFO(dev)->gen == 6)
I915_WRITE(GFX_MODE,
GFX_MODE_ENABLE(GFX_TLB_INVALIDATE_ALWAYS));
The hardware here is an H67 mini-ITX Intel board with Celeron G530 (HD 2000).
Code:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device 2000
Flags: bus master, fast devsel, latency 0, IRQ 49
Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Now I'll leave the machine running and see tomorrow if it's still fine as it seem to be now.
Thanks for following this thread, Patrick!
Best regards,
Philip
Last edited by Philip Lacroix; 05-30-2013 at 07:49 PM.
Sometimes the graphical session in KDE gets frozen and sometimes I cannot enter to graphical session even, with the new rebuild 3.2.45 kernel.
Little help: How can I install back the old 3.2.29 kernel?
Thanks
I used the command upgradepkg oldpackage%newpackage, because I do not have much free space on hard drive, but I think that command installpkg may be appropriate as well. The modified packages were kernel-modules*, kernel-huge* and kernel-generic*.
If you use the generic kernel, then you should make a new mkinitrd and then use the command lilo, assuming you boot with lilo.
Interesting however, that slackpkg does not perceive the change.
I used the command upgradepkg oldpackage%newpackage, because I do not have much free space on hard drive, but I think that command installpkg may be appropriate as well.
No need for oldpackage%newpackage in this case as the pkgtools will accept a downgrade without question (which is a feature, not a bug, I might add). And yep you can just installpkg new kernel packages, rather than upgradepkg allowing you to have both installed.
Quote:
Originally Posted by ecoslacker
Little help: How can I install back the old 3.2.29 kernel?
If you are up to it try reverting the commit that volkerdi highlighted and build your own copy of the 3.2.45 kernel. Or wait, it seems likely that volkerdi will be issuing updated kernels.
Install them with either upgradepkg or installpkg. upgradepkg will replace the 3.2.45 kernel packages with these. installpkg will install them alongside.
Last edited by ruario; 05-31-2013 at 02:54 AM.
Reason: Provided feedback to ecoslacker as well
Ok, Linux 3.2.46 is now available on kernel.org, however the patch doesn't revert the lines discussed above. I decided to try it anyway, so I updated the original 3.2.45 sources with today's 3.2.46 incremental patch, rebuilt the kernel, modules, initrd and so on, and the previous issues are here again. Just FYI
Philip
Last edited by Philip Lacroix; 05-31-2013 at 01:27 PM.
Reason: Fixed link :)
Yeah the 3.2.46 ChangeLog makes no reference to either of the troublesome commits (e12a2d53ae45a69aea499b64f75e7222cca0f12f and 393143615d9f2f581d87387268dc11b95adc339c). Additionally a lot of new stuff has gone in, which considering the problems thus far could mean further regressions. If we are gonna get another kernel update, I'm pretty sure Pat is gonna stick with 3.2.45 and just revert that one further problematic fix. Taking 3.2.46 is not worth the risk.
SalixOS uses the kernel's shipped by Slackware and also had a thread about CVE 2013-1763 - Linux Kernel local root exploit. One of the comments shows another user with this issue after the 3.2.45 kernel update:
Quote:
Originally Posted by laprjns
I upgraded to the new kernel on my Dell laptop with these specs:
It booted into x and the desktop ok, but then completely locked up. I could move the mouse pointer, but no response to clicks or keyboard entries. I reverted back to the old kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.