LinuxQuestions.org
Help answer threads with 0 replies.
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-26-2017, 09:40 AM   #31
PROBLEMCHYLD
Member
 
Registered: Apr 2015
Posts: 481

Rep: Reputation: 115Reputation: 115

Or keep a copy of both 4.14.xx and 4.9.xx. It doesn't hurt to have a contingency plan in case something goes wrong with the new updates.
 
Old 11-26-2017, 09:55 AM   #32
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 270

Rep: Reputation: 115Reputation: 115
Quote:
Originally Posted by Darth Vader View Post
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.
The 4.9.53 kernel packages are here http://butler.cc.tut.fi/~kaukasoi/

I have an archive of all current packages since 2010. But the archive is not on line, I just made the 4.9.53 kernels available.
 
1 members found this post helpful.
Old 11-26-2017, 10:05 AM   #33
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 Petri Kaukasoina View Post
The 4.9.53 kernel packages are here http://butler.cc.tut.fi/~kaukasoi/

I have an archive of all current packages since 2010. But the archive is not on line, I just made the 4.9.53 kernels available.
Brilliant! Thanks you!
 
Old 11-26-2017, 10:06 AM   #34
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
for the time being, I prefer to use the previous LTS kernel: 4.9.65
 
Old 11-26-2017, 10:10 AM   #35
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
for the time being, I prefer to use the previous LTS kernel: 4.9.65
Yeah, having ours BDFL's original kernel .config, the rebuilding is at user exercise, I guess...
 
Old 11-27-2017, 02:45 PM   #36
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
I like to report that while using the (generic) kernel 4.9.65, religious built from the previous 4.9.53 series .config file, everything works like a charm over the last days.

I seen no crash while using the kernel 4.9.65, which is refreshing after that Russian Roulette called "boot", while using the current kernel.

Of course, I talk about my Intel powered mini-PC, used by me as router.

So, definitively the fault is/was in the glorious 4.14.x Kernel series, which was adopted way too early by our BDFL, in my humble opinion...

I wish him to be the same happy trigger also with LinuxPAM and Kerberos, but looks that over 15 years of PAM existence are still not enough...

Last edited by Darth Vader; 11-27-2017 at 05:29 PM.
 
Old 11-27-2017, 08:30 PM   #37
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 238
Blog Entries: 2

Rep: Reputation: 81
Quote:
Originally Posted by Darth Vader View Post
I like to report that while using the (generic) kernel 4.9.65, religious built from the previous 4.9.53 series .config file, everything works like a charm over the last days.

I seen no crash while using the kernel 4.9.65, which is refreshing after that Russian Roulette called "boot", while using the current kernel.

Of course, I talk about my Intel powered mini-PC, used by me as router.

So, definitively the fault is/was in the glorious 4.14.x Kernel series, which was adopted way too early by our BDFL, in my humble opinion...

I wish him to be the same happy trigger also with LinuxPAM and Kerberos, but looks that over 15 years of PAM existence are still not enough...

I don't think early adoption of kernels in current is a bad thing.
 
2 members found this post helpful.
Old 11-27-2017, 10:05 PM   #38
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 khronosschoty View Post
I don't think early adoption of kernels in current is a bad thing.
Same I considered myself, too...

Until I seen that one of my computers successfully boot just one time from two.

So, please explain me, what sense has to adopt a x.y.0 kernel, when you are aware that most likely it will contains bugs, which cannot be fixed in other way than rolling up later up to a x.y.7 or x.y.10?

OK. I will give you a reason: a little innocent (and a bit sadistic) pleasure to know that the users has crashes on their computers. You see another reason for?

Of course, I do not expect the -current to be rock stable. BUT, pushing a thing which you have to suspected from starts that will create problems, is a bit overhand.

And to be honest, when I seen that that unusual move to so early 4.14.0, I imagined that there will be problems somehow, and I am not a world-wide know developer like our BDFL...

Finally, bear in mind that there was the habit to wait until a x.y.7 or x.y.10 was released, before to switch to that Kernel series.

And I appreciated that, because we are NOT the Redhat or SuSE, to test things implemented by US in the kernels, together with some of our brave users.

Nope, we are Slackware, we have no Kernel developers and we are at mercy of Linus Torvalds.

So, why so hurry now?

Last edited by Darth Vader; 11-27-2017 at 10:26 PM.
 
