FreeBSD Bugzilla – Attachment 204020 Details for
Bug 237568
nginx causes host panic when closing socket descriptor?
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
Stack trace from kernel panic
file_237568.txt (text/plain), 1.34 KB, created by
rlwestlund
on 2019-04-25 22:03:41 UTC
(
hide
)
Description:
Stack trace from kernel panic
Filename:
MIME Type:
Creator:
rlwestlund
Created:
2019-04-25 22:03:41 UTC
Size:
1.34 KB
patch
obsolete
> >Fatal trap 12: page fault while in kernel mode > >cpuid = 0; apic id = 00 > >fault virtual address = 0x8 > >fault code = supervisor read data, page not present > >instruction pointer = 0x20:0xffffffff80c2f0f0 > >stack pointer = 0x28:0xfffffe000054a790 > >frame pointer = 0x28:0xfffffe000054a7c0 > >code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, def32 0, gran 1 > >processor eflags = interrupt enabled, resume, IOPL = 0 > >current process = 1010 (nginx) > >trap number = 12 > >panic: page fault > >cpuid = 1 > >time = 1556134521 > >KDB: stack backtrace: > >#0 0xffffffff80be7977 at kdb_backtrace+0x67 > >#1 0xffffffff80b9b563 at vpanic+0x1a3 > >#2 0xffffffff80b9b3b3 at panic+0x43 > >#3 0xffffffff8107496f at trap_fatal+0x35f > >#4 0xffffffff810749c9 at trap_pfault+0x49 > >#5 0xffffffff81073fee at trap+0x29e > >#6 0xffffffff8104f435 at calltrap+0x8 > >#7 0xffffffff80c2e1f8 at sbdestroy+0x28 > >#8 0xffffffff80c30a55 at sofree+0x285 > >#9 0xffffffff80c31600 at soclose+0x330 > >#10 0xffffffff80b4363a at _fdrop+0x1a > >#11 0xffffffff80b466e4 at closef+0x244 > >#12 0xffffffff80b43b69 at closefp+0x99 > >#13 0xffffffff81075449 at amd64_syscall+0x369 > >#14 0xffffffff8104fd1d at fast_syscall_common+0x101 > >Uptime: 56m25s > >Rebooting... > >cpu_reset: Restarting BSP > >cpu_reset_proxy: Stopped CPU 1 > >---<<BOOT>>---
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 237568
: 204020