[Bug 215209] Kernel panic at boot under XEN: integer divide fault while in kernel mode

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Dec 11 10:55:25 UTC 2016


            Bug ID: 215209
           Summary: Kernel panic at boot under XEN: integer divide fault
                    while in kernel mode
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: sylvain at sylvaingarrigues.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Created attachment 177864
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=177864&action=edit
EC2 log

I had a system running FreeBSD 12 dated Nov. 3 2016. I updated from source to
2016-12-10. Now kernel panics on boot:

xenbusb_front0: <Xen Frontend Devices> on xenstore0
xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0
xn0: Ethernet address: 06:f6:cd:2a:fa:e1
xenbusb_back0: <Xen Backend Devices> on xenstore0
xn0: backend features:xenballoon0: <Xen Balloon Device> on xenstore0
 feature-sg feature-gso-tcp4

Fatal trap 18: integer divide fault while in kernel mode
xctrl0: <Xen Control Device> on xenstore0
cpuid = 0; apic id = 00
instruction pointer     = 0x20:0xffffffff808f24ad
stack pointer           = 0x28:0xfffffe003c91d9c0
frame pointer           = 0x28:0xfffffe003c91da50
code segment            = base 0x0, limit 0xfffff, type 0x1b
xs_dev0: <Xenstore user-space device> on xenstore0
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 14 (xenwatch)
[ thread pid 14 tid 100029 ]
Stopped at      xbd_backend_changed+0x84d:      divq   

Attached is full system log. 

When I install a fresh FreeBSD snapshot on Amazon EC2, dated 2016-11-01, I
don't have this bug. With the 2016-11-30, I do have it.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the freebsd-amd64 mailing list