Siduction Forum
Siduction Forum => Software - Support => Topic started by: samoht on 2016/12/03, 13:37:52
-
... after d-u-ing to plasma-workspace
plasma-workspace 4:5.8.4-1
and/or recent x11 transition.
Logout via ctrl+alt+del works (logout selection comes up), window switching via alt+tab works as well ...
Login sometimes works only after restarting runlevel 5, sometimes login stops after kde icon on black background appeared but not reaching plasma desktop.
Bug reports:
http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=2976 (http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=2976)
https://bugs.kde.org/show_bug.cgi?id=373131 (https://bugs.kde.org/show_bug.cgi?id=373131)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846389 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846389)
-
So far, I am not seeing this on my main machine.
I do have nvidia blob installed, will do a du on 2 other machines (amd, nvidia cards, open source drivers) and see what happens, it's been a while for du's on those boxes ;)
-
....
sometimes login stops after kde icon on black background appeared but not reaching plasma desktop.
...
I can confirm this, after switching to runlevel 3 for du using "systemctl stop lightdm.service" and when du finished "systemctl start lightdm.service"
inxi -SG
System: Host: siductionbox Kernel: 4.8.12-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.8.4
Distro: Debian GNU/Linux stretch/sid
Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
Display Server: X.Org 1.19.0 driver: intel Resolution: 1920x1200@59.95hz
GLX Renderer: Mesa DRI Intel Ivybridge Desktop GLX Version: 3.0 Mesa 13.0.2
-
I am seeing this on another box :(
Graphics: Card: Advanced Micro Devices [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550]
Display Server: X.org 1.19.0 drivers: ati,radeon (unloaded: fbdev,vesa)
-
Same problem here. From time to time the plasma panel freezes. K-Menu doen't respond, clock stops and selection of open windows is impossible. All open/visible windows are usable and Alt-Tab, Alt-F2 works. That happens for example with krusader copy-jobs. What helps here is Ctrl+Alt+F1 and after second Atl-F7 back. After that a lot of panel notifications without content are running. Strange to describe. I hope you got ot.
It's a dual-monitor setup with a radeon card/driver.
-
There is hope now: ;)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23847025#25 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23847025#25)
xorg-server (2:1.19.0-3) unstable; urgency=medium
...
* Cherry-pick upstream commit d6da2086951,
Revert "damage: Make damageRegionProcessPending take a damage not a
drawable". Fixes a crash caused by trying to free an invalid pointer.
Closes: #847025, #848321.
-- Emilio Pozuelo Monfort <pochu@debian.org> Fri, 16 Dec 2016 19:39:45 +0100
Greetings
Tom
Pls mark as solved
-
Just wondering how others suffering from this annoyance problem have made out with the alleged cure update. It has made no difference to my machine which continues to freeze randomly and/or during the login. I guess if it's just me I will have to reload the machine. Thanks in advance for any comments.
Cliff
-
cliff6056
I still have the same problem on my amd graphics machine, can't figure it out yet, disabled compositor, nothing, freezes hard within 30-40 seconds, going to install a build I made a few days ago and see if anything changes.
-
Unfortunately, I must confirm those annoying freezes on my KDE siduction install >:(
My initial faith in the proposed fix has been of short lived kind.
-
My newest build makes no difference with/without a du, going to try older kernel when I get home from work
-
For what it's worth, still occurs on the kernel that Dev 2 came with, at least on my machine. As well, in desperation, yesterday I reloaded my machine and switched the debian repo to testing to try and get ahead of the freeze, and while everything installed and worked fine, the freezing remained.
-
Just toadd another voice:
I can watch the same behaviour as described above as well with xserver-xorg-core version 1.19.0-2 as with 1.19.0-3. But I noticed that I can get a working Plasma when switching to a Console (e.g. Ctrl-Alt-F1) and back again (Ctrl-F7). Nevertheless, that only gives me access to the Plasma functionality for a short time. But until now I did not found a deterministic way to reproduce a "freeze" again.
-
Please, to get to the bottom of this we need you to specify your graphics card and the used driver.
-
Same issue on my machine,
with both drivers xserver-xorg-core version 1.19.0-2, 1.19.0-3
System: Host: siductionbox Kernel: 4.9.0-towo.1-siduction-amd64 x86_64 (64 bit)
Desktop: KDE Plasma 5.8.4
Distro: siduction 12.2.0 Riders on the Storm - kde - (201212092131)
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v]
Display Server: X.org 1.19.0 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 90x44 Advanced Data: N/A for root
-
Hi Devil. Hope this is what you want.
System: Host: siductionbox Kernel: 4.9.0-towo.1-siduction-amd64 x86_64 (64 bit gcc: 6.2.1)
Desktop: KDE Plasma 5.8.4 (Qt 5.7.1)
Distro: siduction 15.1.0 Paint It Black - kde - (201601162135)
Machine: Device: desktop Mobo: ASUSTeK model: P5N32-E SLI v: 1.XX
BIOS: Phoenix v: ASUS P5N32-E SLI 1903 date: 11/17/2009
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) cache: 4096 KB
flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 19207
clock speeds: max: 2399 MHz 1: 2399 MHz 2: 2399 MHz 3: 2399 MHz
4: 2399 MHz
Graphics: Card: NVIDIA G92 [GeForce 8800 GT] bus-ID: 02:00.0
Display Server: X.Org 1.19.0 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@59.93hz
GLX Renderer: Gallium 0.4 on NV92
GLX Version: 3.0 Mesa 13.0.2 Direct Rendering: Yes
Audio: Card NVIDIA MCP55 High Definition Audio
driver: snd_hda_intel bus-ID: 00:0f.1
Sound: ALSA v: k4.9.0-towo.1-siduction-amd64
Network: Card-1: NVIDIA MCP55 Ethernet
driver: forcedeth port: ec00 bus-ID: 00:11.0
IF: enp0s17 state: up speed: 1000 Mbps duplex: full
mac: 00:1e:8c:ca:bd:25
Card-2: NVIDIA MCP55 Ethernet
driver: forcedeth port: eb00 bus-ID: 00:12.0
IF: enp0s18 state: down mac: 00:1e:8c:ca:c1:09
Drives: HDD Total Size: 1000.2GB (47.4% used)
ID-1: /dev/sda model: WDC_WD5000AAKS size: 500.1GB
ID-2: /dev/sdb model: WDC_WD5000AAKS size: 500.1GB
Partition: ID-1: / size: 18G used: 7.2G (43%) fs: ext4 dev: /dev/sdb1
ID-2: /home size: 49G used: 18G (38%) fs: ext4 dev: /dev/sdb3
ID-3: swap-1 size: 2.56GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 42.0C mobo: 34.0C gpu: 50.0
Fan Speeds (in rpm): cpu: 1928 sys-1: 0
Info: Processes: 218 Uptime: 7:59 Memory: 1831.1/7988.8MB
Init: systemd runlevel: 5 Gcc sys: 6.2.1
Client: Shell (bash 4.4.51) inxi: 2.3.5
-
$ dpkg -l xserver-xorg-video-nouveau
...
ii xserver-xorg-video-nouveau 1:1.0.13-1+b1 amd64 X.Org X server -- Nouveau display driver
$ dpkg -l xserver-xorg-core
...
ii xserver-xorg-core 2:1.19.0-3 amd64 Xorg X server - core server
$ inxi -G
Graphics: Card: NVIDIA GT218 [GeForce 210]
Display Server: X.Org 1.19.0 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: Gallium 0.4 on NVA8 GLX Version: 3.0 Mesa 13.0.2
-
i dont want to start a flame war, but why does one use nouveau? Isn't sid buggy enough?
-
@melmarker, I appreciate your so enormously helpful remark and respect your wish, otherwise this answer would be different ...
-
xserver-xorg-video-nouveau 1:1.0.13-1+b1 (amd64)
xserver-xorg-core 2:1.19.0-3 (amd64)
Graphics: Card: NVIDIA GF119 [GeForce GT 610]
Display Server: X.Org 1.19.0 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: Gallium 0.4 on NVD9 GLX Version: 3.0 Mesa 13.0.2
~/.xsession-errors and /var/log/Xorg.log.0 say nothing during such a "freese".
-
I don't know if this helps at all, as the problem is not with my siduction system, but with my aptosid one, but I have had the same problem for a while and had reported it in the aptosid forum (as linked above). (Since I had this problems, I am holding on DUIing my siduction system.)
Anyway, here is the system info:
root@finottim83[/home/finotti]# infobash -v3
Host/Kernel/OS "finottim83" running Linux 4.8.0-11.slh.2-aptosid-amd64 x86_64 UEFI64 [ aptosid 2013-01 Ἑσπερίδες - kde-full - (201305050307) ]
CPU Info 8x Intel Core i7-4790 @ 8192 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 3717.114 MHz ]
Videocard Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller X.Org 1.19.0 [ 1920x1200@59.95hz, 1280x1024@60.02hz ]
Network cards Intel I217-LM
Processes 324 | Uptime 2:07 | Memory 5057.6/31977.3MB | HDD Crucial_CT512M55,WDC WD5000AAKX-0,ATAPI-6 Bridge C Size 2012GB (21%used) | Client Shell | Infobash v3.50
(No Nvidia/nouveau in this one.)
-
I have to remember exactly when X.Org 1.19.0 came out,, going to install an older build for now on some secondary machines as there is no ati/amd blob for my video card (old)
-
After a newly update (mostly virtualbox packages) I had no more freeze. - sorry it freezes again ...
-
Sorry, I have had 5 straight days of 12 + hours of work days, haven't had much time for testing :(
-
I have solved this on my secondary machine
apt remove --purge xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-radeon
rebooted and no more lockups, works great
System: Host: x2 Kernel: 4.9.0-towo.2-siduction-amd64 x86_64 (64 bit) Console: tty 2
Distro: siduction 16.1.0 Patience - kde - (201701010034)
Machine: Device: desktop Mobo: Gigabyte model: M61PM-S2 BIOS: Award v: F8 date: 10/05/2007
CPU: Dual core AMD Athlon 64 X2 4200+ (-MCP-) cache: 1024 KB
clock speeds: max: 2200 MHz 1: 1000 MHz 2: 1000 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550]
Display Server: X.org 1.19.0 drivers: modesetting (unloaded: fbdev,vesa)
-
Thank you Piper!
This affected my laptop. I was going to dive into it today, perfect timing.
System: Host: dv7-siduction Kernel: 4.9.0-towo.2-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.8.4
Distro: siduction 16.1.0 Patience - kde - (201612232347)
Machine: Device: laptop System: Hewlett-Packard product: HP Pavilion dv7 Notebook PC v: 049D210000241210000020000
Mobo: Hewlett-Packard model: 3639 v: 33.23 BIOS: Hewlett-Packard v: F.13 date: 01/25/2010
Battery BAT0: charge: 47.7 Wh 100.0% condition: 47.7/51.0 Wh (93%)
CPU: Dual core AMD Turion II Ultra Mobile M620 (-MCP-) cache: 2048 KB
clock speeds: max: 2500 MHz 1: 1600 MHz 2: 1600 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v]
Display Server: X.Org 1.19.0 drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1600x900@60.08hz
-
ghstryder
Did this work for you ?
Before the purge, I had less then 2 minutes before it froze, I have tested this on 3 total builds of kde, it worked on all, latest build is the one I installed (201701010034)
-
Did this work for you ?
Before the purge, I had less then 2 minutes before it froze, I have tested this on 3 total builds of kde, it worked on all, latest build is the one I installed (201701010034)
Yes Piper - mine would freeze that often so if I'm not calling this a fix I am fervently hoping it is. I couldn't "force" it to freeze, but just opening windows would do it, as well as just allowing it to sit. I couldn't find anything searching, and I had forgotten this post.
I've done a number of things since trying your fix - there is no way I'd be typing this before, it would have frozen long ago. Thanks again!
-
Ok great !
Glad it worked, my box was totally unusable before this.
-
That's very strange... My work system with Intel video is freezing. (See above: it's running aptosid, not siduction.) I can't try the fix now, as I am off work, but it seems unlikely to me that this would work on that system.
By the way, the freezes seem very random to me. I've had a few whole days without any freezes, and then, randomly, it would freeze again.
But I will definitely try it! Thanks for sharing.
-
finotti
You could try
apt remove --purge xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-radeon xserver-xorg-video-intel
Remember to reboot
If it doesn't do a thing, you can always reinstall them
-
Thanks piper. I will try that. But I am confused: purging xserver-xorg-video-intel won't break X, as I am using intel driver?
-
If it don't boot, just reinstall xserver-xorg-video-intel
You can also try a 4.7.0-x series kernel if removing xserver-xorg-video-intel don't work
-
OK, removing xserver-xorg-video-intel I cannot start X. Just removing the other packages had no effect... Still freezes. I will try an older kernel later.
Thanks for your help,
Luis
-
Thanks for the feedback.
I didn't think removing xserver-xorg-video-intel would work, why I edited my post to the earlier kernel, it worked for some people with the intel video (kernel)
You could try this also before a different kernel
In /etc/X11/xorg.conf.d/20-intel.conf
Make it look like
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "3"
EndSection
reboot
-
4 month ago I removed the intel-video-driver. Since that, I have no more problems with short freezes.
$ inxi -CG
CPU: Quad core Intel Core i7-4702MQ (-HT-MCP-) cache: 6144 KB
clock speeds: max: 3200 MHz 1: 2201 MHz 2: 2213 MHz 3: 2213 MHz 4: 2220 MHz 5: 2200 MHz 6: 2200 MHz
7: 2265 MHz 8: 2201 MHz
Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
Card-2: NVIDIA GK106M [GeForce GTX 765M]
Display Server: X.Org 1.19.0 drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 13.0.2
-
I now solved the problem by simply installing the nvidia-driver instead of nouveau!
-
Just as follow-up, I removed as per Piper's post, and as well installed nvidia-legacy-340xx-driver, and have not had a freeze for 24 hours.
Thanks Piper.
-
Thanks for the feedback.
I didn't think removing xserver-xorg-video-intel would work, why I edited my post to the earlier kernel, it worked for some people with the intel video (kernel)
You could try this also before a different kernel
In /etc/X11/xorg.conf.d/20-intel.conf
Make it look like
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "3"
EndSection
reboot
@piper: It seems that, indeed, adding
Option "DRI" "3"
fixed the problem. I want to be a bit cautious here, as I had this bug seem to go away before and come back, but it has been a few days without problems. Thanks for your help!
-
Nothing wrong with being cautious, I myself keep waiting for the lockup, so far so good.
Glad to be of assistance ;)
-
Thanks, piper, I adopted your suggestion for my nouveau driven desktop by creating the file
/etc/X11/xorg.conf.d/20-xorg-nouveau.conf
-----------------------------------------------------
Section "Device"
Option "DRI" "3"
Identifier "Nvidia Card"
Driver "nouveau"
BusID "PCI:1:0:0"
EndSection
-----------------------------------------------------
I did not recognize a freese for several hours now and I hope that this might be the (temporary) solution to get rid of that bug (although the BusID may be omitted).
Comparing the /var/log/Xorg.0.log, I now see the entries makred with "(**)" since now they are coming from the configuration file:
[ 2407.593] (**) NOUVEAU(0): Option "DRI" "3"
...
[ 2407.593] (**) NOUVEAU(0): Allowed maximum DRI level 3.
Before that change I saw that only DRI-Level 2 has been used by default:
[ 26931.919] (==) NOUVEAU(0): Allowed maximum DRI level 2.
So this works form me.
-
glimfindel
Thanks for the feedback.
I actually never thought of doing that outside of intel (which I don't own) and this was in my notes and where it was in my notes makes it kinda old(ish) and most likely got the info from a google search somewhere down the line :)
I will do some testing with this using
xserver-xorg-video-ati / xserver-xorg-video-radeon
Thanks to all who tried/tested and gave feedback, hopefully this helps others :)
-
I will do some testing with this using
xserver-xorg-video-ati / xserver-xorg-video-radeon
Thanks Piper that works for me
bevo
-
Hi all,
upstream pretends that this annoying bug should be fixed:
https://bugs.freedesktop.org/show_bug.cgi?id=99333#c4 (https://bugs.freedesktop.org/show_bug.cgi?id=99333#c6)
https://bugs.freedesktop.org/attachment.cgi?id=128844 (https://bugs.freedesktop.org/attachment.cgi?id=128844)
xorg-server (2:1.19.1-1) unstable; urgency=medium
...
[ Andreas Boll ]
* New upstream release.
- AttendClient of grab-pervious client must queue to
saved_ready_clients [v2] (Closes: #846779, #850940).
- present: Only call present_flip_notify if vblank->queued == FALSE
(Closes: #849250).
...
Greetings,
Tom
-
I just got the update for xserver-xorg-core 1.19.1-4 by a d-u, and noticed that bug above mentioned in the changelog:
/usr/share/doc/xserver-xorg-core/changelog.gz:
----------------------------------------------------------------------
...
commit 82dcb68a8782d0cce6e6ce1a375cda05c91fe8c3
Author: Keith Packard <keithp@keithp.com>
Date: Mon Jan 9 18:10:21 2017 -0800
AttendClient of grab-pervious client must queue to saved_ready_clients [v2]
A client which is attended while a grab is blocking execution of its
requests needs to be placed in the saved_ready_clients list so that it
will get scheduled once the grab terminates. Otherwise, if the client
never sends another request, there is no way for it to be placed in
the ready_clients list.
v2: Wrap comment above mark_client_saved_ready.
Remove test for OS_COMM_IGNORED which will always be true.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99333
Reviewed-by: Adam Jackson <ajax@redhat.com>
Signed-off-by: Keith Packard <keithp@keithp.com>
(cherry picked from commit 785053d033e73d2deb0ded4b97eabfd881991978)
...
-----------------------------------------------------------------
I did not see any freese, although I removed the workaround (DRI Level = 3).
so please have a try.