I'm also seeing this issue, also on a Debian Linux 4.19 kernel (on
updated Debian unstable VM), also on KVM, straight after rebooting the
VM. But without any suspending involved, I just reboot the VM, and as
soon as I can log in after rebooting its showing 6+ days of uptime.
The uptime jumps
Hi Salvatore,
>p.s.: my earlier reply to you seem to have been rejected and never
> reached you, hope this one does now.
if you sent from Googlemail, it may reach me in the next weeks or
never *shrug* they don’t play nice with greylisting. The -submitter
or @d.o works, though. I’m following
Hi Thorsten,
On Wed, Jan 02, 2019 at 05:39:39PM +0100, Salvatore Bonaccorso wrote:
> Hi Thorsten,
>
> On Wed, Jan 02, 2019 at 04:08:23PM +, Thorsten Glaser wrote:
> > Package: src:linux
> > Version: 4.19.13-1
> > Severity: normal
> >
> > I???ve just rebooted this VM and get:
> >
> > root@ci
Hi Thorsten,
On Wed, Jan 02, 2019 at 04:08:23PM +, Thorsten Glaser wrote:
> Package: src:linux
> Version: 4.19.13-1
> Severity: normal
>
> I’ve just rebooted this VM and get:
>
> root@ci-busyapps:~ # uptime
> 16:06:57 up 58 days, 21:22, 1 user, load average: 0.62, 0.98, 0.46
>
> In syslo
Package: src:linux
Version: 4.19.13-1
Severity: normal
I’ve just rebooted this VM and get:
root@ci-busyapps:~ # uptime
16:06:57 up 58 days, 21:22, 1 user, load average: 0.62, 0.98, 0.46
In syslog, I see this:
Jan 2 15:55:01 ci-busyapps CRON[3287]: (root) CMD (command -v debian-sa1 >
/dev/n
5 matches
Mail list logo