Old 11-27-2017, 10:14 PM   #39
slackb0t
Member
 
Registered: Apr 2005
Location: Canada
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 246

Rep: Reputation: 60
I am on the latest 4.14.2 and zero problems... just thought I would toss that out there. Perhaps it has something to do with running a fairly new laptop? No idea.

edit: Also, just my 2 cents. I don't think the developers ever do anything without significant thought. If they went to 4.14.x I can tell you it wasn't on a whim.. careful thought went into it and decision was made. I have complete faith in these guys, especially compared to other distros.

Last edited by slackb0t; 11-27-2017 at 10:20 PM.
 
3 members found this post helpful.
Old 11-27-2017, 10:19 PM   #40
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 slackb0t View Post
I am on the latest 4.14.2 and zero problems... just thought I would toss that out there. Perhaps it has something to do with running a fairly new laptop? No idea.
I also run with no problems the -current, and that naughty 4.14.2 kernel, in other 3 computers. AMD powered computers.

In fact, I have just one Intel based computer, out of seven. And this one happens to go nuts.

BUT, like I said somewhere in this thread, because I am not so strongly affected by this issue, and that computer is a bit modded, my comments (or laments?) are, well... relaxed.

Last edited by Darth Vader; 11-28-2017 at 09:40 AM.
 
Old 11-28-2017, 01:31 AM   #41
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
Has someone registered a bug on lkml concerning the subject of this thread?
 
Old 11-28-2017, 03:24 AM   #42
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
Has someone registered a bug on lkml concerning the subject of this thread?
I had a fair number of failures with .0, only a few with .1, and none so far with .2. All of them on 32-bit... x86_64 has been stable for all of the kernels (which partly explains how some fairly unstable kernels slipped into -current; I wasn't spending a lot of time running 32-bit).

Considering the rapid improvement in the 4.14 series, I think they're doing a good job killing bugs. But if anyone has the time to properly bisect an issue, I'm sure they'd welcome that kind of report.
 
7 members found this post helpful.
Old 11-28-2017, 07:32 AM   #43
bormant
Member
 
Registered: Jan 2008
Posts: 278

Rep: Reputation: 156Reputation: 156
Quote:
Originally Posted by Darth Vader View Post
IF someone knows an older synced mirror, I will be glad for.
As I can see, this mirror syncing -current "in wrong way" -- without deleting packages, so old packages are available:
ftp://ftp.pieskovisko.sk/pub/slackware/
http://ftp.pieskovisko.sk/slackware/
 
1 members found this post helpful.
Old 11-28-2017, 04:38 PM   #44
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
And if evidence was not what it seemed? And if the kernel, the ideal culprit was not the faulty component?

For that I tested two hypothesis:

1/ I upgraded a mini slackware-current system (up to 25/11/2017) to kernel-4.14.2, and rebooted the first time in 'single user' mode. Everything was ok. Then I switched to 'multi user' mode and typed : 'telinit 5' and the system segfaulted immediatly.

2/ On my slackware-14.2, I built my own kernel-4.14.2 with the files from slackware-current, and upgraded the system to kernel-4.14.2.As for the first test, I rebooted in 'single user'. Everything was ok. Then I switched to 'multi user' mode and typed : 'telinit 5' and this time everything was ok, and is still ok.

Couldn't it be another component that make segfault the system?
Which package is involved when switching from 'single user' mode to 'multi user' mode?

'eudev' was upgraded nearly as kernel-4.14.0 came in slackware-current.

Last edited by nobodino; 11-28-2017 at 04:49 PM.
 
Old 11-28-2017, 05:04 PM   #45
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
1/ I upgraded a mini slackware-current system (up to 25/11/2017) to kernel-4.14.2, and rebooted the first time in 'single user' mode. Everything was ok. Then I switched to 'multi user' mode and typed : 'telinit 5' and the system segfaulted immediatly.
If you're using a huge kernel, all bets are off.

Quote:
2/ On my slackware-14.2, I built my own kernel-4.14.2 with the files from slackware-current, and upgraded the system to kernel-4.14.2.As for the first test, I rebooted in 'single user'. Everything was ok. Then I switched to 'multi user' mode and typed : 'telinit 5' and this time everything was ok, and is still ok.

Couldn't it be another component that make segfault the system?
If so, and if generic+initrd is being used, it would still be a kernel bug.
 
  


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