This is a recurring theme, right?<div><br></div><div><div>Mar 24 17:16:53 management syslogd: kernel boot file is /boot/kernel/kernel</div><div>Mar 24 17:16:53 management kernel: acd0: acd0: WARNING - PREVENT_ALLOW taskqueue timeout - completing request directlyWARNING - PREVENT_ALLOW taskqueue timeout - completing request directly</div>
<div>Mar 24 17:16:53 management kernel: acd0: </div><div>Mar 24 17:16:53 management kernel: WARNING - PREVENT_ALLOW freeing taskqueue zombie requestacd0: </div><div>Mar 24 17:16:53 management kernel: WARNING - PREVENT_ALLOW freeing taskqueue zombie request</div>
<div>Mar 24 17:16:53 management kernel: </div><div>Mar 24 17:16:53 management kernel: </div><div>Mar 24 17:16:53 management kernel: Fatal trap 12: page fault while in kernel mode</div><div>Mar 24 17:16:53 management kernel: cpuid = 2; apic id = 02</div>
<div>Mar 24 17:16:53 management kernel: fault virtual address = 0x1f4</div><div>Mar 24 17:16:53 management kernel: fault code = supervisor read, page not present</div><div>Mar 24 17:16:53 management kernel: instruction pointer = 0x20:0xc08a1e9f</div>
<div>Mar 24 17:16:53 management kernel: stack pointer = 0x28:0xe6ab1b9c</div><div>Mar 24 17:16:53 management kernel: frame pointer = 0x28:0xe6ab1bb4</div><div>Mar 24 17:16:53 management kernel: code segment = base 0x0, limit 0xfffff, type 0x1b</div>
<div>Mar 24 17:16:53 management kernel: = DPL 0, pres 1, def32 1, gran 1</div><div>Mar 24 17:16:53 management kernel: processor eflags = interrupt enabled, resume, IOPL = 0</div><div>Mar 24 17:16:53 management kernel: current process = 12 (swi6: task queue)</div>
<div>Mar 24 17:16:53 management kernel: trap number = 12</div><div>Mar 24 17:16:53 management kernel: panic: page fault</div><div>Mar 24 17:16:53 management kernel: cpuid = 2</div><div>Mar 24 17:16:53 management kernel: KDB: stack backtrace:</div>
<div>Mar 24 17:16:53 management kernel: #0 0xc08e0d07 at kdb_backtrace+0x47</div><div>Mar 24 17:16:53 management kernel: #1 0xc08b1dc7 at panic+0x117</div><div>Mar 24 17:16:53 management kernel: #2 0xc0be4b53 at trap_fatal+0x323</div>
<div>Mar 24 17:16:53 management kernel: #3 0xc0be4dd0 at trap_pfault+0x270</div><div>Mar 24 17:16:53 management kernel: #4 0xc0be5315 at trap+0x465</div><div>Mar 24 17:16:53 management kernel: #5 0xc0bcbecc at calltrap+0x6</div>
<div>Mar 24 17:16:53 management kernel: #6 0xc08b0d86 at _sema_post+0x46</div><div>Mar 24 17:16:53 management kernel: #7 0xc056fa47 at ata_completed+0x727</div><div>Mar 24 17:16:53 management kernel: #8 0xc08eb97a at taskqueue_run_locked+0xca</div>
<div>Mar 24 17:16:53 management kernel: #9 0xc08ebc8a at taskqueue_run+0xaa</div><div>Mar 24 17:16:53 management kernel: #10 0xc08ebd53 at taskqueue_swi_run+0x13</div><div>Mar 24 17:16:53 management kernel: #11 0xc088903b at intr_event_execute_handlers+0x13b</div>
<div>Mar 24 17:16:53 management kernel: #12 0xc088a75b at ithread_loop+0x6b</div><div>Mar 24 17:16:53 management kernel: #13 0xc0886d51 at fork_exit+0x91</div><div>Mar 24 17:16:53 management kernel: #14 0xc0bcbf44 at fork_trampoline+0x8</div>
<div>Mar 24 17:16:53 management kernel: Uptime: 2d22h59m39s</div><div>Mar 24 17:16:53 management kernel: Cannot dump. Device not defined or unavailable.</div></div><div><br></div><div>Did anyone do anything yesterday afternoon (that's UTC, so 18:16 Paris time) to access the "cd-rom" drive on management? Did anyone notice that it had crashed?</div>
<div><br></div><div>Thanks,</div><div> Bill</div><div><br></div>