Siduction Forum

Siduction Forum => Software - Support => Topic started by: finotti on 2018/07/31, 01:17:25

Title: Help debugging freezes
Post by: finotti on 2018/07/31, 01:17:25
I've been having some freezes in my new laptop running siduction.   Most of the times it happens after boot.  Sometimes right before SDDM starts (I only get a blank screen), sometimes after it starts.  Once or twice it happened after some time in use.  (But maybe those were unrelated.) 

When the problems occurs, rebooting (sometimes two or three times) usually gets the system to start without freezing.

The problem is that I am not sure how to get logs from the previous boot...  Since the system is frozen I cannot get logs then.  (Ctrl+Alt+Fn does not work either.  Nor does Ctrl+Alt+Del to reboot.)

Here is some info on the system (which I haven't DUed in about 2 weeks):
Code: [Select]
$ inxi -v3
System:    Host: l5580 Kernel: 4.17.6-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: KDE Plasma 5.13.2 tk: Qt 5.10.1 Distro: siduction 18.2.0 Patience - kde - (201803072323)
           base: Debian GNU/Linux buster/sid
Machine:   Type: Laptop System: Dell product: Latitude 5580 v: N/A serial: <root required>
           Mobo: Dell model: 0FH6CJ v: A00 serial: <root required> UEFI: Dell v: 1.8.2 date: 01/30/2018
Battery:   ID-1: BAT0 charge: 63.2 Wh condition: 63.2/68.0 Wh (93%) model: BYD DELL KCM8281 status: Full
CPU:       Topology: Quad Core model: Intel Core i7-7820HQ bits: 64 type: MT MCP arch: Skylake rev: 9
           L2 cache: 8192 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 46464
           Speed: 1200 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1200 2: 1200 3: 1200 4: 1200 5: 1200
           6: 1200 7: 1200 8: 1200
Graphics:  Card-1: Intel driver: i915 v: kernel bus ID: 00:02.0
           Card-2: NVIDIA driver: N/A bus ID: 01:00.0
           Display: x11 server: X.Org 1.20.0 driver: modesetting unloaded: fbdev,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.1.3
           direct render: Yes
Network:   Card-1: Intel Ethernet Connection I219-LM driver: e1000e v: 3.2.6-k port: N/A bus ID: 00:1f.6
           IF: enp0s31f6 state: down mac: 10:65:30:2b:cf:45
           Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter driver: ath10k_pci v: kernel
           bus ID: 02:00.0
           IF: wlp2s0 state: up mac: 5c:ea:1d:7c:fe:63
           Card-3: Atheros type: USB driver: btusb bus ID: 1:2
Drives:    HDD Total Size: 238.47 GiB used: 143.76 GiB (60.3%)
Info:      Processes: 251 Uptime: 3h 41m Memory: 15.55 GiB used: 3.22 GiB (20.7%) Init: systemd runlevel: 5
           Compilers: gcc: 7.3.0 Shell: bash v: 4.4.23 inxi: 3.0.15
Any help on finding what is happening would be greatly appreciated!
Title: Re: Help debugging freezes
Post by: Kan on 2018/07/31, 02:12:50
I had this issue with SDDM also. It was random, but kept getting worse. I too would have to reboot, sometimes three times before I could actually login to the desktop. I switched kernels, but nothing worked.

I finally had to switch to LightDM (I use Budgie OS as my desktop), and never had an issue after that.
Title: Re: Help debugging freezes
Post by: finotti on 2018/08/01, 15:48:47
Thanks for the reply!  I might just do that (replace SDDM).


On the other hand, I would really like to know how to check logs after a freeze.  Can any one offer some advice?
Title: Re: Help debugging freezes
Post by: melmarker on 2018/08/01, 16:16:17
@finotti - do what you want to - but a DM don't cause freezes in a running system
Title: Re: Help debugging freezes
Post by: piper on 2018/08/01, 17:06:16
@finotti - This could be your problem, Have you ever tried bumblebee ?
https://wiki.debian.org/Bumblebee

Code: [Select]
Graphics:  Card-1: Intel driver: i915 v: kernel bus ID: 00:02.0
Card-2: NVIDIA driver: N/A bus ID: 01:00.0

@Kan - I use budgie and sddm with no problems, it's one of my personal builds (budgie) and I build it with sddm as default.
Title: Re: Help debugging freezes
Post by: Kan on 2018/08/01, 20:04:27
@Piper, yeah, it is weird. I think maybe it is an intel graphics issue? I think I use the i915 graphics. I have found a few people with the same issues reporting on Ubuntu forums. I have tried all their suggestions, changing the modset, stuff, etc, but nothing work.

I need to clarify, I was able to enter my login info, but then it would pull up a blank screen. Most times it would not go away, yet you could hear my mail notifier dinging, etc (things running in the background.) It would take sometimes three reboots before it would let me into my desktop. This happened on Gnome, so I switch to GDM using xorg, still had the issue. I then switched to Budgie with LightDM, never had the issue again.
Title: Re: Help debugging freezes
Post by: finotti on 2018/08/02, 02:00:56
@finotti - do what you want to - but a DM don't cause freezes in a running system
Indeed, and that's part of the reason why I was trying to find a way to look at the logs and find out what was actually causing the problem.


@finotti - This could be your problem, Have you ever tried bumblebee ?
https://wiki.debian.org/Bumblebee (https://wiki.debian.org/Bumblebee)

Code: [Select]
Graphics:  Card-1: Intel driver: i915 v: kernel bus ID: 00:02.0
Card-2: NVIDIA driver: N/A bus ID: 01:00.0

@Kan - I use budgie and sddm with no problems, it's one of my personal builds (budgie) and I build it with sddm as default.
I did not know about this.  Thanks for the info.  Unfortunately, after installing it would always freeze and I could not get to log in screen at all.  So I had to uninstall it.
BTW, since I had to edit the GRUB line during start up, I was reminded that I had to add "nouveau.modeset=0".  I had to do it with the live CD, or it would not boot.  I am not sure it is relevant at all, but I thought I should mention it just in case.
Title: Re: Help debugging freezes
Post by: melmarker on 2018/08/02, 21:06:06
@finotti - no clue about bumblebee - fut for me it  sounds like hard disabling the nvidia graphics and just using intel would be a good idea if possible - or the other way around - never had a laptop with dual graphics. If this is possible, both things should solve your problem.

TBH - as for KDE i would recommend to go with intel and leave nouveau alone.