[Bug 1131752] New: X server dies after resuming from hibernation
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 Bug ID: 1131752 Summary: X server dies after resuming from hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: opensuse@mike.franken.de QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Sometimes, but not always my X server dies after the system has successfully resumed from hibernation. It is restarted then, so I can login, but of course my previous session is lost. It *seems* to happen only, when the notebook is connected to the Thunderbolt dock (see below) and the external monitor is used. Xorg.log.old contains: ------------------------< snip snip snip >----------------------------- ... [ 65043.707] (II) AIGLX: Suspending AIGLX clients for VT switch [ 65050.192] (II) AIGLX: Resuming AIGLX clients after VT switch [ 65050.212] (EE) modeset(0): failed to set mode: Invalid argument [ 65050.212] (EE) Fatal server error: [ 65050.212] (EE) EnterVT failed for screen 0 [ 65050.212] (EE) [ 65050.212] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 65050.212] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 65050.212] (EE) [ 65050.216] (II) AIGLX: Suspending AIGLX clients for VT switch [ 65050.266] (EE) Server terminated with error (1). Closing log file. ------------------------< snip snip snip >----------------------------- journal says: ------------------------< snip snip snip >----------------------------- org.a11y.Bus[2632]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" org.a11y.Bus[2632]: after 23769 requests (23769 known processed) with 0 events remaining. ------------------------< snip snip snip >----------------------------- - openSUSE Tumbleweed with latest snapshot - Linux thunder 5.0.3-1-default #1 SMP Fri Mar 22 17:30:35 UTC 2019 (2a31831) x86_64 x86_64 x86_64 GNU/Linux - notebook Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.8.1 02/14/2019 - Thunderbolt docking station CalDigit TS3 Plus - my monitor is connected to the display port connector of this docking station -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c1 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |opensuse@mike.franken.de Flags| |needinfo?(opensuse@mike.fra | |nken.de) --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. Could you attach the complete /var/log/Xorg.0.log.old right after this has happeneded? Please also boot with kernel options: drm.debug=0x1e log_buf_len=1M Then also attach the output of dmesg after this has happened. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c2 --- Comment #2 from Michael Hirmke <opensuse@mike.franken.de> --- I prepared everything according to your advice, then updated the system to the latest Tumbleweed snapshot (20190408) - and now I am not able to reproduce the problem. New kernel? I'll keep an eye on it. If it won't come back, I'll close the case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse@mike.fra | |nken.de) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c3 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Let's close as fixed if it's no longer reproducible. You can still reopen it if it occurs again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c4 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #4 from Michael Hirmke <opensuse@mike.franken.de> --- The X server crash reoccurred today 8-< Of course I've already switched off drm debugging, because of the exorbitant number of messages it produces. So I add the Xorg.log.old and the dmesg output up to the crash messages. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c5 --- Comment #5 from Michael Hirmke <opensuse@mike.franken.de> --- Created attachment 803069 --> http://bugzilla.opensuse.org/attachment.cgi?id=803069&action=edit Xorg.log.old -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c6 --- Comment #6 from Michael Hirmke <opensuse@mike.franken.de> --- dmesg.log was uploaded to ftp://support-ftp.suse.com/in/ - sorry, forgot to add the bug number to the file name 8-< -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #803069|application/x-trash |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c7 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Flags| |needinfo?(opensuse@mike.fra | |nken.de) --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Please attach dmesg.log here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c8 --- Comment #8 from Michael Hirmke <opensuse@mike.franken.de> --- Better not - too many sensible information 8-< I uplaod it again - name is 1131752-dmes.log. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c9 --- Comment #9 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Michael Hirmke from comment #8)
Better not - too many sensible information 8-< I uplaod it again - name is 1131752-dmes.log.
Ok. Then please remove this sensible information from the log. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c10 --- Comment #10 from Michael Hirmke <opensuse@mike.franken.de> --- How should I do this? IMHO nearly everything in a log like this is sensible. As I wrote: I uploaded the log with the correct name. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c11 --- Comment #11 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. The last time somebody uploaded anything to incoming directory of our ftp server was - I believe - in the 90s. I would need to figure out, where to find this directory in our mounted tree ... I'm surprised that uploading to the incoming dir of our ftp server still works. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c12 --- Comment #12 from Stefan Dirsch <sndirsch@suse.com> --- Ok. I know where I could find it, if you reupload it to ftp://ftp.suse.com/pub/incoming (or a subdirectory there) No idea where to find things, which have been uploaded to ftp://support-ftp.suse.com/in/ I'm sorry. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c13 --- Comment #13 from Michael Hirmke <opensuse@mike.franken.de> --- But this is what your website states. One should upload to ftp://support-ftp.suse.com/in/. In one of my recent bug reports someone from SUSE even told me explicitly to do so: ----- You can use the upload location for supportconfig as outlined at: https://www.suse.com/support/kb/doc/?id=7023007 Afterwards, please let me know the filename (best is if you add the bug number to the filename). ----- It was Thomas Blume. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c14 --- Comment #14 from Stefan Dirsch <sndirsch@suse.com> --- Ok. this is meant for enterprise product customers. Here you are reporting as a user of a community product ... But meanwhile I could find the file. At least I hope so. # ls -l dmesg.log -rw-r--r-- 1 sndirsch users 351275 Apr 18 06:07 dmesg.log # md5sum dmesg.log f0d0490cc564f20cbc63db82c971790b dmesg.log Is this the right file? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c16 --- Comment #16 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Michael Hirmke from comment #5)
Created attachment 803069 [details] Xorg.log.old
[ 56198.420] (EE) modeset(0): failed to set mode: Invalid argument This reminds me to boo#1129027
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c17 --- Comment #17 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #14)
Ok. this is meant for enterprise product customers. Here you are reporting as a user of a community product ...
But meanwhile I could find the file. At least I hope so.
# ls -l dmesg.log -rw-r--r-- 1 sndirsch users 351275 Apr 18 06:07 dmesg.log
# md5sum dmesg.log f0d0490cc564f20cbc63db82c971790b dmesg.log
Is this the right file?
I already deleted my local copy, but from the contents shown in your next comment it seems to be my file, yes. And sorry for the confusion regarding the ftp server. I didn't know it was for enterprise customers only. Just used it, because I was told so. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c18 --- Comment #18 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #16)
(In reply to Michael Hirmke from comment #5)
Created attachment 803069 [details] Xorg.log.old
[ 56198.420] (EE) modeset(0): failed to set mode: Invalid argument This reminds me to boo#1129027
This doesn't look promising - as you wrote there, the problem was never addressed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c19 --- Comment #19 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Michael Hirmke from comment #17)
I already deleted my local copy, but from the contents shown in your next comment it seems to be my file, yes.
Well, I referred in my comment#16 to Xorg.0.log.old from comment #5. Seems drm.debug=0x1e has not been set (only log_buf_len=1M) , so dmesg.log would be rather useless anyway. I will check, whether I can also find 1131752-dmes.log. Thanks for the pointer to our documentation about how to upload files to our ftp server! :-) (In reply to Michael Hirmke from comment #18)
Xorg.log.old
[ 56198.420] (EE) modeset(0): failed to set mode: Invalid argument This reminds me to boo#1129027
This doesn't look promising - as you wrote there, the problem was never addressed.
We fixed it in our kernel. In the long-term it should also be addressed in the modesetting X driver though. Therefore the bug is still open. I'm just not sure, whether this issue has also been fixed upstream and in our TW kernel (bug is against Leap 15.1) ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c20 --- Comment #20 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #19)
(In reply to Michael Hirmke from comment #17)
I already deleted my local copy, but from the contents shown in your next comment it seems to be my file, yes.
Well, I referred in my comment#16 to Xorg.0.log.old from comment #5. Seems drm.debug=0x1e has not been set (only log_buf_len=1M) , so dmesg.log would be rather useless anyway. I will check, whether I can also find 1131752-dmes.log. Thanks for the pointer to our documentation about how to upload files to our ftp server! :-)
you're welcome :))
(In reply to Michael Hirmke from comment #18)
Xorg.log.old
[ 56198.420] (EE) modeset(0): failed to set mode: Invalid argument This reminds me to boo#1129027
This doesn't look promising - as you wrote there, the problem was never addressed.
We fixed it in our kernel. In the long-term it should also be addressed in the modesetting X driver though. Therefore the bug is still open. I'm just not sure, whether this issue has also been fixed upstream and in our TW kernel (bug is against Leap 15.1) ...
Uh, in this case it would be great if it hasn't been fixed in the Tumbleweed kernel yet :) Should I install the 15.1 kernel and test with this one? Or the kernel from the kernel stable repo? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c21 --- Comment #21 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Michael Hirmke from comment #20)
Uh, in this case it would be great if it hasn't been fixed in the Tumbleweed kernel yet :) Should I install the 15.1 kernel and test with this one?
Not needed.
Or the kernel from the kernel stable repo?
Just verified, that it has also been fixed in TW kernel. So it would be enough to test the current TW kernel. When testing this kernel make sure that in RPM changelog of kernel packages bug number #1129027 is being mentioned. Check with something like this --> rpm --changelog -q kernel-default | grep -A 5 - B5 #1129027 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c23 --- Comment #23 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Stefan Dirsch from comment #21)
--> rpm --changelog -q kernel-default | grep -A 5 - B5 #1129027
rpm --changelog -q kernel-default | grep -A 5 -B5 129027 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c24 --- Comment #24 from Michael Hirmke <opensuse@mike.franken.de> --- rpm --changelog -q kernel-default | grep -A 5 -B5 129027 - efifb: Omit memory map check on legacy boot (bsc#1127339). - commit 0b95959 * So Mär 31 2019 tiwai@suse.de - Revert "drm/i915/fbdev: Actually configure untiled displays" (bsc#1129027, bsc#1131048). - commit 591a6df * Do Mär 28 2019 yousaf.kaukab@suse.com - config: arm64: enable CPPC support - commit 1a52e49 -- - efifb: Omit memory map check on legacy boot (bsc#1127339). - commit 0b95959 * So Mär 31 2019 tiwai@suse.de - Revert "drm/i915/fbdev: Actually configure untiled displays" (bsc#1129027, bsc#1131048). - commit 591a6df * Do Mär 28 2019 yousaf.kaukab@suse.com - config: arm64: enable CPPC support - commit 1a52e49 So it is not included, as far as I can see - but this is the latest Tumbleweed kernel: Source Timestamp: 2019-04-04 04:40:16 +0000 GIT Revision: dff56e4988727a44631953af28f369dc6f96cd57 GIT Branch: stable Distribution: openSUSE Tumbleweed Name : kernel-default Version : 5.0.7 Release : 1.2 Architecture: x86_64 Install Date: So 14 Apr 2019 21:09:53 CEST Group : System/Kernel Size : 363591960 License : GPL-2.0 Signature : RSA/SHA256, Do 11 Apr 2019 17:45:18 CEST, Key ID b88b2fd43dbdc284 Source RPM : kernel-default-5.0.7-1.2.nosrc.rpm Build Date : Do 11 Apr 2019 17:38:29 CEST Build Host : cloud131 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE URL : http://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2019-04-06 14:47:49 +0000 GIT Revision: 8f1834244edbe34ab85ed17d5b24ab001b03cc5a GIT Branch: stable Distribution: openSUSE Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c25 --- Comment #25 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Michael Hirmke from comment #24)
rpm --changelog -q kernel-default | grep -A 5 -B5 129027 - efifb: Omit memory map check on legacy boot (bsc#1127339). - commit 0b95959
* So Mär 31 2019 tiwai@suse.de - Revert "drm/i915/fbdev: Actually configure untiled displays" (bsc#1129027, bsc#1131048). - commit 591a6df
This is the revert. So it's included. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c26 --- Comment #26 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Stefan Dirsch from comment #19)
(In reply to Michael Hirmke from comment #17)
I already deleted my local copy, but from the contents shown in your next comment it seems to be my file, yes.
Well, I referred in my comment#16 to Xorg.0.log.old from comment #5. Seems drm.debug=0x1e has not been set (only log_buf_len=1M) , so dmesg.log would be rather useless anyway. I will check, whether I can also find 1131752-dmes.log.
Found this one as well. Unfortunately it has the same content (only a few network message are different). So I need this again with the right kernel options set. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c27 --- Comment #27 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #26)
(In reply to Stefan Dirsch from comment #19)
(In reply to Michael Hirmke from comment #17)
I already deleted my local copy, but from the contents shown in your next comment it seems to be my file, yes.
Well, I referred in my comment#16 to Xorg.0.log.old from comment #5. Seems drm.debug=0x1e has not been set (only log_buf_len=1M) , so dmesg.log would be rather useless anyway. I will check, whether I can also find 1131752-dmes.log.
Found this one as well. Unfortunately it has the same content (only a few network message are different). So I need this again with the right kernel options set.
Ok, actually the system runs with this kernel option. As soon as X server crashes again, I'll upload the files again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c28 --- Comment #28 from Michael Hirmke <opensuse@mike.franken.de> --- I uploaded 1131752-debug.tbz to ftp://support-ftp.suse.com/in/. It contains dmesg.log and Xorg.0.log.old. drm.debug=0x1e was active. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c33 --- Comment #33 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #32)
Ok. This time debugging was enabled, but I can't see anything obviously wrong in the log. :-(
There is too many debug information written in a given period of time, so the really interesting lines seem to have been overwritten. Can I reduce the amount of debug information? Or can I increase the log size? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c34 --- Comment #34 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. The logsize is already increased via log_buf_len=1M ... You can also try with drm.debug=0x6 (without PRIME and ATOMIC messages) # modinfo drm [...] parm: debug:Enable debug output, where each bit enables a debug category. Bit 0 (0x01) will enable CORE messages (drm core code) Bit 1 (0x02) will enable DRIVER messages (drm controller code) Bit 2 (0x04) will enable KMS messages (modesetting code) Bit 3 (0x08) will enable PRIME messages (prime code) Bit 4 (0x10) will enable ATOMIC messages (atomic code) Bit 5 (0x20) will enable VBL messages (vblank code) Bit 7 (0x80) will enable LEASE messages (leasing code) (int) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c35 --- Comment #35 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Stefan Dirsch from comment #34)
Hmm. The logsize is already increased via log_buf_len=1M ...
This is embarassing for me. The logfile was about 1MB in size. So, yes you can increase that of course ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c36 --- Comment #36 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #35)
(In reply to Stefan Dirsch from comment #34)
Hmm. The logsize is already increased via log_buf_len=1M ...
This is embarassing for me. The logfile was about 1MB in size. So, yes you can increase that of course ...
Hopefully dmesg output from today contains more useful information. I uploaded it to ftp://support-ftp.suse.com/in/ again. Filename is 1131752-20190624-debug.tbz. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c37 --- Comment #37 from Michael Hirmke <opensuse@mike.franken.de> --- In the last days I switched back and forth between the modesetting and the intel driver for the X server - and it seems, as if only the modesetting driver has the problem. When using the intel driver, the X server survives a hibernate/resume cycle. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c38 --- Comment #38 from Stefan Dirsch <sndirsch@suse.com> --- Interesting result. At least a workaround. Unfortunately I couldn't look into your new file 1131752-20190624-debug.tbz yet. The person, who knows where to copy it from hasn't answered yet. :-( If you could upload it to ftp://ftp.suse.com/ pub/incoming instead, I would have access to it myself. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c39 --- Comment #39 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #38)
Interesting result. At least a workaround. Unfortunately I couldn't look into your new file 1131752-20190624-debug.tbz yet. The person, who knows where to copy it from hasn't answered yet. :-( If you could upload it to
ftp://ftp.suse.com/ pub/incoming
instead, I would have access to it myself.
Seems I don't have permissions to write a file there: ftp ftp://ftp.suse.com/ Trying 195.135.221.132:21 ... Connected to ftp.suse.com. 220 "Welcome to ftp.suse.com" 331 Please specify the password. 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. 200 Switching to Binary mode. ftp> cd pub/incoming 250 Directory successfully changed. ftp> bin 200 Switching to Binary mode. ftp> put 1131752-20190624-debug.tbz local: 1131752-20190624-debug.tbz remote: 1131752-20190624-debug.tbz 229 Entering Extended Passive Mode (|||30475|). 553 Could not create file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c40 --- Comment #40 from Stefan Dirsch <sndirsch@suse.com> --- Thanks for trying. This is embarassing for us. Looks like our internal documentation is no longer valid. :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c42 --- Comment #42 from Stefan Dirsch <sndirsch@suse.com> --- [ 31463.805] (II) AIGLX: Suspending AIGLX clients for VT switch [ 31470.512] (II) AIGLX: Resuming AIGLX clients after VT switch [ 31470.533] (EE) modeset(0): failed to set mode: Invalid argument [ 31470.533] (EE) Fatal server error: [ 31470.533] (EE) EnterVT failed for screen 0 [ 31470.533] (EE) [ 31470.534] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 31470.534] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 31470.534] (EE) [ 31470.536] (II) AIGLX: Suspending AIGLX clients for VT switch [ 31470.604] (EE) Server terminated with error (1). Closing log file. [31470.484756] systemd[1]: Starting Backup RPM database... [31470.488935] systemd[1]: Starting Load/Save RF Kill Switch Status... [31470.505947] systemd[1]: check-battery.service: Succeeded. [31470.506282] systemd[1]: Started Check if mainboard battery is Ok. [31470.511829] systemd[1]: Started Load/Save RF Kill Switch Status. [31470.538024] systemd[1]: snapper-timeline.service: Succeeded. [31470.544145] PM: hibernation exit [31470.545118] systemd-sleep[20283]: System resumed. Hmm. I don't seem to find anything obvious in dmesg here. :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c45 --- Comment #45 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Stefan Dirsch from comment #42)
Hmm. I don't seem to find anything obvious in dmesg here. :-(
Back from vacation 8-( Can I provide more information in any way? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c46 --- Comment #46 from Stefan Dirsch <sndirsch@suse.com> --- Not really. I'm running out of ideas. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c47 --- Comment #47 from Michael Hirmke <opensuse@mike.franken.de> --- Problem still exists with latest Tumbleweed snapshot and latest Mesa version. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1131752 http://bugzilla.opensuse.org/show_bug.cgi?id=1131752#c50 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WORKSFORME --- Comment #50 from Michael Hirmke <opensuse@mike.franken.de> --- Decided to stay with the Intel driver permanently. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com