This topic contains 25 replies, has 5 voices, and was last updated by rej May 19-4:46 pm.
May 15, 2019 at 8:07 am #21590Member
Are there any logs that would tell why my desktop is randomly freezing?
Looked in var-log-syslog and var-log-messages. They appear to have the same information.
The files are too large to post.
Are there other logs that would give specific isolated information on system freezes?
It does not appear to be a problem with the laptop hardware, as I have run many diagnostic tests from the BIOS and Memtest86 separately.
I am hoping it is a kernel issue and will be fixed when the missing 4.19.36 kernel arrives in the Package installer. The system was freezing in MX with 4.15.9 and not since installing 4.19.36.
Since it is an intermittent event, that does not mean it will not.
Normally, I would not be in a hurry to fix this, but just purchased this Thinkpad T450s and have less than 2 weeks to return it (which is not a lot with something happening every few days. It is otherwise running perfectly and this has only happened in MX and antiX and only 3 times since May 2. Taking the device apart would be risky and would prefer not to do it if possible.
I have invested in extras for this laptop that will be not be returnable, so under the circumstances, would like to find any information that will shed light as to whether this is kernel related or not.
I have found information online regarding the 4.15.9 kernel and its problems with freezing the CPU, if I am understanding the posts correctly.
Any input regarding this will be appreciated.
rj@antix17rj:~ $ inxi -F System: Host: antix17rj Kernel: 4.15.9-antix.1-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: antiX-17_x64-full Heather Heyer 24 October 2017 Machine: Type: Laptop System: LENOVO product: 20BWS09M00 v: ThinkPad T450s serial: <root required> Mobo: LENOVO model: 20BWS09M00 serial: <root required> UEFI [Legacy]: LENOVO v: JBET47WW (1.12 ) date: 03/10/2015 Battery: ID-1: BAT0 charge: 16.6 Wh condition: 16.7/23.2 Wh (72%) ID-2: BAT1 charge: 18.2 Wh condition: 19.2/23.5 Wh (82%) CPU: Topology: Dual Core model: Intel Core i5-5300U bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 799 MHz min/max: 500/2900 MHz Core speeds (MHz): 1: 798 2: 798 3: 799 4: 798 Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) v: 4.5 Mesa 13.0.6 Audio: Device-1: Intel Broadwell-U Audio driver: snd_hda_intel Device-2: Intel Wildcat Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.15.9-antix.1-amd64-smp Network: Device-1: Intel Ethernet I218-LM driver: e1000e IF: eth0 state: down mac: 68:f7:28:92:d7:06 Device-2: Intel Wireless 7265 driver: iwlwifi IF: wlan0 state: up mac: 34:02:86:02:f7:d8 Drives: Local Storage: total: 305.36 GiB used: 7.01 GiB (2.3%) ID-1: /dev/sda vendor: Seagate model: ST320LT007-9ZV142 size: 298.09 GiB ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 size: 7.27 GiB Partition: ID-1: / size: 39.12 GiB used: 6.90 GiB (17.6%) fs: ext4 dev: /dev/sda6 Sensors: System Temperatures: cpu: 34.0 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 217 Uptime: 1h 01m Memory: 7.50 GiB used: 1.20 GiB (16.0%) Shell: bash inxi: 3.0.33 rj@antix17rj:~May 15, 2019 at 10:15 am #21603Member
The easiest way to check if it’s OK or not would be to simply install the ‘known working’ — Windows 10 1803.
If you insist on Linux to test, then you should check the Linux compatibility list on ‘known issues’ first
and then choose some distro that is supposed to work without too many bugs or ‘known problems’.
Judging by MX is pretty much very risky.
That usually comes down to Linux Mint/Ubuntu and/or Rosa Linux.
How strange is to be anything at all. (Alice in Wonderland)May 15, 2019 at 10:23 am #21605Member
since that is a recent cpu/gpu you can try the 5.0 kernel and
see if that helps with it.
Normal == 🙂
depends on the surrounding crowd ?!May 15, 2019 at 10:32 am #21606Member
* Just don’t try installing 5-series Kernel on MX.
Ubuntu 19.04 comes with 5-series Kernel.
How strange is to be anything at all. (Alice in Wonderland)May 15, 2019 at 10:35 am #21607Forum Admin
I’d look in dmesg logs in /var/log myself. `May 15, 2019 at 10:36 am #21608Member
Judging by MX is pretty much very risky.
What are you using to justify this nonsense?May 15, 2019 at 10:43 am #21609Member
Like somebody once said …
I agree with ‘whoever’ – “MX is a perfect example of a completely misconfigured OS.”
They really ruined their Xfce desktop. If they made such a mess with the distro´s aesthetic,
imagine what could have been made with other configuration options “under the hood”.
I’ll not even try to explain you, it’ll be to no avail.
How strange is to be anything at all. (Alice in Wonderland)May 15, 2019 at 10:54 am #21610Member
I’ll not even try to explain you, it’ll be to no avail.
What I understand very well is you don’t have a clue about MX-Linux.May 15, 2019 at 11:01 am #21612Member
It may be or, maybe you just don’t wanna see …
How strange is to be anything at all. (Alice in Wonderland)May 15, 2019 at 4:21 pm #21617Member
Thanks linuxdaddy – I was considering that, however it is not an LTS. Just a guess, but I think LTS is more stable. I was able to successfully install 4.19.36 a little while ago.
noclue – thanks for your reply – a good point about Windows. I had installed Windows 8.1 and it took a very long time to install drivers, update it and strip it down as far as I could, because it is only used for a few applications for issues with hard drives/flash drives, that I have not yet found the equivalent for in Linux. Working on it though. For the entire time in 8.1, there were no crashes or freezes.
As for MX and antiX, been running them for years with relatively few issues and most were of my own doing. I have both distros on all my many devices and nothing else but 8.1 [multi-boot], for the aforementioned reasons.
When the freeze occurred, I had made copies of var/log syslog, messages, kern.log and user.log.
Also copied home/rj – .xsession-errors and .xsession-errors.old which are lengthy and of course loaded with errors.
I do not understand any of it.
What would I be looking for in dmesg?
Thanks for your help.May 15, 2019 at 8:57 pm #21620Member
It’s not that the LTS are more stable or not … they just get security
updates for a lot longer period of time. The difference being how long it gets
updated for security holes or not.
for the time being you can install a 5.0 kernel and always switch back later.
Normal == 🙂
depends on the surrounding crowd ?!May 15, 2019 at 10:44 pm #21628Member
Don’t get me wrong, I don’t have anything against antiX or MX, quite the opposite but …
The drivers are usually being developed, tested and certified for Windows.
RedHat and Ubuntu have HW & SW certification programs.
ROSA has the biggest HW DB of all Linuxes.
That’s just the simple logic.
… just purchased this Thinkpad T450s and have less than 2 weeks to return it …
On that point, the ‘fun’ stops and you simply need something that’ll give you more reliable answers, emotions here or there.
How strange is to be anything at all. (Alice in Wonderland)May 16, 2019 at 6:06 am #21639Member
linuxdaddy- Thanks for clarifying that.
noClue- Have Ubuntu on an external hard drive – will do some temporary testing with it. The main problem is the fact that the freeze happens so infrequently. I am hoping to find something in the antiX log files that will shed some light sooner.May 16, 2019 at 7:24 am #21640Forum Admin
Just to give a example off my AntiX chromebook.
harry@biker:~ $ dmesg | grep intel [ 1.798087] intel_idle: MWAIT substates: 0x21120 [ 1.798088] intel_idle: v0.4.1 model 0x3A [ 1.798228] intel_idle: lapic_timer_reliable_states 0xffffffff [ 2.322677] intel_pstate: Intel P-state driver initializing [ 2.954433] Btrfs loaded, crc32c=crc32c-intel [ 3.999851] fb0: switching to inteldrmfb from simple [ 4.037941] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 4.051120] fbcon: inteldrmfb (fb0) is primary device [ 4.053443] intel_rapl: Found RAPL domain package [ 4.053445] intel_rapl: Found RAPL domain core [ 4.053446] intel_rapl: Found RAPL domain uncore [ 4.793344] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device harry@biker:~ $ inxi -G Graphics: Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 3.3 Mesa 13.0.6 harry@biker:~ $ dmesg | grep i915 [ 4.001744] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 4.037755] [drm] Initialized i915 1.6.0 20180921 for 0000:00:02.0 on minor 0 [ 4.037941] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 4.793344] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device harry@biker:~ $
Hope it gives you a idea. Freezes are usually hardware related. My 2 commands above is looking for video driver errors. Seeing mine is fine and dandy. No errors. Ar least that I can see.
If you think sound card is freezing stuff. To get info on chip and driver.
harry@biker:~ $ inxi -A Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.20.12-antix.1-amd64-smp
Just to let you know. Years ago on my Acer Aspire One ZG5 . To get the sd card slot to recognize cards when inserted. I edited grub legacy < /boot/grub/menu.list> and caused some kind of hardware conflict which caused the wifi card to get hot and kill the netbook session. Shutdown on over heat. Took me a lot of searching and thinking and trouble shooting before I figured out I induced the problem with my edit. Jest mentioning this just in case. That is why now I religiously make backup text files first before doing any editing in / or /home text files. So if I screw the pooch like in my above adventure. I have a backup of original to bring things back to stock.
Live and learn.May 16, 2019 at 7:31 am #21641Forum Admin
is included in MX and gives a good readout on drives to info on looking with dmesg and grep for hard drive errors. Example off my chromebook
harry@biker:~ $ inxi -Fxxx <snip> Drives: Local Storage: total: 14.91 GiB used: 8.90 GiB (59.7%) ID-1: /dev/sda vendor: SanDisk model: SSD U100 16GB size: 14.91 GiB speed: 3.0 Gb/s serial: 132553400495 rev: 6.14 scheme: MBR <snip>
The above lets know to look for sandisk errors in dmesg.
- This reply was modified 3 months, 1 week ago by rokytnji.
You must be logged in to reply to this topic.