Choose style:

Author Topic: System still locking up after booting up.  (Read 1236 times)

0 Members and 1 Guest are viewing this topic.

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4852
  • Karma: 1026
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 10 (64-bit)
System still locking up after booting up.
« on: June 09, 2017, 08:05:50 pm »
Code: [Select]
andy@andy-Latitude-E6410 ~ $ inxi -Fz
System:    Host: andy-Latitude-E6410 Kernel: 4.8.0-54-generic x86_64 (64 bit) Desktop: N/A
           Distro: Peppermint Eight
Machine:   System: Dell (portable) product: Latitude E6410 v: 0001
           Mobo: Dell model: 0667CC v: A03 Bios: Dell v: A16 date: 12/05/2013
CPU:       Dual core Intel Core i5 M 560 (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2667 MHz 1: 1599 MHz 2: 2133 MHz 3: 1466 MHz 4: 2133 MHz
Graphics:  Card: Intel Core Processor Integrated Graphics Controller
           Display Server: X.Org 1.18.4 driver: intel Resolution: 1280x800@60.00hz
           GLX Renderer: Mesa DRI Intel Ironlake Mobile GLX Version: 2.1 Mesa 17.0.2
Audio:     Card Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.8.0-54-generic
Network:   Card-1: Intel 82577LM Gigabit Network Connection driver: e1000e
           IF: eno1 state: down mac: <filter>
           Card-2: Intel Centrino Advanced-N 6200 driver: iwlwifi
           IF: wlp2s0 state: up mac: <filter>
Drives:    HDD Total Size: 1120.2GB (31.9% used) ID-1: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB
           ID-2: /dev/sdb model: WDC_WD10JPVX size: 1000.2GB
Partition: ID-1: / size: 20G used: 6.8G (37%) fs: ext4 dev: /dev/sda5
           ID-2: /home size: 17G used: 2.9G (19%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 59.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 225 Uptime: 27 min Memory: 1372.8/7908.9MB Client: Shell (bash) inxi: 2.2.35
andy@andy-Latitude-E6410 ~ $

Hi all, I'm still experiencing my system freezing in Peppermint 8 64-bit.  When this happens, my only option is to perform a hard shutdown. Obviously this is not desirable.   This issue only happens when I boot up the machine from a complete shutdown.  The issue doesn't occur when the machine is simply rebooted.  To ensure a stable environment from a standard boot up, I have to immediately reboot my machine.  If I don't do this, my machine invariably freezes after 3 to 5 minutes of running.   I've run a full memory diagnostic.  There are no issues with my RAM memory, all the tests were passed.  It's a real mystery and really annoying  :-\.
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.

Offline VinDSL

  • Global Moderator
  • Hero
  • *****
  • Posts: 5508
  • Karma: 966
  • Peppermint Mod
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: System still locking up after booting up.
« Reply #1 on: June 10, 2017, 01:02:09 pm »
Have you tired running 'sudo cat /proc/kmsg' from CLI ?

If not, open a terminal window, perform the above command, and leave it running in the background.

Actually, you can open another window too, and start stressing things -- like having your machine randomly try to assemble the English alphabet in the correct order.  But, let's leave that for another time.   8)

Okay, I left 'sudo cat /proc/kmsg' running while I was typing this, here are the results, so far:

Code: [Select]
╭─vindsl@Boogaloo-5 ~  
╰─➤  sudo cat /proc/kmsg                                                    1 ↵
[sudo] password for vindsl:

<4>[ 3665.778696] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:c0:56:27:67:8f:8f:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
<4>[ 3668.241789] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=17063 PROTO=2
<4>[ 3791.714260] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:10:40:f3:e7:e0:41:08:00 SRC=10.0.0.222 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=34037 PROTO=2
<4>[ 3917.734932] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=19713 PROTO=2
<4>[ 4044.716160] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=27781 PROTO=2
<4>[ 4169.834560] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:00:18:8b:d0:9b:ac:08:00 SRC=10.0.0.6 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
<4>[ 4293.707522] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=12908 PROTO=2

Looks like my ConkyWX install is generating a few errors now n' then, but whatevs.  It works.

Anyway, just a suggestion ...   ;)
« Last Edit: June 10, 2017, 01:04:19 pm by VinDSL, Reason: Addendum »

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4852
  • Karma: 1026
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 10 (64-bit)
Re: System still locking up after booting up.
« Reply #2 on: June 10, 2017, 05:49:01 pm »
Have you tired running 'sudo cat /proc/kmsg' from CLI ?

If not, open a terminal window, perform the above command, and leave it running in the background.

Actually, you can open another window too, and start stressing things -- like having your machine randomly try to assemble the English alphabet in the correct order.  But, let's leave that for another time.   8)

Okay, I left 'sudo cat /proc/kmsg' running while I was typing this, here are the results, so far:

Code: [Select]
╭─vindsl@Boogaloo-5 ~  
╰─➤  sudo cat /proc/kmsg                                                    1 ↵
[sudo] password for vindsl:

<4>[ 3665.778696] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:c0:56:27:67:8f:8f:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
<4>[ 3668.241789] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=17063 PROTO=2
<4>[ 3791.714260] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:10:40:f3:e7:e0:41:08:00 SRC=10.0.0.222 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=34037 PROTO=2
<4>[ 3917.734932] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=19713 PROTO=2
<4>[ 4044.716160] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=27781 PROTO=2
<4>[ 4169.834560] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:00:18:8b:d0:9b:ac:08:00 SRC=10.0.0.6 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
<4>[ 4293.707522] [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:08:2e:5f:2f:7e:a0:08:00 SRC=10.0.0.20 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=12908 PROTO=2

Looks like my ConkyWX install is generating a few errors now n' then, but whatevs.  It works.

Anyway, just a suggestion ...   ;)

Thanks John, I'm  going to run this after I do a reboot.  It may kick up something.  I'm not sure how I'm going to work it from a straight boot up.  When the system freezes, I've no way of retrieving any info.  It's a bit of a catch 22 situation  :-\.
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.

Online PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26468
  • Karma: 2864
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: System still locking up after booting up.
« Reply #3 on: June 11, 2017, 05:37:23 pm »
Code: [Select]
sudo cat /proc/kmsg > ~/Desktop/kmsg-output.txt
and leave the terminal open.
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec