LinuxQuestions.org
Review your favorite Linux distribution.
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-25-2017, 08:50 PM   #16
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
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).
huge kernels are good only for initial installations.
Other than that, generic + initrd are perfectly fine
 
2 members found this post helpful.
Old 11-26-2017, 03:43 AM   #17
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,135

Rep: Reputation: 391Reputation: 391Reputation: 391Reputation: 391
The current kernel development cycle is very fast, everything can not be tested at length, so I think there will always be some bugs and regressions, some users will be luckier than others depending on their hardware
 
Old 11-26-2017, 04:08 AM   #18
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
Sorry, but I think the problem is not solved. I upgraded both systems (32-bits and x86_64).
- x86_64 is ok
- 32-bits still has the problem, even worse, I booted three times to get it work normally.
update: added two snapshots taken with smartphone
Attached Thumbnails
Click image for larger version

Name:	IMG_20171126_093028m.jpg
Views:	69
Size:	198.4 KB
ID:	26416   Click image for larger version

Name:	IMG_20171126_093316m.jpg
Views:	67
Size:	207.7 KB
ID:	26417  

Last edited by nobodino; 11-26-2017 at 04:25 AM.
 
Old 11-26-2017, 04:36 AM   #19
tazza
Member
 
Registered: Jul 2005
Distribution: Slackware64 -current
Posts: 98

Rep: Reputation: 31
Quote:
Originally Posted by nobodino View Post
<snip>
I booted three times to get it work normally.
This is what I don't understand. The fact that for me at least after the first hang, I hard power off and then it boots normally until another kernel change (totally random, sometimes several kernel updates without the problem, then 2 in a row).

It happened most frequently on my old Core 2 quad, but has still happened once on my newer 7600K. Both of course 64 bit.
 
Old 11-26-2017, 05:31 AM   #20
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,168
Blog Entries: 2

Rep: Reputation: 166Reputation: 166
Question

Can the system somehow update some microcode or something?

Or, the Kernel update some nvram bit (in the real time clock)?

This is more "funny" than it looks at the first glance IMO?

(in a bad way "funny")
 
Old 11-26-2017, 06:02 AM   #21
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,647

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
Quote:
Originally Posted by nobodino View Post
Sorry, but I think the problem is not solved. I upgraded both systems (32-bits and x86_64).
- x86_64 is ok
- 32-bits still has the problem, even worse, I booted three times to get it work normally.
update: added two snapshots taken with smartphone
Your screenshots are the poster child of what happens with my Intel based mini-PC.

Sadly, I think it is because the 4.14.x kernel is too young, and it is still not matured enough. Consider that it got a massive update.

Now, not that is not worth if we find the issue.

To note that my mini-PC runs with a "state of art" Intel microcode cpio, concatenated to initrd.gz, nothing to suspect, in my case, excluding a naughty kernel.
 
Old 11-26-2017, 06:46 AM   #22
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,135

Rep: Reputation: 391Reputation: 391Reputation: 391Reputation: 391
Quote:
Originally Posted by Darth Vader View Post
Your screenshots are the poster child of what happens with my Intel based mini-PC.

Sadly, I think it is because the 4.14.x kernel is too young, and it is still not matured enough. Consider that it got a massive update.

Now, not that is not worth if we find the issue.

To note that my mini-PC runs with a "state of art" Intel microcode cpio, concatenated to initrd.gz, nothing to suspect, in my case, excluding a naughty kernel.
I agree, usually, Pat, waiting for some minor versions, before pushing a major version of the kernel
 
Old 11-26-2017, 06:49 AM   #23
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 microcode is updated through rc.local (installed Intel microcode by sbopkg)

. /etc/rc.d/rc.microcode_ctl start
------------------------------
root@oups:~/scripts# dmesg | grep microcode
[ 4.416937] microcode: sig=0x506e3, pf=0x2, revision=0xa6
[ 4.417645] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 25.027478] microcode: updated to revision 0xba, date = 2017-04-09

Last edited by nobodino; 11-26-2017 at 06:59 AM.
 
Old 11-26-2017, 07:52 AM   #24
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,647

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
Quote:
Originally Posted by gmgf View Post
I agree, usually, Pat, waiting for some minor versions, before pushing a major version of the kernel
Yeah, looks like this time our BDFL was, lets say... a happy trigger.

Last edited by Darth Vader; 11-26-2017 at 07:56 AM.
 
Old 11-26-2017, 08:19 AM   #25
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,867

Rep: Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780Reputation: 2780
Finding issues soon in -current gives more time to solve them before the official release.
 
1 members found this post helpful.
Old 11-26-2017, 08:37 AM   #26
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,135

Rep: Reputation: 391Reputation: 391Reputation: 391Reputation: 391
That's not wrong
 
Old 11-26-2017, 08:53 AM   #27
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.2 (4.14.5) UEFI enabled
Posts: 453

Rep: Reputation: 131Reputation: 131
I'm a shoot first and ask questions later personality.
Compile amd install the newest kernel the day it is released.
It is a very simple thing to keep the old kernel in lilo or elilo as a backup.

Of course I don't do anything critical on my 'puter any more as I am long-time retired.
John
 
1 members found this post helpful.
Old 11-26-2017, 09:17 AM   #28
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,647

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
Quote:
Originally Posted by Didier Spaier View Post
Finding issues soon in -current gives more time to solve them before the official release.
Sure. We got it: our computers crash. Now, how we solve that?

My bet is that we will have to look smiling at our computers while they crash (it will boot, or it will not boot? that's the question!), meanwhile that overlord called Linus Torvalds will do Kernel releases, and our BDFL will push them in to -current, accordingly... until the crap is fixed and the computers will crash no more.

You see another solution for?

Last edited by Darth Vader; 11-26-2017 at 09:22 AM.
 
Old 11-26-2017, 09:23 AM   #29
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,135

Rep: Reputation: 391Reputation: 391Reputation: 391Reputation: 391
Maybe, keep an older version of the kernel in /pasture for a while
 
Old 11-26-2017, 09:27 AM   #30
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,647

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
Quote:
Originally Posted by gmgf View Post
Maybe, keep an older version of the kernel in /pasture for a while
Cool idea, maybe P.V. will consider it...

PS. For your general laugh, to note that I am distracted enough to not keep today a copy of 4.9.53 kernel packages for x86 anymore...

IF someone knows an older synced mirror, I will be glad for.

Last edited by Darth Vader; 11-26-2017 at 09:35 AM.
 
  


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 08:23 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