Panic on 11.0-CURRENT when trying kldload vmm
22:13:~$ uname -a FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r281432: Sun Apr 12 01:35:34 EEST 2015 root@:/work/obj/work/src.svn/sys/MAREK amd64 Went kernel panic twice today when trying to load vmm. Never seen this before (the previous kernel was built out of r278973, Feb 19 2015, was doing well). The panic is not reliable in the sense I could not reproduce it at will just loading/unloading vmm. I regularly work in my bhyve guests, sometimes swap between vmm and vboxdrv, all my scenarios haven't changed from the previous Feb kernel. Except that I re-built my today panicking kernel extending the MINIMAL config (including what I need) as opposed to the previous one reducing GENERIC (excluding what I don't need). Both today panic's back traces look identical. Attaching core.txt.1 (the latter one) and the output of sysctl kern.conftxt. Let me know if someone wants to debug it. Thanks, Markiyan. conftxt Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on 11.0-CURRENT when trying kldload vmm
Hi Markiyan, On Thu, Apr 16, 2015 at 1:30 PM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 2015-04-16 23:20 GMT+03:00 Neel Natu neeln...@gmail.com: Hi Markiyan, On Thu, Apr 16, 2015 at 1:01 PM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 22:13:~$ uname -a FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r281432: Sun Apr 12 01:35:34 EEST 2015 root@:/work/obj/work/src.svn/sys/MAREK amd64 Went kernel panic twice today when trying to load vmm. Never seen this before (the previous kernel was built out of r278973, Feb 19 2015, was doing well). The panic is not reliable in the sense I could not reproduce it at will just loading/unloading vmm. I regularly work in my bhyve guests, sometimes swap between vmm and vboxdrv, all my scenarios haven't changed from the previous Feb kernel. Except that I re-built my today panicking kernel extending the MINIMAL config (including what I need) as opposed to the previous one reducing GENERIC (excluding what I don't need). Both today panic's back traces look identical. Attaching core.txt.1 (the latter one) and the output of sysctl kern.conftxt. Let me know if someone wants to debug it. I don't think that 'core.txt.1' made it through. Regardless, can you try to reproduce after applying r281559. I think it should fix the panic. https://svnweb.freebsd.org/changeset/base/281559 ah ok. Saved on google drive: https://drive.google.com/file/d/0B9Q-zpUXxqCnam0zNjFRcF9XMHc/view?usp=sharing Yup, its the one that is fixed in r281559. best Neel and yes, will shift to r281559, and see if it's ok. Thanks, Markiyan. best Neel Thanks, Markiyan. ___ freebsd-virtualizat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on 11.0-CURRENT when trying kldload vmm
Hi Markiyan, On Thu, Apr 16, 2015 at 1:01 PM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 22:13:~$ uname -a FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r281432: Sun Apr 12 01:35:34 EEST 2015 root@:/work/obj/work/src.svn/sys/MAREK amd64 Went kernel panic twice today when trying to load vmm. Never seen this before (the previous kernel was built out of r278973, Feb 19 2015, was doing well). The panic is not reliable in the sense I could not reproduce it at will just loading/unloading vmm. I regularly work in my bhyve guests, sometimes swap between vmm and vboxdrv, all my scenarios haven't changed from the previous Feb kernel. Except that I re-built my today panicking kernel extending the MINIMAL config (including what I need) as opposed to the previous one reducing GENERIC (excluding what I don't need). Both today panic's back traces look identical. Attaching core.txt.1 (the latter one) and the output of sysctl kern.conftxt. Let me know if someone wants to debug it. I don't think that 'core.txt.1' made it through. Regardless, can you try to reproduce after applying r281559. I think it should fix the panic. https://svnweb.freebsd.org/changeset/base/281559 best Neel Thanks, Markiyan. ___ freebsd-virtualizat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic on 11.0-CURRENT when trying kldload vmm
2015-04-16 23:20 GMT+03:00 Neel Natu neeln...@gmail.com: Hi Markiyan, On Thu, Apr 16, 2015 at 1:01 PM, Markiyan Kushnir markiyan.kush...@gmail.com wrote: 22:13:~$ uname -a FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r281432: Sun Apr 12 01:35:34 EEST 2015 root@:/work/obj/work/src.svn/sys/MAREK amd64 Went kernel panic twice today when trying to load vmm. Never seen this before (the previous kernel was built out of r278973, Feb 19 2015, was doing well). The panic is not reliable in the sense I could not reproduce it at will just loading/unloading vmm. I regularly work in my bhyve guests, sometimes swap between vmm and vboxdrv, all my scenarios haven't changed from the previous Feb kernel. Except that I re-built my today panicking kernel extending the MINIMAL config (including what I need) as opposed to the previous one reducing GENERIC (excluding what I don't need). Both today panic's back traces look identical. Attaching core.txt.1 (the latter one) and the output of sysctl kern.conftxt. Let me know if someone wants to debug it. I don't think that 'core.txt.1' made it through. Regardless, can you try to reproduce after applying r281559. I think it should fix the panic. https://svnweb.freebsd.org/changeset/base/281559 ah ok. Saved on google drive: https://drive.google.com/file/d/0B9Q-zpUXxqCnam0zNjFRcF9XMHc/view?usp=sharing and yes, will shift to r281559, and see if it's ok. Thanks, Markiyan. best Neel Thanks, Markiyan. ___ freebsd-virtualizat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
