Jacob Bachmeyer wrote:
> Speculation: (based on a bug I encountered long ago in the ext3 driver)
There are also other causes of "BUG: soft lockup - CPU#n stuck". One of them
is bad RAM.
You can diagnose bad RAM more reliably through 'memtester' [1]. That did it
in my case (on an x86_64 machine)
Zach van Rijn via cfarm-users wrote:
On Wed, 2022-11-30 at 11:35 +0100, Pierre Muller via cfarm-users
wrote:
Just got this:
Message from syslogd@gcc102 at Nov 30 04:31:20 ...
kernel:[47393.509723] watchdog: BUG: soft lockup - CPU#2
stuck for 48s! [ppc2:203070]
Can I do anything to help fig
On Wed, 30 Nov 2022 08:45:21 -0600 Pierre Muller wrote ---
>
>
> At least 'ppc2' and 'fpmake' are most probably executable on
> my user account that are generated by my cron jobs.
>
>
> Maybe it would be wise to check if the machine is stable if my cron jobs are
> disabled.
I
At least 'ppc2' and 'fpmake' are most probably executable on
my user account that are generated by my cron jobs.
Maybe it would be wise to check if the machine is stable if my cron jobs are
disabled.
I am currently unable to login into gcc102.
I you restart the machine, please also disable
On Wed, 2022-11-30 at 11:35 +0100, Pierre Muller via cfarm-users
wrote:
> Just got this:
> Message from syslogd@gcc102 at Nov 30 04:31:20 ...
> kernel:[47393.509723] watchdog: BUG: soft lockup - CPU#2
> stuck for 48s! [ppc2:203070]
>
> Can I do anything to help figuring out the problem?
Not sur
Just got this:
Message from syslogd@gcc102 at Nov 30 04:31:20 ...
kernel:[47393.509723] watchdog: BUG: soft lockup - CPU#2 stuck for 48s!
[ppc2:203070]
Can I do anything to help figuring out the problem?
Pierre
Le 29/11/2022 à 22:30, Zach van Rijn via cfarm-users a écrit :
On Sun, 2022-11-27
