Mailinglist Archive: opensuse (1352 mails)

< Previous Next >
Re: [opensuse] Black display on media server
On 2018-06-18 19:45, Felix Miata wrote:
Carlos E. R. composed on 2018-06-18 12:39 (UTC+0200):

Felix Miata wrote:

...>> Nothing shows in the journal about display power around 1337508.841?

And what time is that? Because it might be some relative time to when
xorg was started weeks ago.

When you woke the display up from whatever mode constitutes sleep:
[1337508.841] (II) AIGLX: Resuming AIGLX clients after VT switch
[1337508.841] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI3 using pipe
2, position (0, 0), rotation normal, reflection none

I don't see calendar time there.
I see "1337508.841" which I can not read.

The log starts:

[ 432.065]
X.Org X Server 1.18.3
Release Date: 2016-04-04
[ 432.065] X Protocol Version 11, Revision 0


So those are probably milliseconds since X started. It is impossible to
correlate "1337508.841" to the date/time stamp in other logs. In that
case it means 1337, less than one hour since start X, so not relevant at
all then.

It might be when I switched via keyboard without seeing the display to
virtual terminal 1 (ctrl-alt-f1), or VT 1

Notice that the boot session started:

Jun 02 12:47:09 Isengard systemd-journald[115]: Runtime journal
(/run/log/journal/) is currently using 8.0M.

till today:

Jun 18 12:44:36 Isengard systemd-journald[381]: Journal stopped

The problem was yesterday, sometime from 00 till the morning. No "hdmi"
or "vt" or "aigl" in the journal (since Jun 17 00:00:01).

No, I must be confused, it must has happened the night of Jun 17,
because I posted Jun 18 01:04 hours. But any way, I looked in the entire
log since Jun 17 00:00:01.

Huh, the journal doesn't cover it all:

Jun 17 09:06:51 Isengard kernel: SFW2-INext-DROP-DEFLT
...skipping...
Jun 17 23:40:01 Isengard systemd[1]: Started Session 7476 of user root.

that "skipping" is not mine. I'm using "journalctl --boot=-1". I'll go
and see the /var/log/messages file instead.

[...]

This is the trigger:

<0.2> 2018-06-17T19:24:55.009844+02:00 Isengard systemd-coredump 30726 -
- Process 32623 (kodi.bin) of user 1000 dumped core.

There is a corresponding kodi_crashlog-20180617_192455.log file, single
crash that day.

Then comes a lot of ssh activity, I was configuring publickey auth.

And nothing of interest till:

<0.2> 2018-06-18T00:36:53.031888+02:00 Isengard systemd-coredump 15982 -
- Process 15939 (kodi.bin) of user 1000 dumped core.

which means that sometime during those six hours I had restarted
manually kodi, thus got the display failing and working in that
interval. No idea of when exactly I called "kodi" manually.




The current Xorg.0.log says:

[ 39.058] (==) intel(0): DPMS enabled

Despite /etc/X11/xorg.conf.d/50-monitor.conf:

Section "Monitor"
Identifier "DefaultMonitor"
Option "DPMS" "off"
EndSection


The log says:

[ 38.951] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 18
12:50:29 2018
[ 38.955] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 38.955] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 38.970] (==) No Layout section. Using the first Screen section.
[ 38.970] (==) No screen section available. Using defaults.
[ 38.970] (**) |-->Screen "Default Screen Section" (0)
[ 38.970] (**) | |-->Monitor "<default monitor>"
[ 38.970] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.


It is ignoring the manual config. I'll try "Default Monitor" instead.

--
Cheers / Saludos,

Carlos E. R.
(from 42.3 x86_64 "Malachite" at Telcontar)

< Previous Next >
Follow Ups