Dear systemd folks,
Some of you might be interested in firmware. The Open Source Firmware
Conference 2020 [1] is going to start today.
Kind regards,
Paul
[1]: https://osfc.io
--- Begin Message ---
Hello people,
This is a last reminder on the upcoming OSFC 2020 (www.osfc.io) which will
Hi!
Seeing this before, my guess was that at some point the kernel message buffer
is frozen (not read). Then after resume the messages are read from the kernel
buffer and logged.
Ulrich
>>> Paul Menzel schrieb am 01.12.2020
um
12:45 in Nachricht
On Tue, Dec 1, 2020 at 2:31 PM Mantas Mikulėnas wrote:
> On Tue, Dec 1, 2020 at 1:46 PM Paul Menzel <
> pmenzel+systemd-de...@molgen.mpg.de> wrote:
>
>>
>> At least to me, some of the entries with timestamps from resuming should
>> have timestamps from suspending. Is the reason, that “suspend
Dear systemd folks,
Using Debian sid/unstable with systemd 246.5, suspend and resuming a
Dell Precision 3540 the timestamps below can be seen.
```
Nov 28 19:58:47.516555 morley systemd[1]: Reached target Sleep.
Nov 28 19:58:47.517585 morley systemd[1]: Starting Suspend...
Nov 28
On Tue, Dec 1, 2020 at 1:46 PM Paul Menzel <
pmenzel+systemd-de...@molgen.mpg.de> wrote:
>
> At least to me, some of the entries with timestamps from resuming should
> have timestamps from suspending. Is the reason, that “suspend message“
> was only written to the journal after resume?
>
