Date: Thu, 28 Sep 2006 21:09:17 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-emulation@FreeBSD.org Cc: Alexander Leidinger <Alexander@Leidinger.net>, jhb@FreeBSD.org Subject: Re: linuxulator on -CURRENT Message-ID: <200609282109.24348.jkim@FreeBSD.org> In-Reply-To: <20060928073616.yyu76vcnc4g0sowc@webmail.leidinger.net> References: <200609261733.48398.jkim@FreeBSD.org> <200609272020.35161.jkim@FreeBSD.org> <20060928073616.yyu76vcnc4g0sowc@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 28 September 2006 01:36 am, Alexander Leidinger wrote: > In the archive of LTP on my site there's a verbose logfile in the > root of the ltp directory. There you can see in which order and > with which parameters the tests are called. Could you please run > them (at least until the first syscall, the rest isn't important as > long as there is this bug) by hand and add a corresponding status > and comment to the wiki? I wanted little automation, so I did this: http://people.freebsd.org/~jkim/linux/amd64-testgen.sh which generated: http://people.freebsd.org/~jkim/linux/amd64-test.sh Test result is here: http://people.freebsd.org/~jkim/linux/amd64-gentoo.log Failed tests are listed here: http://people.freebsd.org/~jkim/linux/amd64-failed.txt When I had to kill processes, I logged them here: http://people.freebsd.org/~jkim/linux/amd64-killed.txt dmesg buffer for this run is here: http://people.freebsd.org/~jkim/linux/amd64-dmesg.txt > It may be the case that the problem is somewhere in waitpid, but it > could also be the case it is somewhere else (fork, clone, ...). But > we need to see the big picture to determine this. Let me know if you need anything else. Thanks, Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609282109.24348.jkim>