LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware64 current crashes X11 often! (https://www.linuxquestions.org/questions/slackware-14/slackware64-current-crashes-x11-often-4175600899/)

WiseDraco 03-02-2017 04:51 AM

Slackware64 current crashes X11 often!
 
1 Attachment(s)
Hello!
Slackware current, i know, all the time was telled "not very stable, development" and so on, but with time i get accustomed, even current on slackware is quite stable and good.

but some time ago i installed slackware64 current on my work desktop. it was quite good hardware -i7 cpu, 16 Gb RAM, ssd as boot, and two 1tb hdd in software raid1.

i use xfce, and about once in a week, average, i got crashed X and back to black screen.
what was much worse - all opened things, dolphin instances and so, also was gone - as so, as some things who i work on at that crash time.

last crash happen about 20 minutes ago, when i try to open small .txt document on kwrite via dolphin, from my connected usb flash.

i start again xfce via "startx", but -again... that was a pain. i encounter that more than month by now. i do slackpkg update and upgrade-all quite often, but nothing changes.

a two weeks ago i do full hardware test -test all HDD and SSD-s with HDD regenerator programm, and do memtest86 and memtest86+, as cpu burn tests -all looks good.

there is some connections about connect something via USB - say, some times i got X crash few seconds after i connect Sansa Clip + or iphone SE to computer USB port, to charge them.

lspci:
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C220 Series Chipset Family H81 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)
01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

uname -a
Linux draco 4.4.38 #2 SMP Sun Dec 11 16:18:36 CST 2016 x86_64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz GenuineIntel GNU/Linux

procinfo
Memory: Total Used Free Buffers
RAM: 16345920 12259452 4086468 3610452
Swap: 19471956 36 19471920

Bootup: Mon Feb 27 08:43:36 2017 Load average: 0.24 0.20 0.20 2/537 22108

user : 17:17:11.83 2.8% page in : 8310920
nice : 1w 02:40:34.36 28.1% page out: 45652817
system: 04:33:19.59 0.7% page act: 2490821
IOwait: 00:43:29.94 0.1% page dea: 1172764
hw irq: 00:00:00.00 0.0% page flt: 623988336
sw irq: 00:00:29.55 0.0% swap in : 0
idle : 2w 3d 06:35:57.72 68.2% swap out: 9
uptime: 3d 04:03:45.80 context : 2124572987

irq 0: 34 2-edge timer irq 18: 0 18-fasteoi i801_s
irq 1: 271 1-edge i8042 irq 23: 29 23-fasteoi ehci_h
irq 7: 23 7-edge irq 24: 0 0-edge dmar0
irq 8: 4 8-edge rtc0 irq 26: 4077564 512000-edge 0000:
irq 9: 0 9-fasteoi acpi irq 27: 4171123 1572864-edge eth0
irq 14: 0 14-edge pata_lega irq 28: 822766 327680-edge xhci_
irq 15: 0 15-edge pata_lega irq 29: 13 360448-edge mei_m
irq 16: 25 16-fasteoi ehci_h irq 30: 849 442368-edge snd_h
irq 17: 831 17-fasteoi snd_hd irq 31: 24965 524288-edge nvidi

sda 123675r 258320w md2 219r 14w
sdc 26369r 740728w md1 1226401r 1419645w
sdb 903161r 740746w sdd 150r 16w

eth0 TX 326.17MiB RX 3.93GiB lo TX 18.68MiB RX 18.68MiB

i use nvidia driver NVIDIA-Linux-x86_64-375.26.run

xorg log, copied right after crash, is added to this post.

anyone have an ideas, how to stop crash x window system? it was very annoying, actually :(

orbea 03-02-2017 04:59 AM

You have a xorg log with a backtrace included, try showing it to xorg developers at #xorg-devel @ freenode.

Every time I have given them a backtrace after a xorg crash I have gotten a patch fixing it within hours.

WiseDraco 03-02-2017 05:01 AM

Quote:

Originally Posted by orbea (Post 5677977)
You have a xorg log with a backtrace included, try showing it to xorg developers at #xorg-devel @ freenode.

Every time I have given them a backtrace after a xorg crash I have gotten a patch fixing it within hours.


i have a log with backtrace enabled?
it was enabled in current by default?
or i need to enable it first?

orbea 03-02-2017 05:03 AM

Did you even read your Xorg.0.log? Look at the bottom...

WiseDraco 03-02-2017 05:12 AM

Quote:

Originally Posted by orbea (Post 5677979)
Did you even read your Xorg.0.log? Look at the bottom...

no i do not even lift, and two days ago i try to jogging a bit, and results, too, is very drastically :D

thanks for advice, i be joined on xorg devel channel and try work things out :)

