Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Thu, Jul 13, 2017 at 05:06:12PM -0700, Mark Johnston wrote: > On Thu, Jul 13, 2017 at 01:06:30PM +, Glen Barber wrote: > > On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > > > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > > > I suspect that this is a result of r320763. That change removed a > > > > > field > > > > > from struct vm_map_entry, which is embedded in struct vm_map. > > > > > Virtualbox > > > > > does not reference the fields of struct vm_map directly, but it does > > > > > call vm_map_pmap(), which is an inline accessor. > > > > > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > > > stable KBI, but in this case it is simpler to add padding than to follow > > > > principles. > > > > > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > > > > > I think this is the commit: > > > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log=320889 > > > > > > Do you think this will get picked up by/for RC3, which will begin on > > > Friday? > > > https://www.freebsd.org/releases/11.1R/schedule.html > > > > > > > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. > > It should be noted that anyone that recompiled virtualbox for RC2 will > need to do so again after updating to RC3. Anyone going straight from > RC1 or earlier to RC3 ought to be unaffected. > Thank you for mentioning this. I would have forgotten to include this in the RC3 and RELEASE announcement text. I'll make a note of it right now... Glen signature.asc Description: PGP signature
Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Thu, Jul 13, 2017 at 01:06:30PM +, Glen Barber wrote: > On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > > I suspect that this is a result of r320763. That change removed a field > > > > from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox > > > > does not reference the fields of struct vm_map directly, but it does > > > > call vm_map_pmap(), which is an inline accessor. > > > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > > stable KBI, but in this case it is simpler to add padding than to follow > > > principles. > > > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > > > I think this is the commit: > > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log=320889 > > > > Do you think this will get picked up by/for RC3, which will begin on Friday? > > https://www.freebsd.org/releases/11.1R/schedule.html > > > > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. It should be noted that anyone that recompiled virtualbox for RC2 will need to do so again after updating to RC3. Anyone going straight from RC1 or earlier to RC3 ought to be unaffected. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > I suspect that this is a result of r320763. That change removed a field > > > from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox > > > does not reference the fields of struct vm_map directly, but it does > > > call vm_map_pmap(), which is an inline accessor. > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > stable KBI, but in this case it is simpler to add padding than to follow > > principles. > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > I think this is the commit: > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log=320889 > > Do you think this will get picked up by/for RC3, which will begin on Friday? > https://www.freebsd.org/releases/11.1R/schedule.html > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. Glen signature.asc Description: PGP signature
Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On 07/10/2017 10:48 PM, Konstantin Belousov wrote: On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: I suspect that this is a result of r320763. That change removed a field from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox does not reference the fields of struct vm_map directly, but it does call vm_map_pmap(), which is an inline accessor. Thank you for noting. I do not consider vm_map part of the guaranteed stable KBI, but in this case it is simpler to add padding than to follow principles. Fixed in 320889, will ask re for MFS permissions in a day. I think this is the commit: https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log=320889 Do you think this will get picked up by/for RC3, which will begin on Friday? https://www.freebsd.org/releases/11.1R/schedule.html Thanks! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > I suspect that this is a result of r320763. That change removed a field > from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox > does not reference the fields of struct vm_map directly, but it does > call vm_map_pmap(), which is an inline accessor. Thank you for noting. I do not consider vm_map part of the guaranteed stable KBI, but in this case it is simpler to add padding than to follow principles. Fixed in 320889, will ask re for MFS permissions in a day. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
On Mon, Jul 10, 2017 at 09:47:50PM +0200, José G. Juanino wrote: > El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió: > >El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: > >>With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't > >>been able to process the panic completely, but the backtrace looks > >>mysteriously similar to those provided with PR219146. > >> > >> > >>Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then > >>configured as a VirtualBox client. The panic occurs on subsequent > >>reboots when attempting to start vboxservice. > >> > >> > >>Additionally, during the custom configuration process, lsof hangs > >>for more than 2 minutes each time that it is invoked. > >> > >> > >>Please let me know exactly what information is needed to correct > >>this problem. I will be able to provide that information no later > >>than Tuesday morning. > >> > > > >Hi, I am also suffering this panic. > > > >I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I > >upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no > >issues. > > > >But after to upgrade to 11.1-RC2, the system panics just after to > >start vboxservice. I have disabled the service at boot in > >/etc/rc.conf, but it does not help: the system crashes just after > >"service vboxservice start" command. > > > >You can get a full crash dump here: > > > >https://pastebin.com/MkxS9GZn > > > >At this moment, I am going to rebuild the virtualbox-ose-additions > >port (running 11.1-RC2) and I will let you know if there is some > >difference. > > I confirm that after rebuild virtualbox-ose-additions port, the panic > goes away. Regards. I suspect that this is a result of r320763. That change removed a field from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox does not reference the fields of struct vm_map directly, but it does call vm_map_pmap(), which is an inline accessor. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió: El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those provided with PR219146. Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a VirtualBox client. The panic occurs on subsequent reboots when attempting to start vboxservice. Additionally, during the custom configuration process, lsof hangs for more than 2 minutes each time that it is invoked. Please let me know exactly what information is needed to correct this problem. I will be able to provide that information no later than Tuesday morning. Hi, I am also suffering this panic. I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no issues. But after to upgrade to 11.1-RC2, the system panics just after to start vboxservice. I have disabled the service at boot in /etc/rc.conf, but it does not help: the system crashes just after "service vboxservice start" command. You can get a full crash dump here: https://pastebin.com/MkxS9GZn At this moment, I am going to rebuild the virtualbox-ose-additions port (running 11.1-RC2) and I will let you know if there is some difference. I confirm that after rebuild virtualbox-ose-additions port, the panic goes away. Regards. -- José G. Juanino ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those provided with PR219146. Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a VirtualBox client. The panic occurs on subsequent reboots when attempting to start vboxservice. Additionally, during the custom configuration process, lsof hangs for more than 2 minutes each time that it is invoked. Please let me know exactly what information is needed to correct this problem. I will be able to provide that information no later than Tuesday morning. Hi, I am also suffering this panic. I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no issues. But after to upgrade to 11.1-RC2, the system panics just after to start vboxservice. I have disabled the service at boot in /etc/rc.conf, but it does not help: the system crashes just after "service vboxservice start" command. You can get a full crash dump here: https://pastebin.com/MkxS9GZn At this moment, I am going to rebuild the virtualbox-ose-additions port (running 11.1-RC2) and I will let you know if there is some difference. Regards -- José G. Juanino ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice
With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those provided with PR219146. Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a VirtualBox client. The panic occurs on subsequent reboots when attempting to start vboxservice. Additionally, during the custom configuration process, lsof hangs for more than 2 minutes each time that it is invoked. Please let me know exactly what information is needed to correct this problem. I will be able to provide that information no later than Tuesday morning. Thanks, in advance, for your assistance. David Boyd. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
