LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 12-04-2017, 09:56 AM   #16
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled

Oh, great! Now Memtest seems to be frozen.
 
Old 12-04-2017, 10:14 AM   #17
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
The Memtest that froze was installed using these instructions:

https://docs.slackware.com/howtos:sl...ry_boot_option

I'm now trying Memtest from a USB memory stick.
 
Old 12-04-2017, 10:58 AM   #18
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,136
Blog Entries: 4

Rep: Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565
Failure running memtest indicates it's hardware, probably not memory (memtest should be fine with that ) but something else instead. It could (for example) be capacitors on the motherboard that are getting old -- you might find it's ok when running on battery but fails when running on mains power. That kind of thing might not be repairable, unless it's a well known problem with your model and you can find someone brave to give it a shot for nothing.
 
Old 12-04-2017, 11:03 AM   #19
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by 55020 View Post
Failure running memtest indicates it's hardware, probably not memory (memtest should be fine with that ) but something else instead. It could (for example) be capacitors on the motherboard that are getting old -- you might find it's ok when running on battery but fails when running on mains power. That kind of thing might not be repairable, unless it's a well known problem with your model and you can find someone brave to give it a shot for nothing.
If it was something as serious as that, would a reboot apparently (albeit temporarily) fix it, as suggested on the bottom line of the screen?
 
Old 12-04-2017, 11:18 AM   #20
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,136
Blog Entries: 4

Rep: Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565Reputation: 1565
*If* it was something as serious as that, then, depending on how it crashes, yes, a reboot might get it going again (until the next time), or it might need to be powered off before it'll restart.

I'm not stamping my foot and insisting that it's definitely hardware, but we need to prepare you emotionally for that possibility

If you try to carry on with it but the problem gets more frequent as the weeks go by, that'll be another indication that something in the hardware is going bad.
 
Old 12-04-2017, 11:24 AM   #21
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by 55020 View Post
*If* it was something as serious as that, then, depending on how it crashes, yes, a reboot might get it going again (until the next time), or it might need to be powered off before it'll restart.

I'm not stamping my foot and insisting that it's definitely hardware, but we need to prepare you emotionally for that possibility

If you try to carry on with it but the problem gets more frequent as the weeks go by, that'll be another indication that something in the hardware is going bad.
With the proverbial British stiff upper lip, I shall face up to the possibility that my X200 could be dying.
https://www.youtube.com/watch?v=WlBiLNN1NhQ
 
Old 12-07-2017, 02:48 PM   #22
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
Not sure, but I might have fixed it using guess work. Since some of the error message entries seemed to refer to the kernel (kthread_worker, kthread_data) I thought I'd try rebuilding the initrd, using mkinitrd_command_generator.sh again. I've shut it down, and switched it back on after an interval, 3 times today. And the error has not occurred. So it may be fixed, or not.
-----------------------------
Fingers crossed - still OK.

Last edited by brianL; 12-08-2017 at 05:34 AM. Reason: updated information
 
1 members found this post helpful.
Old 12-08-2017, 06:36 AM   #23
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
The original initrd must have become corrupted, somehow, after working OK for months.
 
Old 12-09-2017, 06:54 AM   #24
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
No, the rebuilt initrd was not the solution. Only a temporary reprieve. Switched on & booted up this morning and got what's shown in the attached photo. Tried the "have you switched it off and on again" routine, and got the original error as in post #1. Off & on again, and it boots OK.
Attached Thumbnails
Click image for larger version

Name:	boot_error_2.jpg
Views:	15
Size:	89.9 KB
ID:	26500  
 
Old 12-09-2017, 08:14 AM   #25
TracyTiger
Member
 
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 465

Rep: Reputation: 190Reputation: 190
If you have a spare (good) HDD/SSD you could replace the original disk and then reinstall Slackware.

That would tell you if the problem is the disk drive/software or not.

(I just assume everyone has spare computers and components lying around. )

Last edited by TracyTiger; 12-09-2017 at 08:20 AM.
 
Old 12-09-2017, 08:24 AM   #26
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
I haven't got a spare HDD or SSD. If it was the SSD, wouldn't problems show up when it was running - not just on boot? Once it boots OK, it runs with no problems whatsoever.
 
Old 12-09-2017, 08:41 AM   #27
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,663

Rep: Reputation: 600Reputation: 600Reputation: 600Reputation: 600Reputation: 600Reputation: 600
Brian, could be you are just affected by a kernel bug, like the one described for 4.14.x ?

I wonder if the Kernel guys "managed" to backport a bug, thought...

Last edited by Darth Vader; 12-09-2017 at 08:42 AM.
 
Old 12-09-2017, 08:46 AM   #28
TracyTiger
Member
 
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 465

Rep: Reputation: 190Reputation: 190
Over the years I've gotten in trouble by making assumptions about how things work. ("Oh this couldn't possibly be the problem because ...")

Now days I just follow good troubleshooting technique to isolate a problem without presuming to know the cause of the failure.

It would be nice to know if the problem is with an easily replaced component (RAM, Disk, Software) or not.

Without spare computers and components my ideas won't work. Hopefully others will have some more sophisticated techniques you can use without swapping out hardware.
 
1 members found this post helpful.
Old 12-09-2017, 08:51 AM   #29
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,654
Blog Entries: 56

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Darth Vader View Post
Brian, could be you are just affected by a kernel bug, like the one described for 4.14.x ?
I'll have a look at that thread: "Strange behavior...". Although it's worked OK since the update to 4.4.88, up to now. And I haven't had problems on my other 2 machines running it (Thinkpad T410 & Dell T3600).
 
Old 12-09-2017, 08:56 AM   #30
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,663

Rep: Reputation: 600Reputation: 600Reputation: 600Reputation: 600Reputation: 600Reputation: 600
Quote:
Originally Posted by brianL View Post
Although it's worked OK since the update to 4.4.88, up to now. And I haven't had problems on my other 2 machines running it (Thinkpad T410 & Dell T3600).
That's exactly what make me to question the Kernel, and the experience made me to learn in a hard-way that just because it works well in three machines, is not a guarantee that it will not crash in the fourth one.
 
  


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
"A disk read error occured" error for Win 7 boot after changing boot order in grub myrddin123 Linux - Newbie 2 10-31-2013 11:40 AM
When I boot with PXE Boot into openSuse, error says 'invalid or corrupt kernel image' rfelsburg SUSE / openSUSE 0 05-13-2010 09:51 PM
error 15 then error 18 in boot sequence dual boot. xp and ubuntu peteman Linux - Newbie 2 09-16-2008 07:38 AM
solaris boot problem boot error loading interpreter(misc/krtld) Johncy_j Solaris / OpenSolaris 5 08-18-2005 02:47 AM
Grub (error 17) won't boot after new motherboard/vid card.. boot disk anyone? r3dhatter Linux - Newbie 5 02-16-2005 07:52 PM

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

All times are GMT -5. The time now is 12:39 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