Re: 8.0 crash inside KVM
Michael van Elst wrote: > al...@yandex.ru (Alexander Nasonov) writes: > > >inside ProxMox kvm and rebooted it a couple of times. But on the > >last reboot, the kernel stuck at something and I sent a reboot from > >the console. A bit later it panicked. > > If "console" means: issuing the reboot from DDB, then this can be > expected. If it means: running multiple /sbin/reboot concurrently, > then it's a bug. >From ProxMox noVNC console. -- Alex
Re: 8.0 crash inside KVM
al...@yandex.ru (Alexander Nasonov) writes: >inside ProxMox kvm and rebooted it a couple of times. But on the >last reboot, the kernel stuck at something and I sent a reboot from >the console. A bit later it panicked. If "console" means: issuing the reboot from DDB, then this can be expected. If it means: running multiple /sbin/reboot concurrently, then it's a bug. -- -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: 8.0 crash inside KVM
Alexander Nasonov wrote: > I don't know if a panic in a VM should be reported to gnats. I'm sending > the report to tech-kern instead. > > I successfully installed 8.0_BETA amd64 GENERIC, which I downloaded from > > https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-8/201802240710Z/images/ > One more panic on shutdown: panic: kernel diagnostic assertion "pipe != NULL" failed: /usr/src/sys/dev/usb/usbdi.c", line 670 Fatal breakpoint trap in supervisor mode Trap type 1 code 0 rip 0x80224d95 cs 0x8 rflags 0x246 cr2 0 ilevel 0 rsp 0xfe80028a7d30 curlwp 0xfe8022707500 pi 0.24 lowest kstack 0xe80028a42c0 Stopped in pid 0.24 (system) at netbsd:breakpoint+0x5c: leave breakpoint() at netbsd:breakpoint+9x5c vpanic() at netbsd:vpanic+0x140 ch_voltag_convert_in() at netbsd:ch_voltag_convert_in usbd_abort_pipe() at netbsd:usbd_abort_pipe+0x6b usbd_kill_pipe() at netbsd:usbd_kill_pipe+0x11 usbd_new_device() at netbsd:usbd_new_device+0x3ec usb_doattach() at netbsd:usb_doattach+0xa8 config_interrupt_thread() at netbsd:config_interrupt_thread+0x30 Snapshots are available. I can give remote access to noVNC for debugging. -- Alex
