[ Note this is a -current issue, not necessarily a 5.2-RC issue. ] Just FYI, the amd64 reference machine in the cluster (sledge) hasn't been happy with the -current kernel for the past two days. This is what the console logs say: SMP: AP CPU #1 Launched! panic: sched_add: KSE 0xffffff01e9121000 is still assigned to a run queue cpuid = 1; boot() called on cpu#1 syncing disks, buffers remaining... done Uptime: 1s panic: mi_switch: switch in a critical section cpuid = 1; boot() called on cpu#1 Uptime: 1s panic: msleep cpuid = 1; boot() called on cpu#1 Uptime: 1s panic: msleep cpuid = 1; boot() called on cpu#1 Uptime: 1s panic: msleep cpuid = 1; boot() called on cpu#1 Uptime: 1s panic: msleep -- Ken Smith - From there to here, from here to | kensmith_at_cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |Received on Sat Dec 13 2003 - 10:13:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:34 UTC