Thanks, Pat I really appreciate your response.

Hmmm .... weird. I used the binary kernel packages from -current and was able to successfully recompile the VirtualBox kernel module (I have even tested VirtualBox and it works) but you are obviously much more experienced with this stuff so to avoid potential problems in the future I will recompile 3.8.13, just to be safe.

Thanks for the tip. I learned something new!

EDIT: Ok, 3.8.13 is now recompiled. So I have the system just right for me.

I built the 3.4.47 (huge) kernel using Patrick's config and left the machine running overnight, after launching lots of applications and mounting two USB hard drives. The system seems to be rock-solid again and I couldn't see any issues so far. I guess the 3.4.x kernel has matured since the release of Slackware 14.0.

Now I'll see what happens with 3.8.13 from -current, but since 3.8.x is EOL and 3.4.x has long term support, I think I'll stick to the latter.

Anyway, I found ruario's and Patrick's tips most helpful, thanks!

Philip

F.Y.I. (just in case you missed the news) the 3.8.x kernel will be receiving extended support from the Ubuntu kernel team (since Ubuntu 13.04 "Raring" uses this kernel). So you will continue to be able to get security updates until August 2014 at least. Granted this is a couple of months less than the projected EOL for 3.4.x (October 2014) but still long enough that you might want to give 3.8.13 a serious consideration if it performs better for you (it does for me).

EDIT: By the way new releases of stable patches for the 3.8.x kernel will be announced at kernel-team@lists.ubuntu.com. You might want to follow this if Pat changes his mind and decides against 3.8.x for the next Slackware stable release.

1 members found this post helpful.

Much appreciated, thanks! This sounds interesting and I saved a bookmark of it. I don't see any issues with 3.4 so far, but I'll keep an entry in lilo for 3.8.13 as well, if it works.

EDIT: I rebuilt the 3.8.13 kernel on Slackware 14.0 using config-generic-smp from -current, and it really seems to be another good option to solve the mentioned 3.2.45 issues.

Best regards,
Philip

I also have the same problem with the rebuilt 3.2.45 kernel as Ruario (and others).
After command startx different window managers (blackbox, fluxbox, kde) were frozen, I couldn't use the keyboard and needed to do forced reboot.
My CPU is also Intel Core i3.
I installed back the old 3.2.29 kernel temporarily.

I was going to post this in a separate thread but it seems related so I'll add it here for reference.

I use a virtualbox guest vm that I clone and copy to a desktop and a laptop as needed (for experimentation, testing stuff etc.)
The guest runs Slackware 14.0 with the 3.2.29 stock kernel, upgrading to 3.2.45 was straightforward as usual but launching X within the guest brought up a frozen black screen with a blinking cursor at the top left corner. I rebooted the guest and tried again after uninstalling/reinstalling the guest additions but that didn't help.

Aside from reverting to 3.2.29, found only these 2 workarounds:
-remove the guest additions, X starts working again (issue re-occurs if I reinstall the additions)
-upgrade to 3.8.13, this apparently resolves everything with no issues so far, guest + X + additions working smoothly.


Thanks for the tip.

1 members found this post helpful.

I have the same issue. Have you found what causes the problem? I would like to keep both the additions and 3.2.45 :-)
Thank you.

...and forward to 3.4.47

As other users did before me, I built 3.4.47 with Pat's 3.4.11 config and the result has been working fine so far - no glitches, no crashes.

After the upgrade, all of my Slackware VMs (QEMU-KVM) paniced immediately and wouldn't boot any longer. This was easily fixed by replacing "-cpu native" with "-cpu kvm64,+sse3" in my run script (I need the SSE3 capability and "native" was the easiest way to get it).

If newer kernels don't work for you, rebuilding with this patch should be all you need to get a non-exploitable 3.2.29.

Ahhh okay... I get it now. When you offer a new kernel package in stable you use the same version of gcc that was used at the time of release, which is why 3.2.45 works fine for me, but if I go any further I may run into problems. Took me a while to figure it out but I'm on the same page now.

Just guessing something must have been introduced in 3.2.45 that makes guest additions fail, X + 3.2.45 without the additions worked well. I'd be curious to try again when Virtualbox releases an update.

I uninstalled/reinstalled and tested the guest additions with other kernels (3.4.x and 3.8.x) in the same VM and everything worked as expected.

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

Is this with Intel graphics again?

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.

4 members found this post helpful.

FYI, I have updated to the kernel patch few days after the last 14.0 update (the rebuilt one). I still encounter freeze issue with my Intel HD Graphics 3000.

I decided to downgrade to the original 3.2.29 to make my machine usable again.

@ecoslacker - pass "nomodeset" at lilo prompt so you can work on your machine with minimal graphics then download the original 3.2.29 kernels and install it again via installpkg.

So if I'm not wrong, the issue with upgrading kernel to 3.2.45 is still pretty much there even after the second rebuild?
I've still not upgraded my 32 bit stable box with Intel HD graphics, but I have downloaded that second rebuild already.

Regards.