-
Notifications
You must be signed in to change notification settings - Fork 96
Open
Description
Just a few minutes ago I saw this from my byobu remote session:
e>/-1, .owner_cpu: 152518656 [0/0]
Message from syslogd@nas at Nov 4 16:25:26 ...
kernel:[66559.853169] BUG: spinlock lockup suspected on CPU#3, swapper/3/0
Message from syslogd@nas at Nov 4 16:25:26 ...
kernel:[66559.857273] lock: 0xffffffc0f5e27e10, .magic: 00000040, .owner: <non
e>/-1, .owner_cpu: 152518656
Message from syslogd@nas at Nov 4 16:25:26 ...
kernel:[66552.808519] BUG: spinlock bad magic on CPU#3, swapper/3/0
Message from syslogd@nas at Nov 4 16:25:26 ...
kernel:[66552.809119] lock: 0xffffffc0f5e27e10, .magic: 00000040, .owner: <non
e>/-1, .owner_cpu: 152518656
Message from syslogd@nas at Nov 4 16:25:26 ...
kernel:[66559.853169] BUG: spinlock lockup suspected on CPU#3, swapper/3/0
Message from syslogd@nas at Nov 4 16:25:26 ...
kernel:[66559.857273] lock: 0xffffffc0f5e27e10, .magic: 00000040, .owner: <non
e>/-1, .owner_cpu: 152518656
And then my R64 just reached a complete lockdown. Have no idea what happened, what caused this.
Metadata
Metadata
Assignees
Labels
No labels