Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#10442 closed bug (duplicate)

KDL during shutdown

Reported by: luroh Owned by: pdziepak
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #10436
Platform: All

Description (last modified by pdziepak)

hrev46705, gcc2, a two-CPU VBox machine running on an Intel CPU host.

scheduler: disabling CPU 1
PANIC: ASSERT FAILED (src/system/kernel/scheduler/scheduler_cpu.h:386): fCPUCount > 0
Welcome to Kernel Debugging Land...
Thread 49286 "shutdown worker" running on CPU 1
stack trace for thread 49286 "shutdown worker"
    kernel stack: 0xccebd000 to 0xccec1000
      user stack: 0x70cda000 to 0x70d1a000
frame               caller     <image>:function + offset
 0 ccec0b24 (+  32) 8013fee2   <kernel_x86> arch_debug_stack_trace + 0x12
 1 ccec0b44 (+  16) 8009ffcf   <kernel_x86> stack_trace_trampoline(NULL) + 0x0b
 2 ccec0b54 (+  12) 80131bae   <kernel_x86> arch_debug_call_with_fault_handler + 0x1b
 3 ccec0b60 (+  48) 800a1a36   <kernel_x86> debug_call_with_fault_handler + 0x5a
 4 ccec0b90 (+  64) 800a01eb   <kernel_x86> kernel_debugger_loop([34m0x80181eb7[0m [36m"PANIC: "[0m, [34m0x8017f1a7[0m [36m"ASSERT FAILED (%s:%d): %s"[0m, [34m0xccec0c3c[0m [36m""[0m, int32: [34m1[0m) + 0x217
 5 ccec0bd0 (+  48) 800a0567   <kernel_x86> kernel_debugger_internal([34m0x80181eb7[0m [36m"PANIC: "[0m, [34m0x8017f1a7[0m [36m"ASSERT FAILED (%s:%d): %s"[0m, [34m0xccec0c3c[0m [36m""[0m, int32: [34m1[0m) + 0x53
 6 ccec0c00 (+  48) 800a1dbe   <kernel_x86> panic + 0x3a
 7 ccec0c30 (+  64) 80096094   <kernel_x86> Scheduler::CoreEntry<[32m0x8214bc44[0m>::UpdateLoad(int32: [34m-986[0m) + 0xc4
 8 ccec0c70 (+ 208) 80092647   <kernel_x86> reschedule(int32: [34m2[0m) + 0x723
 9 ccec0d40 (+  48) 80092fbd   <kernel_x86> scheduler_reschedule + 0x61
10 ccec0d70 (+  64) 8014150d   <kernel_x86> x86_hardware_interrupt + 0xe1
11 ccec0db0 (+  12) 801345ec   <kernel_x86> int_bottom + 0x3c
kernel iframe at 0xccec0dbc (end = 0xccec0e0c)
 eax 0x801c2e5c    ebx 0x2            ecx 0x801ba820  edx 0x801b1550
 esi 0x2           edi 0x1            ebp 0xccec0e34  esp 0xccec0df0
 eip 0x8005571d eflags 0x10202   
 vector: 0xfb, error code: 0x0
12 ccec0dbc (+ 120) 8005571d   <kernel_x86> _user_set_cpu_enabled + 0x129
13 ccec0e34 (+  48) 8013c4f3   <kernel_x86> acpi_shutdown([34mfalse[0m) + 0x8b
14 ccec0e64 (+  48) 8013e50f   <kernel_x86> arch_cpu_shutdown + 0x17
15 ccec0e94 (+ 144) 8006d108   <kernel_x86> system_shutdown + 0x60
16 ccec0f24 (+  32) 8006d12f   <kernel_x86> _user_shutdown + 0x1f
17 ccec0f44 (+ 100) 801347ef   <kernel_x86> handle_syscall + 0xdc
user iframe at 0xccec0fa8 (end = 0xccec1000)
 eax 0x4           ebx 0xc919d0       ecx 0x70d19c74  edx 0x603f1114
 esi 0x1836f7f0    edi 0x1836f6e0     ebp 0x70d19ca0  esp 0xccec0fdc
 eip 0x603f1114 eflags 0x3202    user esp 0x70d19c74
 vector: 0x63, error code: 0x0
18 ccec0fa8 (+   0) 603f1114   <commpage> commpage_syscall + 0x04
19 70d19ca0 (+  96) 00c5718d   <_APP_> ShutdownProcess<[32m0x1836f6e0[0m>::_WorkerDoShutdown([34m0x0[0m) + 0x539
20 70d19d00 (+  48) 00c56ba8   <_APP_> ShutdownProcess<[32m0x1836f6e0[0m>::_Worker([34m0x0[0m) + 0x20
21 70d19d30 (+  48) 00c56b7f   <_APP_> ShutdownProcess<[32m0x1836f6e0[0m>::_WorkerEntry(NULL) + 0x1f
22 70d19d60 (+  48) 00cc6583   <libroot.so> _get_next_team_info (nearest) + 0x5f
23 70d19d90 (+   0) 603f1250   <commpage> commpage_thread_exit + 0x00
kdebug> 

Attachments (1)

IMG_0115.JPG (1.7 MB ) - added by vidrep 7 years ago.

Download all attachments as: .zip

Change History (4)

comment:1 by pdziepak, 7 years ago

Blocking: 10436 added
Description: modified (diff)
Resolution: duplicate
Status: newclosed

Despite slightly different KDL message this bug and #10436 are both results of trying to update load statistics on a disabled (thus removed from the scheduler structures).

comment:2 by vidrep, 7 years ago

I'm not sure if this is related or not (hrev46720) screenshot IMG_0115 attached

by vidrep, 7 years ago

Attachment: IMG_0115.JPG added

comment:3 by pdziepak, 7 years ago

It's definitely related. This is #10436, which, hopefully, was fixed in hrev46731.

Note: See TracTickets for help on using tickets.