[REVISED] Panic with FreeBSD 11.1-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"
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"
Re: 11.1-RC2 breaks wine, creates unkillable process
On 09.07.2017 14:23, Konstantin Belousov wrote: On Sun, Jul 09, 2017 at 01:53:24PM +0200, Jan Kokem??ller wrote: Same here on -CURRENT r320620. r319481 (I think) was working fine. I'm using the i386-wine-devel package from the official repository. This should fix creation of the unkillable processes, but untested. After that, if wine still does not work, you need to look exactly what breaks, perhaps using ktrace. Most likely there would be some unsuccessfull mmap(2) syscall. The patch fixes the issue. No problems so far, but only tested simple applications. Thank you for the quick fix. ___ 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: 11.1-RC2 breaks wine, creates unkillable process
> This should fix creation of the unkillable processes, but untested. Thank you, wine works fine again with this patch applied. ___ 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: 11.1-RC2 breaks wine, creates unkillable process
On Sun, Jul 09, 2017 at 01:53:24PM +0200, Jan Kokem??ller wrote: > Same here on -CURRENT r320620. r319481 (I think) was working fine. > > I'm using the i386-wine-devel package from the official repository. This should fix creation of the unkillable processes, but untested. After that, if wine still does not work, you need to look exactly what breaks, perhaps using ktrace. Most likely there would be some unsuccessfull mmap(2) syscall. diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c index 0a99ddde486..a0688fe4f0c 100644 --- a/sys/vm/vm_map.c +++ b/sys/vm/vm_map.c @@ -1571,7 +1571,7 @@ vm_map_find_min(vm_map_t map, vm_object_t object, vm_ooffset_t offset, find_space, prot, max, cow); if (rv == KERN_SUCCESS || min_addr >= hint) return (rv); - *addr = min_addr; + *addr = hint = min_addr; } } ___ 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: 11.1-RC2 breaks wine, creates unkillable process
Same here on -CURRENT r320620. r319481 (I think) was working fine. I'm using the i386-wine-devel package from the official repository. Cheers, Jan ___ 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"
