On 9/30/22 12:31, Andriy Gapon wrote:
On 26/09/2022 18:13, Hans Petter Selasky wrote:
On 9/23/22 23:43, Hans Petter Selasky wrote:
vpanic() at 0x808f4c84 = vpanic+0x184/frame 0xfe003590e900
panic() at 0x808f4a33 = panic+0x43/frame 0xfe003590e960
sleepq_add() at
On 26/09/2022 18:13, Hans Petter Selasky wrote:
On 9/23/22 23:43, Hans Petter Selasky wrote:
vpanic() at 0x808f4c84 = vpanic+0x184/frame 0xfe003590e900
panic() at 0x808f4a33 = panic+0x43/frame 0xfe003590e960
sleepq_add() at 0x809521ab = sleepq_add+0x37b/frame
On 9/23/22 23:43, Hans Petter Selasky wrote:
vpanic() at 0x808f4c84 = vpanic+0x184/frame 0xfe003590e900
panic() at 0x808f4a33 = panic+0x43/frame 0xfe003590e960
sleepq_add() at 0x809521ab = sleepq_add+0x37b/frame
0xfe003590e9b0
_sleep() at 0x80902118
On 9/23/22 23:33, Andriy Gapon wrote:
It seems that the problem may be related to different keyboard LED
states between the VTs. The system is a fresh stable/13. The panic
looks like an attempt to sleep while in an interrupt thread (a callout?).
Hi,
I suspect vt_switch_timer must have
It seems that the problem may be related to different keyboard LED states
between the VTs. The system is a fresh stable/13. The panic looks like an
attempt to sleep while in an interrupt thread (a callout?).
panic: sleepq_add: td 0xf80006af to sleep on wchan 0xf802ea752e08
