From tinderbox at freebsd.org Wed Jul 1 07:02:33 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Jul 1 07:02:55 2009 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20090701070230.076767302F@freebsd-current.sentex.ca> TB --- 2009-07-01 05:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-07-01 05:00:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-07-01 05:00:00 - cleaning the object tree TB --- 2009-07-01 05:01:03 - cvsupping the source tree TB --- 2009-07-01 05:01:03 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-07-01 05:01:10 - building world TB --- 2009-07-01 05:01:10 - MAKEOBJDIRPREFIX=/obj TB --- 2009-07-01 05:01:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-07-01 05:01:10 - TARGET=amd64 TB --- 2009-07-01 05:01:10 - TARGET_ARCH=amd64 TB --- 2009-07-01 05:01:10 - TZ=UTC TB --- 2009-07-01 05:01:10 - __MAKE_CONF=/dev/null TB --- 2009-07-01 05:01:10 - cd /src TB --- 2009-07-01 05:01:10 - /usr/bin/make -B buildworld >>> World build started on Wed Jul 1 05:01:12 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Wed Jul 1 07:01:31 UTC 2009 TB --- 2009-07-01 07:01:31 - generating LINT kernel config TB --- 2009-07-01 07:01:31 - cd /src/sys/amd64/conf TB --- 2009-07-01 07:01:31 - /usr/bin/make -B LINT TB --- 2009-07-01 07:01:31 - building LINT kernel TB --- 2009-07-01 07:01:31 - MAKEOBJDIRPREFIX=/obj TB --- 2009-07-01 07:01:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-07-01 07:01:31 - TARGET=amd64 TB --- 2009-07-01 07:01:31 - TARGET_ARCH=amd64 TB --- 2009-07-01 07:01:31 - TZ=UTC TB --- 2009-07-01 07:01:31 - __MAKE_CONF=/dev/null TB --- 2009-07-01 07:01:31 - cd /src TB --- 2009-07-01 07:01:31 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jul 1 07:01:31 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies -------------------------------------------------------------- cd /obj/amd64/src/sys/LINT; MAKEOBJDIRPREFIX=/obj/amd64 MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/obj/amd64/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/obj/amd64/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/obj/amd64/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=/obj/amd64/src/tmp VERSION="FreeBSD 8.0-CURRENT i386 800003" INSTALL="sh /src/tools/install.sh" PATH=/obj/amd64/src/tmp/legacy/usr/sbin:/obj/amd64/src/tmp/legacy/usr/bin:/obj/amd64/src/tmp/legacy/usr/games:/obj/amd64/src/tmp/usr/sbin:/obj/amd64/src/tmp/usr/bin:/obj/amd64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin NO_CTF=1 /usr/bin/make KERNEL=kernel depend -DNO_MODULES_OBJ machine -> /src/sys/amd64/include cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/gnu/fs/xfs/FreeBSD -I/src/sys/gnu/fs/xfs/FreeBSD/support -I/src/sys/gnu/fs/xfs -I/src/sys/contrib/opensolaris/compat -I/src/sys/dev/cxgb -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector /src/sys/amd64/amd64/g enassym.c /src/sys/amd64/amd64/genassym.c:67:23: error: nfs/rpcv2.h: No such file or directory *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-07-01 07:02:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-07-01 07:02:29 - ERROR: failed to build lint kernel TB --- 2009-07-01 07:02:29 - 5708.16 user 602.27 system 7349.05 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From karthy at netic.dk Wed Jul 1 07:16:39 2009 From: karthy at netic.dk (Karsten Thygesen) Date: Wed Jul 1 07:16:47 2009 Subject: Netvault on FreeBSD-7.2 AMD64 In-Reply-To: <20090629182642.GA3248@slackbox.xs4all.nl> References: <237A4FC3-3CBD-453B-A606-9F07E3F56FBD@netic.dk> <20090629182642.GA3248@slackbox.xs4all.nl> Message-ID: <3945011B-1308-44E8-AB3D-F6BC224475C0@netic.dk> Hi Thanks a lot to all of you, who responded on my query. The solution was to install lib32 (I still wonder why I did de-select them during installation) as many of you pointed out. When I did this, the Netvault binaries could almost run, but they had problems finding their dynamic libraries, and after quite a lot of googling, I figured out, that I had to set LD_32_LIBRARY_PATH instead of LD_LIBRARY_PATH - that little, but crusial, difference took quite some hours to figure out. But after we got this knowledge, everything seems to work and we do now have Netvault on FreeBSD-7.2-amd64 (but it is an unsupported platform from Bakbone - come on, Bakbone, get up to speed!). A small wish is, that it would be wonderful if the FreeBSD handbook could be extended with a small chapter on how to run 32 bit binaries on 64 bit platforms - especially hints like LD_32_LIBRARY_PATH would be nice to know about... :-) But thanks guys - the FreeBSD community is the best!! Karsten On Jun 29, 2009, at 20:26 , Roland Smith wrote: > On Mon, Jun 29, 2009 at 12:19:44PM +0200, Karsten Thygesen wrote: >> Hi >> >> We use FreeBSD-7.2 (p2, amd64) but it turns out, that there is >> problems running Netvault. >> >> Netvault only support FreeBSD in 32bit (and I can verify, that it >> works just fine here), so we are on out own with 64bit support. >> >> I'm quite new to 64bit edition of FreeBSD, so there might be >> something >> simple, that I do not know about, but when I try to run one of the >> netvault binaries, I get this error: >> >> [karthy@karthywork ~]$ ./txtconfig >> ELF interpreter /libexec/ld-elf.so.1 not found >> Abort trap: 6 > > AFAIK, a 32-bit app should be looking for /libexec/ld-elf32.so.1! > > Does /libexec/ld-elf32.so.1 exist? Are there any libraries in /usr/ > lib32? > If not, you need to install or build 32-bit compatible libraries. Not > just the system libraries (you should be able to get those from the > install CD with sysinstall), but also any 3rd party libraries that > netvault requires! > >> [karthy@karthywork ~]$ ls -l /libexec/ld-elf.so.1 >> -r-xr-xr-x 1 root wheel 198456 Jun 29 11:32 /libexec/ld-elf.so.1 > >> [karthy@karthywork ~]$ file txtconfig >> txtconfig: ELF 32-bit LSB executable, Intel 80386, version 1 >> (FreeBSD), dynamically linked (uses shared libs), stripped >> >> [karthy@karthywork ~]$ uname -a >> FreeBSD karthywork.netic.dk 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: >> Wed Jun 24 00:14:35 UTC 2009 root@amd64-builder.daemonology.net:/ >> usr/obj/usr/src/sys/GENERIC amd64 > > Seems that you are using a GENERIC kernel. That does include 32-bit > compatibility. > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much > appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: > C321A725) From dfr at rabson.org Wed Jul 1 08:30:38 2009 From: dfr at rabson.org (Doug Rabson) Date: Wed Jul 1 14:03:00 2009 Subject: [head tinderbox] failure on amd64/amd64 In-Reply-To: <20090701070230.076767302F@freebsd-current.sentex.ca> References: <20090701070230.076767302F@freebsd-current.sentex.ca> Message-ID: Fixed. On 1 Jul 2009, at 08:02, FreeBSD Tinderbox wrote: > TB --- 2009-07-01 05:00:00 - tinderbox 2.6 running on freebsd- > current.sentex.ca > TB --- 2009-07-01 05:00:00 - starting HEAD tinderbox run for amd64/ > amd64 > TB --- 2009-07-01 05:00:00 - cleaning the object tree > TB --- 2009-07-01 05:01:03 - cvsupping the source tree > TB --- 2009-07-01 05:01:03 - /usr/bin/csup -z -r 3 -g -L 1 -h > localhost -s /tinderbox/HEAD/amd64/amd64/supfile > TB --- 2009-07-01 05:01:10 - building world > TB --- 2009-07-01 05:01:10 - MAKEOBJDIRPREFIX=/obj > TB --- 2009-07-01 05:01:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-07-01 05:01:10 - TARGET=amd64 > TB --- 2009-07-01 05:01:10 - TARGET_ARCH=amd64 > TB --- 2009-07-01 05:01:10 - TZ=UTC > TB --- 2009-07-01 05:01:10 - __MAKE_CONF=/dev/null > TB --- 2009-07-01 05:01:10 - cd /src > TB --- 2009-07-01 05:01:10 - /usr/bin/make -B buildworld >>>> World build started on Wed Jul 1 05:01:12 UTC 2009 >>>> Rebuilding the temporary build tree >>>> stage 1.1: legacy release compatibility shims >>>> stage 1.2: bootstrap tools >>>> stage 2.1: cleaning up the object tree >>>> stage 2.2: rebuilding the object tree >>>> stage 2.3: build tools >>>> stage 3: cross tools >>>> stage 4.1: building includes >>>> stage 4.2: building libraries >>>> stage 4.3: make dependencies >>>> stage 4.4: building everything >>>> stage 5.1: building 32 bit shim libraries >>>> World build completed on Wed Jul 1 07:01:31 UTC 2009 > TB --- 2009-07-01 07:01:31 - generating LINT kernel config > TB --- 2009-07-01 07:01:31 - cd /src/sys/amd64/conf > TB --- 2009-07-01 07:01:31 - /usr/bin/make -B LINT > TB --- 2009-07-01 07:01:31 - building LINT kernel > TB --- 2009-07-01 07:01:31 - MAKEOBJDIRPREFIX=/obj > TB --- 2009-07-01 07:01:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-07-01 07:01:31 - TARGET=amd64 > TB --- 2009-07-01 07:01:31 - TARGET_ARCH=amd64 > TB --- 2009-07-01 07:01:31 - TZ=UTC > TB --- 2009-07-01 07:01:31 - __MAKE_CONF=/dev/null > TB --- 2009-07-01 07:01:31 - cd /src > TB --- 2009-07-01 07:01:31 - /usr/bin/make -B buildkernel > KERNCONF=LINT >>>> Kernel build for LINT started on Wed Jul 1 07:01:31 UTC 2009 >>>> stage 1: configuring the kernel >>>> stage 2.1: cleaning up the object tree >>>> stage 2.2: rebuilding the object tree >>>> stage 2.3: build tools >>>> stage 3.1: making dependencies > -------------------------------------------------------------- > cd /obj/amd64/src/sys/LINT; MAKEOBJDIRPREFIX=/obj/amd64 > MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/obj/ > amd64/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/obj/amd64/src/tmp/ > legacy/usr/share/groff_font GROFF_TMAC_PATH=/obj/amd64/src/tmp/ > legacy/usr/share/tmac _SHLIBDIRPREFIX=/obj/amd64/src/tmp > VERSION="FreeBSD 8.0-CURRENT i386 800003" INSTALL="sh /src/tools/ > install.sh" PATH=/obj/amd64/src/tmp/legacy/usr/sbin:/obj/amd64/src/ > tmp/legacy/usr/bin:/obj/amd64/src/tmp/legacy/usr/games:/obj/amd64/ > src/tmp/usr/sbin:/obj/amd64/src/tmp/usr/bin:/obj/amd64/src/tmp/usr/ > games:/sbin:/bin:/usr/sbin:/usr/bin NO_CTF=1 /usr/bin/make > KERNEL=kernel depend -DNO_MODULES_OBJ > machine -> /src/sys/amd64/include > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 - > Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes - > Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef - > Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/ > sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf - > I/src/sys/dev/ath -I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/ > ngatm -I/src/sys/dev/twa -I/src/sys/gnu/fs/xfs/FreeBSD -I/src/sys/ > gnu/fs/xfs/FreeBSD/support -I/src/sys/gnu/fs/xfs -I/src/sys/contrib/ > opensolaris/compat -I/src/sys/dev/cxgb -D_KERNEL - > DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline- > limit=8000 --param inline-unit-growth=100 --param large-function- > growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno- > builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone - > mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft- > float -fno-asynchronous-unwind-tables -ffreestanding -fstack- > protector /src/sys/amd64/amd64/g > enassym.c > /src/sys/amd64/amd64/genassym.c:67:23: error: nfs/rpcv2.h: No such > file or directory > *** Error code 1 > > Stop in /obj/amd64/src/sys/LINT. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > TB --- 2009-07-01 07:02:29 - WARNING: /usr/bin/make returned exit > code 1 > TB --- 2009-07-01 07:02:29 - ERROR: failed to build lint kernel > TB --- 2009-07-01 07:02:29 - 5708.16 user 602.27 system 7349.05 real > > > http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org > " From stas at net.utcluj.ro Wed Jul 1 13:50:03 2009 From: stas at net.utcluj.ro (Stas Sușcov) Date: Wed Jul 1 14:28:52 2009 Subject: amd64/136218: Exported ZFS pools can't be imported into (Open)Solaris Message-ID: <200907011346.n61Dkd9o075472@www.freebsd.org> >Number: 136218 >Category: amd64 >Synopsis: Exported ZFS pools can't be imported into (Open)Solaris >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 01 13:50:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Stas Sușcov >Release: 7.2 to 8-current >Organization: UTCN >Environment: >Description: # zpool import -f pool: tank id: 2794438138141825953 state: UNAVAIL status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: http://www.sun.com/msg/ZFS-8000-5E config: tank UNAVAIL insufficient replicas raidz1 UNAVAIL corrupted data c0t1d0p0 ONLINE c0t2d0s8 UNAVAIL corrupted data c0t3d0s2 ONLINE # zpool import -f tank cannot import 'tank': no such pool or dataset # zdb -l /dev/dsk/c0t2d0s8 -------------------------------------------- LABEL 0 -------------------------------------------- version=13 name='tank' state=1 txg=2563123 pool_guid=2794438138141825953 hostname='' top_guid=15872320949015295970 guid=6991675266341970117 vdev_tree type='raidz' id=0 guid=15872320949015295970 nparity=1 metaslab_array=14 metaslab_shift=34 ashift=9 asize=3000599838720 is_log=0 children[0] type='disk' id=0 guid=7503403694738120161 path='/dev/da0' whole_disk=0 DTL=142 children[1] type='disk' id=1 guid=6991675266341970117 path='/dev/da1' whole_disk=0 DTL=139 children[2] type='disk' id=2 guid=12393268613817866398 path='/dev/da2' whole_disk=0 DTL=141 -------------------------------------------- LABEL 1 -------------------------------------------- version=13 name='tank' state=1 txg=2563123 pool_guid=2794438138141825953 hostname='' top_guid=15872320949015295970 guid=6991675266341970117 vdev_tree type='raidz' id=0 guid=15872320949015295970 nparity=1 metaslab_array=14 metaslab_shift=34 ashift=9 asize=3000599838720 is_log=0 children[0] type='disk' id=0 guid=7503403694738120161 path='/dev/da0' whole_disk=0 DTL=142 children[1] type='disk' id=1 guid=6991675266341970117 path='/dev/da1' whole_disk=0 DTL=139 children[2] type='disk' id=2 guid=12393268613817866398 path='/dev/da2' whole_disk=0 DTL=141 -------------------------------------------- LABEL 2 -------------------------------------------- failed to unpack label 2 -------------------------------------------- LABEL 3 -------------------------------------------- failed to unpack label 3 >How-To-Repeat: Pool `tank` was created in FreeBSD 7.2-R. After it I booted into FreeBSD 8-current and imported and upgraded the pool to V.13. After I installed Nexenta CP2 (formerly OpenSolaris Nevada build 20081207) which uses ZFS V.14. The full description (inside Nexenta) is above. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From rsmith at xs4all.nl Wed Jul 1 17:44:28 2009 From: rsmith at xs4all.nl (Roland Smith) Date: Wed Jul 1 17:44:34 2009 Subject: Netvault on FreeBSD-7.2 AMD64 In-Reply-To: <3945011B-1308-44E8-AB3D-F6BC224475C0@netic.dk> References: <237A4FC3-3CBD-453B-A606-9F07E3F56FBD@netic.dk> <20090629182642.GA3248@slackbox.xs4all.nl> <3945011B-1308-44E8-AB3D-F6BC224475C0@netic.dk> Message-ID: <20090701174426.GB37269@slackbox.xs4all.nl> On Wed, Jul 01, 2009 at 08:47:00AM +0200, Karsten Thygesen wrote: > Hi > > Thanks a lot to all of you, who responded on my query. The solution > was to install lib32 (I still wonder why I did de-select them during > installation) as many of you pointed out. > > When I did this, the Netvault binaries could almost run, but they had > problems finding their dynamic libraries, and after quite a lot of > googling, I figured out, that I had to set LD_32_LIBRARY_PATH instead > of LD_LIBRARY_PATH - that little, but crusial, difference took quite > some hours to figure out. But after we got this knowledge, everything > seems to work and we do now have Netvault on FreeBSD-7.2-amd64 (but it > is an unsupported platform from Bakbone - come on, Bakbone, get up to > speed!). > > A small wish is, that it would be wonderful if the FreeBSD handbook > could be extended with a small chapter on how to run 32 bit binaries > on 64 bit platforms - especially hints like LD_32_LIBRARY_PATH would > be nice to know about... :-) The thing is, I don't think you should have to set LD_32_LIBRARY_PATH. Did you reboot after installing the 32 bits libraries? Because if you do, /etc/rc.d/ldconfig should run ldconfig for the 32-bits libraries in /usr/lib32. See ldconfig32_paths in /etc/defaults/rc.conf and /etc/rc.d/ldconfig. Alternatively you can run '/etc/rc.d/ldconfig start' as root after installing the libraries. If that doesn't work, it would be a bug. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20090701/f0f99e4a/attachment.pgp From karthy at netic.dk Wed Jul 1 19:16:30 2009 From: karthy at netic.dk (Karsten Thygesen) Date: Wed Jul 1 19:16:45 2009 Subject: Netvault on FreeBSD-7.2 AMD64 In-Reply-To: <20090701174426.GB37269@slackbox.xs4all.nl> References: <237A4FC3-3CBD-453B-A606-9F07E3F56FBD@netic.dk> <20090629182642.GA3248@slackbox.xs4all.nl> <3945011B-1308-44E8-AB3D-F6BC224475C0@netic.dk> <20090701174426.GB37269@slackbox.xs4all.nl> Message-ID: Hi Ronald Oh, I guess I wrote it a bit confusing - the binaries could find the lib32 libraries just fine, but they also need some netvault specific libraries, which is stored in a vendor specific directory - I had to set LD_32_LIBRARY_PATH to point to that library - there was no problems with the compatibility libraries. Karsten On Jul 1, 2009, at 19:44 , Roland Smith wrote: > On Wed, Jul 01, 2009 at 08:47:00AM +0200, Karsten Thygesen wrote: >> Hi >> >> Thanks a lot to all of you, who responded on my query. The solution >> was to install lib32 (I still wonder why I did de-select them during >> installation) as many of you pointed out. >> >> When I did this, the Netvault binaries could almost run, but they had >> problems finding their dynamic libraries, and after quite a lot of >> googling, I figured out, that I had to set LD_32_LIBRARY_PATH instead >> of LD_LIBRARY_PATH - that little, but crusial, difference took quite >> some hours to figure out. But after we got this knowledge, everything >> seems to work and we do now have Netvault on FreeBSD-7.2-amd64 (but >> it >> is an unsupported platform from Bakbone - come on, Bakbone, get up to >> speed!). >> >> A small wish is, that it would be wonderful if the FreeBSD handbook >> could be extended with a small chapter on how to run 32 bit binaries >> on 64 bit platforms - especially hints like LD_32_LIBRARY_PATH would >> be nice to know about... :-) > > The thing is, I don't think you should have to set LD_32_LIBRARY_PATH. > > Did you reboot after installing the 32 bits libraries? Because if you > do, /etc/rc.d/ldconfig should run ldconfig for the 32-bits libraries > in > /usr/lib32. See ldconfig32_paths in /etc/defaults/rc.conf and > /etc/rc.d/ldconfig. > > Alternatively you can run '/etc/rc.d/ldconfig start' as root after > installing the libraries. > > If that doesn't work, it would be a bug. > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much > appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: > C321A725) From stas at net.utcluj.ro Wed Jul 1 21:50:03 2009 From: stas at net.utcluj.ro (Stas SUSHKOV) Date: Wed Jul 1 22:09:32 2009 Subject: amd64/136218: Exported ZFS pools can't be imported into (Open)Solaris Message-ID: <200907012150.n61Lo2xt051296@freefall.freebsd.org> The following reply was made to PR amd64/136218; it has been noted by GNATS. From: Stas SUSHKOV To: bug-followup@FreeBSD.org, stas@net.utcluj.ro Cc: Cristi Magherusan , pjd@freebsd.org Subject: Re: amd64/136218: Exported ZFS pools can't be imported into (Open)Solaris Date: Thu, 02 Jul 2009 00:41:49 +0300 Finally I was able to import the poll on OpenSolaris 2009.06 (snv_111b) with ZFS v.14. I had to remove all slices from /dev/rdsk and than retry zpool import. This helped me: # mkdir /tmp/bad_devs # cd /tmp/bad_devs # for i in /dev/rdsk/c7t[0123456789]d0s*; do mv $i ./; done # zpool import -f tank # zpool upgrade -V 14 tank # zpool export tank Thanks. -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ From linimon at FreeBSD.org Thu Jul 2 10:41:41 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Jul 2 13:12:15 2009 Subject: kern/136218: [zfs] Exported ZFS pools can't be imported into (Open)Solaris Message-ID: <200907021041.n62AfegV089453@freefall.freebsd.org> Old Synopsis: Exported ZFS pools can't be imported into (Open)Solaris New Synopsis: [zfs] Exported ZFS pools can't be imported into (Open)Solaris Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jul 2 10:41:22 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=136218 From tim at bishnet.net Thu Jul 2 16:40:05 2009 From: tim at bishnet.net (Tim Bishop) Date: Thu Jul 2 16:51:35 2009 Subject: amd64/136251: xn0 doesn't DHCP Message-ID: <200907021630.n62GU32G099711@www.freebsd.org> >Number: 136251 >Category: amd64 >Synopsis: xn0 doesn't DHCP >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 02 16:40:04 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Tim Bishop >Release: FreeBSD 8.0-CURRENT amd64 >Organization: >Environment: FreeBSD xenserver.kent.ac.uk 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Jul 1 22:55:53 BST 2009 tdb@xenserver.kent.ac.uk:/usr/obj/usr/src/sys/XENHVM amd64 Running 8.0-CURRENT as of yesterday on Citrix XenServer 5.5.0. >Description: When using the amd64 XENHVM kernel (which has the xenpci device) the machine has a network device called xn0: xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 30 at device 3.0 on pci0 xenbus0: on xenpci0 xn0: at device/vif/0 on xenbus0 xn0: Ethernet address: 36:ab:02:63:a3:ff However, this device doesn't behave like a normal network device, so adding the following to rc.conf doesn't do DHCP: ifconfig_xn0="DHCP" After some poking around I realised dhclient was launched by devd. However, the xn0 device has properties which don't match the existing rules: setting system=IFNET setting subsystem=xn0 setting type=ATTACH >How-To-Repeat: See above: 8.0-CURRENT, amd64 XENHVM kernel, Citrix XenServer. >Fix: I've worked around this problem by adding the following entry to /etc/devd.conf at line 77 (after the IFNET/LINK_UP/802.11 section): notify 0 { match "system" "IFNET"; match "subsystem" "xn[0-9]+"; match "type" "ATTACH"; action "/etc/rc.d/dhclient quietstart $subsystem"; }; This is my first look at devd, so apologies if this fix isn't appropriate. It'd be great if this fix could make it in to 8.0. >Release-Note: >Audit-Trail: >Unformatted: From tdb at FreeBSD.org Thu Jul 2 17:15:20 2009 From: tdb at FreeBSD.org (tdb@FreeBSD.org) Date: Thu Jul 2 18:17:38 2009 Subject: amd64/136251: xn0 doesn't DHCP Message-ID: <200907021715.n62HFJbO092710@freefall.freebsd.org> Synopsis: xn0 doesn't DHCP Responsible-Changed-From-To: freebsd-amd64->freebsd-xen Responsible-Changed-By: tdb Responsible-Changed-When: Thu Jul 2 17:15:19 UTC 2009 Responsible-Changed-Why: Reassign my PR to a more appropriate group. http://www.freebsd.org/cgi/query-pr.cgi?pr=136251 From kamikaze at bsdforen.de Fri Jul 3 07:50:05 2009 From: kamikaze at bsdforen.de (Dominic Fandrey) Date: Fri Jul 3 13:36:08 2009 Subject: amd64/127276: ldd(1) invokes linux yes Message-ID: <200907030750.n637o4S5090416@freefall.freebsd.org> The following reply was made to PR amd64/127276; it has been noted by GNATS. From: Dominic Fandrey To: bug-followup@FreeBSD.org, kamikaze@bsdforen.de Cc: Subject: Re: amd64/127276: ldd(1) invokes linux yes Date: Fri, 03 Jul 2009 09:22:37 +0200 How about documenting this behaviour in the manual page and closing this bug? I'm willing to write a patch if someone thinks this would be an acceptable solution. From ogreve at millennics.com Fri Jul 3 18:31:00 2009 From: ogreve at millennics.com (Olaf Greve) Date: Fri Jul 3 18:31:07 2009 Subject: Howto do SW RAID? Message-ID: Hi guys, Firstly, thanks to the robustness of FreeBSD-AMD64 it's been many moons since I last found myself in need of help from the pros. :) However, such a situation has arissen now. Up until two weeks ago I was happily running the AMD64 version on my primary server and the i386 version on my secondary machine, with both of them using Adaptec SCSI hardware RAID arrays. All fine but for a failed disc in my secondary machine. Now, it was about time I'd revise the fallback machine anyway, and last week a server from work was phased out and given to me. :) Now, unfortunately I have precious little time to wipe the inferior Debian installation that's currently on it. ;) Some questions: 1-The BIOS lists it as having a Pentium 4 processor that mentions being EM64T compatible, so I think the AMD64 version should be the best choice, right? 2-Unfortunately the drives are not as fancy as my current servers. It has two SATA 160GB drives, set up in software RAID mode. For now, I want to set up fbsd in SW RAID mode too (too little time to buy other drives!). Can anyone explain me briefly how I can set it up? Tnx in advance and cheers, Olafo From ianjhart at ntlworld.com Fri Jul 3 19:46:33 2009 From: ianjhart at ntlworld.com (Ian J Hart) Date: Fri Jul 3 19:46:41 2009 Subject: Howto do SW RAID? In-Reply-To: References: Message-ID: <20090703202958.978655ejfxy0r8kk@webmail.private.lan> Quoting Olaf Greve : > Hi guys, > > Firstly, thanks to the robustness of FreeBSD-AMD64 it's been many > moons since I last found myself in need of help from the pros. :) > However, such a situation has arissen now. > > Up until two weeks ago I was happily running the AMD64 version on my > primary server and the i386 version on my secondary machine, with > both of them using Adaptec SCSI hardware RAID arrays. All fine but > for a failed disc in my secondary machine. > > Now, it was about time I'd revise the fallback machine anyway, and > last week a server from work was phased out and given to me. :) > Now, unfortunately I have precious little time to wipe the inferior > Debian installation that's currently on it. ;) > > Some questions: > 1-The BIOS lists it as having a Pentium 4 processor that mentions > being EM64T compatible, so I think the AMD64 version should be the > best choice, right? > 2-Unfortunately the drives are not as fancy as my current servers. > It has two SATA 160GB drives, set up in software RAID mode. For now, > I want to set up fbsd in SW RAID mode too (too little time to buy > other drives!). Can anyone explain me briefly how I can set it up? > > Tnx in advance and cheers, > Olafo > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html -- ian j hart ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From ogreve at millennics.com Sat Jul 4 08:43:43 2009 From: ogreve at millennics.com (Olaf Greve) Date: Sat Jul 4 08:43:51 2009 Subject: Howto do SW RAID? In-Reply-To: <20090703185046.3782125a@bhuda.mired.org> References: <20090703202958.978655ejfxy0r8kk@webmail.private.lan> <20090703185046.3782125a@bhuda.mired.org> Message-ID: <1BBC202D-920C-480A-B59D-BA0F1581E301@millennics.com> Hi Mike and Ian, Firtsly: thanks a lot for your answers; they're very much appreciated! :) Then some specifics: >> >> Some questions: >> 1-The BIOS lists it as having a Pentium 4 processor that mentions >> being EM64T compatible, so I think the AMD64 version should be the >> best choice, right? >I'd say yes - I've been running a P4 that way for about three years >now, but there may still be some things for which ix86 might be a >better choice. Most commented on is probably that the nvidia >proprietary video drivers don't (yet) work on amd64 FreeBSD >builds. I'm perfectly happy with the OSS ATI drivers, but others >aren't. Roger that! As for video performance... As long as it can handle text mode, I'm o.k. with it. ;) The machine will only be used as a web and back-up server, so X will not even be installed by me. Now for the more tricky decision: Ian wrote: > > http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html And Mike wrote: >If you're willing to run a little bit experimental, zfs is a much >nicer storage solution in general: >https://www.ish.com.au/solutions/articles/freebsdzfs I must say, ZFS sounds very cool, yet.... the experimental thingy attached to it is somewhat off-putting at present. I noticed a remark about the kernel memory tuning possibly being hasslesome. I'm not exactly certain what to do best at this point in time, but perhaps that can best be decided by looking at what this very installation will have to do. At present, the anticipated use of the machine, is to become my fallback server for the primary one. That means that it will nightly rsync files from then primary one, as well as the MySQL DB instances running on it, and some other data I want backed up to the fallback machine. Performance (i.e. speed) is not the main key indicator, but stability and realibility are, as is -possibly- easiness of restoration when a drive fails completeley or partially. I've read the pages you both refer too, and it seems ZFS has good capabilities for disaster recovery, as well as automatic healing and snapshots. It certainly sounds like something to experiment with, but I'm not certain if now is the best time to do so. I still have to read the gmirror man pages to see what would be involved in disaster recovery, so I'm not certain yet if that's trivial or not. Hmmm, tough call... Meanwhile: can anyone comment om these points? Any hands-on experience with either, perhaps? Cheers! Olafo From petefrench at ticketswitch.com Sat Jul 4 09:52:37 2009 From: petefrench at ticketswitch.com (Pete French) Date: Sat Jul 4 09:52:44 2009 Subject: Howto do SW RAID? In-Reply-To: <1BBC202D-920C-480A-B59D-BA0F1581E301@millennics.com> Message-ID: > I must say, ZFS sounds very cool, yet.... the experimental thingy > attached to it is somewhat off-putting at present. I noticed a remark > about the kernel memory tuning possibly being hasslesome. I'm not None of those things are true anymore on the latest -STABLE and amd64. I use a ZFS based machine for backup, much as you describe. Nightly rsync and continuous stream of data to a mysql slave. ZFS gives you the distinct advantage of being bale to sake snapshots - so I have dailys for the last 5 days, and I keep the sunday one of those as weeklies going back as far as I have disc space for. All online and not actually taking up any significant space as snapshots will only use disc space for the changes. If you are clever with symobilc links you can even arrange it so your database snapshot is actually online inside your mysql linstance. One of my machine has the live database, plus 'live-7am', 'live-9am', 'live-11am' so if people make a mess of a table then they can grab the data from no older than two hours ago instantly "insert into live.table_i_screwed_up select * from live-9am.table_i_screwed_up;" Given your system I'd acquire a 3rd drive (4 gig flash card will do) for boot and then make a ZFS mirror our of the existing two and stick everything significant onto that. It works very nicely indeed. -pete. From freebsd-current at chrishedley.com Sat Jul 4 21:37:30 2009 From: freebsd-current at chrishedley.com (Chris Hedley) Date: Sat Jul 4 21:37:42 2009 Subject: New builds won't boot (fwd) In-Reply-To: <20090630175731.4c589f80@ernst.jennejohn.org> References: <4A2C124A.1050707@freebsd.org> <3c1674c90906291830g1c79c80bq42ce99f44588e968@mail.gmail.com> <20090630113544.3e2bef31@ernst.jennejohn.org> <20090630175731.4c589f80@ernst.jennejohn.org> Message-ID: On Tue, 30 Jun 2009, Gary Jennejohn wrote: > Ah, yes. Now that I think about it again, you're right. That's also > when I started seeing it. > > I'm now running mav's ata-cam patches and took ATA_STATIC_ID out of > my config file. I'd sort of forgotten when/why I'd done it. > > Sorry for the confusion. No problems, I may have a look at the ata-cam patch myself to see if that's any more successful. So thanks for the idea. :) On a completely different subject (and unrelated to the kind souls who have helped out), I'm a bit miffed to find these messages have been gated onto the web by freebsd.org, kerneltrap.org et al with complete, intact email addresses making them easily available to every spammer, 419er and other miscreant on the net. I was wondering why the amount of spam I was getting had tripled in the last fortnight. >:( From ogreve at millennics.com Sat Jul 4 22:24:42 2009 From: ogreve at millennics.com (Olaf Greve) Date: Sat Jul 4 22:24:48 2009 Subject: Howto do SW RAID? In-Reply-To: References: Message-ID: Hi Pete, >None of those things are true anymore on the latest -STABLE and amd64. + >Given your system I'd acquire a 3rd drive (4 gig flash card will do) for >boot and then make a ZFS mirror our of the existing two and stick >everything significant onto that. It works very nicely indeed. Alright, thanks for the extra input! Good to hear that the reported initial issues are now a thing of the past too. Meanwhile... earlier today I made up my mind: it seemed to me that the gmirror way involved less steps to configure it, and I need to have the machine set-up in as little time as possible, between a million of other matters. Also, the machine that has the failed drive will in due time be used by me for experimenting with some things (a.o. using newer PHP and MySQL versions than I use at present too), and I shall keep the e-mails and links on this subject and conduct a test with it when I've got some more air in my schedule. It certainly sounds like a cool filesystem! Then, as written above, in between matters I've set up the system using gmirror; it all worked very easily and I'm now at the level that I've set-up the ports tree, SSH access, etc. Tomorrow I'll reconstruct the rsync calls and DB syncing scripts etc. and then the machine should be go for acting as back-up machine while I'm abroad for a few weeks. Thanks again to you guys for your help and ideas! Cheers, Olafo From peter at vk2pj.dyndns.org Mon Jul 6 08:49:07 2009 From: peter at vk2pj.dyndns.org (Peter Jeremy) Date: Mon Jul 6 14:10:00 2009 Subject: Howto do SW RAID? In-Reply-To: <1BBC202D-920C-480A-B59D-BA0F1581E301@millennics.com> References: <20090703202958.978655ejfxy0r8kk@webmail.private.lan> <20090703185046.3782125a@bhuda.mired.org> <1BBC202D-920C-480A-B59D-BA0F1581E301@millennics.com> Message-ID: <20090706073248.GA8044@server.vk2pj.dyndns.org> On 2009-Jul-04 10:43:34 +0200, Olaf Greve wrote: >I must say, ZFS sounds very cool, yet.... the experimental thingy >attached to it is somewhat off-putting at present. I wouldn't use ZFS unless you are running 7-stable _after_ 7.2-RELEASE (after 20th May to be precise) or -current. 7.2-RELEASE has a much older ZFS. I'm running ZFS on -current my home server without problems but it's not heavily loaded. >I've read the pages you both refer too, and it seems ZFS has good >capabilities for disaster recovery, as well as automatic healing and >snapshots. It certainly sounds like something to experiment with, but >I'm not certain if now is the best time to do so. I would agree with this. ZFS is still a somewhat experimental feature and some people have found some rough edges. I'd recommend finding a spare amd64-capable box with a couple of disks and >=2GB RAM, install 7-stable and try both replicating data into it and load-stressing it to see how well it behaves for you. (Mind you, if you've not used gmirror before, I'd suggest you do the same for it). -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20090706/a787cd19/attachment.pgp From bugmaster at FreeBSD.org Mon Jul 6 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 6 14:10:20 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200907061106.n66B6q1K010669@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 FreeBSD/amd64 does not (always) detect disk on SB600/A o amd64/134978 amd64 g_up pmap amd64 panic o amd64/134786 amd64 [vfs] [patch] vfs.bufspace sysctl wideness on amd64 o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT o amd64/132372 amd64 [ata] No disks found (nVidia nForce MCP55 sata control o amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe f amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128810 amd64 AMD 64 port installation o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128686 amd64 [ata] can't detect SATA Disk on 8.0-Current with NF550 o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails o amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 90 problems total. From nexther0 at gmail.com Mon Jul 6 11:20:03 2009 From: nexther0 at gmail.com (Yevgeniy) Date: Mon Jul 6 14:10:43 2009 Subject: amd64/136376: net-mgmt/openvmps port does not build and running correctly on amd64 Message-ID: <200907061119.n66BJ5Hg089903@www.freebsd.org> >Number: 136376 >Category: amd64 >Synopsis: net-mgmt/openvmps port does not build and running correctly on amd64 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jul 06 11:20:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Yevgeniy >Release: 7.1-RELEASE-p4 >Organization: >Environment: FreeBSD noc.umc.com.ua 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #3: Thu Apr 2 09:57:28 EEST 2009 root@noc.umc.com.ua:/usr/obj/usr/src/sys/NOC amd64 >Description: net-mgmt/openvmps port does not build and running correctly on amd64 port produce lots of warning on building: vqp.c:43: warning: incompatible implicit declaration of built-in function 'memcpy' vqp.c:48: warning: incompatible implicit declaration of built-in function 'strcpy' vqp.c:51: warning: incompatible implicit declaration of built-in function 'bzero' vqp.c: In function 'send_response': vqp.c:144: warning: incompatible implicit declaration of built-in function 'memcpy' vqp.c:154: warning: incompatible implicit declaration of built-in function 'strlen' vqp.c: In function 'get_vlan': vqp.c:233: warning: incompatible implicit declaration of built-in function 'strcpy' vqp.c:237: warning: incompatible implicit declaration of built-in function 'strcpy' vqp.c:243: warning: incompatible implicit declaration of built-in function 'strcpy' vqp.c:253: warning: incompatible implicit declaration of built-in function 'strcpy' after installing vmpsd sends packet without VlanName >How-To-Repeat: simply build and install >Fix: >Release-Note: >Audit-Trail: >Unformatted: From linimon at FreeBSD.org Tue Jul 7 09:36:26 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Tue Jul 7 12:50:25 2009 Subject: ports/136376: net-mgmt/openvmps port does not build and running correctly on amd64 Message-ID: <200907070936.n679aPV4022986@freefall.freebsd.org> Synopsis: net-mgmt/openvmps port does not build and running correctly on amd64 Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Jul 7 09:35:38 UTC 2009 Responsible-Changed-Why: Even though this applies to amd64, this is a ports issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=136376 From markocpc at gmail.com Thu Jul 9 06:56:16 2009 From: markocpc at gmail.com (Lagrange Marc) Date: Thu Jul 9 06:56:24 2009 Subject: Building kernel : CPUID_FXSR undeclared (first use...) Message-ID: <1b5ab4050907082324m1c70a304s8487192e46f63fc8@mail.gmail.com> Hi, I've just installed a 8-BETA1 on my new computer, checkouted the sources via svn (http://svn.freebsd.org/base/head). I've recompiled a kernel without debug and whitheness sucessfully, but when i've try to remove some things and it fails. The kernel configuration is here : http://banane.rhaamo.li/NAWAK The CPU is : CPU: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz (2499.73-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10677 Stepping = 7 Features=0xbfebfbff Features2=0x8e3fd AMD Features=0x20000800 AMD Features2=0x1 TSC: P-state invariant The kernel build error: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/amd64/in_cksum.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/amd64/initcpu.c /usr/src/sys/amd64/amd64/initcpu.c: In function 'initializecpu': /usr/src/sys/amd64/amd64/initcpu.c:146: error: 'CPUID_FXSR' undeclared (first use in this function) /usr/src/sys/amd64/amd64/initcpu.c:146: error: (Each undeclared identifier is reported only once /usr/src/sys/amd64/amd64/initcpu.c:146: error: for each function it appears in.) *** Error code 1 Stop in /usr/obj/usr/src/sys/NAWAK. *** Error code 1 Stop in /usr/src. I've also experiencing the same issue with audio/oss, it failed on CPUID_FXSR, but now fail with CPU_SSE or CPU_SSE2... If someone have an idea with this problem, Thanks. -- rhaamo on irc.freenode.net/oftc/geeknode From markocpc at gmail.com Thu Jul 9 08:11:13 2009 From: markocpc at gmail.com (Lagrange Marc) Date: Thu Jul 9 08:11:26 2009 Subject: Building kernel : CPUID_FXSR undeclared (first use...) In-Reply-To: References: <1b5ab4050907082324m1c70a304s8487192e46f63fc8@mail.gmail.com> Message-ID: <1b5ab4050907090111q4cb29ea7t2f7518e844efbf54@mail.gmail.com> On Thu, Jul 9, 2009 at 9:53 AM, Eygene Ryabinkin wrote: > Thu, Jul 09, 2009 at 08:24:20AM +0200, Lagrange Marc wrote: >> cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native >> -std=c99 ?-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes >> ?-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual ?-Wundef >> -Wno-pointer-sign -fformat-extensions -nostdinc ?-I. -I/usr/src/sys >> -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS >> -include opt_global.h -fno-common -finline-limit=8000 --param >> inline-unit-growth=100 --param large-function-growth=1000 >> -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone ?-mfpmath=387 >> -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow ?-msoft-float >> -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector >> -Werror ?/usr/src/sys/amd64/amd64/initcpu.c >> /usr/src/sys/amd64/amd64/initcpu.c: In function 'initializecpu': >> /usr/src/sys/amd64/amd64/initcpu.c:146: error: 'CPUID_FXSR' undeclared >> (first use in this function) >> /usr/src/sys/amd64/amd64/initcpu.c:146: error: (Each undeclared >> identifier is reported only once >> /usr/src/sys/amd64/amd64/initcpu.c:146: error: for each function it appears in.) > > What output will be produced by the following command (should be invoked > from your kernel compile directory, /sys/amd64/compile/ if > you compile manually or /usr/obj/usr/src/sys/ for 'make > kernel' builds; looks like you is NAWAK): > ----- > cpp -dD -O2 -frename-registers -pipe -fno-strict-aliasing -march=native \ > -std=c99 ?-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ > ?-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual ?-Wundef \ > ?-Wno-pointer-sign -fformat-extensions -nostdinc ?-I. -I/usr/src/sys \ > ?-I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS \ > ?-include opt_global.h -fno-common -finline-limit=8000 --param \ > ?inline-unit-growth=100 --param large-function-growth=1000 \ > ?-fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone ?-mfpmath=387 \ > ?-mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow ?-msoft-float \ > ?-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector \ > ?-Werror ?/usr/src/sys/amd64/amd64/initcpu.c 2>&1 > ----- Output here : http://banane.rhaamo.li/bugs/CPUID_FXSR/output_cpp > And what is inside the file 'machine/specialreg.h' when you're sitting > in the same directory? File here : http://banane.rhaamo.li/bugs/CPUID_FXSR/specialreg.h > I'd expect that 'make clean && make kernel' invoked from /usr/src > should fix your problems, but may be it is not the case, so information > requested above will be helpful. Tryied make clean && make kernel after getting requested infos, same error. Thx. > -- > Eygene > ?_ ? ? ? ? ? ? ? ?___ ? ? ? _.--. ? # > ?\`.|\..----...-'` ? `-._.-'_.-'` ? # ?Remember that it is hard > ?/ ?' ` ? ? ? ? , ? ? ? __.--' ? ? ?# ?to read the on-line manual > ?)/' _/ ? ? \ ? `-_, ? / ? ? ? ? ? ?# ?while single-stepping the kernel. > ?`-'" `"\_ ?,_.-;_.-\_ ', ?fsc/as ? # > ? ? _.-'_./ ? {_.' ? ; / ? ? ? ? ? # ? ?-- FreeBSD Developers handbook > ? ?{_.-``-' ? ? ? ? {_/ ? ? ? ? ? ?# > -- rhaamo on irc.freenode.net/oftc/geeknode From markocpc at gmail.com Thu Jul 9 08:29:12 2009 From: markocpc at gmail.com (Lagrange Marc) Date: Thu Jul 9 08:29:25 2009 Subject: Building kernel : CPUID_FXSR undeclared (first use...) In-Reply-To: References: <1b5ab4050907082324m1c70a304s8487192e46f63fc8@mail.gmail.com> <1b5ab4050907090111q4cb29ea7t2f7518e844efbf54@mail.gmail.com> Message-ID: <1b5ab4050907090129g5599d754w469170297e1b459a@mail.gmail.com> On Thu, Jul 9, 2009 at 10:19 AM, Eygene Ryabinkin wrote: > Thu, Jul 09, 2009 at 10:11:09AM +0200, Lagrange Marc wrote: >> > And what is inside the file 'machine/specialreg.h' when you're sitting >> > in the same directory? >> >> File here : http://banane.rhaamo.li/bugs/CPUID_FXSR/specialreg.h > > Then, it is simple: you had manually commented the line 105: > ----- > /*#define ? ? ? CPUID_FXSR ? ? ?0x01000000*/ > ----- > Uncomment it (inside /sys/amd64/include/specialreg.h) and rebuild > the stuff. ?Better will be to resync the sources, get rid of all > local modifications (if any) and rebuild. Argl yes... i remember commented this !@# line in oss source (thx symlinks) because oss fail on CPUID_FXSR .. Thx. > -- > Eygene > ?_ ? ? ? ? ? ? ? ?___ ? ? ? _.--. ? # > ?\`.|\..----...-'` ? `-._.-'_.-'` ? # ?Remember that it is hard > ?/ ?' ` ? ? ? ? , ? ? ? __.--' ? ? ?# ?to read the on-line manual > ?)/' _/ ? ? \ ? `-_, ? / ? ? ? ? ? ?# ?while single-stepping the kernel. > ?`-'" `"\_ ?,_.-;_.-\_ ', ?fsc/as ? # > ? ? _.-'_./ ? {_.' ? ; / ? ? ? ? ? # ? ?-- FreeBSD Developers handbook > ? ?{_.-``-' ? ? ? ? {_/ ? ? ? ? ? ?# > -- rhaamo on irc.freenode.net/oftc/geeknode From rea-fbsd at codelabs.ru Thu Jul 9 08:04:31 2009 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Thu Jul 9 13:27:20 2009 Subject: Building kernel : CPUID_FXSR undeclared (first use...) In-Reply-To: <1b5ab4050907082324m1c70a304s8487192e46f63fc8@mail.gmail.com> References: <1b5ab4050907082324m1c70a304s8487192e46f63fc8@mail.gmail.com> Message-ID: Thu, Jul 09, 2009 at 08:24:20AM +0200, Lagrange Marc wrote: > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native > -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-common -finline-limit=8000 --param > inline-unit-growth=100 --param large-function-growth=1000 > -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 > -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > -Werror /usr/src/sys/amd64/amd64/initcpu.c > /usr/src/sys/amd64/amd64/initcpu.c: In function 'initializecpu': > /usr/src/sys/amd64/amd64/initcpu.c:146: error: 'CPUID_FXSR' undeclared > (first use in this function) > /usr/src/sys/amd64/amd64/initcpu.c:146: error: (Each undeclared > identifier is reported only once > /usr/src/sys/amd64/amd64/initcpu.c:146: error: for each function it appears in.) What output will be produced by the following command (should be invoked from your kernel compile directory, /sys/amd64/compile/ if you compile manually or /usr/obj/usr/src/sys/ for 'make kernel' builds; looks like you is NAWAK): ----- cpp -dD -O2 -frename-registers -pipe -fno-strict-aliasing -march=native \ -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef \ -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys \ -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS \ -include opt_global.h -fno-common -finline-limit=8000 --param \ inline-unit-growth=100 --param large-function-growth=1000 \ -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 \ -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float \ -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector \ -Werror /usr/src/sys/amd64/amd64/initcpu.c 2>&1 ----- And what is inside the file 'machine/specialreg.h' when you're sitting in the same directory? I'd expect that 'make clean && make kernel' invoked from /usr/src should fix your problems, but may be it is not the case, so information requested above will be helpful. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From rea-fbsd at codelabs.ru Thu Jul 9 08:19:50 2009 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Thu Jul 9 13:27:28 2009 Subject: Building kernel : CPUID_FXSR undeclared (first use...) In-Reply-To: <1b5ab4050907090111q4cb29ea7t2f7518e844efbf54@mail.gmail.com> References: <1b5ab4050907082324m1c70a304s8487192e46f63fc8@mail.gmail.com> <1b5ab4050907090111q4cb29ea7t2f7518e844efbf54@mail.gmail.com> Message-ID: Thu, Jul 09, 2009 at 10:11:09AM +0200, Lagrange Marc wrote: > > And what is inside the file 'machine/specialreg.h' when you're sitting > > in the same directory? > > File here : http://banane.rhaamo.li/bugs/CPUID_FXSR/specialreg.h Then, it is simple: you had manually commented the line 105: ----- /*#define CPUID_FXSR 0x01000000*/ ----- Uncomment it (inside /sys/amd64/include/specialreg.h) and rebuild the stuff. Better will be to resync the sources, get rid of all local modifications (if any) and rebuild. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From bugmaster at FreeBSD.org Mon Jul 13 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 13 11:11:24 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200907131106.n6DB6nJW040500@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/134978 amd64 [panic] g_up pmap amd64 panic o amd64/134786 amd64 [vfs] [patch] vfs.bufspace sysctl wideness on amd64 o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT o amd64/132372 amd64 [ata] No disks found (nVidia nForce MCP55 sata control o amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe f amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128810 amd64 AMD 64 port installation o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128686 amd64 [ata] can't detect SATA Disk on 8.0-Current with NF550 o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails o amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 90 problems total. From freebsd-current at chrishedley.com Mon Jul 13 13:03:29 2009 From: freebsd-current at chrishedley.com (Chris Hedley) Date: Mon Jul 13 13:03:36 2009 Subject: New builds won't boot (fwd) In-Reply-To: References: <4A2C124A.1050707@freebsd.org> <3c1674c90906291830g1c79c80bq42ce99f44588e968@mail.gmail.com> <20090630113544.3e2bef31@ernst.jennejohn.org> <20090630175731.4c589f80@ernst.jennejohn.org> Message-ID: On Sat, 4 Jul 2009, Chris Hedley wrote: > On Tue, 30 Jun 2009, Gary Jennejohn wrote: > >> Ah, yes. Now that I think about it again, you're right. That's also >> when I started seeing it. >> >> I'm now running mav's ata-cam patches and took ATA_STATIC_ID out of >> my config file. I'd sort of forgotten when/why I'd done it. >> >> Sorry for the confusion. > > No problems, I may have a look at the ata-cam patch myself to see if that's > any more successful. So thanks for the idea. :) Hmm, still having no luck with this, although I haven't tried the ata-cam patch (partly due to an irrational fear that it'll eat all my data, partly as I don't really want to make things any more complicated than they already are by just trying random things to see if they work). Perhaps my best bet is to ask the person who submitted the changes to the ATA system at the time - listed as "mav" in CVS. Could anybody point me in their direction (or point them in this direction)? Thanks, Chris. From freebsd-current at chrishedley.com Mon Jul 13 16:47:55 2009 From: freebsd-current at chrishedley.com (Chris Hedley) Date: Mon Jul 13 16:48:08 2009 Subject: New builds won't boot (fwd) In-Reply-To: References: <4A2C124A.1050707@freebsd.org> <3c1674c90906291830g1c79c80bq42ce99f44588e968@mail.gmail.com> <20090630113544.3e2bef31@ernst.jennejohn.org> <20090630175731.4c589f80@ernst.jennejohn.org> Message-ID: On Mon, 13 Jul 2009, Chris Hedley wrote: > Perhaps my best bet is to ask the person who submitted the changes to the ATA > system at the time - listed as "mav" in CVS. Could anybody point me in their > direction (or point them in this direction)? Just a follow up, now it's been brought to his attention "mav" has already appeared with a working patch for my problem. I have to say I'm impressed. Many thanks to everyone who has assisted me with their help, advice and encouragement. I appreciate it. :) Chris. From jhb at freebsd.org Mon Jul 13 17:24:50 2009 From: jhb at freebsd.org (John Baldwin) Date: Mon Jul 13 17:25:01 2009 Subject: amd64/136161: sysinstall installs wrong architecture In-Reply-To: <200906291442.n5TEgMNL040053@www.freebsd.org> References: <200906291442.n5TEgMNL040053@www.freebsd.org> Message-ID: <200907131140.33550.jhb@freebsd.org> On Monday 29 June 2009 10:42:22 am Yuriy Glukhov wrote: > > >Number: 136161 > >Category: amd64 > >Synopsis: sysinstall installs wrong architecture > >Confidential: no > >Severity: non-critical > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon Jun 29 14:50:00 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Yuriy Glukhov > >Release: 7.2 > >Organization: > >Environment: > FreeBSD test.localdomain 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > >Description: > 1. Install an amd64 distribution on a USB pen drive. > 2. Install the pen drive to a Xeon server. > 3. Boot from the pen drive. > 4. Run sysinstall, and install (standard installation) the OS to the local HDD, using one of FreeBSD FTPs. > 5. Remove the pen drive and boot from the HDD with newly installed system. > 6. Observe the uname -a. > > Actual result: the architecture is i386. > Expected result: the architecture should be amd64. Are you sure you had amd64 on the pen drive (verified with uname -a). The arch to install is hard-coded into the sysinstall binary at build time such that an amd64 sysinstall can only install an amd64 release. -- John Baldwin From mav at FreeBSD.org Mon Jul 13 19:07:51 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Jul 13 19:07:58 2009 Subject: New builds won't boot (fwd) In-Reply-To: <1244398986.00123728.1244388603@10.7.7.3> References: <1244398986.00123728.1244388603@10.7.7.3> Message-ID: <4A5B77E2.8030602@FreeBSD.org> Chris Hedley wrote: > Hope it's not bad form for me to forward this on to -current for > comments; I guess since nobody else has brought this up it's something > I'm doing wrong rather than a serious flaw, but I'd be most grateful for > a pointer nonetheless. :) > > And, since I think I forgot to mention it, I'm using -current/amd64 and > ZFS v13. > > ---------- Forwarded message ---------- > Date: Fri, 5 Jun 2009 11:00:48 > From: Chris Hedley > To: freebsd-amd64@freebsd.org > Subject: New builds won't boot > > I was wondering if anybody has any suggestions for me. Since around > January this year, I've been unable to get new builds to boot on my > system: they go through the usual kernel initialisation stage, reach the > "ZFS is an experimental feature" message, sometimes followed a few other > random notices, and then it hangs indefinitely. Fixed. It was a bug in Marvell SATA driver in 8-CURRENT. -- Alexander Motin From yuriy.glukhov at gmail.com Wed Jul 15 18:23:53 2009 From: yuriy.glukhov at gmail.com (Yuriy Glukhov) Date: Wed Jul 15 20:29:48 2009 Subject: amd64/136161: sysinstall installs wrong architecture In-Reply-To: <200907131140.33550.jhb@freebsd.org> References: <200906291442.n5TEgMNL040053@www.freebsd.org> <200907131140.33550.jhb@freebsd.org> Message-ID: <0F379C7A-C190-4819-9F81-51E370BF4D2B@gmail.com> Yes, after booting from a pen drive "uname -a" displays amd64 arch. If the arch is hard-coded to sysinstall, could it be that the wrong sysinstall is installed on the pen-drive? I'm not sure if the sysinstall just copies itself during the installation or it downloads itself with another packages from ftp. In second case it could be explained with an incorrect ftp distribution. Best regards, Yuriy Glukhov. On Jul 13, 2009, at 6:40 PM, John Baldwin wrote: > On Monday 29 June 2009 10:42:22 am Yuriy Glukhov wrote: >> >>> Number: 136161 >>> Category: amd64 >>> Synopsis: sysinstall installs wrong architecture >>> Confidential: no >>> Severity: non-critical >>> Priority: medium >>> Responsible: freebsd-amd64 >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: sw-bug >>> Submitter-Id: current-users >>> Arrival-Date: Mon Jun 29 14:50:00 UTC 2009 >>> Closed-Date: >>> Last-Modified: >>> Originator: Yuriy Glukhov >>> Release: 7.2 >>> Organization: >>> Environment: >> FreeBSD test.localdomain 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri >> May 1 > 07:18:07 UTC 2009 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >>> Description: >> 1. Install an amd64 distribution on a USB pen drive. >> 2. Install the pen drive to a Xeon server. >> 3. Boot from the pen drive. >> 4. Run sysinstall, and install (standard installation) the OS to >> the local > HDD, using one of FreeBSD FTPs. >> 5. Remove the pen drive and boot from the HDD with newly installed >> system. >> 6. Observe the uname -a. >> >> Actual result: the architecture is i386. >> Expected result: the architecture should be amd64. > > Are you sure you had amd64 on the pen drive (verified with uname - > a). The > arch to install is hard-coded into the sysinstall binary at build > time such > that an amd64 sysinstall can only install an amd64 release. > > -- > John Baldwin From ohunermund at logmein.com Thu Jul 16 07:30:03 2009 From: ohunermund at logmein.com (Oliver Hunermund) Date: Thu Jul 16 11:35:50 2009 Subject: amd64/136814: mxge driver error Message-ID: <200907160723.n6G7N7Z3012983@www.freebsd.org> >Number: 136814 >Category: amd64 >Synopsis: mxge driver error >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 16 07:30:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Oliver Hunermund >Release: 7.2 >Organization: LogMeIn, Inc. >Environment: FreeBSD freebsd 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: We are running FreeBSD v7.2 amd64 edition with the MyriCom 10G-PCIE-8A-R+E cards. When the slices are enabled and we try to bring up the interfaces we get the following error: mxge0: alloced 256/1024 bigs mxge0: couldn't open slice 6 >How-To-Repeat: enable slices attempt to bring up interfaces >Fix: >Release-Note: >Audit-Trail: >Unformatted: From office at adaptcom.ro Sat Jul 18 08:50:02 2009 From: office at adaptcom.ro (Theodor Chirana) Date: Sat Jul 18 14:30:10 2009 Subject: amd64/136884: Try to install FreeBSD 7.2 amd64 on a proliant DL360 G4 Message-ID: <200907180843.n6I8hLIc084309@www.freebsd.org> >Number: 136884 >Category: amd64 >Synopsis: Try to install FreeBSD 7.2 amd64 on a proliant DL360 G4 >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jul 18 08:50:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Theodor Chirana >Release: 7.2 amd64 >Organization: >Environment: HP Proliant DL 360 G4 with 1 Intel XEON 64 bit 3GHz >Description: When Trying to begin the installation it gives kernel trap 12 ciss0: Cannot allocate interrupt This is olso with or without MPS APIC enabled or disabled and with a normal install or with a normal install with APIC disabled. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From killing at multiplay.co.uk Sun Jul 19 13:10:57 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Sun Jul 19 13:11:09 2009 Subject: i386_set_ldt on FreeBSD 7.x amd64 Message-ID: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> I'm trying to convert some audio streams and the only app which seems to be capable of this mplayer with the w32codecs Unfortunately the machine is 7.1 amd64. I've compiled the binaries up on an old i386 box but when running said bins on the amd64 box it errors with: Opening audio decoder: [dmo] Win32/DMO decoders install_fs: Invalid argument Couldn't install fs segment, expect segfault Looking at the code the call to i386_set_ldt is failing is there any know workaround? Looking on Google there is a thread: i386_set_ldt and wine on AMD64 which mentions some patches by kib but no mention if this ever worked. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=233316+0+archive/2008/freebsd-amd64/20081214.freebsd-amd64 The latest version I can find is: http://people.freebsd.org/~kib/misc/amd64_ldt-pre.4.patch Anyone info appreciated. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From kostikbel at gmail.com Sun Jul 19 13:48:56 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Sun Jul 19 13:49:03 2009 Subject: i386_set_ldt on FreeBSD 7.x amd64 In-Reply-To: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> References: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> Message-ID: <20090719134850.GX55190@deviant.kiev.zoral.com.ua> On Sun, Jul 19, 2009 at 02:00:00PM +0100, Steven Hartland wrote: > I'm trying to convert some audio streams and the only app > which seems to be capable of this mplayer with the w32codecs > > Unfortunately the machine is 7.1 amd64. I've compiled the > binaries up on an old i386 box but when running said bins > on the amd64 box it errors with: > > Opening audio decoder: [dmo] Win32/DMO decoders > install_fs: Invalid argument > Couldn't install fs segment, expect segfault > > Looking at the code the call to i386_set_ldt is failing > is there any know workaround? > > Looking on Google there is a thread: > i386_set_ldt and wine on AMD64 which mentions some patches by kib > but no mention if this ever worked. > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=233316+0+archive/2008/freebsd-amd64/20081214.freebsd-amd64 > > The latest version I can find is: > http://people.freebsd.org/~kib/misc/amd64_ldt-pre.4.patch > > Anyone info appreciated. The patches were committed to HEAD. mplayer/win32 codecs were tested, it was one of the goal of the patch to have these codecs working on amd64. No MFC to 7.x is planned. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20090719/411ec300/attachment.pgp From killing at multiplay.co.uk Sun Jul 19 14:29:52 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Sun Jul 19 14:29:58 2009 Subject: i386_set_ldt on FreeBSD 7.x amd64 References: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> <20090719134850.GX55190@deviant.kiev.zoral.com.ua> Message-ID: ----- Original Message ----- From: "Kostik Belousov" >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=233316+0+archive/2008/freebsd-amd64/20081214.freebsd-amd64 >> >> The latest version I can find is: >> http://people.freebsd.org/~kib/misc/amd64_ldt-pre.4.patch > > Anyone info appreciated. > The patches were committed to HEAD. mplayer/win32 codec's were tested, > it was one of the goal of the patch to have these codec's working on amd64. > > No MFC to 7.x is planned. Thanks for the confirmation Kostik. Do you believe there is any reason to stop that patch working on 7.X if manually applied? Is the patch above the final version that went into HEAD? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From kostikbel at gmail.com Sun Jul 19 15:11:47 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Sun Jul 19 15:11:59 2009 Subject: i386_set_ldt on FreeBSD 7.x amd64 In-Reply-To: References: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> <20090719134850.GX55190@deviant.kiev.zoral.com.ua> Message-ID: <20090719151141.GZ55190@deviant.kiev.zoral.com.ua> On Sun, Jul 19, 2009 at 03:29:51PM +0100, Steven Hartland wrote: > ----- Original Message ----- > From: "Kostik Belousov" > >>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=233316+0+archive/2008/freebsd-amd64/20081214.freebsd-amd64 > >> > >>The latest version I can find is: > >>http://people.freebsd.org/~kib/misc/amd64_ldt-pre.4.patch > > > >Anyone info appreciated. > >The patches were committed to HEAD. mplayer/win32 codec's were tested, > >it was one of the goal of the patch to have these codec's working on amd64. > > > >No MFC to 7.x is planned. > > Thanks for the confirmation Kostik. Do you believe there is any reason to > stop that patch working on 7.X if manually applied? Is the patch above the > final version that went into HEAD? No and no, but I think that back-porting is not that trivial. Upgrade is probably easier then backport. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20090719/2c94a4f1/attachment.pgp From killing at multiplay.co.uk Sun Jul 19 16:28:31 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Sun Jul 19 16:28:43 2009 Subject: i386_set_ldt on FreeBSD 7.x amd64 References: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> <20090719134850.GX55190@deviant.kiev.zoral.com.ua> <20090719151141.GZ55190@deviant.kiev.zoral.com.ua> Message-ID: ----- Original Message ----- From: "Kostik Belousov" >> Thanks for the confirmation Kostik. Do you believe there is any reason to >> stop that patch working on 7.X if manually applied? Is the patch above the >> final version that went into HEAD? > > No and no, but I think that back-porting is not that trivial. > Upgrade is probably easier then backport. When you say HEAD would that require an upgrade to 7-STABLE or 8-CURRENT? I never did get what the official meaning of HEAD is, as it seems to be used by different people to mean both of the above. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From ed at 80386.nl Sun Jul 19 20:07:37 2009 From: ed at 80386.nl (Ed Schouten) Date: Sun Jul 19 21:06:24 2009 Subject: i386_set_ldt on FreeBSD 7.x amd64 In-Reply-To: References: <34D8564661E84455B8DA136799C649ED@multiplay.co.uk> <20090719134850.GX55190@deviant.kiev.zoral.com.ua> <20090719151141.GZ55190@deviant.kiev.zoral.com.ua> Message-ID: <20090719200735.GG68469@hoeg.nl> Hi Steven, * Steven Hartland wrote: > When you say HEAD would that require an upgrade to 7-STABLE or 8-CURRENT? Right now HEAD (or head/ in SVN) is 8-CURRENT. RELENG_7 (or stable/7) is 7-STABLE. -- Ed Schouten WWW: http://80386.nl/ From bugmaster at FreeBSD.org Mon Jul 20 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 20 12:10:24 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200907201106.n6KB6nI6002177@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/136884 amd64 [install] Try to install FreeBSD 7.2 amd64 on a prolia o amd64/136814 amd64 [mxge] mxge driver error s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/134978 amd64 [panic] g_up pmap amd64 panic o amd64/134786 amd64 [vfs] [patch] vfs.bufspace sysctl wideness on amd64 o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT o amd64/132372 amd64 [ata] No disks found (nVidia nForce MCP55 sata control o amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe f amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128810 amd64 AMD 64 port installation o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128686 amd64 [ata] can't detect SATA Disk on 8.0-Current with NF550 o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails o amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 92 problems total. From killing at multiplay.co.uk Tue Jul 21 02:33:23 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Tue Jul 21 02:33:30 2009 Subject: FreeBSD 7.0-RELEASE amd64 on Dell M600 Blade References: <39DC135F7F0571489196E0B6F5D58B4A03B460D0@MWBEXCH.mweb.com> Message-ID: <415DF72E19E24DBEA840BAB408A3442E@multiplay.co.uk> Did anyone ever get anywhere with this, just retried with 8.0-BETA2 and still the same hangs as depicted in the attached screen shots. Sorry got no serial console :( Would like to get this working if possible so anything I can try to gain some more info on this issue? Regards Steve ----- Original Message ----- From: "Adam Jacob Muller" > > Anyone ever get this to work? Perhaps this was fixed in a newer > FreeBSD? Have some M600 that i'd like to get FreeBSD running on :) > > hint.apic.0.disabled seemed to change things a bit, it would reach ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From cpe at fullrate.dk Tue Jul 21 12:20:06 2009 From: cpe at fullrate.dk (Christoffer Persson) Date: Tue Jul 21 12:33:19 2009 Subject: amd64/136957: Kernel panic during boot with ProLiant DL360 G6 Message-ID: <200907211216.n6LCGaTG069050@www.freebsd.org> >Number: 136957 >Category: amd64 >Synopsis: Kernel panic during boot with ProLiant DL360 G6 >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 21 12:20:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Christoffer Persson >Release: 8.0-BETA2 >Organization: N/A >Environment: Unable to boot >Description: Kernel crashed at boot on a ProLiant DL360 G6, reporting run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config until it times out at 300 seconds and crashes, reporting: KBD: enter: panic [thread pid 0 tid 100000] Stopped at kdb_enter+0x3d: movq $0,0687f60(%rip) >How-To-Repeat: Happens during boot, every time. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From af.gourmet at videotron.ca Tue Jul 21 15:22:07 2009 From: af.gourmet at videotron.ca (PJ) Date: Tue Jul 21 15:22:14 2009 Subject: turion on acer travelmate 4400 Message-ID: <4A65CF01.3070002@videotron.ca> Unable to make custom kernel on FreeBSD 7.2 The default kernel works except for acpi errors on bootup. The amd GENERIC kernel is for "HAMMER". make buildkernel generates error messages regarding "undefined reference" to "critical_enter" and "critical_exit" in functions "sysarch" and "cpu_set_user_tls" What needs to be done to correct? -- Herv? Kempf: "Pour sauver la plan?te, sortez du capitalisme." ------------------------------------------------------------- Phil Jourdan --- pj@ptahhotep.com http://www.ptahhotep.com http://www.chiccantine.com/andypantry.php From gavin at FreeBSD.org Tue Jul 21 18:55:24 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Tue Jul 21 18:55:35 2009 Subject: ports/136965: php5 sigsegv Message-ID: <200907211855.n6LItNdf028881@freefall.freebsd.org> Synopsis: php5 sigsegv Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: gavin Responsible-Changed-When: Tue Jul 21 18:48:06 UTC 2009 Responsible-Changed-Why: Assume this is a ports bug at least initially. To submitter: can you explain how you ended up with things like this? Is the system a fresh install of 7.2, or is it an upgrade from a previous version (if so, how was it upgraded, and what version from?) http://www.freebsd.org/cgi/query-pr.cgi?pr=136965 From gavin at FreeBSD.org Tue Jul 21 20:16:52 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Tue Jul 21 20:16:58 2009 Subject: amd64/136957: Kernel panic during boot with ProLiant DL360 G6 Message-ID: <200907212016.n6LKGpBd089248@freefall.freebsd.org> Synopsis: Kernel panic during boot with ProLiant DL360 G6 State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Tue Jul 21 20:15:50 UTC 2009 State-Changed-Why: To submitter: At the "ddb" prompt, can you please enter the "bt" command and show the result? Responsible-Changed-From-To: freebsd-amd64->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Tue Jul 21 20:15:50 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=136957 From tot at cs.huji.ac.il Tue Jul 21 17:00:24 2009 From: tot at cs.huji.ac.il (Roman Melnikov) Date: Tue Jul 21 21:16:40 2009 Subject: amd64/136965: php5 sigsegv Message-ID: >Number: 136965 >Category: amd64 >Synopsis: php5 sigsegv >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 21 17:00:18 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Roman Melnikov >Release: FreeBSD 7.2-STABLE amd64 >Organization: >Environment: System: FreeBSD sunfire 7.2-STABLE FreeBSD 7.2-STABLE #29: Tue Jun 30 13:04:10 IDT 2009 danny@sunfire:/r+d/obj/sunfire/r+d/7/sys/HUJI amd64 >Description: sunfire# php Segmentation fault (core dumped) sunfire# gdb php GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) run Starting program: /dist/local/amd64=FreeBSD_7.2/bin/php (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100077] [New Thread 0x8012cf0b0 (LWP 100077)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x8012cf0b0 (LWP 100077)] 0x0000000806b20d72 in hash_lookup (hashtab=0x809e08560, key=0x7fffffffe4a0 "8\b\b") at misc.c:349 349 misc.c: No such file or directory. in misc.c >How-To-Repeat: php5 install from ports with default configuration , and this what I get ( sigsegv ) >Fix: >Release-Note: >Audit-Trail: >Unformatted: From tot at cs.huji.ac.il Tue Jul 21 19:52:44 2009 From: tot at cs.huji.ac.il (Roman Melnikov) Date: Tue Jul 21 21:16:52 2009 Subject: amd64/136965: php5 sigsegv In-Reply-To: <200907211700.n6LH0IV3035123@freefall.freebsd.org> References: <200907211700.n6LH0IV3035123@freefall.freebsd.org> Message-ID: <53e301600907211220l2b98f28frb859304a23629f83@mail.gmail.com> In addition to sigsegv. In more close look in gdb, I find that php get sigsegv from php5-recode, so when I deinstall php5-recode, php start work normally. On Tue, Jul 21, 2009 at 20:00, wrote: > Thank you very much for your problem report. > It has the internal identification `amd64/136965'. > The individual assigned to look at your > report is: freebsd-amd64. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=136965 > > >Category: amd64 > >Responsible: freebsd-amd64 > >Synopsis: php5 sigsegv > >Arrival-Date: Tue Jul 21 17:00:18 UTC 2009 > -- Ted Turner - "Sports is like a war without the killing." From jhb at freebsd.org Wed Jul 22 13:21:07 2009 From: jhb at freebsd.org (John Baldwin) Date: Wed Jul 22 13:21:29 2009 Subject: turion on acer travelmate 4400 In-Reply-To: <4A65CF01.3070002@videotron.ca> References: <4A65CF01.3070002@videotron.ca> Message-ID: <200907220815.44948.jhb@freebsd.org> On Tuesday 21 July 2009 10:21:53 am PJ wrote: > Unable to make custom kernel on FreeBSD 7.2 > The default kernel works except for acpi errors on bootup. > The amd GENERIC kernel is for "HAMMER". > make buildkernel generates error messages regarding "undefined > reference" to "critical_enter" and "critical_exit" in functions > "sysarch" and "cpu_set_user_tls" > What needs to be done to correct? Do you have any local modifications to your source tree? -- John Baldwin From ralf.folkerts at gmx.de Thu Jul 23 17:31:29 2009 From: ralf.folkerts at gmx.de (Ralf Folkerts) Date: Thu Jul 23 17:32:34 2009 Subject: amd64/135040: [ata] FreeBSD/amd64 does not (always) detect disk on SB600/AliveXFire eSata 2 Message-ID: <200907231731.n6NHVSwL030370@freefall.freebsd.org> The following reply was made to PR amd64/135040; it has been noted by GNATS. From: Ralf Folkerts To: bug-followup@FreeBSD.org, ralf.folkerts@gmx.de Cc: Subject: Re: amd64/135040: [ata] FreeBSD/amd64 does not (always) detect disk on SB600/AliveXFire eSata 2 Date: Thu, 23 Jul 2009 19:02:47 +0200 Hi, unfortunately I did not manage to get the Info re. the BIOS-Bug that was mentioned in the amd64-Mailing-List-Post by Jung-uk Kim :-( So, would it be possible to "generally" limit the DMA-Size in the ATA-Driver for the SB600? After running a few Tests I reverted back to the hw.physmem as I'm afraid of having to re-apply the Mod. to the DMA code each time rebuild the Kernel ;-) Cheers, _ralf_ From tinderbox at freebsd.org Fri Jul 24 23:20:18 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Jul 24 23:20:25 2009 Subject: [releng_7 tinderbox] failure on amd64/amd64 Message-ID: <20090724232014.EA2F11B5060@freebsd-stable.sentex.ca> TB --- 2009-07-24 21:39:39 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-07-24 21:39:39 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2009-07-24 21:39:39 - cleaning the object tree TB --- 2009-07-24 21:40:06 - cvsupping the source tree TB --- 2009-07-24 21:40:06 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2009-07-24 21:40:15 - building world TB --- 2009-07-24 21:40:15 - MAKEOBJDIRPREFIX=/obj TB --- 2009-07-24 21:40:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-07-24 21:40:15 - TARGET=amd64 TB --- 2009-07-24 21:40:15 - TARGET_ARCH=amd64 TB --- 2009-07-24 21:40:15 - TZ=UTC TB --- 2009-07-24 21:40:15 - __MAKE_CONF=/dev/null TB --- 2009-07-24 21:40:15 - cd /src TB --- 2009-07-24 21:40:15 - /usr/bin/make -B buildworld >>> World build started on Fri Jul 24 21:40:16 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Fri Jul 24 23:10:05 UTC 2009 TB --- 2009-07-24 23:10:05 - generating LINT kernel config TB --- 2009-07-24 23:10:05 - cd /src/sys/amd64/conf TB --- 2009-07-24 23:10:05 - /usr/bin/make -B LINT TB --- 2009-07-24 23:10:05 - building LINT kernel TB --- 2009-07-24 23:10:05 - MAKEOBJDIRPREFIX=/obj TB --- 2009-07-24 23:10:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-07-24 23:10:05 - TARGET=amd64 TB --- 2009-07-24 23:10:05 - TARGET_ARCH=amd64 TB --- 2009-07-24 23:10:05 - TZ=UTC TB --- 2009-07-24 23:10:05 - __MAKE_CONF=/dev/null TB --- 2009-07-24 23:10:05 - cd /src TB --- 2009-07-24 23:10:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jul 24 23:10:05 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/inflate.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/init_main.c cc1: warnings being treated as errors In file included from /src/sys/kern/init_main.c:71: /src/sys/sys/sysproto.h:1705: warning: redundant redeclaration of 'lkmnosys' /src/sys/sys/sysent.h:164: warning: previous declaration of 'lkmnosys' was here /src/sys/sys/sysproto.h:1802: warning: redundant redeclaration of 'lkmressys' /src/sys/sys/sysent.h:165: warning: previous declaration of 'lkmressys' was here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-07-24 23:20:14 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-07-24 23:20:14 - ERROR: failed to build lint kernel TB --- 2009-07-24 23:20:14 - 5024.71 user 564.53 system 6035.52 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full From mclos.lin at gmail.com Sun Jul 26 03:20:02 2009 From: mclos.lin at gmail.com (Guixian Lin) Date: Sun Jul 26 03:38:35 2009 Subject: amd64/137145: Reference count computing isn't correct when more than one threads call function m_copypacket Message-ID: <200907260314.n6Q3ElRh052143@www.freebsd.org> >Number: 137145 >Category: amd64 >Synopsis: Reference count computing isn't correct when more than one threads call function m_copypacket >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jul 26 03:20:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Guixian Lin >Release: FreeBSD 7.0 >Organization: Array Networks Inc. >Environment: FreeBSD AN 7.0-RELEASE FreeBSD 7.0-RELEASE #6: Sun Jul 19 16:30:17 UTC 2009 lin_gx@lingxvm.arraynetworks.com.cn:/array/rel_8/smp/FreeBSD/src/sys/compile/SERVER amd6 >Description: In our products, there exists one mbuf+mclust which is used to storage the certificate. And there're 3 threads will call m_copypacket to copy the packet during the communication. At some cases, the reference count of the mclust isn't correct, and which will cause double free the mclust. >How-To-Repeat: In kernel, you can write a test program, which will call m_copypacket. Then use loadrunner to stress the program. After some time, system will panic. >Fix: Following is my fix for this problem: --- uipc_mbuf.c.org 2009-07-26 10:58:56.000000000 +0800 +++ uipc_mbuf.c 2009-07-26 10:59:27.000000000 +0800 @@ -317,10 +317,7 @@ mb_dupcl(struct mbuf *n, struct mbuf *m) KASSERT(m->m_ext.ref_cnt != NULL, ("%s: ref_cnt not set", __func__)); KASSERT((n->m_flags & M_EXT) == 0, ("%s: M_EXT set", __func__)); - if (*(m->m_ext.ref_cnt) == 1) - *(m->m_ext.ref_cnt) += 1; - else - atomic_add_int(m->m_ext.ref_cnt, 1); + atomic_add_int(m->m_ext.ref_cnt, 1); n->m_ext.ext_buf = m->m_ext.ext_buf; n->m_ext.ext_free = m->m_ext.ext_free; n->m_ext.ext_args = m->m_ext.ext_args; Patch attached with submission follows: --- uipc_mbuf.c.org 2009-07-26 10:58:56.000000000 +0800 +++ uipc_mbuf.c 2009-07-26 10:59:27.000000000 +0800 @@ -317,10 +317,7 @@ mb_dupcl(struct mbuf *n, struct mbuf *m) KASSERT(m->m_ext.ref_cnt != NULL, ("%s: ref_cnt not set", __func__)); KASSERT((n->m_flags & M_EXT) == 0, ("%s: M_EXT set", __func__)); - if (*(m->m_ext.ref_cnt) == 1) - *(m->m_ext.ref_cnt) += 1; - else - atomic_add_int(m->m_ext.ref_cnt, 1); + atomic_add_int(m->m_ext.ref_cnt, 1); n->m_ext.ext_buf = m->m_ext.ext_buf; n->m_ext.ext_free = m->m_ext.ext_free; n->m_ext.ext_args = m->m_ext.ext_args; >Release-Note: >Audit-Trail: >Unformatted: From linimon at FreeBSD.org Mon Jul 27 04:42:10 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Jul 27 05:15:05 2009 Subject: kern/137145: [mbuf] [patch] Reference count computing isn't correct when more than one threads call function m_copypacket Message-ID: <200907270442.n6R4g9iE086739@freefall.freebsd.org> Old Synopsis: Reference count computing isn't correct when more than one threads call function m_copypacket New Synopsis: [mbuf] [patch] Reference count computing isn't correct when more than one threads call function m_copypacket Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 27 04:41:05 UTC 2009 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=137145 From bugmaster at FreeBSD.org Mon Jul 27 11:06:49 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jul 27 14:29:01 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200907271106.n6RB6mQt018835@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/136884 amd64 [install] Try to install FreeBSD 7.2 amd64 on a prolia o amd64/136814 amd64 [mxge] mxge driver error s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/134978 amd64 [panic] g_up pmap amd64 panic o amd64/134786 amd64 [vfs] [patch] vfs.bufspace sysctl wideness on amd64 o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT o amd64/132372 amd64 [ata] No disks found (nVidia nForce MCP55 sata control o amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe f amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128810 amd64 AMD 64 port installation o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128686 amd64 [ata] can't detect SATA Disk on 8.0-Current with NF550 o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails o amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 92 problems total. From tinderbox at freebsd.org Thu Jul 30 20:35:07 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jul 30 20:35:25 2009 Subject: [releng_7 tinderbox] failure on amd64/amd64 Message-ID: <20090730203503.ECAFC1B5060@freebsd-stable.sentex.ca> TB --- 2009-07-30 18:59:06 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-07-30 18:59:06 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2009-07-30 18:59:06 - cleaning the object tree TB --- 2009-07-30 18:59:36 - cvsupping the source tree TB --- 2009-07-30 18:59:36 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2009-07-30 18:59:43 - building world TB --- 2009-07-30 18:59:43 - MAKEOBJDIRPREFIX=/obj TB --- 2009-07-30 18:59:43 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-07-30 18:59:43 - TARGET=amd64 TB --- 2009-07-30 18:59:43 - TARGET_ARCH=amd64 TB --- 2009-07-30 18:59:43 - TZ=UTC TB --- 2009-07-30 18:59:43 - __MAKE_CONF=/dev/null TB --- 2009-07-30 18:59:43 - cd /src TB --- 2009-07-30 18:59:43 - /usr/bin/make -B buildworld >>> World build started on Thu Jul 30 18:59:44 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Jul 30 20:30:21 UTC 2009 TB --- 2009-07-30 20:30:21 - generating LINT kernel config TB --- 2009-07-30 20:30:21 - cd /src/sys/amd64/conf TB --- 2009-07-30 20:30:21 - /usr/bin/make -B LINT TB --- 2009-07-30 20:30:21 - building LINT kernel TB --- 2009-07-30 20:30:21 - MAKEOBJDIRPREFIX=/obj TB --- 2009-07-30 20:30:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-07-30 20:30:21 - TARGET=amd64 TB --- 2009-07-30 20:30:21 - TARGET_ARCH=amd64 TB --- 2009-07-30 20:30:21 - TZ=UTC TB --- 2009-07-30 20:30:21 - __MAKE_CONF=/dev/null TB --- 2009-07-30 20:30:21 - cd /src TB --- 2009-07-30 20:30:21 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jul 30 20:30:21 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/an/if_an_isa.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/an/if_an_pccard.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/an/if_an_pci.c awk -f /src/sys/tools/makeobjops.awk /src/sys/dev/ata/ata_if.m -c ; cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue ata_if.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/ata/ata-all.c /src/sys/dev/ata/ata-all.c: In function 'ata_device_ioctl': /src/sys/dev/ata/ata-all.c:454: error: request for member 'max_iosize' in something not a structure or union /src/sys/dev/ata/ata-all.c:454: error: request for member 'max_iosize' in something not a structure or union *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-07-30 20:35:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-07-30 20:35:03 - ERROR: failed to build lint kernel TB --- 2009-07-30 20:35:03 - 4754.02 user 554.41 system 5757.06 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full From david at vizion2000.net Fri Jul 31 08:36:56 2009 From: david at vizion2000.net (David Southwell) Date: Fri Jul 31 08:37:02 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 Message-ID: <200907310919.57775.david@vizion2000.net> 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 This system uses an intel quad core processor.on an Asus p5QL-E Mobo. Can someone please advise me on the best settings to take maximum advantage of the quad cores especially for compiling. Thanks David From killing at multiplay.co.uk Fri Jul 31 08:55:09 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Fri Jul 31 08:55:15 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 References: <200907310919.57775.david@vizion2000.net> Message-ID: <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> Look at the -j XX option to make is the key things really. Regards Steve ----- Original Message ----- From: "David Southwell" > 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > This system uses an intel quad core processor.on an Asus p5QL-E Mobo. > > Can someone please advise me on the best settings to take maximum advantage of > the quad cores especially for compiling. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From david at vizion2000.net Fri Jul 31 12:33:57 2009 From: david at vizion2000.net (David Southwell) Date: Fri Jul 31 12:34:04 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 In-Reply-To: <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> References: <200907310919.57775.david@vizion2000.net> <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> Message-ID: <200907311333.53815.david@vizion2000.net> > > > 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > > This system uses an intel quad core processor.on an Asus p5QL-E Mobo. > > > > Can someone please advise me on the best settings to take maximum > > advantage of the quad cores especially for compiling. > > Look at the -j XX option to make is the key things really. > > Regards > Steve > > ----- Original Message ----- > From: "David Southwell" Thanks Steve I have two further questions: 1. What is a reasonable setting for a quad core 2. Whatever the setting for xx is would it be appropriate to use: portupgrade -a -m --j xx ?? Thanks in advance David From killing at multiplay.co.uk Fri Jul 31 12:40:41 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Fri Jul 31 12:40:48 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 References: <200907310919.57775.david@vizion2000.net> <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> <200907311333.53815.david@vizion2000.net> Message-ID: <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> ----- Original Message ----- From: "David Southwell" > Thanks Steve > > I have two further questions: > 1. What is a reasonable setting for a quad core > 2. Whatever the setting for xx is would it be appropriate to use: > portupgrade -a -m --j xx > ?? #1 It depends on the code we have found but 4+ #2 Not sure portupgrade in 7.2 supports -j properly yet, I know there's been some recent work in that area not sure who far its got. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From rsmith at xs4all.nl Fri Jul 31 13:05:02 2009 From: rsmith at xs4all.nl (Roland Smith) Date: Fri Jul 31 13:05:09 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 In-Reply-To: <200907311333.53815.david@vizion2000.net> References: <200907310919.57775.david@vizion2000.net> <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> <200907311333.53815.david@vizion2000.net> Message-ID: <20090731124619.GB65912@slackbox.xs4all.nl> On Fri, Jul 31, 2009 at 01:33:53PM +0100, David Southwell wrote: > > > > > > 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 > > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > This system uses an intel quad core processor.on an Asus p5QL-E Mobo. > > > > > > Can someone please advise me on the best settings to take maximum > > > advantage of the quad cores especially for compiling. > > > > > Look at the -j XX option to make is the key things really. > > > > Regards > > Steve > > > > ----- Original Message ----- > > From: "David Southwell" > > Thanks Steve > > I have two further questions: > 1. What is a reasonable setting for a quad core For a quad core you can use up to '-j 8'. > 2. Whatever the setting for xx is would it be appropriate to use: > portupgrade -a -m --j xx The ports system automatically does parallel builds on an SMP system, unless the port in question is marked unsuitable with MAKE_JOBS_UNSAFE. For a quad core '-j 4' will be used. See /usr/ports/Mk/bsd.port.mk Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20090731/c1778b88/attachment.pgp From schulra at earlham.edu Fri Jul 31 13:16:12 2009 From: schulra at earlham.edu (Randy Schultz) Date: Fri Jul 31 13:16:18 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 In-Reply-To: <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> References: <200907310919.57775.david@vizion2000.net> <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> <200907311333.53815.david@vizion2000.net> <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> Message-ID: On Fri, 31 Jul 2009, Steven Hartland spaketh thusly: -} -}#1 It depends on the code we have found but 4+ -}#2 Not sure portupgrade in 7.2 supports -j properly yet, I know there's -}been some recent work in that area not sure who far its got. Also, pls note that /usr/src/UPDATING advises against the -j option when compiling the system sources. -- Randy (schulra@earlham.edu) 765.983.1283 <*> Love with your heart, think with your head; not the other way around. From killing at multiplay.co.uk Fri Jul 31 14:04:48 2009 From: killing at multiplay.co.uk (Steven Hartland) Date: Fri Jul 31 14:04:55 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 References: <200907310919.57775.david@vizion2000.net><0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk><200907311333.53815.david@vizion2000.net><1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> Message-ID: ----- Original Message ----- From: "Randy Schultz" > -}#1 It depends on the code we have found but 4+ > -}#2 Not sure portupgrade in 7.2 supports -j properly yet, I know there's > -}been some recent work in that area not sure who far its got. > > Also, pls note that /usr/src/UPDATING advises against the -j option when > compiling the system sources. Can't say I've ever had issues compiling system sources and we use -j 32 on a dual quad with HT so 16 cores. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From dougb at FreeBSD.org Fri Jul 31 19:23:37 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Jul 31 19:23:43 2009 Subject: Taking full advantage of Intel Quad Core with Freebsd 7.2p2 In-Reply-To: <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> References: <200907310919.57775.david@vizion2000.net> <0C3FFA484EC8423AB26C13C6737C8533@multiplay.co.uk> <200907311333.53815.david@vizion2000.net> <1518B86CFB8242F8B605034460287EB1@multiplay.co.uk> Message-ID: <4A733E72.5040607@FreeBSD.org> Steven Hartland wrote: > #2 Not sure portupgrade in 7.2 supports -j properly yet, I know there's > been some recent work in that area not sure who far its got. The ports infrastructure already supports this, but you have to add the following option to your /etc/make.conf file: FORCE_MAKE_JOBS= true You will occasionally run into ports that don't build successfully with this option, so you can overcome that per port by doing 'make -DMAKE_JOBS_UNSAFE' for that port. It would be a big help to the community if you could report any ports you run into that problem with so that they can be marked in the Makefile. For building the world if you want the system to be responsive while you're building a good rule of thumb for -j is " -1". If you want maximum speed and don't care about using the system while it builds then " +1" will get it done a little faster. Values much higher than that are not likely to increase speed much, mostly due to the fact that you'll get IO-bound sooner than later. hth, Doug -- This .signature sanitized for your protection From mw at apathia.net Fri Jul 31 16:50:06 2009 From: mw at apathia.net (Martin W) Date: Sat Aug 1 14:33:35 2009 Subject: amd64/128263: [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 and 16gb ram, crash and dump mem Message-ID: <200907311650.n6VGo5qx068623@freefall.freebsd.org> The following reply was made to PR amd64/128263; it has been noted by GNATS. From: Martin W To: bug-followup@FreeBSD.org, martin.wikesjo@cypoint.se Cc: Subject: Re: amd64/128263: [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 and 16gb ram, crash and dump mem Date: Fri, 31 Jul 2009 18:30:41 +0200 Sorry for the late follow up. Since this has been rated as "serious" and with a "high" priority, yet I have recieved no real feedback I haven't put much effort into reporting anymore. Anyhow, we have been having the same issues with a few more machines now. Random spontaneous crashes. I do suspect faulty hardware, more specifically RAM or CPU. But since the errors I see don't provide me any proof I am unable to convince our hardware vendor, HP, that they are broken. I have ran the HP diagnostics for 7 loops as HP recommends, and it reports no errors. I have also recompiled the kernel on one of these machines with "options PRINTF_BUFR_SIZE=128" to see if the output would be more than just garbage, but it did not help. We will attempt to upgrade one machine to 7.2 next week to see if it will produce better error logs if/when they crash again(or maybe we'll be incredibly lucky and its a software bug that is now fixed). FWIW, these machine are part of a large online gaming platform. It has well over 100 more of these machines with the same hardware and FreeBSD setup. If someone could look into this that would be much appreciated. From joel at FreeBSD.org Fri Jul 31 17:00:12 2009 From: joel at FreeBSD.org (Joel Dahl) Date: Sat Aug 1 14:33:41 2009 Subject: amd64/128263: [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 and 16gb ram, crash and dump mem Message-ID: <200907311700.n6VH0Bhq075551@freefall.freebsd.org> The following reply was made to PR amd64/128263; it has been noted by GNATS. From: Joel Dahl To: bug-followup@FreeBSD.org, martin.wikesjo@cypoint.se Cc: Subject: Re: amd64/128263: [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 and 16gb ram, crash and dump mem Date: Fri, 31 Jul 2009 18:32:05 +0200 For the record: I've chatted with the submitter and with jhb. The panics are due to NMI's and most likely bad RAM. One workaround would be to turn off machdep.panic_on_nmi ... -- Joel