WiseDraco 03-02-2017 06:07 AM

looks like all on that channel be asleep :D

orbea 03-02-2017 10:28 AM

The trick to asking help in irc is too just ask the whole question and lurk until someone replies. If no one who can help notices and replies causing the question to get buried after ~24 hours or so ask again.

With all due honesty this is a question for xorg developers, especially since you are running current. I doubt anyone here will know what do about a xorg segfault without asking them or looking through their mailing list or commit history hoping it has already been fixed upstream.

WiseDraco 03-03-2017 12:55 AM

ajax said, he was released 1.19.2, and there, maybe, that problem is fixing, too. as so i wait when 1.19.2 was putting in slackware64 current, so i can test it :D

WiseDraco 03-15-2017 08:09 AM

no any cvhanges - x11 still crashing. developers seems strange.

there is any alternatives xorg, for can be running xfce in slackware?

aaazen 03-15-2017 09:26 AM

Quote:

Originally Posted by WiseDraco (Post 5677997)
looks like all on that channel be asleep :D

I can understand why they are sleeping. The machine is not running pure xorg.

There is a mix of open source xorg and proprietary Nvidia.

It is unreasonable to expect open source developers to support proprietary software over which they have no control.

There is a newer Nvidia module, 378.13, with this in it's change log (release highlights):
Code:

...
Added support for X.Org xserver ABI 23 (xorg-server 1.19)
...,

Maybe try a new module?

http://www.nvidia.com/object/unix.html

http://www.nvidia.com/Download/drive...x/115031/en-us

If it still does not work, one probably has to ask the Nvidia folks for help...

orbea 03-15-2017 10:03 AM

Quote:

Originally Posted by WiseDraco (Post 5683669)
no any cvhanges - x11 still crashing. developers seems strange.

there is any alternatives xorg, for can be running xfce in slackware?

If its still happening with the newer xorg try telling ajax that. While the nvidia blob may play a role here, the crash is happening in xorg and that is where it should be fixed.

Alien Bob 03-15-2017 11:02 AM

I noticed that you have a NVIDIA GPU. Did you install the Nvidia proprietary drivers? If so, did you re-install these drivers after every upgrade of the xorg-server / mesa packages?
I could not see if you are also running multilib, in that case be sure to first update your multilib as well before upgrading the proprietary Nvidia drivers.

ReaperX7 03-16-2017 09:17 AM

Whenever you update any part of the kernel or Xorg, you should rebuild the nvidia-driver and nvidia-kernel packages and reinstall them.

As an alternative try using nvidia-switch to restore the xorg libraries and symlinks and uninstall the Nvidia packages and see if nouveau will work either by the modesetting or nouveau drivers.

Your log file actually was saying the driver and x-server were mismatched.

WiseDraco 03-17-2017 02:43 AM

Quote:

Originally Posted by aaazen (Post 5683690)
I can understand why they are sleeping. The machine is not running pure xorg.

There is a mix of open source xorg and proprietary Nvidia.

It is unreasonable to expect open source developers to support proprietary software over which they have no control.

There is a newer Nvidia module, 378.13, with this in it's change log (release highlights):
Code:

...
Added support for X.Org xserver ABI 23 (xorg-server 1.19)
...,

Maybe try a new module?

http://www.nvidia.com/object/unix.html

http://www.nvidia.com/Download/drive...x/115031/en-us

If it still does not work, one probably has to ask the Nvidia folks for help...


why you are so sure, this case is because of nvidia module?

WiseDraco 03-17-2017 02:45 AM

Quote:

Originally Posted by Alien Bob (Post 5683733)
I noticed that you have a NVIDIA GPU. Did you install the Nvidia proprietary drivers? If so, did you re-install these drivers after every upgrade of the xorg-server / mesa packages?
I could not see if you are also running multilib, in that case be sure to first update your multilib as well before upgrading the proprietary Nvidia drivers.

thanks. not know, i must reinstall nvidia driver after xorg update - never do that earlier, and not have problems with that too.

ok, yesterday i agfain get x crash, then update slackware64-current to the latest, and then install latest nvidia driver. see, who it does...


All times are GMT -5. The time now is 06:42 PM.