Current problem reports assigned to freebsd-amd64@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o amd64/182740 amd64 BTX halted on Jetway NF81 motherboard when RAID is ena o amd64/182686 amd64 bios lost HDD after installing freebsd-9.x o amd64/182568 amd64 FreeBSD 10 Alpha 4 fails installation under Hyper-V o amd64/181358 amd64 Suspend to RAM not working correctly on Lenovo X121e ( o amd64/181357 amd64 LCD Brightness Control not working on Lenovo X121e (AC o amd64/181285 amd64 x11/xorg does not start if Nvidia Optimus is enabled o o amd64/181282 amd64 3h of work on battery on FreeBSD while 10h on Windows o amd64/180862 amd64 [install] Installing FreeBSD 9.1 (AMD64 DVD) and then o amd64/180562 amd64 amdtemp and ACPI not working with motherboard ASUS M5A o amd64/180018 amd64 [panic] System panics when bsnmpd is started o amd64/179556 amd64 FreeBSD 9-1 amd64 - Install freeze on HP Proliant DL58 o amd64/179376 amd64 xhci ehci irq storm o amd64/179288 amd64 unable to install on HP ProLiant DL380p Gen8 with 128G o amd64/179282 amd64 [PATCH] Intel SMAP for FreeBSD-CURRENT o amd64/179038 amd64 instant reboot doesnt even try too install o amd64/178792 amd64 -march=native fails with clang on certain CPU's o amd64/178357 amd64 [patch] export CPU physical and virtual address sizes o amd64/176835 amd64 Fatal trap 12: page fault while in kernel mode o amd64/176474 amd64 kernel panic o amd64/175725 amd64 Audio through USB has not as good hi quality as it has o amd64/175655 amd64 When enabled tty console OS hang during boot o amd64/175370 amd64 kernel panic the rebuild kernel with vimage options in o amd64/175282 amd64 Freebsd 9.1 release amd64, mb Intel D525MW, not worked o amd64/175129 amd64 laptop won't suspend on lid close o amd64/174679 amd64 Intel i5 laptop overheats and shuts down [regression] o amd64/173869 amd64 buildworld breaks with clang o amd64/173680 amd64 9.1rc3 installer hangs at rootpass o amd64/173502 amd64 Patch inhibition of warnings that appear in the combin o amd64/173465 amd64 FreeBSD 9.1 restarts in random fashion after upgrade t o amd64/173311 amd64 FreeBSD 9.1 RC2 , 12 servers restart in random fashion o amd64/173235 amd64 Have received two crashes within 1 day after installin o amd64/172926 amd64 [boot] booting hangs after 9.1-RC2 install in 2nd (MBR o amd64/171835 amd64 bsdinstall abort on Dell PowerEdge R420 with PERC H310 o amd64/171814 amd64 [panic] bioq_init or bioq_remove (unsure which) o amd64/171701 amd64 [install] 9.0-rel amd64 installer 'guided' or 'manual' o amd64/171250 amd64 ldd32 cannot find some i386 libraries o amd64/170487 amd64 [boot] Thinkpad X61s cannot boot 9.1-BETA1 o amd64/170351 amd64 [kernel] [patch] amd64: 64-bit process can't always ge o amd64/170115 amd64 Serial boot broken in 9.0 o amd64/168659 amd64 [boot] FreeBSD 9 - Crash upon booting off install CD ( o amd64/167582 amd64 Compile of MySQL NDB Cluster Fails 8.2 AMD64 o amd64/167543 amd64 [kernel] Install FreeBSD can show error message with c o amd64/167393 amd64 [boot] MacBook4,1 hangs on SMP boot o amd64/166639 amd64 [boot] Syscons issue Intel D2700 o amd64/166229 amd64 [boot] Unable to install FreeBSD 9 on Acer Extensa 522 o amd64/165850 amd64 [build] 8.3-RC1 (amd64): world doesn't build with CPUT o amd64/165845 amd64 [build] Unable to build kernel on 8.2-STABLE o amd64/165351 amd64 [boot] Error while installing or booting the freeBSD O o amd64/164773 amd64 [boot] 9.0 amd64 fails to boot on HP DL145 G3 [regress o amd64/164707 amd64 FreeBSD 9 installer does not work with IBM uefi o amd64/164643 amd64 Kernel Panic at 9.0-RELEASE o amd64/164619 amd64 when logged in as root the user and group applications o amd64/164457 amd64 [install] Can't install FreeBSD 9.0 (amd64) on HP Blad o amd64/164301 amd64 [install] 9.0 - Can't install, no DHCP lease o amd64/164136 amd64 after fresh install 8.1 release or 8.2 release the har o amd64/164116 amd64 [boot] FreeBSD 9.0-RELEASE installations mediums fails o amd64/164089 amd64 FreeBSD-9.0-RELEASE-amd64-memstick.img does not boot o amd64/164073 amd64 /etc/rc warning after booting o amd64/164036 amd64 [keyboard] Moused fails on 9_0_RELENG o amd64/163736 amd64 Freebsd 8.2 with MPD5 and about 100 PPPoE clients pani o amd64/163710 amd64 setjump in userboot.so causes stack corruption o amd64/163625 amd64 Install problems of RC3 amd64 on ASRock N68 GE3 UCC o amd64/163568
Re: amd64/182686: bios lost HDD after installing freebsd-9.x
On Saturday, October 05, 2013 10:18:42 am XX wrote: Number: 182686 Category: amd64 Synopsis: bios lost HDD after installing freebsd-9.x Confidential: no Severity: serious Priority: medium Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Sat Oct 05 14:20:00 UTC 2013 Closed-Date: Last-Modified: Originator: áÎÄÒÅÊ Release:9.2 Organization: Environment: Description: I have installed freebsd-9.1 on my AMD 64 machine it worked well. But I have decided to go on 9.2 version and. I booted from usb, create slice and bsd- partitions on IDE hard drive using gpart and newfs. then i used bsdinstall to install the system. after installing i make shutdown -p now. When i turned my computer on, BIOS did not detect any hard drive. Then i installed system on SATA hard drive and have got the same result. When i connect this SATA drive to windows machine via USB - disk is OK. After deleting FreeBSD slice and connecting the disk back to AMD64 its BIOS has detected the drive. Did you use GPT? If so, try using MBR instead for partitioning your disk. -- John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: amd64/182568: FreeBSD 10 Alpha 4 fails installation under Hyper-V
On Wednesday, October 02, 2013 6:45:24 am Chavdar Ivanov wrote: Number: 182568 Category: amd64 Synopsis: FreeBSD 10 Alpha 4 fails installation under Hyper-V Confidential: no Severity: non-critical Priority: low Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Wed Oct 02 10:50:00 UTC 2013 Closed-Date: Last-Modified: Originator: Chavdar Ivanov Release:FreeBSD 10 Alpha 4 Organization: Delcam Plc Environment: n/a Description: Tried installing FreeBSD-10.0-ALPHA4-amd64-disc1.iso on Hyper-V 2008 R2, Hyper-V 2012 and Hyper-V 2012 R2 (preview) with identical results. The kernel appears not to recognize the CD drive, the message about it does not appear. The last message is as follows: I believe the Hyper-V guys are working on a fix for this. -- John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: amd64/182568: FreeBSD 10 Alpha 4 fails installation under Hyper-V
The following reply was made to PR amd64/182568; it has been noted by GNATS. From: John Baldwin j...@freebsd.org To: freebsd-amd64@freebsd.org Cc: Chavdar Ivanov c...@delcam.com, freebsd-gnats-sub...@freebsd.org Subject: Re: amd64/182568: FreeBSD 10 Alpha 4 fails installation under Hyper-V Date: Mon, 7 Oct 2013 10:28:39 -0400 On Wednesday, October 02, 2013 6:45:24 am Chavdar Ivanov wrote: Number: 182568 Category: amd64 Synopsis: FreeBSD 10 Alpha 4 fails installation under Hyper-V Confidential: no Severity: non-critical Priority: low Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Wed Oct 02 10:50:00 UTC 2013 Closed-Date: Last-Modified: Originator: Chavdar Ivanov Release:FreeBSD 10 Alpha 4 Organization: Delcam Plc Environment: n/a Description: Tried installing FreeBSD-10.0-ALPHA4-amd64-disc1.iso on Hyper-V 2008 R2, Hyper-V 2012 and Hyper-V 2012 R2 (preview) with identical results. The kernel appears not to recognize the CD drive, the message about it does not appear. The last message is as follows: I believe the Hyper-V guys are working on a fix for this. -- John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: amd64/182686: bios lost HDD after installing freebsd-9.x
The following reply was made to PR amd64/182686; it has been noted by GNATS. From: John Baldwin j...@freebsd.org To: freebsd-amd64@freebsd.org Cc: XX reku...@gmail.com, freebsd-gnats-sub...@freebsd.org Subject: Re: amd64/182686: bios lost HDD after installing freebsd-9.x Date: Mon, 7 Oct 2013 11:41:27 -0400 On Saturday, October 05, 2013 10:18:42 am XX wrote: =20 Number: 182686 Category: amd64 Synopsis: bios lost HDD after installing freebsd-9.x Confidential: no Severity: serious Priority: medium Responsible:freebsd-amd64 State: open Quarter: =20 Keywords: =20 Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Sat Oct 05 14:20:00 UTC 2013 Closed-Date: Last-Modified: Originator: =E1=CE=C4=D2=C5=CA Release:9.2 Organization: Environment: Description: I have installed freebsd-9.1 on my AMD 64 machine it worked well. But I h= ave=20 decided to go on 9.2 version and. I booted from usb, create slice and bsd- partitions on IDE hard drive using gpart and newfs. then i used bsdinstall = to=20 install the system. after installing i make shutdown -p now. When i turne= d=20 my computer on, BIOS did not detect any hard drive. Then i installed system on SATA hard drive and have got the same result.= =20 When i connect this SATA drive to windows machine via USB - disk is OK. Aft= er=20 deleting FreeBSD slice and connecting the disk back to AMD64 its BIOS has=20 detected the drive. Did you use GPT? If so, try using MBR instead for partitioning your disk. =2D-=20 John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: amd64/182740: BTX halted on Jetway NF81 motherboard when RAID is enabled
The following reply was made to PR amd64/182740; it has been noted by GNATS. From: John Baldwin j...@freebsd.org To: freebsd-amd64@freebsd.org Cc: Julian Pidancet julian.pidan...@gmail.com, freebsd-gnats-sub...@freebsd.org Subject: Re: amd64/182740: BTX halted on Jetway NF81 motherboard when RAID is enabled Date: Mon, 7 Oct 2013 11:47:32 -0400 On Sunday, October 06, 2013 7:28:31 am Julian Pidancet wrote: Number: 182740 Category: amd64 Synopsis: BTX halted on Jetway NF81 motherboard when RAID is enabled Confidential: no Severity: non-critical Priority: low Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Sun Oct 06 11:30:00 UTC 2013 Closed-Date: Last-Modified: Originator: Julian Pidancet Release:8.2 Organization: Environment: Description: Just got this brand new motherboard with an AMD APU and an AMD chipset. Whenever I try to boot FreeBSD and AHCI or RAID is enabled in the BIOS, I am getting this message: BTX loader 1.00 BTX version is 1.02 int=000a err= efl=6402 eip=93e0 eax=534d4150 ebx=0001 ecx=0014 edx=534d4150 esi= edi=0004 ebp= esp=004e cs=0008 ds=0033 es=0033fs=0033 gs=0033 ss=0010 cs:eip=cf 83 f8 01 75 1a 16 87-86 1f 1e 0f a1 0f a0 0f a9 b8 00 a0 00 00 03 44-24 0c 8d 60 04 58 ff d0 ss:esp=00 f0 39 e7 00 f0 e3 21-80 ce 2e e8 00 f0 d2 ef 00 f0 00 e0 00 f0 f2 e6-00 f0 6e fe 00 f0 53 ff BTX halted It looks like to me the BTX is taking an Invalid TSS exception while executing an iret instruction. How-To-Repeat: I tried: - Booting from the install cdrom - Booting from an USB install disk - Booting from boot/pxeboot in PXE mode All exhibit the same issue. Fix: Selecting Legacy IDE mode in the BIOS configuration instead of AHCI/RAID. Ok, can you take this patch and use it to build an updated pxeboot and test if it fixes disk access with AHCI enabled? Index: boot/i386/btx/btx/btx.S === --- boot/i386/btx/btx/btx.S(revision 247010) +++ boot/i386/btx/btx/btx.S(working copy) @@ -41,6 +41,8 @@ .set PSL_RESERVED_DEFAULT,0x0002 .set PSL_T,0x0100 # Trap flag .set PSL_I,0x0200 # Interrupt enable flag + .set PSL_D,0x0400 # String instruction direction + .set PSL_NT,0x4000 # Nested task flag .set PSL_VM,0x0002 # Virtual 8086 mode flag .set PSL_AC,0x0004 # Alignment check flag /* @@ -611,8 +613,8 @@ pushl %ds # regs pushl %es pushfl # Save %eflags - cli # Disable interrupts - std # String ops dec + pushl $PSL_RESERVED_DEFAULT|PSL_D # Use clean %eflags with + popfl # string ops dec xorw %ax,%ax# Reset seg movw %ax,%ds# regs movw %ax,%es# (%ss is already 0) @@ -675,6 +677,7 @@ testl $V86F_FLAGS,%edx # User wants flags? jz rret_tramp.3 # No movl MEM_ESPR-0x3c,%eax # Read real mode flags + andl $~(PSL_T|PSL_NT),%eax # Clear unsafe flags movw %ax,-0x08(%esi)# Update user flags (low 16) /* * Return to the user task -- John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: amd64/182740: BTX halted on Jetway NF81 motherboard when RAID is enabled
On Sunday, October 06, 2013 7:28:31 am Julian Pidancet wrote: Number: 182740 Category: amd64 Synopsis: BTX halted on Jetway NF81 motherboard when RAID is enabled Confidential: no Severity: non-critical Priority: low Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Sun Oct 06 11:30:00 UTC 2013 Closed-Date: Last-Modified: Originator: Julian Pidancet Release:8.2 Organization: Environment: Description: Just got this brand new motherboard with an AMD APU and an AMD chipset. Whenever I try to boot FreeBSD and AHCI or RAID is enabled in the BIOS, I am getting this message: BTX loader 1.00 BTX version is 1.02 int=000a err= efl=6402 eip=93e0 eax=534d4150 ebx=0001 ecx=0014 edx=534d4150 esi= edi=0004 ebp= esp=004e cs=0008 ds=0033 es=0033fs=0033 gs=0033 ss=0010 cs:eip=cf 83 f8 01 75 1a 16 87-86 1f 1e 0f a1 0f a0 0f a9 b8 00 a0 00 00 03 44-24 0c 8d 60 04 58 ff d0 ss:esp=00 f0 39 e7 00 f0 e3 21-80 ce 2e e8 00 f0 d2 ef 00 f0 00 e0 00 f0 f2 e6-00 f0 6e fe 00 f0 53 ff BTX halted It looks like to me the BTX is taking an Invalid TSS exception while executing an iret instruction. How-To-Repeat: I tried: - Booting from the install cdrom - Booting from an USB install disk - Booting from boot/pxeboot in PXE mode All exhibit the same issue. Fix: Selecting Legacy IDE mode in the BIOS configuration instead of AHCI/RAID. Ok, can you take this patch and use it to build an updated pxeboot and test if it fixes disk access with AHCI enabled? Index: boot/i386/btx/btx/btx.S === --- boot/i386/btx/btx/btx.S (revision 247010) +++ boot/i386/btx/btx/btx.S (working copy) @@ -41,6 +41,8 @@ .set PSL_RESERVED_DEFAULT,0x0002 .set PSL_T,0x0100 # Trap flag .set PSL_I,0x0200 # Interrupt enable flag + .set PSL_D,0x0400 # String instruction direction + .set PSL_NT,0x4000 # Nested task flag .set PSL_VM,0x0002 # Virtual 8086 mode flag .set PSL_AC,0x0004 # Alignment check flag /* @@ -611,8 +613,8 @@ pushl %ds # regs pushl %es pushfl # Save %eflags - cli # Disable interrupts - std # String ops dec + pushl $PSL_RESERVED_DEFAULT|PSL_D # Use clean %eflags with + popfl # string ops dec xorw %ax,%ax# Reset seg movw %ax,%ds# regs movw %ax,%es# (%ss is already 0) @@ -675,6 +677,7 @@ testl $V86F_FLAGS,%edx # User wants flags? jz rret_tramp.3 # No movl MEM_ESPR-0x3c,%eax # Read real mode flags + andl $~(PSL_T|PSL_NT),%eax # Clear unsafe flags movw %ax,-0x08(%esi)# Update user flags (low 16) /* * Return to the user task -- John Baldwin ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
[head tinderbox] failure on amd64/amd64
TB --- 2013-10-07 18:40:22 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-07 18:40:22 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-07 18:40:22 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-10-07 18:40:22 - cleaning the object tree TB --- 2013-10-07 18:40:22 - /usr/local/bin/svn stat /src TB --- 2013-10-07 18:40:27 - At svn revision 256119 TB --- 2013-10-07 18:40:28 - building world TB --- 2013-10-07 18:40:28 - CROSS_BUILD_TESTING=YES TB --- 2013-10-07 18:40:28 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-07 18:40:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-07 18:40:28 - SRCCONF=/dev/null TB --- 2013-10-07 18:40:28 - TARGET=amd64 TB --- 2013-10-07 18:40:28 - TARGET_ARCH=amd64 TB --- 2013-10-07 18:40:28 - TZ=UTC TB --- 2013-10-07 18:40:28 - __MAKE_CONF=/dev/null TB --- 2013-10-07 18:40:28 - cd /src TB --- 2013-10-07 18:40:28 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Oct 7 18:40:37 UTC 2013 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 Oct 7 22:29:10 UTC 2013 TB --- 2013-10-07 22:29:10 - generating LINT kernel config TB --- 2013-10-07 22:29:10 - cd /src/sys/amd64/conf TB --- 2013-10-07 22:29:10 - /usr/bin/make -B LINT TB --- 2013-10-07 22:29:10 - cd /src/sys/amd64/conf TB --- 2013-10-07 22:29:10 - /usr/sbin/config -m LINT TB --- 2013-10-07 22:29:10 - building LINT kernel TB --- 2013-10-07 22:29:10 - CROSS_BUILD_TESTING=YES TB --- 2013-10-07 22:29:10 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-07 22:29:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-07 22:29:10 - SRCCONF=/dev/null TB --- 2013-10-07 22:29:10 - TARGET=amd64 TB --- 2013-10-07 22:29:10 - TARGET_ARCH=amd64 TB --- 2013-10-07 22:29:10 - TZ=UTC TB --- 2013-10-07 22:29:10 - __MAKE_CONF=/dev/null TB --- 2013-10-07 22:29:10 - cd /src TB --- 2013-10-07 22:29:10 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Mon Oct 7 22:29:10 UTC 2013 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg /src/sys/dev/cxgbe/t4_sge.c -I/src/sys/dev/cxgbe /src/sys/dev/cxgbe/t4_sge.c:228:12: error: use of undeclared identifier 'cpu_clflush_line_size' pad = max(cpu_clflush_line_size, 16); ^ /src/sys/dev/cxgbe/t4_sge.c:273:9: error: use of undeclared identifier 'cpu_clflush_line_size' len = cpu_clflush_line_size 64 ? 128 : 64; ^ 2 errors generated. *** Error code 1 Stop. bmake[1]: stopped in /obj/amd64.amd64/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-10-07 22:38:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-10-07 22:38:25 - ERROR: failed to build LINT kernel TB --- 2013-10-07 22:38:25 - 11075.36 user 2371.61 system 14282.78 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
