Re: Rebooting from loader causes a "fault" in VMware Workstation

2013-04-19 Thread Jeremy Chadwick
On Fri, Apr 19, 2013 at 05:49:34PM -0500, Joshua Isom wrote: > Basically, the loader finds a simple safe way to reboot that's > worked since the 286, and VMWare doesn't like it. It's called a > triple fault. FreeBSD and Linux even use it to reboot as a fail > safe. Read sys/i386/i386/vm_machdep.

Re: Rebooting from loader causes a "fault" in VMware Workstation

2013-04-19 Thread Joshua Isom
Basically, the loader finds a simple safe way to reboot that's worked since the 286, and VMWare doesn't like it. It's called a triple fault. FreeBSD and Linux even use it to reboot as a fail safe. Read sys/i386/i386/vm_machdep.c and cpu_reset_real to see how FreeBSD handles it. VMWare at le

[patch] accept4

2013-04-19 Thread Jilles Tjoelker
The accept4() function, compared to accept(), allows setting the new file descriptor atomically close-on-exec and explicitly controlling the non-blocking status on the new socket. (Note that the latter point means that accept() is not equivalent to any form of accept4().) The linuxulator's accept4

Re: MADV_FREE and wait4 EFAULT

2013-04-19 Thread Carl Shapiro
On Fri, Apr 19, 2013 at 5:49 AM, Konstantin Belousov wrote: > It would be of some interest to see the evidence. > Certainly. Here is some of the debugging messages that I added to my application. The first line is a print statement that executes after the system call returns. (As an aside, we

Rebooting from loader causes a "fault" in VMware Workstation

2013-04-19 Thread Jeremy Chadwick
(Please keep me CC'd as I'm not subscribed to -hackers) When running FreeBSD under VMware Workstation (I'm using 9.0.1, but this issue has existed for many years now, I remember it occurring on Workstation 6.x), the following is reproducible: 1. Power on + boot FreeBSD VM 2. At loader menu, press

RE: PV6 bind fails with 49 (#define EADDRNOTAVAIL 49 /* Can't assign requested address */)

2013-04-19 Thread Sreenivasa Honnur
roundhay# sysctl -a | grep jailed security.jail.jailed: 0 Oh, of course, I mean, what do you have in td->td_ucred? [Sreenivas] not sure, I referred to socreate() usage in the kernel source and used it. One more observation. Interface "cxgbe1" has a IPv6 interface and an IPv4 interface, print in

RE: IPV6 bind fails with 49 (#define EADDRNOTAVAIL 49 /* Can't assign requested address */)

2013-04-19 Thread Sreenivasa Honnur
roundhay# sysctl -a | grep jailed security.jail.jailed: 0 Oh, of course, I mean, what do you have in td->td_ucred? [Sreenivas] not sure, I referred to socreate() usage in the kernel source and used it. One more observation. Interface "cxgbe1" has a IPv6 interface and an IPv4 interface, print in

sdt panic

2013-04-19 Thread Andriy Gapon
#0 doadump (textdump=1) at pcpu.h:233 #1 0x80591d69 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:444 #2 0x8059210c in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:620 #3 0x80775fee in trap_fatal (frame=0xc, eva=18446744071571306953) at /usr/src/sy

Re: MADV_FREE and wait4 EFAULT

2013-04-19 Thread Konstantin Belousov
On Thu, Apr 18, 2013 at 02:51:43PM -0700, Carl Shapiro wrote: > On Wed, Apr 17, 2013 at 1:21 AM, Konstantin Belousov > wrote: > > > Did you ensured with e.g. ktrace and procstat -v that your assumptions > > hold, i.e. the addresses supplied as wait4(2) arguments are valid ? > > Please provide the