LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-23-2017, 02:31 AM   #1
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 189

Rep: Reputation: 146Reputation: 146
strange behavior with kernel-4.14.x


Each time I update a system with kernel from 4.14.x series, the kernel segfaults the first time it boots.
Then I reboot a second time, it boots normally.
It's the same problem, if I build myself the kernel for slackware from scratch.
Nothing of that kind happens with 4.4.x, 4.9.x or 4.13.x kernels.

What's wrong with that kernel?
 
Old 11-23-2017, 02:44 AM   #2
trollog
Member
 
Registered: Oct 2014
Posts: 102

Rep: Reputation: Disabled
I second that

I've also gotten a lot of odd behaviour out of this kernel
 
Old 11-23-2017, 08:11 AM   #3
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,641

Rep: Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583
Quote:
Originally Posted by nobodino View Post
Each time I update a system with kernel from 4.14.x series, the kernel segfaults the first time it boots.
Then I reboot a second time, it boots normally.
It's the same problem, if I build myself the kernel for slackware from scratch.
Nothing of that kind happens with 4.4.x, 4.9.x or 4.13.x kernels.

What's wrong with that kernel?
And happens to have an Intel processor?

I have a small PC, model Fujitsu Esprimo Q5030, which have hardware similar with a laptop, with CPU: Intel Core2 Duo P8400, but in a small desktop, and it have same behavior.

Something is wrong with (some of) the Intel CPUs on our current kernel.

Last edited by Darth Vader; 11-23-2017 at 09:46 AM.
 
Old 11-23-2017, 10:08 AM   #4
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 508

Rep: Reputation: 211Reputation: 211Reputation: 211
I experienced that behavior a couple of times in an earlier kernel series. I'm not sure if it was the later 4.4.0 series or early 4.9.0 series where I experienced it. My computer feels more responsive with this kernel.
 
Old 11-23-2017, 12:08 PM   #5
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
Quote:
Originally Posted by nobodino View Post
Each time I update a system with kernel from 4.14.x series, the kernel segfaults the first time it boots.
Then I reboot a second time, it boots normally.
32-bit? I've seen it a few times here, but never with x86_64.
 
Old 11-23-2017, 12:37 PM   #6
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,703

Rep: Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997
Quote:
Originally Posted by volkerdi View Post
32-bit? I've seen it a few times here, but never with x86_64.
Yes, it seems to happen with my machine as well (32 bit)
 
Old 11-23-2017, 12:51 PM   #7
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint, Niresh (MacOS)...
Posts: 189

Original Poster
Rep: Reputation: 146Reputation: 146
My machine is rather new: INTEL with i7-6700, no RYZEN.
I'll test on x86_64 to see if the behavior is the same.
update: I updated a partition with Slackware-current x86_64, it booted normally. Seems to be limited to 32-bit systems.

Last edited by nobodino; 11-23-2017 at 01:43 PM.
 
Old 11-24-2017, 05:24 AM   #8
tazza
Member
 
Registered: Jul 2005
Distribution: Slackware64 -current
Posts: 98

Rep: Reputation: 31
Mines done the exact same thing on a number of earlier kernels, but interestingly enough it didn't happen on 4.14. Weird. Seems to be no rhyme or reason to it.
 
Old 11-25-2017, 03:27 PM   #9
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,703

Rep: Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997
Good news. I found that 4.14.2 didn't have the strange behaviour anymore yay.....
 
Old 11-25-2017, 03:56 PM   #10
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,239
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
None of them have had issues for me on 7 machines. Latest 4.14 kernels piss off virtualbox but hey patched it myself.
I always build an initrd.gz for the new kernel before I reboot to the new kernel image. then boot vmlinuz-generic. This may be a huge or huge-smp thing.
 
Old 11-25-2017, 04:05 PM   #11
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
Quote:
Originally Posted by willysr View Post
Good news. I found that 4.14.2 didn't have the strange behaviour anymore yay.....
My machine seems to be cured as well.
 
Old 11-25-2017, 04:09 PM   #12
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
Quote:
Originally Posted by Drakeo View Post
None of them have had issues for me on 7 machines. Latest 4.14 kernels piss off virtualbox but hey patched it myself.
I always build an initrd.gz for the new kernel before I reboot to the new kernel image. then boot vmlinuz-generic. This may be a huge or huge-smp thing.
The issues I had here were with kernel-generic + initrd. To be honest, I'd like to get rid of the huge kernels. They're a hack that was developed back before we had anything like udev, and if initrd generation could be added to the installer there would be no good reason to keep the huge kernels. Either way, there's no advantage to using a huge kernel. And there are a few things that the huge kernel does not do as well - some of the modules don't load properly into a huge kernel, and having the huge kernel has forced a few things to be built into kernel-generic that really shouldn't be (in the interest in keeping the module tree mostly compatible with both kernels).
 
13 members found this post helpful.
Old 11-25-2017, 05:06 PM   #13
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,641

Rep: Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583
Quote:
Originally Posted by volkerdi View Post
My machine seems to be cured as well.
My Intel based Esprimo Q5030 still do the crash thing. And the single strange thing in that mini-PC is a dual Ethernet on mini-PCIE, instead of WIFI card, something like this:

https://www.amazon.com/IO-Crest-SI-M.../dp/B01N9HNXBB

Because I replaced also the DVD drive with a caddy for a second (internal) hard-disk, I had the possibility to speculate the space to mount those Ethernet ports in the case, and I use that mini-PC as a router for a 1Gbps down connection, while it ran also a LAMP stack, as a (home) web server.

The good news for me is that this little thingie does not is rebooted often, so the issue does not disturb me too much.

Also, my modding make it a bit non-standard, so my laments are with half of mouth...

Last edited by Darth Vader; 11-25-2017 at 05:15 PM.
 
Old 11-25-2017, 05:38 PM   #14
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,135

Rep: Reputation: 391Reputation: 391Reputation: 391Reputation: 391
No problem here 4.14.2 work.
 
Old 11-25-2017, 05:56 PM   #15
Olek
Member
 
Registered: Jul 2012
Location: Wroclaw Poland
Distribution: Slackware
Posts: 56

Rep: Reputation: Disabled
4.14.2 on old machine not work

Quote:
I upgraded kernel to 4.14.2 (64bit) on my old machine with AMD Athlon 64 CPU.
After upgrade I can't boot to Slackware.
Just after lilo my screen is going blank immediately.
It doesn't matter which kernel to choose, both huge and generic kernel hangs my machine.
Now I can only boot by pendrive with 4.14.0 kernel and I am waiting for newer kernel to try.
I run lilo with additional Luks encrypted disk which get /dev/sda name.
Since I had boot=/dev/sda in my lilo.conf my appropriate BIOS boot disk wan't overwritten.
Now I put to lilo.conf boot=/dev/disk/by-id/... and everything is OK.

Last edited by Olek; 11-26-2017 at 07:46 AM. Reason: I found my mistake
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Strange behavior battles Linux - Newbie 5 07-10-2014 09:59 AM
dcgui-qt's strange behavior harken Linux - Software 2 02-24-2005 03:10 PM
Very Strange Behavior raysr Mandriva 4 08-31-2004 03:06 PM
Strange Behavior andrewb758 Linux - Hardware 5 08-31-2003 03:42 PM
strange behavior abhijit Linux - General 3 07-10-2003 12:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:33 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration