10-STABLE panic in atkbd due to Qemu+virtio
Hi,
I've been seeing this panic with 10-STABLE kfreebsd-amd64 snapshots from
the past two weeks or more (but not affecting our 10.0 kernel). The
stack trace implicated atkbd, but I've just discovered it only happens
in Qemu with -net nic,model=virtio and not with model=e1000.
Is there someplace to get 'official' upstream 10-STABLE kernels? Mine
are built with Debian's usual config and packaging, and Clang 3.4. Thanks!
> virtio_pci0: <VirtIO PCI Network adapter> port 0xc000-0xc01f mem 0xfebf1000-0xfebf1fff irq 11 at device 3.0 on pci0
> vtnet0: <VirtIO Networking Adapter> on virtio_pci0
> virtio_pci0: host features: 0x711f8060 <EventIdx,RingIndirect,NotifyOnEmpty,RxModeExtra,VLanFilter,RxMode,ControlVq,Status,MrgRxBuf,TxAllGSO,MacAddress>
> virtio_pci0: negotiated features: 0x300f8060 <EventIdx,RingIndirect,VLanFilter,RxMode,ControlVq,Status,MrgRxBuf,TxAllGSO,MacAddress>
> vtnet0: Ethernet address: 52:54:00:12:34:56
> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
> atkbd0: <AT Keyboard> irq 1 on atkbdc0
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x0
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0xffffffff80b9c7db
> stack pointer = 0x28:0xffffffff85e457a0
> frame pointer = 0x28:0xffffffff85e457f0
> 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 = 0 (swapper)
> trap number = 12
> panic: page fault
> cpuid = 0
> KDB: stack backtrace:
> #0 0xffffffff808ed020 at kdb_backtrace+0x60
> #1 0xffffffff808b4f9f at panic+0x14f
> #2 0xffffffff80b8a3af at trap_fatal+0x38f
> #3 0xffffffff80b8a65c at trap_pfault+0x29c
> #4 0xffffffff80b89d5f at trap+0x41f
> #5 0xffffffff80b709af at calltrap+0x8
> #6 0xffffffff80b9bd7d at atkbd_init+0x33d
> #7 0xffffffff80b9b7af at atkbd_attach_unit+0x8f
> #8 0xffffffff80b9d04b at atkbdattach+0x4b
> #9 0xffffffff808e4052 at device_attach+0x3a2
> #10 0xffffffff808e514d at bus_generic_attach+0x2d
> #11 0xffffffff80b9f19c at atkbdc_isa_attach+0x17c
> #12 0xffffffff808e4052 at device_attach+0x3a2
> #13 0xffffffff808e514d at bus_generic_attach+0x2d
> #14 0xffffffff8035038a at acpi_attach+0xd9a
> #15 0xffffffff808e4052 at device_attach+0x3a2
> #16 0xffffffff808e514d at bus_generic_attach+0x2d
> #17 0xffffffff80b6e853 at nexus_acpi_attach+0x73
> Uptime: 1s
> Automatic reboot in 15 seconds - press a key on the console to abort
> qemu: terminating on signal 2
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: