Re: Failure to make world for RELENG_6_4
Xin LI wrote: > > According to kan@, it looks like a bug in FreeBSD 6.x :( unfortunately. > The good news is that the problem has been fixed in 7.x series. Yes, I confirm that "make buildworld" works fine for RELENG_7_1 under VMWare ESXi with 2 virtual CPUs, even with -j4 or -j8. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor Sudakov wrote: > Xin LI wrote: misc/133264 >>> This one however is not so simple. I have tried building world under >>> VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building >>> process crashed occasionally if more than 1 CPU is allocated to the >>> virtual machine. The failures are due to various processes like sh, >>> sed or cc1 dupming core on signal 11 during the build. >>> >>> The problem seems to be SMP related because enabling only 1 virtual >>> CPU removes the problem. Of course it is also VMWare related. >> - From what you have described, it's likely that there is some memory >> issue. The FreeBSD Virtual Memory system tends to use all physical >> memory and this could be a problem for faulty memory chips (i.e. it's >> more easy for FreeBSD to trigger problems). > > How is this connected with the number of virtual CPUs? > When I give only 1 CPU to the virtual machine, the problem is gone. > >> If you have access to the host system and possible, would you please try >> to install FreeBSD directly and see if the problem still occurs? > > Sorry, I cannot do that. This host is already running several Windows > servers and has been thoroughly tested before production use. > > I have however run Memtest-86 v3.2 in the virtual machine for > 2 hours and it has found no errors. No, memtest is known to be weaker than a 'make world'. According to kan@, it looks like a bug in FreeBSD 6.x :( unfortunately. The good news is that the problem has been fixed in 7.x series. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknZivsACgkQi+vbBBjt66Ag+QCeKj/hsbvPLuiKa65iLsxWj5lt 0JEAnjWtwrGKX11P8h9W2ATmO13dwFT7 =ZVZj -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
Alexander Kabaev wrote:
>
> this seems to be the issue with combination of FreeBSD 6.x and VMWare
> hypervisor when running with more than one virtual CPUs. I see it will
> the full range of VMWare products, from Player to Fusion and
> Workstation. FreeBSD 7 and up are working fine.
Is there a hypervisor which has no problems with FreeBSD? I have tried
several.
1. Under Microsoft (former Connectix) VirtualPC, FreeBSD has timer
problems ("microuptime went backwards").
2. Under VirtualBox, some processes tend to hang with the obscure
kernel mesage "sigreturn: eflags = 0x80286" (the VirtualBox
bugtracker claims the issue is fixed, but it is not).
3. Under ESXi, you know.
4. What about Xen? Is it worth trying?
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
Xin LI wrote: > >> misc/133264 > > > > This one however is not so simple. I have tried building world under > > VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building > > process crashed occasionally if more than 1 CPU is allocated to the > > virtual machine. The failures are due to various processes like sh, > > sed or cc1 dupming core on signal 11 during the build. > > > > The problem seems to be SMP related because enabling only 1 virtual > > CPU removes the problem. Of course it is also VMWare related. > > - From what you have described, it's likely that there is some memory > issue. The FreeBSD Virtual Memory system tends to use all physical > memory and this could be a problem for faulty memory chips (i.e. it's > more easy for FreeBSD to trigger problems). How is this connected with the number of virtual CPUs? When I give only 1 CPU to the virtual machine, the problem is gone. > > If you have access to the host system and possible, would you please try > to install FreeBSD directly and see if the problem still occurs? Sorry, I cannot do that. This host is already running several Windows servers and has been thoroughly tested before production use. I have however run Memtest-86 v3.2 in the virtual machine for 2 hours and it has found no errors. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
On Sun, 05 Apr 2009 19:09:57 -0700 Xin LI wrote: > > - From what you have described, it's likely that there is some memory > issue. The FreeBSD Virtual Memory system tends to use all physical > memory and this could be a problem for faulty memory chips (i.e. it's > more easy for FreeBSD to trigger problems). > > If you have access to the host system and possible, would you please > try to install FreeBSD directly and see if the problem still occurs? > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! JFYI, this seems to be the issue with combination of FreeBSD 6.x and VMWare hypervisor when running with more than one virtual CPUs. I see it will the full range of VMWare products, from Player to Fusion and Workstation. FreeBSD 7 and up are working fine. -- Alexander Kabaev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Kabaev wrote: > On Sun, 05 Apr 2009 19:09:57 -0700 > Xin LI wrote: >> - From what you have described, it's likely that there is some memory >> issue. The FreeBSD Virtual Memory system tends to use all physical >> memory and this could be a problem for faulty memory chips (i.e. it's >> more easy for FreeBSD to trigger problems). >> >> If you have access to the host system and possible, would you please >> try to install FreeBSD directly and see if the problem still occurs? >> >> Cheers, >> - -- >> Xin LI http://www.delphij.net/ >> FreeBSD - The Power to Serve! > JFYI, > > this seems to be the issue with combination of FreeBSD 6.x and VMWare > hypervisor when running with more than one virtual CPUs. I see it will > the full range of VMWare products, from Player to Fusion and > Workstation. FreeBSD 7 and up are working fine. I see, thanks for the pointer. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknZbgAACgkQi+vbBBjt66D7fACgiiqUD6G0YobszxnDpQEvrdtM g80AoJPh1UDufIml6i66iWJw5EdH6uEH =rlCg -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor Sudakov wrote: >> misc/133264 > > This one however is not so simple. I have tried building world under > VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building > process crashed occasionally if more than 1 CPU is allocated to the > virtual machine. The failures are due to various processes like sh, > sed or cc1 dupming core on signal 11 during the build. > > The problem seems to be SMP related because enabling only 1 virtual > CPU removes the problem. Of course it is also VMWare related. - From what you have described, it's likely that there is some memory issue. The FreeBSD Virtual Memory system tends to use all physical memory and this could be a problem for faulty memory chips (i.e. it's more easy for FreeBSD to trigger problems). If you have access to the host system and possible, would you please try to install FreeBSD directly and see if the problem still occurs? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknZZHUACgkQi+vbBBjt66DbrACfY0tbGQImQgm9PJJGbWDQPZLt FvIAoK+fWNP2eA37Zs6WpSaF0zG83vWg =7wMS -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failure to make world for RELENG_6_4
Victor Sudakov wrote: > > I have recently submitted 2 PRs > misc/133066 This one was due to a dirty source tree. > misc/133264 This one however is not so simple. I have tried building world under VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building process crashed occasionally if more than 1 CPU is allocated to the virtual machine. The failures are due to various processes like sh, sed or cc1 dupming core on signal 11 during the build. The problem seems to be SMP related because enabling only 1 virtual CPU removes the problem. Of course it is also VMWare related. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
