I never seen a Linux where you have to hard reset ten times the computer for a successfully boot, just to freeze on middle of writing an ordinary document on Kate (TXT of course) or browsing a News site.

Yet, this way behave Slackware 14.2 on my computers, ranged from P4 to Bulldozer x8.

WTF?

BTW, anyone, please do not reply to this thread! This way it will popup "random" in the eyes of the Slackware Team, just like my systems freeze.

I've never had Slackware 14.2 up and freeze on me, and I've had it installed on a few different machines so far. Sounds like you have some bad components in your computer, first guess would probably be RAM or PSU, or maybe your installation media is corrupt...

So, all six of them, are going nuts from bad components? Every one? Nice try!

PS, I give you a hint: kernel, that kernels epic sucks.

Bulldozer FX-9590 8-core here. No freezes at all. Was on current for months before it went stable.

1 members found this post helpful.

So, Darth Vader, in the past two and a half years between Slackware 14.1 and 14.2 you never ever tested the slackware-current development? If everyone sits back on his ass and waits for the next release to be delivered on the doorstep, Slackware will never be stable, because it gets better from user feedback. You missed your chance.
Find the reason behind your crashes (graphics driver, old user profile, ...?) and we'll all help you fix it.

FYI I have Slackware 14.2 running on several computers and virtually never have crashes.

3 members found this post helpful.

All six with different motherboards from different companies? How's the power supply in Romania? Constant? No spikes/brownouts?

I'm not claiming that you aren't having lockups, but you appear to be the only one. Maybe others will chime in that are seeing what you are seeing. (Hard to fix a problem that you can't reproduce.)

3 members found this post helpful.

Darth Vader,
Have you at least verified that your install medium has proper checksum?

I had 14.2 hard-lock on me one time so far, but I suspected overheating.
Hot laptop CPU in very hot room.

I'm havig some freezing problems as well under Slackware 14.2 and i have narrowed it down to GPU Hangs: xxx xxx xxx in Xorg.log and syslog. I have a intel graphics 5500 in this laptop. not sure why it's happening, a intel gpu driver update is maybe required?

Maybe your power there fluctuates enough to cause your PSUs to drop the voltages to your components.

You seriously think that if it requires you to reboot 10 times before you getting a working system (that is still prone to crashes) that it is something software related? That's laughable. What would change on the harddrive with those 10 reboots that would suddenly make the system want to have a successful boot?

And if 14.2 is so problematic, why do you have it installed on 6 different systems? Are you a glutton for punishment?

2 members found this post helpful.

So build yourself another kernel?

No-one else is having this problem, and if we're not having this problem we can't fix it for you.

1 members found this post helpful.

The intel-driver bit has seen a lot of development. Unfortunately that for me means that it needs a bit of tweaking on some machines to get it stable. Look under freezes/crashes on the Arch-Linux page: https://wiki.archlinux.org/index.php/intel_graphics

Is this a serious post or a vendetta against Slackware team?

Oh btw, next time it happens, see if you can ssh into the box and run things like dmesg on it.

4.1.29 works fine, on every system, and no freezes.

I do not point my finger to Slackware team, excluding that, well, that shipped 4.4.x behave crazy on my systems. All of them. Why? Linus Torvalds know why.

BTW, the single common points of them are:

Radeon HD4450 -> 6450

The rest, one is GeForce 210 and one GeForce 6200 (AGP, on a P4)

OH, and IF is important, everyone has Gigabyte motherboard.

The Intel graphics were a major consideration during the development process. Intel drivers are so inconsistent on various hardware that it was a nightmare trying to find a good version that worked with everyone's hardware. Maybe yours didn't make the cut.

Pat does have a script in the source/ folder on 14.2 that will grab the latest git version and create a tarball. You can then use the x11.SlackBuild to create a new intel package and see if it fixes your problem.

Off the top of my head, you should be able to build the newest version with the following commands (I know running the SlackBuild and upgradepkg needs to be done as root, but the rest should be up to you).