Hi Paul,
On Sun, Jul 03, 2022 at 09:57:59PM +0200, Paul Gevers wrote:
> Hi all,
>
> Just a minor follow-up. I just had to restart one of my arm64 workers again.
>
> root@ci-worker-arm64-05:~# uname -a
> Linux ci-worker-arm64-05 5.10.0-15-arm64 #1 SMP Debian 5.10.120-1
> (2022-06-09) aarch64
Hi all,
Just a minor follow-up. I just had to restart one of my arm64 workers again.
root@ci-worker-arm64-05:~# uname -a
Linux ci-worker-arm64-05 5.10.0-15-arm64 #1 SMP Debian 5.10.120-1
(2022-06-09) aarch64 GNU/Linux
Anything you want me to extract from the current logs?
Paul
Hi Paul,
On Thursday, 23 June 2022 10:44:49 CEST Paul Gevers wrote:
> Hi Diederik,
>
> On 22-06-2022 23:15, Diederik de Haas wrote:
> > Hmm ...interesting. AFAIK that is a watchdog's task.
> >
> > On Saturday, 4 December 2021 22:44:38 CEST Paul Gevers wrote:
> >> I noticed in the logs that
Hi Diederik,
On 22-06-2022 23:15, Diederik de Haas wrote:
Hmm ...interesting. AFAIK that is a watchdog's task.
And I was certain I saw sth about it as I've seen (a yet to be reported) an
issue related to watchdog myself, hence why I remembered it.
On Saturday, 4 December 2021 22:44:38 CEST
On Wednesday, 22 June 2022 23:15:46 CEST Diederik de Haas wrote:
> Via sources.list.erb I found that "<%= node['debian_release'] %>-backports"
> gets enabled, which I assume results in Stable-backports.
> It appears that various tools get installed (but I don't see qemu mentioned
> (explicitly)),
Hi Paul,
On Wednesday, 22 June 2022 21:57:06 CEST Paul Gevers wrote:
> On 21-06-2022 23:19, Diederik de Haas wrote:
>
> > I think that the install logs aren't that important (anymore) as the
> > issue/symptoms appear to be the same:
> > - some swap action resulting in some failure
> > - CPU gets
Hi Diederik,
On 21-06-2022 23:19, Diederik de Haas wrote:
I think that the install logs aren't that important (anymore) as the issue/
symptoms appear to be the same:
- some swap action resulting in some failure
- CPU gets stuck
- watchdog triggers a reboot
If the reboot would actually
Hi,
On Tuesday, 21 June 2022 22:31:45 CEST Paul Gevers wrote:
> On 21-06-2022 22:07, Diederik de Haas wrote:
>
> > Do these errors still occur? Still with 5.10.103-1 or a later one?
>
> The last occurrence of a machine hang I had is from 5 May 2022, but I'm
> not sure if I checked if it was
Hi Diederik,
On 21-06-2022 22:07, Diederik de Haas wrote:
Do these errors still occur? Still with 5.10.103-1 or a later one?
The last occurrence of a machine hang I had is from 5 May 2022, but I'm
not sure if I checked if it was this same issue. Normally our kernels
are up-to-date, but I
Control: found -1 linux/5.10.103-1
Hi Paul,
On Tuesday, 29 March 2022 20:58:59 CEST Paul Gevers wrote:
> On 20-02-2022 13:44, Paul Gevers wrote:
>
> > Sad to say, but this week we had two hangs again.
>
> And this week another two.
>
> ci-worker-arm64-07 ==
>
> Mar
Hi all,
On 04-12-2021 22:44, Paul Gevers wrote:
On Thu, 02 Dec 2021 13:44:15 +0100 Paul Gevers wrote:
The last couple of days, two of the ci.debian.net arm64 workers became
unresponsive. The systems were rebooted and I found the message in
the journal pasted below.
Of course the absence of
Hi,
On Thu, 02 Dec 2021 13:44:15 +0100 Paul Gevers wrote:
The last couple of days, two of the ci.debian.net arm64 workers became
unresponsive. The systems were rebooted and I found the message in
the journal pasted below.
Please let me know if you need more info about these systems.
As
12 matches
Mail list logo
