Re: viomb0 at virtio0panic: Non dma-reachable buffer at curaddr 0x11f7c0a14(raw)
On 2013-02-23, Johan Huldtgren johan+openbsd-m...@huldtgren.com wrote: On 2/22/13 8:21 PM, Johan Huldtgren wrote: hello, upgraded to the latest amd64 snapshot today (dated Feb 21st) and server panics on boot. This is a KVM guest at a hosted facility, as I can't boot I am unable to get a dmesg, but here is the text from the panic (with the last few lines) Did the previous version have viomb(4) in the kernel, i.e. did this work successfully with viomb in the past or did it not use viomb before? It might be prudent to disable viomb in GENERIC for release. vga1 at pci0 dev 2 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 3 function 0 Intel PRO/1000MT (82540EM) rev 0x03: apic 1 int 11, address 52:54:00:4e:22:85 virtio0 at pci0 dev 4 function 0 Qumranet Virtio Memory rev 0x00: Virtio Memory Balloon Device viomb0 at virtio0panic: Non dma-reachable buffer at curaddr 0x11f7c0a14(raw) Stopped at Debugger+0x5: leave Debugger() at Debugger+0x5 panic() at panic+0xe4 _bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x198 _bus_dmamap_load() at _bus_dmamap_load+0x68 viomb_attach() at viomb_attach+0x219 config_attach() at config_attach+0x1d4 virtio_pci_attach() at virtio_pci_attach+0x144 config_attach() at config_attach+0x1d4 pci_probe_device() at pci_probe_device+0x3e2 pci_enumerate_bus() at pci_enumerate_bus+0xe9 end trace frame: 0x80e64d80, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger() at Debugger+0x5 panic() at panic+0xe4 _bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x198 _bus_dmamap_load() at _bus_dmamap_load+0x68 viomb_attach() at viomb_attach+0x219 config_attach() at config_attach+0x1d4 virtio_pci_attach() at virtio_pci_attach+0x1d4 pci_probe_device() at pci_probe_device+0x3e2 pci_enumerate_bus() at pci_enumerate_bus+0xe9 config_attach() at config_attach_0x1d4 mainbus_attach() at mainbus_attach+0x163 config_attach() at config_attach+0x1d4 cpu_configure() at cpu_configure+0x17 main() at main+0x3d5 end trace frame: 0x0, count: -15 ddb ps PID PPID PGRPUIDS FLAGS WAIT COMMAND *0 -10 07 0x200 swapper ddb show registers ds 0x2bd0 es 0x48f0 acpi_pdirpa+0x3e8 fs 0x1 gs 0 rdi 0x1 rsi 0x5 rbp 0x80e648e0end+0xd6540 rbx 0x80822bd0 x86_bus_space_mem_ops+0x250 rdx 0x8082093f_length_code+0xb1f rcx0 rax 0x1 r8 0x80e64800end+0xd6460 r9 0x1 r100 r110x20 r12 0x100 r13 0x80e648f0end+0xd6550 r14 0x8013d280 r150 rip 0x80459475Debugger+0x5 cs 0x8 rflags 0x202 rsp 0x80e648e0end+0xd6540 ss0x10 Debugger+0x5: leave ddb bsd -c disable viomb got me back up and running at least. dmesg is attached for completeness. .jh OpenBSD 5.3 (GENERIC) #41: Thu Feb 21 20:31:41 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4293853184 (4094MB) avail mem = 4157087744 (3964MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfbd3f (10 entries) bios0: vendor QEMU version QEMU date 01/01/2007 acpi0 at bios0: rev 0 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 mpbios at bios0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: QEMU Virtual CPU version 0.9.1, 2667.29 MHz cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,LONG,PERF cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped pci0
Re: viomb0 at virtio0panic: Non dma-reachable buffer at curaddr 0x11f7c0a14(raw)
On 2/23/13 6:51 AM, Stuart Henderson wrote: On 2013-02-23, Johan Huldtgren johan+openbsd-m...@huldtgren.com wrote: On 2/22/13 8:21 PM, Johan Huldtgren wrote: hello, upgraded to the latest amd64 snapshot today (dated Feb 21st) and server panics on boot. This is a KVM guest at a hosted facility, as I can't boot I am unable to get a dmesg, but here is the text from the panic (with the last few lines) Did the previous version have viomb(4) in the kernel, i.e. did this work successfully with viomb in the past or did it not use viomb before? I did not have viomb(4) before, my previous snapshot was: OpenBSD 5.2-current (GENERIC) #103: Tue Dec 4 03:56:18 MST 2012 It might be prudent to disable viomb in GENERIC for release. not sure if I hit a corner case or not, but perhaps a good idea. .jh
Re: viomb0 at virtio0panic: Non dma-reachable buffer at curaddr 0x11f7c0a14(raw)
On 2/22/13 8:21 PM, Johan Huldtgren wrote: hello, upgraded to the latest amd64 snapshot today (dated Feb 21st) and server panics on boot. This is a KVM guest at a hosted facility, as I can't boot I am unable to get a dmesg, but here is the text from the panic (with the last few lines) vga1 at pci0 dev 2 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 3 function 0 Intel PRO/1000MT (82540EM) rev 0x03: apic 1 int 11, address 52:54:00:4e:22:85 virtio0 at pci0 dev 4 function 0 Qumranet Virtio Memory rev 0x00: Virtio Memory Balloon Device viomb0 at virtio0panic: Non dma-reachable buffer at curaddr 0x11f7c0a14(raw) Stopped at Debugger+0x5: leave Debugger() at Debugger+0x5 panic() at panic+0xe4 _bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x198 _bus_dmamap_load() at _bus_dmamap_load+0x68 viomb_attach() at viomb_attach+0x219 config_attach() at config_attach+0x1d4 virtio_pci_attach() at virtio_pci_attach+0x144 config_attach() at config_attach+0x1d4 pci_probe_device() at pci_probe_device+0x3e2 pci_enumerate_bus() at pci_enumerate_bus+0xe9 end trace frame: 0x80e64d80, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger() at Debugger+0x5 panic() at panic+0xe4 _bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x198 _bus_dmamap_load() at _bus_dmamap_load+0x68 viomb_attach() at viomb_attach+0x219 config_attach() at config_attach+0x1d4 virtio_pci_attach() at virtio_pci_attach+0x1d4 pci_probe_device() at pci_probe_device+0x3e2 pci_enumerate_bus() at pci_enumerate_bus+0xe9 config_attach() at config_attach_0x1d4 mainbus_attach() at mainbus_attach+0x163 config_attach() at config_attach+0x1d4 cpu_configure() at cpu_configure+0x17 main() at main+0x3d5 end trace frame: 0x0, count: -15 ddb ps PID PPID PGRPUIDS FLAGS WAIT COMMAND *0 -10 07 0x200 swapper ddb show registers ds 0x2bd0 es 0x48f0 acpi_pdirpa+0x3e8 fs 0x1 gs 0 rdi 0x1 rsi 0x5 rbp 0x80e648e0end+0xd6540 rbx 0x80822bd0 x86_bus_space_mem_ops+0x250 rdx 0x8082093f_length_code+0xb1f rcx0 rax 0x1 r8 0x80e64800end+0xd6460 r9 0x1 r100 r110x20 r12 0x100 r13 0x80e648f0end+0xd6550 r14 0x8013d280 r150 rip 0x80459475Debugger+0x5 cs 0x8 rflags 0x202 rsp 0x80e648e0end+0xd6540 ss0x10 Debugger+0x5: leave ddb bsd -c disable viomb got me back up and running at least. dmesg is attached for completeness. .jh OpenBSD 5.3 (GENERIC) #41: Thu Feb 21 20:31:41 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4293853184 (4094MB) avail mem = 4157087744 (3964MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfbd3f (10 entries) bios0: vendor QEMU version QEMU date 01/01/2007 acpi0 at bios0: rev 0 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 mpbios at bios0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: QEMU Virtual CPU version 0.9.1, 2667.29 MHz cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,LONG,PERF cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel 82441FX rev 0x02 pcib0 at pci0 dev 1 function 0 Intel 82371SB ISA rev 0x00 pciide0 at pci0 dev 1 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: QEMU HARDDISK wd0
