From heeroy at heeroy.no-ip.org Sun Jun 1 04:00:15 2008 From: heeroy at heeroy.no-ip.org (heeroy) Date: Sun Jun 1 04:08:14 2008 Subject: amd64/91195: [ata] FreeBSD 6.0(amd64) and Asus A8R-MVP Message-ID: <200806010400.m5140EmF076617@freefall.freebsd.org> The following reply was made to PR amd64/91195; it has been noted by GNATS. From: heeroy To: bug-followup@FreeBSD.org, heeroy@starlight.twbbs.org, linimon@FreeBSD.org Cc: Subject: Re: amd64/91195: [ata] FreeBSD 6.0(amd64) and Asus A8R-MVP Date: Sun, 01 Jun 2008 11:40:42 +0800 sorry, I can't follow up this bug any more because my friend sold out this mainboard last year. From bugmaster at FreeBSD.org Mon Jun 2 11:06:45 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 2 11:36:16 2008 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200806021106.m52B6it2093086@freefall.freebsd.org> Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number o amd64/124200 amd64 kernel panic on mutex sleepq chain 2 problems total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 [panic] System panic on shutdown when process will not o amd64/76136 amd64 [hang] system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys f amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 f amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/89501 amd64 [install] System crashes on install using ftp on local f amd64/89503 amd64 [boot] Cant Boot Installation Disk o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 f amd64/91492 amd64 [boot] BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati f amd64/94989 amd64 [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled f amd64/102122 amd64 [boot] 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work a amd64/109584 amd64 zdump(8) doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 f amd64/111992 amd64 [boot] BTX failed - HP Laptop dv2315nr f amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/116159 amd64 [panic] Panic while debugging on CURRENT o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/119936 amd64 [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/121439 amd64 [boot] Installation of FreeBSD 7.0 fails: ACPI problem o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/122423 amd64 Port install fails after upgrade o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123562 amd64 [install] FreeBSD amd64 not installs 53 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l f amd64/91195 amd64 [ata] FreeBSD 6.0(amd64) and Asus A8R-MVP f amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o bin/105542 amd64 on amd64, ldd(1) produces bogus output for i386 execut o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot f amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect f amd64/116457 amd64 [install] can't install freebsd on dv9420us f amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car f amd64/116670 amd64 [ata] onboard SATA RAID1 controllers not supported for s amd64/116689 amd64 [request] support for MSI K9MM-V f amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 f amd64/119949 amd64 [install] 6.3-RELEASE install; cannot find packages/IN f amd64/121590 amd64 powerd(8) may not work correctly f amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang o amd64/124134 amd64 The kernel doesn't follow the calling convention in th 23 problems total. From tinderbox at freebsd.org Mon Jun 2 20:39:55 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 2 20:40:03 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080602203952.3AD5B73039@freebsd-current.sentex.ca> TB --- 2008-06-02 18:50:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-02 18:50:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-02 18:50:00 - cleaning the object tree TB --- 2008-06-02 18:50:51 - cvsupping the source tree TB --- 2008-06-02 18:50:51 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-02 18:50:57 - building world (CFLAGS=-O -pipe) TB --- 2008-06-02 18:50:57 - cd /src TB --- 2008-06-02 18:50:57 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 2 18:51:00 UTC 2008 >>> 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 Mon Jun 2 20:31:05 UTC 2008 TB --- 2008-06-02 20:31:05 - generating LINT kernel config TB --- 2008-06-02 20:31:05 - cd /src/sys/amd64/conf TB --- 2008-06-02 20:31:05 - /usr/bin/make -B LINT TB --- 2008-06-02 20:31:05 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-02 20:31:05 - cd /src TB --- 2008-06-02 20:31:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jun 2 20:31:05 UTC 2008 >>> 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 -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nfsserver/nfs_srvsubs.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nfsserver/nfs_syscalls.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nlm/nlm_prot_clnt.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nlm/nlm_prot_impl.c; /src/sys/nlm/nlm_prot_impl.c: In function 'nlm_check_idle': /src/sys/nlm/nlm_prot_impl.c:697: error: 'nlm_global_lock' undeclared (first use in this function) /src/sys/nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-02 20:39:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-02 20:39:51 - ERROR: failed to build lint kernel TB --- 2008-06-02 20:39:51 - tinderbox aborted TB --- 4777.43 user 610.84 system 6591.74 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Tue Jun 3 02:15:00 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jun 3 02:15:14 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080603021456.AB52973039@freebsd-current.sentex.ca> TB --- 2008-06-03 00:25:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-03 00:25:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-03 00:25:00 - cleaning the object tree TB --- 2008-06-03 00:25:46 - cvsupping the source tree TB --- 2008-06-03 00:25:46 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-03 00:25:52 - building world (CFLAGS=-O -pipe) TB --- 2008-06-03 00:25:52 - cd /src TB --- 2008-06-03 00:25:52 - /usr/bin/make -B buildworld >>> World build started on Tue Jun 3 00:25:54 UTC 2008 >>> 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 Tue Jun 3 02:06:14 UTC 2008 TB --- 2008-06-03 02:06:14 - generating LINT kernel config TB --- 2008-06-03 02:06:14 - cd /src/sys/amd64/conf TB --- 2008-06-03 02:06:14 - /usr/bin/make -B LINT TB --- 2008-06-03 02:06:14 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-03 02:06:14 - cd /src TB --- 2008-06-03 02:06:14 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jun 3 02:06:14 UTC 2008 >>> 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 -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nfsserver/nfs_srvsubs.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nfsserver/nfs_syscalls.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nlm/nlm_prot_clnt.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nlm/nlm_prot_impl.c; /src/sys/nlm/nlm_prot_impl.c: In function 'nlm_check_idle': /src/sys/nlm/nlm_prot_impl.c:697: error: 'nlm_global_lock' undeclared (first use in this function) /src/sys/nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-03 02:14:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-03 02:14:56 - ERROR: failed to build lint kernel TB --- 2008-06-03 02:14:56 - tinderbox aborted TB --- 4773.32 user 613.60 system 6596.18 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From linimon at FreeBSD.org Tue Jun 3 02:31:58 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Tue Jun 3 02:36:50 2008 Subject: amd64/91195: [ata] FreeBSD 6.0(amd64) and Asus A8R-MVP Message-ID: <200806030231.m532VvJu084668@freefall.freebsd.org> Synopsis: [ata] FreeBSD 6.0(amd64) and Asus A8R-MVP State-Changed-From-To: feedback->closed State-Changed-By: linimon State-Changed-When: Tue Jun 3 02:31:10 UTC 2008 State-Changed-Why: Submitter no longer has this hardware, and this PR is about a version of FreeBSD that is no longer supported, so nothing to do but close this. http://www.freebsd.org/cgi/query-pr.cgi?pr=91195 From tinderbox at freebsd.org Tue Jun 3 07:52:20 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jun 3 07:52:32 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080603075217.31FE473039@freebsd-current.sentex.ca> TB --- 2008-06-03 06:00:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-03 06:00:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-03 06:00:00 - cleaning the object tree TB --- 2008-06-03 06:00:41 - cvsupping the source tree TB --- 2008-06-03 06:00:41 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-03 06:00:46 - building world (CFLAGS=-O -pipe) TB --- 2008-06-03 06:00:46 - cd /src TB --- 2008-06-03 06:00:46 - /usr/bin/make -B buildworld >>> World build started on Tue Jun 3 06:00:49 UTC 2008 >>> 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 Tue Jun 3 07:43:09 UTC 2008 TB --- 2008-06-03 07:43:09 - generating LINT kernel config TB --- 2008-06-03 07:43:09 - cd /src/sys/amd64/conf TB --- 2008-06-03 07:43:09 - /usr/bin/make -B LINT TB --- 2008-06-03 07:43:09 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-03 07:43:09 - cd /src TB --- 2008-06-03 07:43:09 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jun 3 07:43:09 UTC 2008 >>> 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 -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nfsserver/nfs_srvsubs.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nfsserver/nfs_syscalls.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nlm/nlm_prot_clnt.c; cc -c -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-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/nlm/nlm_prot_impl.c; /src/sys/nlm/nlm_prot_impl.c: In function 'nlm_check_idle': /src/sys/nlm/nlm_prot_impl.c:697: error: 'nlm_global_lock' undeclared (first use in this function) /src/sys/nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-03 07:52:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-03 07:52:17 - ERROR: failed to build lint kernel TB --- 2008-06-03 07:52:17 - tinderbox aborted TB --- 4781.23 user 612.91 system 6736.79 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Tue Jun 3 08:50:24 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jun 3 08:50:36 2008 Subject: [releng_6 tinderbox] failure on amd64/amd64 Message-ID: <20080603085033.5A2A8241A2@freebsd-legacy.sentex.ca> TB --- 2008-06-03 08:25:39 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:25:39 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2008-06-03 08:25:39 - cleaning the object tree TB --- 2008-06-03 08:26:23 - cvsupping the source tree TB --- 2008-06-03 08:26:23 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2008-06-03 08:26:44 - building world (CFLAGS=-O2 -pipe) TB --- 2008-06-03 08:26:44 - cd /src TB --- 2008-06-03 08:26:44 - /usr/bin/make -B buildworld >>> 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 [...] cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.5"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=9 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I/src/lib/bind/bind /../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/gettimeofday.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.5"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=9 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I/src/lib/bind/bind /../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/mktemp.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.5"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=9 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I/src/lib/bind/bind /../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/putenv.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.5"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=9 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I/src/lib/bind/bind /../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/readv.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.5"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=9 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I/src/lib/bind/bind /../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/setenv.c In file included from /src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/setenv.c:43: /obj/amd64/src/tmp/usr/include/string.h:68: error: conflicting types for 'bcopy' /obj/amd64/src/tmp/usr/include/string.h:68: error: conflicting types for 'bcopy' *** Error code 1 Stop in /src/lib/bind/bind. *** Error code 1 Stop in /src/lib/bind. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-03 08:50:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-03 08:50:33 - ERROR: failed to build world TB --- 2008-06-03 08:50:33 - tinderbox aborted TB --- 1119.02 user 149.53 system 1493.36 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From uwe at laverenz.de Wed Jun 4 03:58:54 2008 From: uwe at laverenz.de (Uwe Laverenz) Date: Wed Jun 4 03:58:58 2008 Subject: amd64 @ vmware esx 3.5? In-Reply-To: <2E85A565F92C62AE50A7C0FC@girgBook.local> References: <2E85A565F92C62AE50A7C0FC@girgBook.local> Message-ID: <20080604034704.GA4368@laverenz.de> On Sat, May 31, 2008 at 12:27:02PM +0200, Palle Girgensohn wrote: > I cannot install FreeBSD 7.0 amd64 on VmWare ESX 3.5. The kernel panics > when trying to read the virtual cd-image that I mount in the VmWare client. > Did anyone else succeed? Yes, I successfully installed several 6.3 and 7.0 machines on ESX 3.x without a problem (amd64 and i386). Uwe From nimnod at eranet.pl Wed Jun 4 15:36:57 2008 From: nimnod at eranet.pl (Nimnod) Date: Wed Jun 4 15:37:08 2008 Subject: amd64 @ vmware esx 3.5? In-Reply-To: <20080604034704.GA4368@laverenz.de> References: <2E85A565F92C62AE50A7C0FC@girgBook.local> <20080604034704.GA4368@laverenz.de> Message-ID: <4846A86D.1070905@eranet.pl> Hi, I have been using 7.0 amd64 under ESX 3.5 for a few weeks without any problems. Do you mount the CD image remotely from a local workstation, or from within the internal ESX storage volume? As far as I recall I tried both ways, but for performance reasons usually stick to the latter. Uwe Laverenz wrote: > On Sat, May 31, 2008 at 12:27:02PM +0200, Palle Girgensohn wrote: > > >> I cannot install FreeBSD 7.0 amd64 on VmWare ESX 3.5. The kernel panics >> when trying to read the virtual cd-image that I mount in the VmWare client. >> Did anyone else succeed? >> > > Yes, I successfully installed several 6.3 and 7.0 machines on ESX 3.x > without a problem (amd64 and i386). > > Uwe > > _______________________________________________ > 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" > > From tinderbox at freebsd.org Fri Jun 6 10:29:28 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Jun 6 10:29:32 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080606102924.D5D1F73039@freebsd-current.sentex.ca> TB --- 2008-06-06 09:45:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-06 09:45:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-06 09:45:00 - cleaning the object tree TB --- 2008-06-06 09:45:58 - cvsupping the source tree TB --- 2008-06-06 09:45:58 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-06 09:46:05 - building world (CFLAGS=-O -pipe) TB --- 2008-06-06 09:46:05 - cd /src TB --- 2008-06-06 09:46:05 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 6 09:46:07 UTC 2008 >>> 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 [...] cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o kill kill.o gzip -cn /src/bin/kill/kill.1 > kill.1.gz ===> bin/ln (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/bin/ln/ln.c cc1: warnings being treated as errors /src/bin/ln/ln.c: In function 'linkit': /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' *** Error code 1 Stop in /src/bin/ln. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-06 10:29:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-06 10:29:24 - ERROR: failed to build world TB --- 2008-06-06 10:29:24 - tinderbox aborted TB --- 1829.73 user 267.45 system 2664.01 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Fri Jun 6 14:34:21 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Jun 6 14:34:33 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080606143415.8A5A573039@freebsd-current.sentex.ca> TB --- 2008-06-06 13:50:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-06 13:50:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-06 13:50:01 - cleaning the object tree TB --- 2008-06-06 13:50:26 - cvsupping the source tree TB --- 2008-06-06 13:50:26 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-06 13:50:32 - building world (CFLAGS=-O -pipe) TB --- 2008-06-06 13:50:32 - cd /src TB --- 2008-06-06 13:50:32 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 6 13:50:37 UTC 2008 >>> 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 [...] cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o kill kill.o gzip -cn /src/bin/kill/kill.1 > kill.1.gz ===> bin/ln (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/bin/ln/ln.c cc1: warnings being treated as errors /src/bin/ln/ln.c: In function 'linkit': /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' *** Error code 1 Stop in /src/bin/ln. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-06 14:34:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-06 14:34:15 - ERROR: failed to build world TB --- 2008-06-06 14:34:15 - tinderbox aborted TB --- 1830.76 user 262.62 system 2654.01 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Fri Jun 6 18:38:43 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Jun 6 18:38:46 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080606183841.33EF973039@freebsd-current.sentex.ca> TB --- 2008-06-06 17:55:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-06 17:55:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-06 17:55:00 - cleaning the object tree TB --- 2008-06-06 17:55:21 - cvsupping the source tree TB --- 2008-06-06 17:55:21 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-06 17:55:31 - building world (CFLAGS=-O -pipe) TB --- 2008-06-06 17:55:31 - cd /src TB --- 2008-06-06 17:55:31 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 6 17:55:34 UTC 2008 >>> 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 [...] cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o kill kill.o gzip -cn /src/bin/kill/kill.1 > kill.1.gz ===> bin/ln (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/bin/ln/ln.c cc1: warnings being treated as errors /src/bin/ln/ln.c: In function 'linkit': /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' *** Error code 1 Stop in /src/bin/ln. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-06 18:38:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-06 18:38:40 - ERROR: failed to build world TB --- 2008-06-06 18:38:40 - tinderbox aborted TB --- 1828.39 user 265.26 system 2620.66 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Fri Jun 6 23:19:12 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Fri Jun 6 23:19:19 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080606231909.11D8A73039@freebsd-current.sentex.ca> TB --- 2008-06-06 22:35:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-06 22:35:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-06 22:35:00 - cleaning the object tree TB --- 2008-06-06 22:35:20 - cvsupping the source tree TB --- 2008-06-06 22:35:20 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-06 22:35:29 - building world (CFLAGS=-O -pipe) TB --- 2008-06-06 22:35:29 - cd /src TB --- 2008-06-06 22:35:29 - /usr/bin/make -B buildworld >>> World build started on Fri Jun 6 22:35:33 UTC 2008 >>> 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 [...] cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o kill kill.o gzip -cn /src/bin/kill/kill.1 > kill.1.gz ===> bin/ln (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/bin/ln/ln.c cc1: warnings being treated as errors /src/bin/ln/ln.c: In function 'linkit': /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' *** Error code 1 Stop in /src/bin/ln. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-06 23:19:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-06 23:19:08 - ERROR: failed to build world TB --- 2008-06-06 23:19:08 - tinderbox aborted TB --- 1828.85 user 264.09 system 2648.15 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From dfeustel at mindspring.com Sat Jun 7 03:20:14 2008 From: dfeustel at mindspring.com (dfeustel@mindspring.com) Date: Sat Jun 7 03:20:18 2008 Subject: FreeBSD 7.0 Mount Strangeness Message-ID: <20080607032014.0521B8FC1A@mx1.freebsd.org> I have encountere what seems to be strangeness in the way mount works when mounting msdos file systems on usb mass storage devices. I have a 14-in-one usb reader connected to my computer running AMD 64-bit FreeBSD 7.0 release. At boot, there are four special files in /dev for the usb devices: /dev/da[0-3]. All attempts to mount an msdos file system using the command "mount -t msdosfs /dev/daNs1 /mnt" fail with the message "no such file or directory". Checking /dev, there are no special files of the form daNs1. If I then do "mount -t msdosfs /dev/daN" I get the message "invalid argument", BUT there is now in the /dev directory an entry daNs1, and the next "mount -t /dev/daNs1 /mnt" command succeeds :-). This behavior is repeated for each mount of an msdos file system on a previously unused device socket on the usb reader. The newly created devices remain after they are unmounted, so this problem goes away until reboot, at which time the device files of form daNs1 are deleted. I have not found any FreeBSD documentation of this behavior yet. Is this behavior known and expected? (I'm a FreeBSD newbie.) Thanks, Dave Feustel From tinderbox at freebsd.org Sat Jun 7 03:59:19 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sat Jun 7 03:59:32 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080607035916.8BA7E73039@freebsd-current.sentex.ca> TB --- 2008-06-07 03:15:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-07 03:15:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-07 03:15:00 - cleaning the object tree TB --- 2008-06-07 03:15:27 - cvsupping the source tree TB --- 2008-06-07 03:15:27 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-07 03:15:37 - building world (CFLAGS=-O -pipe) TB --- 2008-06-07 03:15:37 - cd /src TB --- 2008-06-07 03:15:37 - /usr/bin/make -B buildworld >>> World build started on Sat Jun 7 03:15:40 UTC 2008 >>> 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 [...] cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o kill kill.o gzip -cn /src/bin/kill/kill.1 > kill.1.gz ===> bin/ln (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/bin/ln/ln.c cc1: warnings being treated as errors /src/bin/ln/ln.c: In function 'linkit': /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' *** Error code 1 Stop in /src/bin/ln. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-07 03:59:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-07 03:59:16 - ERROR: failed to build world TB --- 2008-06-07 03:59:16 - tinderbox aborted TB --- 1829.10 user 264.66 system 2655.60 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Sat Jun 7 08:47:25 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sat Jun 7 08:47:33 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080607084722.4989773039@freebsd-current.sentex.ca> TB --- 2008-06-07 08:00:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-07 08:00:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-07 08:00:00 - cleaning the object tree TB --- 2008-06-07 08:00:24 - cvsupping the source tree TB --- 2008-06-07 08:00:24 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-07 08:00:34 - building world (CFLAGS=-O -pipe) TB --- 2008-06-07 08:00:34 - cd /src TB --- 2008-06-07 08:00:34 - /usr/bin/make -B buildworld >>> World build started on Sat Jun 7 08:00:36 UTC 2008 >>> 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 [...] cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o kill kill.o gzip -cn /src/bin/kill/kill.1 > kill.1.gz ===> bin/ln (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/bin/ln/ln.c cc1: warnings being treated as errors /src/bin/ln/ln.c: In function 'linkit': /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' /src/bin/ln/ln.c:236: warning: field precision should have type 'int', but argument 4 has type 'long int' *** Error code 1 Stop in /src/bin/ln. *** Error code 1 Stop in /src/bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-07 08:47:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-07 08:47:22 - ERROR: failed to build world TB --- 2008-06-07 08:47:22 - tinderbox aborted TB --- 1835.66 user 267.62 system 2841.32 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From jhs at berklix.org Sat Jun 7 12:20:21 2008 From: jhs at berklix.org (Julian Stacey) Date: Sat Jun 7 12:20:26 2008 Subject: FreeBSD 7.0 Mount Strangeness In-Reply-To: Your message "Sat, 07 Jun 2008 03:20:13 -0000." <20080607032014.0521B8FC1A@mx1.freebsd.org> Message-ID: <200806071220.m57CKQ6L034768@fire.js.berklix.net> Reference: > From: dfeustel@mindspring.com > Date: Sat, 7 Jun 2008 03:20:13 +0000 (UTC) > Message-id: <20080607032014.0521B8FC1A@mx1.freebsd.org> dfeustel@mindspring.com wrote: > I have encountere what seems to be strangeness in the way mount works > when mounting msdos file systems on usb mass storage devices. I have a > 14-in-one usb reader connected to my computer running AMD 64-bit FreeBSD > 7.0 release. At boot, there are four special files in /dev for the usb > devices: /dev/da[0-3]. All attempts to mount an msdos file system using > the command "mount -t msdosfs /dev/daNs1 /mnt" fail with the message "no > such file or directory". Checking /dev, there are no special files of > the form daNs1. If I then do "mount -t msdosfs /dev/daN" I get the > message "invalid argument", BUT there is now in the /dev directory an > entry daNs1, and the next "mount -t /dev/daNs1 /mnt" command succeeds > :-). This behavior is repeated for each mount of an msdos file system > on a previously unused device socket on the usb reader. The newly > created devices remain after they are unmounted, so this problem goes > away until reboot, at which time the device files of form daNs1 are > deleted. > > I have not found any FreeBSD documentation of this behavior yet. > Is this behavior known and expected? (I'm a FreeBSD newbie.) Behaviour is known. Same on 6.2 as well. Both on i386 & amd64. In my 6 usbd.conf & 7 devd.conf I have dummy reads to first trigger creation of extra devices. > > Thanks, > Dave Feustel > _______________________________________________ > 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" > Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail just Ascii plain text. HTML & Base64 text are spam. From dfeustel at mindspring.com Sat Jun 7 16:09:15 2008 From: dfeustel at mindspring.com (dfeustel@mindspring.com) Date: Sat Jun 7 16:09:19 2008 Subject: FreeBSD 7.0 Suddenly Dead mouse Message-ID: <20080607160915.2AEFB8FC17@mx1.freebsd.org> My optical mouse has suddenly died for the 2nd time in both kde and X on a new computer running 64-bit AMD FreeBSD 7.0. This is the second time this mouse has died this way (last time was when I was using the mouse on a different AMD 64-bit computer running X/kde onOpenBSD). Cycling power and rebooting the computer does not revive the mouse. Assuming (dangerous, I know :-) ) that the mouse is not broken, where in the X code might the mouse be 'turned off' and how, (if that has been done) would I turn it back on? Also, is there a way to simulate the mouse commands using the keyboard when the mouse becomes catatonic? I hate to have to keep using ctl-alt-bksp to abort X. Thanks, Dave Feustel From gpalmer at freebsd.org Sat Jun 7 17:20:59 2008 From: gpalmer at freebsd.org (Gary Palmer) Date: Sat Jun 7 17:21:05 2008 Subject: FreeBSD 7.0 Suddenly Dead mouse In-Reply-To: <20080607160915.2AEFB8FC17@mx1.freebsd.org> References: <20080607160915.2AEFB8FC17@mx1.freebsd.org> Message-ID: <20080607171807.GA998@in-addr.com> On Sat, Jun 07, 2008 at 04:09:15PM +0000, dfeustel@mindspring.com wrote: > My optical mouse has suddenly died for the 2nd time in both kde and X on > a new computer running 64-bit AMD FreeBSD 7.0. This is the second time > this mouse has died this way (last time was when I was using the mouse > on a different AMD 64-bit computer running X/kde onOpenBSD). Cycling > power and rebooting the computer does not revive the mouse. > > Assuming (dangerous, I know :-) ) that the mouse is not broken, where in > the X code might the mouse be 'turned off' and how, (if that has been > done) would I turn it back on? > > Also, is there a way to simulate the mouse commands using the keyboard > when the mouse becomes catatonic? I hate to have to keep using > ctl-alt-bksp to abort X. I cannot answer the "turned off" question, but if you have a keyboard with a numlock key and a numeric keypad, pressing SHIFT-NUMLOCK will turn the keypad into a low quality mouse. 8 moves the pointer up, 2 moves it down, etc. Pressing SHIFT-NUMLOCK again disables the feature. At least on my system, the system speaker beeps when you toggle the feature. Regards, Gary From dfeustel at mindspring.com Sat Jun 7 17:43:04 2008 From: dfeustel at mindspring.com (dfeustel@mindspring.com) Date: Sat Jun 7 17:43:07 2008 Subject: FreeBSD 7.0 Suddenly Dead mouse In-Reply-To: <20080607171807.GA998@in-addr.com> Message-ID: <20080607174303.CC1A08FC13@mx1.freebsd.org> On Sat, Jun 07, 2008 at 01:18:07PM -0400, Gary Palmer wrote: > On Sat, Jun 07, 2008 at 04:09:15PM +0000, dfeustel@mindspring.com wrote: > > My optical mouse has suddenly died for the 2nd time in both kde and X on > > a new computer running 64-bit AMD FreeBSD 7.0. This is the second time > > this mouse has died this way (last time was when I was using the mouse > > on a different AMD 64-bit computer running X/kde onOpenBSD). Cycling > > power and rebooting the computer does not revive the mouse. > > > > Assuming (dangerous, I know :-) ) that the mouse is not broken, where in > > the X code might the mouse be 'turned off' and how, (if that has been > > done) would I turn it back on? > > > > Also, is there a way to simulate the mouse commands using the keyboard > > when the mouse becomes catatonic? I hate to have to keep using > > ctl-alt-bksp to abort X. > > I cannot answer the "turned off" question, but if you have a keyboard > with a numlock key and a numeric keypad, pressing SHIFT-NUMLOCK > will turn the keypad into a low quality mouse. 8 moves the pointer up, > 2 moves it down, etc. Pressing SHIFT-NUMLOCK again disables the feature. > > At least on my system, the system speaker beeps when you toggle > the feature. > > Regards, > > Gary Thanks for this info! It works. Is there also a way to simulate clicking the mouse buttons? From gpalmer at freebsd.org Sat Jun 7 17:50:09 2008 From: gpalmer at freebsd.org (Gary Palmer) Date: Sat Jun 7 17:50:11 2008 Subject: FreeBSD 7.0 Suddenly Dead mouse In-Reply-To: <20080607174303.9F9278FC12@mx1.freebsd.org> References: <20080607171807.GA998@in-addr.com> <20080607174303.9F9278FC12@mx1.freebsd.org> Message-ID: <20080607175004.GB998@in-addr.com> On Sat, Jun 07, 2008 at 05:43:03PM +0000, dfeustel@mindspring.com wrote: > On Sat, Jun 07, 2008 at 01:18:07PM -0400, Gary Palmer wrote: > > On Sat, Jun 07, 2008 at 04:09:15PM +0000, dfeustel@mindspring.com wrote: > > > My optical mouse has suddenly died for the 2nd time in both kde and X on > > > a new computer running 64-bit AMD FreeBSD 7.0. This is the second time > > > this mouse has died this way (last time was when I was using the mouse > > > on a different AMD 64-bit computer running X/kde onOpenBSD). Cycling > > > power and rebooting the computer does not revive the mouse. > > > > > > Assuming (dangerous, I know :-) ) that the mouse is not broken, where in > > > the X code might the mouse be 'turned off' and how, (if that has been > > > done) would I turn it back on? > > > > > > Also, is there a way to simulate the mouse commands using the keyboard > > > when the mouse becomes catatonic? I hate to have to keep using > > > ctl-alt-bksp to abort X. > > > > I cannot answer the "turned off" question, but if you have a keyboard > > with a numlock key and a numeric keypad, pressing SHIFT-NUMLOCK > > will turn the keypad into a low quality mouse. 8 moves the pointer up, > > 2 moves it down, etc. Pressing SHIFT-NUMLOCK again disables the feature. > > > > At least on my system, the system speaker beeps when you toggle > > the feature. > > > > Regards, > > > > Gary > > Thanks for this info! It works. Is there also a way to simulate clicking the > mouse buttons? 5 is left click. 0 is left-click and hold. * changes the 5 to be middle click. / changes the 5 back to left click. - changes the 5 to be right click (at least on my setup, YMMV) Regards, Gary From dfeustel at mindspring.com Sat Jun 7 18:04:17 2008 From: dfeustel at mindspring.com (dfeustel@mindspring.com) Date: Sat Jun 7 18:04:23 2008 Subject: FreeBSD 7.0 Suddenly Dead mouse In-Reply-To: <20080607175004.GB998@in-addr.com> Message-ID: <20080607180417.6187D8FC15@mx1.freebsd.org> On Sat, Jun 07, 2008 at 01:50:04PM -0400, Gary Palmer wrote: > On Sat, Jun 07, 2008 at 05:43:03PM +0000, dfeustel@mindspring.com wrote: > > On Sat, Jun 07, 2008 at 01:18:07PM -0400, Gary Palmer wrote: > > > On Sat, Jun 07, 2008 at 04:09:15PM +0000, dfeustel@mindspring.com wrote: > > > > My optical mouse has suddenly died for the 2nd time in both kde and X on > > > > a new computer running 64-bit AMD FreeBSD 7.0. This is the second time > > > > this mouse has died this way (last time was when I was using the mouse > > > > on a different AMD 64-bit computer running X/kde onOpenBSD). Cycling > > > > power and rebooting the computer does not revive the mouse. > > > > > > > > Assuming (dangerous, I know :-) ) that the mouse is not broken, where in > > > > the X code might the mouse be 'turned off' and how, (if that has been > > > > done) would I turn it back on? > > > > > > > > Also, is there a way to simulate the mouse commands using the keyboard > > > > when the mouse becomes catatonic? I hate to have to keep using > > > > ctl-alt-bksp to abort X. > > > > > > I cannot answer the "turned off" question, but if you have a keyboard > > > with a numlock key and a numeric keypad, pressing SHIFT-NUMLOCK > > > will turn the keypad into a low quality mouse. 8 moves the pointer up, > > > 2 moves it down, etc. Pressing SHIFT-NUMLOCK again disables the feature. > > > > > > At least on my system, the system speaker beeps when you toggle > > > the feature. > > > > > > Regards, > > > > > > Gary > > > > Thanks for this info! It works. Is there also a way to simulate clicking the > > mouse buttons? > > 5 is left click. 0 is left-click and hold. * changes the 5 to be middle > click. / changes the 5 back to left click. - changes the 5 to be right > click (at least on my setup, YMMV) > > Regards, > > Gary Thanks Very Much! This will be a handy hack for me! From bugmaster at FreeBSD.org Mon Jun 9 11:06:51 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 9 11:27:13 2008 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200806091106.m59B6oUM070672@freefall.freebsd.org> Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 [panic] System panic on shutdown when process will not o amd64/76136 amd64 [hang] system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys f amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 f amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/89501 amd64 [install] System crashes on install using ftp on local f amd64/89503 amd64 [boot] Cant Boot Installation Disk o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 f amd64/91492 amd64 [boot] BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati f amd64/94989 amd64 [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled f amd64/102122 amd64 [boot] 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work a amd64/109584 amd64 zdump(8) doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 f amd64/111992 amd64 [boot] BTX failed - HP Laptop dv2315nr f amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/116159 amd64 [panic] Panic while debugging on CURRENT o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/119936 amd64 [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/121439 amd64 [boot] Installation of FreeBSD 7.0 fails: ACPI problem o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/122423 amd64 Port install fails after upgrade o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/124200 amd64 [panic] kernel panic on mutex sleepq chain 54 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l f amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o bin/105542 amd64 on amd64, ldd(1) produces bogus output for i386 execut o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot f amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect f amd64/116457 amd64 [install] can't install freebsd on dv9420us f amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car f amd64/116670 amd64 [ata] onboard SATA RAID1 controllers not supported for s amd64/116689 amd64 [request] support for MSI K9MM-V f amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 f amd64/119949 amd64 [install] 6.3-RELEASE install; cannot find packages/IN f amd64/121590 amd64 powerd(8) may not work correctly f amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent 22 problems total. From tinderbox at freebsd.org Mon Jun 9 12:55:50 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 9 12:55:55 2008 Subject: [releng_6 tinderbox] failure on amd64/amd64 Message-ID: <20080609125600.3EFBC241A2@freebsd-legacy.sentex.ca> TB --- 2008-06-09 11:22:52 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-09 11:22:52 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2008-06-09 11:22:52 - cleaning the object tree TB --- 2008-06-09 11:23:29 - cvsupping the source tree TB --- 2008-06-09 11:23:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2008-06-09 11:23:36 - building world (CFLAGS=-O2 -pipe) TB --- 2008-06-09 11:23:36 - cd /src TB --- 2008-06-09 11:23:36 - /usr/bin/make -B buildworld >>> 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 TB --- 2008-06-09 12:40:20 - generating LINT kernel config TB --- 2008-06-09 12:40:20 - cd /src/sys/amd64/conf TB --- 2008-06-09 12:40:20 - /usr/bin/make -B LINT TB --- 2008-06-09 12:40:20 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-06-09 12:40:20 - cd /src TB --- 2008-06-09 12:40:20 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jun 9 12:40:20 UTC 2008 >>> 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 [...] objcopy --strip-debug nfsclient.ko ===> nfslockd (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/nfslockd/../../nlm/nlm_prot_clnt.c cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c: In function `nlm_check_idle': /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: `nlm_global_lock' undeclared (first use in this function) /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /src/sys/modules/nfslockd. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-09 12:56:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-09 12:56:00 - ERROR: failed to build lint kernel TB --- 2008-06-09 12:56:00 - tinderbox aborted TB --- 4486.69 user 532.27 system 5587.97 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From yrletov at mir-aero.ru Mon Jun 9 13:20:01 2008 From: yrletov at mir-aero.ru (yriy) Date: Mon Jun 9 13:43:43 2008 Subject: amd64/124416: cant build kernel Message-ID: <200806091312.m59DCvuh066464@www.freebsd.org> >Number: 124416 >Category: amd64 >Synopsis: cant build kernel >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 09 13:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: yriy >Release: 7.0 cvsup to releng >Organization: magy class >Environment: FreeBSD dao 7.0-Release FreeBSD 7-0-Release #0: Sun Feb 24 10:35:36 UTC 2008 root@driscoll.cse.boofalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: when build kernel after buildworld get /usr/src/sys/nlm/nlm_prot_impl.c:697:error:'nlm_global_lock' undeclared (first use in this function) /usr/src/sys/nlm/nlm_prot_impl.c:697:error:(each undeclared identifier is reported only once /usr/src/sys/nlm/nlm_prot_impl.c:697:error: for each function it aappears in.) *** Error code 1 and stop in /usr/src. >How-To-Repeat: cvsup 7.0-release amd64 to releng, make buildworld, make buildkernel KERNCONF=GENERIC then error appear >Fix: >Release-Note: >Audit-Trail: >Unformatted: From kris at FreeBSD.org Mon Jun 9 14:12:20 2008 From: kris at FreeBSD.org (kris@FreeBSD.org) Date: Mon Jun 9 14:12:31 2008 Subject: amd64/124416: cant build kernel Message-ID: <200806091412.m59ECJD1093322@freefall.freebsd.org> Synopsis: cant build kernel State-Changed-From-To: open->closed State-Changed-By: kris State-Changed-When: Mon Jun 9 14:11:56 UTC 2008 State-Changed-Why: Believed to be fixed already. If not, please follow up on freebsd-stable@FreeBSD.org. http://www.freebsd.org/cgi/query-pr.cgi?pr=124416 From kris at FreeBSD.org Mon Jun 9 14:20:04 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Mon Jun 9 14:20:12 2008 Subject: amd64/124416: cant build kernel Message-ID: <200806091420.m59EK3YE094737@freefall.freebsd.org> The following reply was made to PR amd64/124416; it has been noted by GNATS. From: Kris Kennaway To: yriy Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/124416: cant build kernel Date: Mon, 09 Jun 2008 16:11:50 +0200 yriy wrote: > cvsup 7.0-release amd64 to releng, make buildworld, make buildkernel KERNCONF=GENERIC then error appear Should be fixed already. Usually it is not worth opening a PR about build failures; ask on the mailing list or just wait an hour or two and retry. Kris From joe at zircon.seattle.wa.us Mon Jun 9 22:50:04 2008 From: joe at zircon.seattle.wa.us (Joe Kelsey) Date: Mon Jun 9 22:57:35 2008 Subject: amd64/124432: 7.0-STABLE panic: invalbuf: dirty bufs Message-ID: <20080609221823.1797.qmail@zircon.seattle.wa.us> >Number: 124432 >Category: amd64 >Synopsis: 7.0-STABLE panic: invalbuf: dirty bufs >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 09 22:50:04 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Joe Kelsey >Release: FreeBSD 7.0-STABLE amd64 >Organization: Joseph M. Kelsey >Environment: System: FreeBSD zircon.zircon.seattle.wa.us 7.0-STABLE FreeBSD 7.0-STABLE #18: Sun May 25 15:43:06 PDT 2008 root@zircon.zircon.seattle.wa.us:/usr/obj/usr/src/sys/ZIRCON amd64 >Description: Kernel panic: invalbuf: dirty bufs Seems to happen under moderate disk activity. It happened twice so far during my attempt to move several directories from one disk to another. I do not see any real issue with the disk traffic, except that I am moving from a gmirror device to a normal device, on different ata attach points. The gmirror is on a fast SATA (300) interface and the other device is on a slower (150) SATA interface. I have 4 SATA interfaces on this system, the two standard ata interfaces on the mother board and two SATA interfaces to attach my real SATA disks. So, the gmirror gets the fast one and everyone else gets the slower one. I have vmcore if it is of interest to anyone. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From benjsc at FreeBSD.org Tue Jun 10 02:16:45 2008 From: benjsc at FreeBSD.org (benjsc@FreeBSD.org) Date: Tue Jun 10 02:34:16 2008 Subject: amd64/124200: [panic] kernel panic on mutex sleepq chain Message-ID: <200806100216.m5A2Gide038897@freefall.freebsd.org> Synopsis: [panic] kernel panic on mutex sleepq chain Responsible-Changed-From-To: freebsd-amd64->benjsc Responsible-Changed-By: benjsc Responsible-Changed-When: Tue Jun 10 02:15:53 UTC 2008 Responsible-Changed-Why: Problem currently under investigation by benjsc,attilo,kris, stay tuned! http://www.freebsd.org/cgi/query-pr.cgi?pr=124200 From shinjii at maydias.com Tue Jun 10 13:51:18 2008 From: shinjii at maydias.com (Warren Liddell) Date: Tue Jun 10 13:51:23 2008 Subject: ohci_add_done PANIC Message-ID: <200806101338.m5ADcd2V002743@mail5.tpg.com.au> I have seen many posts and articles floating around that deals with this issue, so id like to know how to get around it, without the need to disable legacy support? amt my only work around is disabling legacy support, unplugging ALL USB devices then FreeBSD not only installs without causing a panic as well as runs, but it detects all the USB devices AFTER boot has been done, how ever X dosent seem to want to recognise it. There other issues, however with having to swap from 1 comp to another running from FreeBSD, i have no ability to paste dmesg or anything like that. ports & world are upto date as of 2 days ago .. however i am unable to configure the kernel, so its using factory defaults that came with 6.3-RELEASE a few mnths ago .. issues with that are related to various options not beign able to determine size. I understand a lot of this is vague, but more information can be provided if needs be. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 270.2.0/1493 - Release Date: 9/06/2008 5:25 PM From sweeney at addr.com Fri Jun 13 01:50:02 2008 From: sweeney at addr.com (Tony Sweeney) Date: Fri Jun 13 02:28:00 2008 Subject: amd64/124538: Kernel panic on install Message-ID: <200806130143.m5D1h0hn095184@www.freebsd.org> >Number: 124538 >Category: amd64 >Synopsis: Kernel panic on install >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 13 01:50:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Tony Sweeney >Release: 7.0 >Organization: Self >Environment: Gigabyte GA-MA78GM-S2H motherboard >Description: Kernel panic on install: uptime 1s >How-To-Repeat: Try to install on GA-MA78GM-S2H motherboard >Fix: n/a >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Fri Jun 13 14:17:18 2008 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Fri Jun 13 14:24:01 2008 Subject: amd64/124538: Kernel panic on install Message-ID: <200806131417.m5DEHI0s077293@freefall.freebsd.org> Synopsis: Kernel panic on install State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Fri Jun 13 14:14:14 UTC 2008 State-Changed-Why: To submitter: could you please give us some more details about the panic you are experiencing? At a minimum, we really need the full panic text (all 15 or so lines) and a few lines from before the panic to try to establish exactly where this is panicing. A good quality digital photo is usually enough unless you have a serial console set up or some other way of capturing an image. Lastly, is this a new system, or has it run a previous version of FreeBSD successfully? Responsible-Changed-From-To: freebsd-amd64->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Fri Jun 13 14:14:14 UTC 2008 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=124538 From tinderbox at freebsd.org Sat Jun 14 12:21:03 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sat Jun 14 12:21:16 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080614122058.AF52373039@freebsd-current.sentex.ca> TB --- 2008-06-14 12:20:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-14 12:20:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-14 12:20:00 - cleaning the object tree TB --- 2008-06-14 12:20:51 - cvsupping the source tree TB --- 2008-06-14 12:20:51 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-14 12:20:58 - building world (CFLAGS=-O -pipe) TB --- 2008-06-14 12:20:58 - cd /src TB --- 2008-06-14 12:20:58 - /usr/bin/make -B buildworld TB --- 2008-06-14 12:20:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-14 12:20:58 - ERROR: failed to build world TB --- 2008-06-14 12:20:58 - tinderbox aborted TB --- 2.32 user 4.49 system 58.40 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From ed at 80386.nl Sat Jun 14 17:48:12 2008 From: ed at 80386.nl (Ed Schouten) Date: Sat Jun 14 19:22:31 2008 Subject: VM_PROT_EXEC on the stack Message-ID: <20080614174412.GU1176@hoeg.nl> Hello everyone, I'm not a real guru when it comes to low level x86 hardware stuff, but some time ago I read somewhere that the NX bit on AMD64 CPU's could be used to mark the stack as non-executable, making it impossible to execute code on the stack (through buffer overflows). When I look at procstat -v's output on FreeBSD/amd64, I see the stack has VM_PROT_EXEC. Is there a specific reason for this? Yours, -- Ed Schouten WWW: http://80386.nl/ -------------- 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/20080614/0ac72405/attachment.pgp From peter at wemm.org Sat Jun 14 19:50:49 2008 From: peter at wemm.org (Peter Wemm) Date: Sat Jun 14 19:50:53 2008 Subject: VM_PROT_EXEC on the stack In-Reply-To: <20080614174412.GU1176@hoeg.nl> References: <20080614174412.GU1176@hoeg.nl> Message-ID: gcc copies code to the stack and runs it in certain circumstances (nested functions). We'd need code added to libgcc to do the appropriate mprotect() calls. I think code exists for NetBSD to do this if somebody wants to pick this up. Search for mprotect in gcc source. Also, the very top page has the signal trampoline executable code. If you wanted to turn off EXEC, you'd either have to leave the very top page executable or move the trampoline elsewhere (eg: libc, like on sparc64). BTW: I'd like the latter. On Sat, Jun 14, 2008 at 10:44 AM, Ed Schouten wrote: > Hello everyone, > > I'm not a real guru when it comes to low level x86 hardware stuff, but > some time ago I read somewhere that the NX bit on AMD64 CPU's could be > used to mark the stack as non-executable, making it impossible to > execute code on the stack (through buffer overflows). > > When I look at procstat -v's output on FreeBSD/amd64, I see the stack > has VM_PROT_EXEC. Is there a specific reason for this? > > Yours, > -- > Ed Schouten > WWW: http://80386.nl/ > -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From kostikbel at gmail.com Sat Jun 14 20:46:50 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Sat Jun 14 20:46:52 2008 Subject: VM_PROT_EXEC on the stack In-Reply-To: <20080614174412.GU1176@hoeg.nl> References: <20080614174412.GU1176@hoeg.nl> Message-ID: <20080614200833.GZ94309@deviant.kiev.zoral.com.ua> On Sat, Jun 14, 2008 at 07:44:12PM +0200, Ed Schouten wrote: > Hello everyone, > > I'm not a real guru when it comes to low level x86 hardware stuff, but > some time ago I read somewhere that the NX bit on AMD64 CPU's could be > used to mark the stack as non-executable, making it impossible to > execute code on the stack (through buffer overflows). > > When I look at procstat -v's output on FreeBSD/amd64, I see the stack > has VM_PROT_EXEC. Is there a specific reason for this? There are at least two issues with marking stack non-executable. First, kernel copies the signal trampoline code fragments at the top of the stack. This may be worked around by splitting one page from the stack and marking it executable. Or, the code may be moved to the libc. Second issue is that, in principle, stack may be used by the compiler-generated trampolines. New gnu toolchain creates the GNU_STACK phdr that informs ld.so that non-executable stack is permitted (in fact, I think that it is p_flags of the phdr that defines required protection for the stack segment mappings). GNU_STACK is created when all linked relocatable objects contain .note.GNU-stack. -------------- 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/20080614/5ffa14c5/attachment.pgp From tinderbox at freebsd.org Sun Jun 15 07:38:42 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Jun 15 07:38:49 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080615073840.331C973039@freebsd-current.sentex.ca> TB --- 2008-06-15 07:05:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-15 07:05:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-15 07:05:01 - cleaning the object tree TB --- 2008-06-15 07:06:00 - cvsupping the source tree TB --- 2008-06-15 07:06:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-15 07:06:07 - building world (CFLAGS=-O -pipe) TB --- 2008-06-15 07:06:07 - cd /src TB --- 2008-06-15 07:06:07 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 15 07:06:10 UTC 2008 >>> 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 [...] cc -O -pipe -DPLATFORM_CONFIG_H=\"config_freebsd.h\" -I/obj/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libarchive/archive_read_support_format_iso9660.c cc -O -pipe -DPLATFORM_CONFIG_H=\"config_freebsd.h\" -I/obj/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libarchive/archive_read_support_format_mtree.c cc -O -pipe -DPLATFORM_CONFIG_H=\"config_freebsd.h\" -I/obj/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libarchive/archive_read_support_format_tar.c cc -O -pipe -DPLATFORM_CONFIG_H=\"config_freebsd.h\" -I/obj/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libarchive/archive_read_support_format_zip.c cc -O -pipe -DPLATFORM_CONFIG_H=\"config_freebsd.h\" -I/obj/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libarchive/archive_string.c cc1: warnings being treated as errors /src/lib/libarchive/archive_string.c: In function 'my_wctomb_utf8': /src/lib/libarchive/archive_string.c:202: warning: overflow in implicit constant conversion *** Error code 1 Stop in /src/lib/libarchive. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-15 07:38:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-15 07:38:40 - ERROR: failed to build world TB --- 2008-06-15 07:38:40 - tinderbox aborted TB --- 1380.58 user 190.62 system 2018.93 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From lushijia at gmail.com Sun Jun 15 06:00:08 2008 From: lushijia at gmail.com (Ray) Date: Sun Jun 15 11:11:47 2008 Subject: amd64/124606: add of some packages aborted Message-ID: <200806150557.m5F5vdxs078008@www.freebsd.org> >Number: 124606 >Category: amd64 >Synopsis: add of some packages aborted >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jun 15 06:00:07 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Ray >Release: freebsd 7.0 amd64 >Organization: student in university >Environment: intel core 2 duo >Description: I want to install packages post-installation, but I think I have met some problems. I selected all the pre-compiled packages binaries to install including apache-1.3.39_2.tbz, apache-2.2.6_2.tbz and apache+mod_ssl-1.3.39+2.8.30.tbz. Unfortunately, during the installation, the FreeBSD told me that "package apache-1.3.39 was added successfully" but "add of package apache-2.2.6_2 aborted, error code 1 - Please check the debug screen for more info." Is there someone can help me? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From linimon at FreeBSD.org Sun Jun 15 13:58:38 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jun 15 15:27:26 2008 Subject: amd64/124606: add of some packages aborted Message-ID: <200806151358.m5FDwcmC058895@freefall.freebsd.org> Synopsis: add of some packages aborted State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Jun 15 13:58:20 UTC 2008 State-Changed-Why: This is a question better asked on freebsd-questions@. http://www.freebsd.org/cgi/query-pr.cgi?pr=124606 From tinderbox at freebsd.org Mon Jun 16 07:08:01 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 16 07:08:06 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080616070754.244B97303E@freebsd-current.sentex.ca> TB --- 2008-06-16 07:05:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-16 07:05:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-16 07:05:01 - cleaning the object tree TB --- 2008-06-16 07:05:58 - cvsupping the source tree TB --- 2008-06-16 07:05:58 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-16 07:06:06 - building world (CFLAGS=-O -pipe) TB --- 2008-06-16 07:06:06 - cd /src TB --- 2008-06-16 07:06:06 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 16 07:06:08 UTC 2008 >>> 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 [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/compress (cleandir) rm -f compress compress.o zopen.o compress.1.gz compress.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/cpio (cleandir) "Makefile", line 12: Malformed conditional (${MK_GNU_CPIO} != "yes") "Makefile", line 15: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-16 07:07:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-16 07:07:54 - ERROR: failed to build world TB --- 2008-06-16 07:07:54 - tinderbox aborted TB --- 43.58 user 13.80 system 173.12 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Mon Jun 16 07:16:52 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 16 07:17:04 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080616071648.C32C873044@freebsd-current.sentex.ca> TB --- 2008-06-16 07:15:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-16 07:15:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-16 07:15:00 - cleaning the object tree TB --- 2008-06-16 07:15:03 - cvsupping the source tree TB --- 2008-06-16 07:15:03 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-16 07:15:12 - building world (CFLAGS=-O -pipe) TB --- 2008-06-16 07:15:12 - cd /src TB --- 2008-06-16 07:15:12 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 16 07:15:13 UTC 2008 >>> 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 [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/compress (cleandir) rm -f compress compress.o zopen.o compress.1.gz compress.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/cpio (cleandir) "Makefile", line 12: Malformed conditional (${MK_GNU_CPIO} != "yes") "Makefile", line 15: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-16 07:16:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-16 07:16:48 - ERROR: failed to build world TB --- 2008-06-16 07:16:48 - tinderbox aborted TB --- 41.84 user 10.28 system 108.02 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Mon Jun 16 07:26:10 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 16 07:26:20 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080616072608.3D10173039@freebsd-current.sentex.ca> TB --- 2008-06-16 07:25:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-16 07:25:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-16 07:25:01 - cleaning the object tree TB --- 2008-06-16 07:25:04 - cvsupping the source tree TB --- 2008-06-16 07:25:04 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-16 07:25:10 - building world (CFLAGS=-O -pipe) TB --- 2008-06-16 07:25:10 - cd /src TB --- 2008-06-16 07:25:10 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 16 07:25:11 UTC 2008 >>> 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 [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/compress (cleandir) rm -f compress compress.o zopen.o compress.1.gz compress.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/cpio (cleandir) "Makefile", line 12: Malformed conditional (${MK_GNU_CPIO} != "yes") "Makefile", line 15: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-16 07:26:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-16 07:26:08 - ERROR: failed to build world TB --- 2008-06-16 07:26:08 - tinderbox aborted TB --- 41.45 user 10.11 system 67.16 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Mon Jun 16 07:31:09 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 16 07:31:14 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080616073107.1C24F7303E@freebsd-current.sentex.ca> TB --- 2008-06-16 07:30:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-16 07:30:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-16 07:30:01 - cleaning the object tree TB --- 2008-06-16 07:30:03 - cvsupping the source tree TB --- 2008-06-16 07:30:03 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-16 07:30:08 - building world (CFLAGS=-O -pipe) TB --- 2008-06-16 07:30:08 - cd /src TB --- 2008-06-16 07:30:08 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 16 07:30:09 UTC 2008 >>> 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 [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/compress (cleandir) rm -f compress compress.o zopen.o compress.1.gz compress.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/cpio (cleandir) "Makefile", line 12: Malformed conditional (${MK_GNU_CPIO} != "yes") "Makefile", line 15: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-16 07:31:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-16 07:31:07 - ERROR: failed to build world TB --- 2008-06-16 07:31:07 - tinderbox aborted TB --- 41.80 user 9.76 system 66.07 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Mon Jun 16 07:36:14 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 16 07:36:35 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080616073607.ED99273039@freebsd-current.sentex.ca> TB --- 2008-06-16 07:35:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-16 07:35:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-16 07:35:01 - cleaning the object tree TB --- 2008-06-16 07:35:03 - cvsupping the source tree TB --- 2008-06-16 07:35:03 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-16 07:35:09 - building world (CFLAGS=-O -pipe) TB --- 2008-06-16 07:35:09 - cd /src TB --- 2008-06-16 07:35:09 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 16 07:35:10 UTC 2008 >>> 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 [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/compress (cleandir) rm -f compress compress.o zopen.o compress.1.gz compress.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/cpio (cleandir) "Makefile", line 12: Malformed conditional (${MK_GNU_CPIO} != "yes") "Makefile", line 15: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-16 07:36:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-16 07:36:07 - ERROR: failed to build world TB --- 2008-06-16 07:36:07 - tinderbox aborted TB --- 41.55 user 9.98 system 66.82 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Mon Jun 16 07:41:13 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Jun 16 07:41:30 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080616074106.DF7D87303E@freebsd-current.sentex.ca> TB --- 2008-06-16 07:40:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-16 07:40:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-16 07:40:01 - cleaning the object tree TB --- 2008-06-16 07:40:03 - cvsupping the source tree TB --- 2008-06-16 07:40:03 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-16 07:40:09 - building world (CFLAGS=-O -pipe) TB --- 2008-06-16 07:40:09 - cd /src TB --- 2008-06-16 07:40:09 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 16 07:40:09 UTC 2008 >>> 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 [...] rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/compress (cleandir) rm -f compress compress.o zopen.o compress.1.gz compress.1.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.bin/cpio (cleandir) "Makefile", line 12: Malformed conditional (${MK_GNU_CPIO} != "yes") "Makefile", line 15: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-16 07:41:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-16 07:41:06 - ERROR: failed to build world TB --- 2008-06-16 07:41:06 - tinderbox aborted TB --- 41.76 user 9.88 system 65.76 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From bugmaster at FreeBSD.org Mon Jun 16 11:06:50 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 16 11:25:43 2008 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200806161106.m5GB6n8T036641@freefall.freebsd.org> Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 [panic] System panic on shutdown when process will not o amd64/76136 amd64 [hang] system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys f amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 f amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/89501 amd64 [install] System crashes on install using ftp on local f amd64/89503 amd64 [boot] Cant Boot Installation Disk o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 f amd64/91492 amd64 [boot] BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati f amd64/94989 amd64 [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled f amd64/102122 amd64 [boot] 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work a amd64/109584 amd64 zdump(8) doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 f amd64/111992 amd64 [boot] BTX failed - HP Laptop dv2315nr f amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/116159 amd64 [panic] Panic while debugging on CURRENT o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/119936 amd64 [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/121439 amd64 [boot] Installation of FreeBSD 7.0 fails: ACPI problem o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/122423 amd64 Port install fails after upgrade o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs 54 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l f amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o bin/105542 amd64 on amd64, ldd(1) produces bogus output for i386 execut o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot f amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect f amd64/116457 amd64 [install] can't install freebsd on dv9420us f amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car f amd64/116670 amd64 [ata] onboard SATA RAID1 controllers not supported for s amd64/116689 amd64 [request] support for MSI K9MM-V f amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 f amd64/119949 amd64 [install] 6.3-RELEASE install; cannot find packages/IN f amd64/121590 amd64 powerd(8) may not work correctly f amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent 22 problems total. From das at FreeBSD.ORG Mon Jun 16 19:35:33 2008 From: das at FreeBSD.ORG (David Schultz) Date: Mon Jun 16 20:36:18 2008 Subject: saving FPU state in setjmp/longjmp Message-ID: <20080616191308.GA25248@zim.MIT.EDU> Are setjmp/longjmp supposed to save and restore the FPU control word (rounding mode, exception masks, etc.)? They're specifically not supposed to touch the status word, and one would think that they shouldn't touch the control word either. From a pragmatic point of view, most apps don't touch the FP control word anyway, and the few that do are better off with fegetenv/fesetenv and friends. A brief survey of setjmp/longjmp implementations indicates: - freebsd/arm saves and restores the FPU status word, which is wrong. - freebsd/i386 and freebsd/amd64 save and restore the x87 control word but not the SSE control word, which is half wrong in one direction or the other. - freebsd/everything-else don't touch the FPU. - linux doesn't touch the FPU. - solaris doesn't touch the FPU. So the real question is whether to remove the part of setjmp and longjmp that fiddle with the x87 control word, or whether to extend these functions to also save and restore the SSE control word. The fact that SSE has been around for a while and nobody has noticed the breakage suggests that either change should have minimal impact on compatibility. From brde at optusnet.com.au Wed Jun 18 05:39:03 2008 From: brde at optusnet.com.au (Bruce Evans) Date: Wed Jun 18 05:39:06 2008 Subject: saving FPU state in setjmp/longjmp In-Reply-To: <20080616191308.GA25248@zim.MIT.EDU> References: <20080616191308.GA25248@zim.MIT.EDU> Message-ID: <20080617225302.Y52409@delplex.bde.org> On Mon, 16 Jun 2008, David Schultz wrote: > Are setjmp/longjmp supposed to save and restore the FPU control > word (rounding mode, exception masks, etc.)? They're specifically > not supposed to touch the status word, and one would think that s/specifically not supposed to/unspecifically supposed to/ (C99 footnote 212 -- see below) > they shouldn't touch the control word either. From a pragmatic > point of view, most apps don't touch the FP control word anyway, > and the few that do are better off with fegetenv/fesetenv and friends. All my tests would fail if longjmp() didn't restore the control word. longjmp() from a signal handler can't possibly work unless the control word is restored, and my tests reduce to little more than testing this. longjmp() from a signal handler also needs to touch the status word to work -- it needs to at least clear the exception flags; on i386 it has used fninit to reset the entire FP status word for 15+ years since I fixed it, since this seemed to be the fastest way of resetting enough. More details: - long ago, the FP state in signal handlers was fairly broken -- it was the same as the preempted state except for special breakage (clearing) of the exception flags. My tests were written at this time. - longjump() from a signal handler thus restored the control word at the time of the setjmp(). The fninit in the i386 version of it prevents it keeping the (specially broken) status word at the time of the signal, so the exception flags are normally already clear. - Return from a signal handler (which gives undefined behaviour in most cases including all returns from SIGFPU handlers, especially in plain C99) gave reasonable behaviour -- both the control and (broken) status word at the time of the signal were kept. The broken status word was required for signal handlers to use floating point without having to clear the exception flags themself (but any useful use of FP in a signal handler caused undefined behaviour slightly before the signal handler returned; specifically, it could trap due to the settings of the preempted state, and it could corrupt the preempted state), and as a side effect this kept the cleared flags on return so that the preempted code could also continue using floating point without clearing the flags. - A copy of status word at the time of the exception was kept in the "exception status word" in the pcb and passed to signal handlers in in the signal context. gdb supported printing the copy in the pcb only. To restore and/or fix up the original state, the e.s.w. had to be merged with the active s.w. I don't know of any software that did this. - now, signal handlers get a private (reset) state. This fixes some of the bugs described above and helps implement the following new ones: - longjmp() from a signal handler has unchanged behaviour, but now it is even more necessary to restore the control word at the time of the setjmp() and to do something to not keep the current status word, since the current control and status word are private to the signal handler. If longjmp() didn't touch the FP state, then the only way to get back to the preempted state after the longjmp() would be for the signal handler to restore the preempted state before the longjmp(). Signal handlers would have a hard time supporting this unportable complication, epsecially if they are not SIGFPE handers. - Return from a signal handler now restores the preempted FP state, modulo the breakage of the exception flags. When signal handlers started getting a reset state, I thought that the exception flags didn't need to be broken and changed npxtrap() to not break them, but this broke my tests of returning from SIGFPE handlers -- the tests just set a flag and return, but this no longer works since nothing including the tests clears the exception flags. (The tests also change the control word so that SIGFPE's for FP exceptions actually occur if the relevant exception flags are set; then if they remain set the fault repeats like an integer divide-by-0 SIGFPE.) - The exception status word and gdb's support for it have been lost (except in cvs history). Before clearing the flags, the flags are encoded in a number in the sigcontext. Then some info is lost when the flags are cleared. > A brief survey of setjmp/longjmp implementations indicates: > - freebsd/arm saves and restores the FPU status word, which is wrong. I think this is least broken. On i386, it is just an optimization to not save/restore the status word. Save/restore of it at least keeps any exception flags that are set at the time of the setjmp(). > - freebsd/i386 and freebsd/amd64 save and restore the x87 control word > but not the SSE control word, which is half wrong in one direction or > the other. These also reset the status word. This is mainly an optimization. When they were written, there was no support for FP state in C, so setjmp()/longjmp() only had to preserve as much FP state as a normal function. > - freebsd/everything-else don't touch the FPU. > - linux doesn't touch the FPU. > - solaris doesn't touch the FPU. All of these are broken. C99 unspecifically requires the arm behaviour: - in n869.txt, it requires restoring the "calling environment of the abstract machine" at the time of the setjmp(). - in n1124.pdf footnote 212, it specifically says that FP status flags are part of the calling env. Footnotes are not normative, and it doesn't seem to say anything specifically about the control word, but clearly the calling environment is intended to include all FP state. I must have interpreted the corresponding requirement in C90 loosely to justify not preserving any FP status when I fixed the i386 version to restore the control word. The abstract machine in C90 required little or nothing of FP. > So the real question is whether to remove the part of setjmp and > longjmp that fiddle with the x87 control word, or whether to > extend these functions to also save and restore the SSE control > word. The fact that SSE has been around for a while and nobody has > noticed the breakage suggests that either change should have > minimal impact on compatibility. According to C99, all FP state must be preserved, but we can still avoid preserving data registers and some perhaps other details that aren't part of the abstract machine. Breakage of the exception flags is rarely observed since no one uses these :-). Breakage of SIGFPE handlers is even more rarely observed since no one unmasks FP exceptions :-), and signals for FP exceptions give undefined behaviour anyway. The most interesting case is for longjmp() from a signal handler for non-FP signal. Some cases should work, without the signal handler knowing anything about FP. When the signal occurs, the FP state may be arbitrarily exotic, and it must become normal when longjmp() returns. The current i386 implementation gives this except it messes up the C99 exception flags. Bruce From bugmaster at FreeBSD.org Mon Jun 23 11:06:51 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 23 11:21:49 2008 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200806231106.m5NB6oW5064891@freefall.freebsd.org> Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 [panic] System panic on shutdown when process will not o amd64/76136 amd64 [hang] system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys f amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 f amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/89501 amd64 [install] System crashes on install using ftp on local f amd64/89503 amd64 [boot] Cant Boot Installation Disk o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 f amd64/91492 amd64 [boot] BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati f amd64/94989 amd64 [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled f amd64/102122 amd64 [boot] 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work a amd64/109584 amd64 zdump(8) doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 f amd64/111992 amd64 [boot] BTX failed - HP Laptop dv2315nr f amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/116159 amd64 [panic] Panic while debugging on CURRENT o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/119936 amd64 [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/121439 amd64 [boot] Installation of FreeBSD 7.0 fails: ACPI problem o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/122423 amd64 Port install fails after upgrade o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs 54 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l f amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o bin/105542 amd64 on amd64, ldd(1) produces bogus output for i386 execut o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot f amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect f amd64/116457 amd64 [install] can't install freebsd on dv9420us f amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car f amd64/116670 amd64 [ata] onboard SATA RAID1 controllers not supported for s amd64/116689 amd64 [request] support for MSI K9MM-V f amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 f amd64/119949 amd64 [install] 6.3-RELEASE install; cannot find packages/IN f amd64/121590 amd64 powerd(8) may not work correctly f amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent 22 problems total. From edwin at FreeBSD.org Mon Jun 23 14:31:08 2008 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Mon Jun 23 14:37:44 2008 Subject: bin/105542: on amd64, ldd(1) produces bogus output for i386 executables Message-ID: <200806231431.m5NEV82H003170@freefall.freebsd.org> Synopsis: on amd64, ldd(1) produces bogus output for i386 executables State-Changed-From-To: open->closed State-Changed-By: edwin State-Changed-When: Mon Jun 23 14:30:55 UTC 2008 State-Changed-Why: A patch can be found in bin/124906 http://www.freebsd.org/cgi/query-pr.cgi?pr=105542 From tinderbox at freebsd.org Thu Jun 26 00:53:17 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jun 26 00:53:22 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080626005313.ED30073039@freebsd-current.sentex.ca> TB --- 2008-06-25 23:05:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-25 23:05:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-25 23:05:00 - cleaning the object tree TB --- 2008-06-25 23:05:54 - cvsupping the source tree TB --- 2008-06-25 23:05:54 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-25 23:06:01 - building world (CFLAGS=-O -pipe) TB --- 2008-06-25 23:06:01 - cd /src TB --- 2008-06-25 23:06:01 - /usr/bin/make -B buildworld >>> World build started on Wed Jun 25 23:06:05 UTC 2008 >>> 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 Jun 26 00:43:03 UTC 2008 TB --- 2008-06-26 00:43:03 - generating LINT kernel config TB --- 2008-06-26 00:43:03 - cd /src/sys/amd64/conf TB --- 2008-06-26 00:43:03 - /usr/bin/make -B LINT TB --- 2008-06-26 00:43:03 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-26 00:43:03 - cd /src TB --- 2008-06-26 00:43:03 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jun 26 00:43:04 UTC 2008 >>> 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 [...] subr_ntoskrnl.o(.text+0x63c0): In function `PsCreateSystemThread': : undefined reference to `__stack_chk_fail' subr_pe.o(.text+0x6bb): In function `pe_relocate': : undefined reference to `__stack_chk_guard' subr_pe.o(.text+0x934): In function `pe_relocate': : undefined reference to `__stack_chk_guard' subr_pe.o(.text+0x93b): In function `pe_relocate': : undefined reference to `__stack_chk_fail' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-26 00:53:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-26 00:53:13 - ERROR: failed to build lint kernel TB --- 2008-06-26 00:53:13 - tinderbox aborted TB --- 4794.88 user 609.80 system 6492.80 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Thu Jun 26 05:46:51 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jun 26 05:46:55 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080626054648.C6F0573039@freebsd-current.sentex.ca> TB --- 2008-06-26 04:00:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-26 04:00:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-26 04:00:01 - cleaning the object tree TB --- 2008-06-26 04:00:46 - cvsupping the source tree TB --- 2008-06-26 04:00:46 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-26 04:00:52 - building world (CFLAGS=-O -pipe) TB --- 2008-06-26 04:00:52 - cd /src TB --- 2008-06-26 04:00:52 - /usr/bin/make -B buildworld >>> World build started on Thu Jun 26 04:00:54 UTC 2008 >>> 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 Jun 26 05:36:59 UTC 2008 TB --- 2008-06-26 05:36:59 - generating LINT kernel config TB --- 2008-06-26 05:36:59 - cd /src/sys/amd64/conf TB --- 2008-06-26 05:36:59 - /usr/bin/make -B LINT TB --- 2008-06-26 05:36:59 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-26 05:36:59 - cd /src TB --- 2008-06-26 05:36:59 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jun 26 05:36:59 UTC 2008 >>> 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 [...] subr_ntoskrnl.o(.text+0x63c0): In function `PsCreateSystemThread': : undefined reference to `__stack_chk_fail' subr_pe.o(.text+0x6bb): In function `pe_relocate': : undefined reference to `__stack_chk_guard' subr_pe.o(.text+0x934): In function `pe_relocate': : undefined reference to `__stack_chk_guard' subr_pe.o(.text+0x93b): In function `pe_relocate': : undefined reference to `__stack_chk_fail' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-26 05:46:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-26 05:46:48 - ERROR: failed to build lint kernel TB --- 2008-06-26 05:46:48 - tinderbox aborted TB --- 4797.90 user 605.09 system 6407.56 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From goodbitster at gmail.com Thu Jun 26 07:10:06 2008 From: goodbitster at gmail.com (J.C.) Date: Thu Jun 26 11:14:40 2008 Subject: amd64/125002: amd64, SATA hard disks not detected Message-ID: <200806260707.m5Q77wUW001592@www.freebsd.org> >Number: 125002 >Category: amd64 >Synopsis: amd64, SATA hard disks not detected >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 26 07:10:05 UTC 2008 >Closed-Date: >Last-Modified: >Originator: J.C. >Release: 7.0 amd64 >Organization: >Environment: amd64 >Description: The FreeBSD 7.0 amd64 installer says it can't find any disk drives on my computer. For whatever it's worth, here's the dmesg output from my OpenBSD installation (which found and installed on the SATA disk drives in question without any changes to the system or BIOS): real mem = 3489198080 (3327MB) avail mem = 3373871104 (3217MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0000 (38 entries) bios0: vendor Phoenix Technologies, LTD version "6.00 PG" date 12/17/2007 bios0: http://www.abit.com.tw/ FP-IN9 SLI(C55-MCP51) acpi0 at bios0: rev 0 acpi0: tables DSDT FACP HPET MCFG APIC SSDT acpi0: wakeup devices HUB0(S5) XVRA(S5) XVRB(S5) XVRC(S5) XVRD(S5) UAR1(S5) USB0(S3) USB2(S3) AZAD(S5) MMAC(S5) MMCI(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 25000000 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (HUB0) acpicpu0 at acpi0 acpitz0 at acpi0: critical temperature 80 degC acpibtn0 at acpi0: PWRB cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz, 2400.32 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG cpu0: 4MB 64b/line 16-way L2 cache pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 "NVIDIA C55 Host" rev 0xa2 "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 0 function 1 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 0 function 2 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 0 function 3 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 0 function 4 not configured "NVIDIA C55 Memory" rev 0xa2 at pci0 dev 0 function 5 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 0 function 6 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 0 function 7 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 0 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 1 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 2 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 3 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 4 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 5 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 1 function 6 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 2 function 0 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 2 function 1 not configured "NVIDIA C55 Memory" rev 0xa1 at pci0 dev 2 function 2 not configured ppb0 at pci0 dev 3 function 0 "NVIDIA C55 PCIE" rev 0xa1 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor "NVIDIA", unknown product 0x0600 rev 0xa2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) "NVIDIA MCP51 Host" rev 0xa2 at pci0 dev 9 function 0 not configured pcib0 at pci0 dev 10 function 0 "NVIDIA MCP51 ISA" rev 0xa3 nviic0 at pci0 dev 10 function 1 "NVIDIA MCP51 SMBus" rev 0xa3 iic0 at nviic0 iic0: addr 0x2e 00=c1 01=0f 02=00 03=00 04=00 05=00 06=00 07=c0 08=14 09=62 10=02 11=00 12=00 words 00=c1ff 01=0fff 02=00ff 03=00ff 04=00ff 05=00ff 06=00ff 07=c0ff 08=14ff 09=62ff 0a=ffff 0b=ffff 0c=ffff 0d=ffff 0e=ffff 0f=ffff spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL5 spdmem1 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-6400CL5 iic1 at nviic0 "NVIDIA MCP51 Memory" rev 0xa3 at pci0 dev 10 function 2 not configured ohci0 at pci0 dev 11 function 0 "NVIDIA MCP51 USB" rev 0xa3: irq 10, version 1.0, legacy support ehci0 at pci0 dev 11 function 1 "NVIDIA MCP51 USB" rev 0xa3: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "NVIDIA EHCI root hub" rev 2.00/1.00 addr 1 pciide0 at pci0 dev 13 function 0 "NVIDIA MCP51 IDE" rev 0xa1: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 14 function 0 "NVIDIA MCP51 SATA" rev 0xa1: DMA pciide1: using irq 11 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 476940MB, 976773168 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide1 channel 1 drive 0: wd1: 16-sector PIO, LBA48, 476940MB, 976773168 sectors wd1(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide2 at pci0 dev 15 function 0 "NVIDIA MCP51 SATA" rev 0xa1: DMA pciide2: using irq 10 for native-PCI interrupt atapiscsi0 at pciide2 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable cd0(pciide2:0:0): using PIO mode 4 atapiscsi1 at pciide2 channel 1 drive 0 scsibus1 at atapiscsi1: 2 targets cd1 at scsibus1 targ 0 lun 0: SCSI0 5/cdrom removable cd1(pciide2:1:0): using PIO mode 4 ppb1 at pci0 dev 16 function 0 "NVIDIA MCP51 PCI-PCI" rev 0xa2 pci2 at ppb1 bus 2 rl0 at pci2 dev 9 function 0 "Realtek 8139" rev 0x10: irq 5, address 00:0e:2e:32:99:77 rlphy0 at rl0 phy 0: RTL internal PHY "Creative Labs SoundBlaster X-Fi" rev 0x00 at pci2 dev 10 function 0 not configured nfe0 at pci0 dev 20 function 0 "NVIDIA MCP51 LAN" rev 0xa3: irq 5, address 00:50:8d:9d:8e:7e nfe0: no PHY found! isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: spkr0 at pcppi0 wbsio0 at isa0 port 0x2e/2: W83627DHG rev 0x23 lm1 at wbsio0 port 0x290/8: W83627DHG fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec usb1 at ohci0: USB revision 1.0 uhub1 at usb1 "NVIDIA OHCI root hub" rev 1.00/1.00 addr 1 uhidev0 at uhub1 port 1 configuration 1 interface 0 "Logitech USB Gaming Mouse" rev 2.00/52.00 addr 2 uhidev0: iclass 3/1 ums0 at uhidev0: 16 buttons and Z dir. wsmouse0 at ums0 mux 0 uhidev1 at uhub1 port 1 configuration 1 interface 1 "Logitech USB Gaming Mouse" rev 2.00/52.00 addr 2 uhidev1: iclass 3/0, 17 report ids uhid0 at uhidev1 reportid 16: input=6, output=6, feature=0 uhid1 at uhidev1 reportid 17: input=19, output=19, feature=0 uhub2 at uhub1 port 2 "Logitech G15 Keyboard Hub" rev 1.10/0.20 addr 3 uhidev2 at uhub2 port 1 configuration 1 interface 0 "Logitech G15 Gaming Keyboard" rev 2.00/1.00 addr 4 uhidev2: iclass 3/1 ukbd0 at uhidev2: 8 modifier keys, 6 key codes wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhidev3 at uhub2 port 1 configuration 1 interface 1 "Logitech G15 Gaming Keyboard" rev 2.00/1.00 addr 4 uhidev3: iclass 3/0, 3 report ids uhid2 at uhidev3 reportid 1: input=1, output=0, feature=0 uhid3 at uhidev3 reportid 2: input=7, output=0, feature=0 uhid4 at uhidev3 reportid 3: input=1, output=20, feature=1 uhidev4 at uhub2 port 4 configuration 1 interface 0 "Logitech G15 GamePanel LCD" rev 2.00/0.20 addr 5 uhidev4: iclass 3/0, 3 report ids uhid5 at uhidev4 reportid 1: input=6, output=0, feature=0 uhid6 at uhidev4 reportid 2: input=4, output=6, feature=3 uhid7 at uhidev4 reportid 3: input=0, output=991, feature=0 softraid0 at root root on wd1a swap on wd1b dump on wd1b >How-To-Repeat: Attempt to install FreeBSD 7.0. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From svein-listmail at d80.iso100.no Fri Jun 27 11:02:46 2008 From: svein-listmail at d80.iso100.no (Svein Skogen) Date: Fri Jun 27 11:02:53 2008 Subject: Status of NVidia support on x64 Message-ID: <4864C48B.9050006@d80.iso100.no> According to NVidia's site, NVidia is still waiting for changes to the memory management subsystem in FreeBSD/x64 before a driver can be shipped. What is the status of the changes they have requested? Is there code we can betatest? //Svein From gnn at freebsd.org Fri Jun 27 15:13:57 2008 From: gnn at freebsd.org (gnn@freebsd.org) Date: Fri Jun 27 15:14:01 2008 Subject: Status of NVidia support on x64 In-Reply-To: <4864C48B.9050006@d80.iso100.no> References: <4864C48B.9050006@d80.iso100.no> Message-ID: At Fri, 27 Jun 2008 12:44:27 +0200, Svein Skogen wrote: > > According to NVidia's site, NVidia is still waiting for changes to the > memory management subsystem in FreeBSD/x64 before a driver can be shipped. > > What is the status of the changes they have requested? Is there code we > can betatest? > This is an ongoing discussion. I do not believe that there are any patches as yet. Best, George From tinderbox at freebsd.org Sun Jun 29 05:35:44 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Jun 29 05:35:56 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20080629053541.2E35673039@freebsd-current.sentex.ca> TB --- 2008-06-29 03:50:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-06-29 03:50:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-06-29 03:50:00 - cleaning the object tree TB --- 2008-06-29 03:50:52 - cvsupping the source tree TB --- 2008-06-29 03:50:52 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-06-29 03:50:59 - building world (CFLAGS=-O -pipe) TB --- 2008-06-29 03:50:59 - cd /src TB --- 2008-06-29 03:50:59 - /usr/bin/make -B buildworld >>> World build started on Sun Jun 29 03:51:01 UTC 2008 >>> 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 Sun Jun 29 05:27:19 UTC 2008 TB --- 2008-06-29 05:27:19 - generating LINT kernel config TB --- 2008-06-29 05:27:19 - cd /src/sys/amd64/conf TB --- 2008-06-29 05:27:19 - /usr/bin/make -B LINT TB --- 2008-06-29 05:27:19 - building LINT kernel (COPTFLAGS=) TB --- 2008-06-29 05:27:19 - cd /src TB --- 2008-06-29 05:27:19 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jun 29 05:27:19 UTC 2008 >>> 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 [...] /src/sys/netinet6/in6_rmx.c:337: error: 'rtq_timeout6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:337: error: (Each undeclared identifier is reported only once /src/sys/netinet6/in6_rmx.c:337: error: for each function it appears in.) /src/sys/netinet6/in6_rmx.c:373: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:373: error: 'timer6' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c: In function 'in6_inithead': /src/sys/netinet6/in6_rmx.c:472: error: 'rtq' undeclared (first use in this function) /src/sys/netinet6/in6_rmx.c:472: error: 'timer6' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-29 05:35:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-29 05:35:40 - ERROR: failed to build lint kernel TB --- 2008-06-29 05:35:40 - tinderbox aborted TB --- 4732.38 user 603.80 system 6340.09 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From fabian at wenks.ch Sun Jun 29 15:30:08 2008 From: fabian at wenks.ch (Fabian Wenk) Date: Sun Jun 29 15:30:09 2008 Subject: amd64/125002: amd64, SATA hard disks not detected Message-ID: <200806291530.m5TFU7wV059073@freefall.freebsd.org> The following reply was made to PR amd64/125002; it has been noted by GNATS. From: Fabian Wenk To: "J.C." Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/125002: amd64, SATA hard disks not detected Date: Sun, 29 Jun 2008 17:27:59 +0200 Hello J.C. On 26.06.08 09:07, J.C. wrote: >>Number: 125002 >>Category: amd64 >>Synopsis: amd64, SATA hard disks not detected >>Description: > The FreeBSD 7.0 amd64 installer says it can't find any disk > drives on my computer. > > For whatever it's worth, here's the dmesg output from my OpenBSD > installation (which found and installed on the SATA disk drives > in question without any changes to the system or BIOS): > wd0 at pciide1 channel 0 drive 0: > wd0: 16-sector PIO, LBA48, 476940MB, 976773168 sectors > wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 > wd1 at pciide1 channel 1 drive 0: > wd1: 16-sector PIO, LBA48, 476940MB, 976773168 sectors > wd1(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 OpenBSD did find them as IDE (aka P-ATA) disks. Somewhere in the BIOS settings should be an option to switch the SATA controller to AHCI, maybe this helps. On most computers this setting defaults to P-ATA mode, which is a slower compatibility mode and is needed for an other OS to work. bye Fabian From bugmaster at FreeBSD.org Mon Jun 30 11:06:53 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 30 13:06:06 2008 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200806301106.m5UB6rhj095675@freefall.freebsd.org> Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 [panic] System panic on shutdown when process will not o amd64/76136 amd64 [hang] system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys f amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 f amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/89501 amd64 [install] System crashes on install using ftp on local f amd64/89503 amd64 [boot] Cant Boot Installation Disk o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 f amd64/91492 amd64 [boot] BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati f amd64/94989 amd64 [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled f amd64/102122 amd64 [boot] 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work a amd64/109584 amd64 zdump(8) doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 f amd64/111992 amd64 [boot] BTX failed - HP Laptop dv2315nr f amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/116159 amd64 [panic] Panic while debugging on CURRENT o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/119936 amd64 [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/121439 amd64 [boot] Installation of FreeBSD 7.0 fails: ACPI problem o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/122423 amd64 Port install fails after upgrade o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/125002 amd64 [install] amd64, SATA hard disks not detected 55 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l f amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot f amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect f amd64/116457 amd64 [install] can't install freebsd on dv9420us f amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car f amd64/116670 amd64 [ata] onboard SATA RAID1 controllers not supported for s amd64/116689 amd64 [request] support for MSI K9MM-V f amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 f amd64/119949 amd64 [install] 6.3-RELEASE install; cannot find packages/IN f amd64/121590 amd64 powerd(8) may not work correctly f amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent 21 problems total.