From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 20 10:50:39 2009 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7823F10656A7; Sun, 20 Dec 2009 10:50:39 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8817A8FC1F; Sun, 20 Dec 2009 10:50:38 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA12223; Sun, 20 Dec 2009 12:34:24 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1NMJ7I-0007iX-8n; Sun, 20 Dec 2009 12:34:24 +0200 Message-ID: <4B2DFD4B.8000006@freebsd.org> Date: Sun, 20 Dec 2009 12:32:43 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091128) MIME-Version: 1.0 To: stable@freebsd.org, amd64@freebsd.org References: <20091219204950.F39471B5078__27076.8647933894$1261255891$gmane$org@freebsd-stable.sentex.ca> In-Reply-To: <20091219204950.F39471B5078__27076.8647933894$1261255891$gmane$org@freebsd-stable.sentex.ca> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 20 Dec 2009 12:33:52 +0000 Cc: Subject: Re: [releng_7 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2009 10:50:39 -0000 on 19/12/2009 22:49 FreeBSD Tinderbox said the following: > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/amd64/amd64/machdep.c > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/amd64/amd64/mca.c > cc1: warnings being treated as errors > /src/sys/amd64/amd64/mca.c: In function 'mca_init': > /src/sys/amd64/amd64/mca.c:510: warning: implicit declaration of function 'CPUID_TO_FAMILY' > /src/sys/amd64/amd64/mca.c:510: warning: nested extern declaration of 'CPUID_TO_FAMILY' > /src/sys/amd64/amd64/mca.c:511: warning: implicit declaration of function 'CPUID_TO_MODEL' > /src/sys/amd64/amd64/mca.c:511: warning: nested extern declaration of 'CPUID_TO_MODEL' My apologies for breaking the build by not being careful enough during MFC. Should be fixed now. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 21 11:06:50 2009 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97B0B106566B for ; Mon, 21 Dec 2009 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6C4638FC26 for ; Mon, 21 Dec 2009 11:06:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBLB6onb004008 for ; Mon, 21 Dec 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBLB6n1C004006 for freebsd-amd64@FreeBSD.org; Mon, 21 Dec 2009 11:06:49 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Dec 2009 11:06:49 GMT Message-Id: <200912211106.nBLB6n1C004006@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org X-Mailman-Approved-At: Mon, 21 Dec 2009 12:30:28 +0000 Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 11:06:50 -0000 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/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze o amd64/141112 amd64 [ata] [panic] Kernel panic when booting with any sATA o amd64/141060 amd64 [install] Can't install 8.0-RELEASE on the server wher o amd64/140715 amd64 [boot] Dell M600 Blade fails to boot 7.2+ 64 bit o amd64/140596 amd64 [panic] Kernel panic/crash o amd64/140391 amd64 [hang] powerd(8) freezes computer on Phenom II compute o amd64/140145 amd64 [boot] Installation boot sequence freezes o amd64/139998 amd64 [panic] 7.2 amd64 panic in kern_mutex.c:339 o amd64/139924 amd64 [boot] cd or dvd not load o amd64/139614 amd64 [minidump] minidumps fail when many interrupts fire f amd64/138661 amd64 [panic] Kernel Panic after typing "reboot" o amd64/138626 amd64 telepites o amd64/138029 amd64 [panic] periodically kernel panic and reboot o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu o amd64/136814 amd64 [mxge] mxge driver error s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/135014 amd64 [padlock] Using padlock(4) in 8-current triggers "fpud o amd64/134978 amd64 [panic] g_up pmap amd64 panic o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT f amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe o amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128810 amd64 AMD 64 port installation o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 102 problems total. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 22 21:40:01 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8886D1065679 for ; Tue, 22 Dec 2009 21:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9F18FC28 for ; Tue, 22 Dec 2009 21:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBMLe12U046159 for ; Tue, 22 Dec 2009 21:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBMLe10Q046158; Tue, 22 Dec 2009 21:40:01 GMT (envelope-from gnats) Resent-Date: Tue, 22 Dec 2009 21:40:01 GMT Resent-Message-Id: <200912222140.nBMLe10Q046158@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Andriy Tovstik Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52FC3106566B for ; Tue, 22 Dec 2009 21:38:24 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 40BB58FC0A for ; Tue, 22 Dec 2009 21:38:24 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nBMLcN1T010456 for ; Tue, 22 Dec 2009 21:38:24 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nBMLcNAo010455; Tue, 22 Dec 2009 21:38:23 GMT (envelope-from nobody) Message-Id: <200912222138.nBMLcNAo010455@www.freebsd.org> Date: Tue, 22 Dec 2009 21:38:23 GMT From: Andriy Tovstik To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Tue, 22 Dec 2009 21:43:57 +0000 Cc: Subject: amd64/141905: pf kernel panic on 7.2-RELEASE with empty pf.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 21:40:01 -0000 >Number: 141905 >Category: amd64 >Synopsis: pf kernel panic on 7.2-RELEASE with empty pf.conf >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 22 21:40:00 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Andriy Tovstik >Release: 7.2-RELEASE-p4 >Organization: RedTram >Environment: uname -a FreeBSD utel-gw.intra 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 08:22:32 UTC 2009 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: i try to load pf on my gateway with empty pf.conf (for testing purposes) and i get a kernel panic every time i try to 'pfctl -d': kgdb message: kgdb kernel.debug /var/crash/vmcore.4 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff80564a3d stack pointer = 0x10:0xfffffffef5f5e6b0 frame pointer = 0x10:0xfffffffef5f5e830 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 35 (nfe0 taskq) trap number = 9 panic: general protection fault cpuid = 0 Uptime: 56m49s Physical memory: 4083 MB Dumping 288 MB: 273 257 241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1 Reading symbols from /boot/kernel/if_bridge.ko...Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_bridge.ko Reading symbols from /boot/kernel/bridgestp.ko...Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. done. Loaded symbols for /boot/kernel/bridgestp.ko Reading symbols from /boot/kernel/pf.ko...Reading symbols from /boot/kernel/pf.ko.symbols...done. done. Loaded symbols for /boot/kernel/pf.ko #0 doadump () at pcpu.h:195 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) list *0xffffffff80564a3d 0xffffffff80564a3d is in m_tag_locate (/usr/src/sys/kern/uipc_mbuf2.c:391). 386 if (t == NULL) 387 p = SLIST_FIRST(&m->m_pkthdr.tags); 388 else 389 p = SLIST_NEXT(t, m_tag_link); 390 while (p != NULL) { 391 if (p->m_tag_cookie == cookie && p->m_tag_id == type) 392 return p; 393 p = SLIST_NEXT(p, m_tag_link); 394 } 395 return NULL; (kgdb) bt #0 doadump () at pcpu.h:195 #1 0x0000000000000004 in ?? () #2 0xffffffff8050df99 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #3 0xffffffff8050e3a2 in panic (fmt=0x104
) at /usr/src/sys/kern/kern_shutdown.c:574 #4 0xffffffff807d2273 in trap_fatal (frame=0xffffff000157f6e0, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:757 #5 0xffffffff807d2dc5 in trap (frame=0xfffffffef5f5e600) at /usr/src/sys/amd64/amd64/trap.c:558 #6 0xffffffff807b70ee in calltrap () at /usr/src/sys/amd64/amd64/exception.S:209 #7 0xffffffff80564a3d in m_tag_locate (m=0xffffff0004cf4300, cookie=0, type=21, t=Variable "t" is not available. ) at /usr/src/sys/kern/uipc_mbuf2.c:390 #8 0xffffffff80e3d7ed in pf_test (dir=2, ifp=0xffffff0001611800, m0=0xfffffffef5f5e890, eh=0x0, inp=0x0) at mbuf.h:957 #9 0xffffffff80e43b55 in pf_check_out (arg=Variable "arg" is not available. ) at /usr/src/sys/modules/pf/../../contrib/pf/net/pf_ioctl.c:3687 #10 0xffffffff805b98c1 in pfil_run_hooks (ph=Variable "ph" is not available. ) at /usr/src/sys/net/pfil.c:78 #11 0xffffffff805f46eb in ip_output (m=0xffffff0004cf4300, opt=Variable "opt" is not available. ) at /usr/src/sys/netinet/ip_output.c:443 #12 0xffffffff805e99bb in in_gif_output (ifp=0xffffff0004756800, family=Variable "family" is not available. ) at /usr/src/sys/netinet/in_gif.c:244 #13 0xffffffff805b083f in gif_output (ifp=0xffffff0004756800, m=0xffffff0004b9ac00, dst=0xffffff0004792590, rt=Variable "rt" is not available. ) at /usr/src/sys/net/if_gif.c:455 #14 0xffffffff805b0c09 in gif_start (ifp=0xffffff0004756800) at /usr/src/sys/net/if_gif.c:351 #15 0xffffffff80e26023 in bridge_forward (sc=0xffffff0004721c00, sbif=Variable "sbif" is not available. ) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2083 #16 0xffffffff80e2653f in bridge_input (ifp=0xffffff0001611000, m=0xffffff0004b9ac00) at /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2287 #17 0xffffffff805ae407 in ether_input (ifp=0xffffff0001611000, m=0xffffff0004b9ac00) at /usr/src/sys/net/if_ethersubr.c:655 #18 0xffffffff807fca8d in nfe_int_task (arg=Variable "arg" is not available. ) at /usr/src/sys/dev/nfe/if_nfe.c:2116 #19 0xffffffff80545efd in taskqueue_run (queue=0xffffff0004500380) at /usr/src/sys/kern/subr_taskqueue.c:282 #20 0xffffffff8054618e in taskqueue_thread_loop (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/subr_taskqueue.c:401 #21 0xffffffff804ea993 in fork_exit (callout=0xffffffff80546140 , arg=0xfffffffe8022e1c8, frame=0xfffffffef5f5ec80) at /usr/src/sys/kern/kern_fork.c:810 #22 0xffffffff807b74ae in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:455 #23 0x0000000000000000 in ?? () #47 0x0000000000cf9000 in ?? () #48 0xffffffff80b325c0 in tdg_maxid () #49 0xffffffff80b3edc0 in tdq_cpu () #50 0xffffffff80b40830 in sleepq_chains () #51 0xffffff000157f6e0 in ?? () #52 0xffffff000157fa10 in ?? () #53 0xfffffffef5f5eb08 in ?? () #54 0xffffff000157f6e0 in ?? () #55 0xffffffff80531608 in sched_switch (td=0xffffffff80546140, newtd=0x800533350, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1938 #123 0x0000000000000000 in ?? () Cannot access memory at address 0xfffffffef5f5f000 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 22 22:32:05 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AEFE106566B; Tue, 22 Dec 2009 22:32:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 31BFD8FC1B; Tue, 22 Dec 2009 22:32:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBMMW52I000100; Tue, 22 Dec 2009 22:32:05 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBMMW5un099995; Tue, 22 Dec 2009 22:32:05 GMT (envelope-from linimon) Date: Tue, 22 Dec 2009 22:32:05 GMT Message-Id: <200912222232.nBMMW5un099995@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-pf@FreeBSD.org From: linimon@FreeBSD.org X-Mailman-Approved-At: Tue, 22 Dec 2009 22:49:56 +0000 Cc: Subject: Re: kern/141905: [pf] [panic] pf kernel panic on 7.2-RELEASE with empty pf.conf X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 22:32:05 -0000 Old Synopsis: pf kernel panic on 7.2-RELEASE with empty pf.conf New Synopsis: [pf] [panic] pf kernel panic on 7.2-RELEASE with empty pf.conf Responsible-Changed-From-To: freebsd-amd64->freebsd-pf Responsible-Changed-By: linimon Responsible-Changed-When: Tue Dec 22 22:31:27 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141905 From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 23 05:37:08 2009 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53C28106568B; Wed, 23 Dec 2009 05:37:08 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 2B82C8FC0A; Wed, 23 Dec 2009 05:37:07 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nBN5b7LD018266; Wed, 23 Dec 2009 00:37:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nBN5b7T2018243; Wed, 23 Dec 2009 05:37:07 GMT (envelope-from tinderbox@freebsd.org) Date: Wed, 23 Dec 2009 05:37:07 GMT Message-Id: <200912230537.nBN5b7T2018243@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 05:37:08 -0000 TB --- 2009-12-23 04:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-12-23 04:00:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-12-23 04:00:00 - cleaning the object tree TB --- 2009-12-23 04:00:26 - cvsupping the source tree TB --- 2009-12-23 04:00:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-12-23 04:00:55 - building world TB --- 2009-12-23 04:00:55 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-23 04:00:55 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-23 04:00:55 - TARGET=amd64 TB --- 2009-12-23 04:00:55 - TARGET_ARCH=amd64 TB --- 2009-12-23 04:00:55 - TZ=UTC TB --- 2009-12-23 04:00:55 - __MAKE_CONF=/dev/null TB --- 2009-12-23 04:00:55 - cd /src TB --- 2009-12-23 04:00:55 - /usr/bin/make -B buildworld >>> World build started on Wed Dec 23 04:00:56 UTC 2009 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Wed Dec 23 05:26:21 UTC 2009 TB --- 2009-12-23 05:26:21 - generating LINT kernel config TB --- 2009-12-23 05:26:21 - cd /src/sys/amd64/conf TB --- 2009-12-23 05:26:21 - /usr/bin/make -B LINT TB --- 2009-12-23 05:26:21 - building LINT kernel TB --- 2009-12-23 05:26:21 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-23 05:26:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-23 05:26:21 - TARGET=amd64 TB --- 2009-12-23 05:26:21 - TARGET_ARCH=amd64 TB --- 2009-12-23 05:26:21 - TZ=UTC TB --- 2009-12-23 05:26:21 - __MAKE_CONF=/dev/null TB --- 2009-12-23 05:26:21 - cd /src TB --- 2009-12-23 05:26:21 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Dec 23 05:26:21 UTC 2009 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet/ip_ecn.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet/ip_encap.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet/ip_fastfwd.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netinet/ipfw/ip_fw2.c -I/src/sys/contrib/pf cc1: warnings being treated as errors /src/sys/netinet/ipfw/ip_fw2.c: In function 'ipfw_chk': /src/sys/netinet/ipfw/ip_fw2.c:1977: warning: cast from pointer to integer of different size /src/sys/netinet/ipfw/ip_fw2.c:1978: warning: cast from pointer to integer of different size *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-12-23 05:37:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-12-23 05:37:07 - ERROR: failed to build lint kernel TB --- 2009-12-23 05:37:07 - 4340.70 user 968.73 system 5826.84 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 23 17:40:03 2009 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E32C106568F for ; Wed, 23 Dec 2009 17:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 09E308FC0C for ; Wed, 23 Dec 2009 17:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBNHe20F080506 for ; Wed, 23 Dec 2009 17:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBNHe2t5080505; Wed, 23 Dec 2009 17:40:02 GMT (envelope-from gnats) Date: Wed, 23 Dec 2009 17:40:02 GMT Message-Id: <200912231740.nBNHe2t5080505@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Mas Vio X-Mailman-Approved-At: Wed, 23 Dec 2009 17:49:35 +0000 Cc: Subject: Re: amd64/140715: [boot] Dell M600 Blade fails to boot 7.2 64 bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mas Vio List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 17:40:03 -0000 The following reply was made to PR amd64/140715; it has been noted by GNATS. From: Mas Vio To: freebsd-gnats-submit@FreeBSD.org, cliff.spradlin@gmail.com Cc: Subject: Re: amd64/140715: [boot] Dell M600 Blade fails to boot 7.2 64 bit Date: Thu, 24 Dec 2009 00:08:30 +0700 --001485e8aca027739e047b685f7c Content-Type: text/plain; charset=ISO-8859-1 add this hint.acpi.0.disabled="1" to /boot/device.hints but it makes status on CMC to be blinking anybody can solve this problem? --001485e8aca027739e047b685f7c Content-Type: text/html; charset=ISO-8859-1 add this hint.acpi.0.disabled="1" to /boot/device.hints
but it makes status on CMC to be blinking
anybody can solve this problem?
--001485e8aca027739e047b685f7c-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 24 18:49:29 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DF3A1065672 for ; Thu, 24 Dec 2009 18:49:29 +0000 (UTC) (envelope-from grimjow.smitty@gmail.com) Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx1.freebsd.org (Postfix) with ESMTP id 5638B8FC2C for ; Thu, 24 Dec 2009 18:49:29 +0000 (UTC) Received: by pzk15 with SMTP id 15so5701387pzk.3 for ; Thu, 24 Dec 2009 10:49:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=47g0lVbGAdIUNlYB+w9vjPTYpV4FWUDr60g5QDBHr2I=; b=e60pul3e1q9+ylVEovlmOGiaklVULKEG2Q42Y/nmyU0ZfBpLsBsfEQDyrF6tU05Zm/ g8N1yNVSchFFZsD6twro91FIEyTqDg79Z2Nlr8aZZLSbFWmtQw3QxMjqc174SdKES3TM MQ9tg26+yVgZiCEHoAd8w3ZbRmHqAcjTTsErg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=n9i0dptEdXGFe891+iuTQG6xLZ7L8Q3vIRMHtyRQTwX+F+PliX8OG9CZ0gC6s9tQpp ibktR7enjRQOluTxHiB07gNMIlty4oh1M5L7xlUrtgANeYo01biFnyLVOkt8dkD4pzxG oYg5eF0oI80HcAlwlUk2LMEi3xq23Idvijv4A= MIME-Version: 1.0 Received: by 10.142.55.20 with SMTP id d20mr7738063wfa.322.1261678732529; Thu, 24 Dec 2009 10:18:52 -0800 (PST) Date: Thu, 24 Dec 2009 10:18:52 -0800 Message-ID: From: grimjow espada To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: question about installing msi netbook from usb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 18:49:29 -0000 *Hello i tried creating a usb bootable for 8.0-RELEASE-amd64-disc1 and 8.0-RELEASE-amd64-bootonly using MS netbootin but i always get this error. My MSI netbook specs are below, anyone tried installing with this netbook? Invalid* or corrupt *kernel image * *AMD=AE* Yukon AMD Athlon=99 Neo X2 *Dual-Core* L335 1.6GHz Processor 320 GB sata 2 GB ram ATI Radeon X1270 shared upto 700MB From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 24 19:25:02 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B877E106566B for ; Thu, 24 Dec 2009 19:25:02 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout5.freenet.de (mout5.freenet.de [IPv6:2001:748:100:40::2:7]) by mx1.freebsd.org (Postfix) with ESMTP id 503D68FC21 for ; Thu, 24 Dec 2009 19:25:02 +0000 (UTC) Received: from [195.4.92.11] (helo=1.mx.freenet.de) by mout5.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1NNtIz-0007NI-5A; Thu, 24 Dec 2009 20:25:01 +0100 Received: from p57ae1ba3.dip0.t-ipconnect.de ([87.174.27.163]:19358 helo=ernst.jennejohn.org) by 1.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1NNtIy-0002GO-Dt; Thu, 24 Dec 2009 20:25:00 +0100 Date: Thu, 24 Dec 2009 20:24:58 +0100 From: Gary Jennejohn To: grimjow espada Message-ID: <20091224202458.7148873b@ernst.jennejohn.org> In-Reply-To: References: X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.2; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: question about installing msi netbook from usb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 19:25:02 -0000 On Thu, 24 Dec 2009 10:18:52 -0800 grimjow espada wrote: > *Hello i tried creating a usb bootable for 8.0-RELEASE-amd64-disc1 and > 8.0-RELEASE-amd64-bootonly using MS netbootin but i always get this error. > My MSI netbook specs are below, anyone tried installing with this netbook? > > Invalid* or corrupt *kernel image > > > * > > *AMD__* Yukon AMD Athlon___ Neo X2 *Dual-Core* L335 1.6GHz Processor > > 320 GB sata > > 2 GB ram > > ATI Radeon X1270 shared upto 700MB So, why don't you use something like ftp://ftp.tw.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/8.0/8.0-RELEASE-amd64-memstick.img which already _is_ a USB stick image? --- Gary Jennejohn From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 25 11:41:01 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F22921065695 for ; Fri, 25 Dec 2009 11:41:01 +0000 (UTC) (envelope-from benny.goemans@belgacom.net) Received: from louis.schedom-europe.net (louis.schedom-europe.net [193.109.184.93]) by mx1.freebsd.org (Postfix) with ESMTP id 52DCF8FC24 for ; Fri, 25 Dec 2009 11:41:01 +0000 (UTC) Received: (qmail 1424 invoked by uid 507); 25 Dec 2009 12:14:21 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on louis.schedom-europe.net X-Spam-Level: *********** X-Spam-Status: No, score=11.7 required=15.0 tests=BAYES_99,HELO_LH_HOME, RCVD_IN_PBL,RDNS_DYNAMIC autolearn=disabled version=3.2.5 Received: from ip184.dyn3.bkc3.schedom-europe.net (HELO bennypc.home) (83.101.50.184) by louis.schedom-europe.net with SMTP; 25 Dec 2009 12:14:15 +0100 From: Benny Goemans To: freebsd-amd64@freebsd.org Date: Fri, 25 Dec 2009 12:14:19 +0100 User-Agent: KMail/1.12.4 (FreeBSD/8.0-RELEASE; KDE/4.3.4; i386; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200912251214.19788.benny.goemans@belgacom.net> Subject: Intel Matrixraid on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 11:41:02 -0000 Hi, I'm running 8.0-release (i386) on a Asus P5WDG2 motherboard with integrated Intel Matrixraid (software raid) controller. Everything runs fine in this one. Since I've noticed 64 bit support for the Nvidia driver I've been trying to install the AMD64 8.0 version. During install dmesg shows my hard drives and raid drives (ar0, ar1) perfectly, just as it does in the i386 version. But when I enter sysinstall it can't locate my drive(s). It just doesn't find a single drive, no arN but also no hdaN (which do show up in dmesg). Has anyone seen this behaviour before and is there some kind of solution? Maybe some parameters to sysinstall, extra kernel modules to load that are on the install disk or something? Kind regards, Benny Goemans ps. I'm currently redownloading the iso file for the cd and will check its checksum to make sure I don't have some bizarre bad download From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 25 17:33:19 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B09D1065679 for ; Fri, 25 Dec 2009 17:33:19 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from mail.deployis.eu (mail.deployis.eu [217.20.135.253]) by mx1.freebsd.org (Postfix) with ESMTP id CCE288FC13 for ; Fri, 25 Dec 2009 17:33:17 +0000 (UTC) Received: from localhost ([127.0.0.1]:44047 helo=mail.deployis.eu) by mail.deployis.eu with esmtp (Exim 4.69 #1 (Debian)) id 1NOE01-0005uA-QF from ; Fri, 25 Dec 2009 18:30:50 +0100 Received: from 188.156.82.138 (SquirrelMail authenticated user andrej@antiszoc.hu) by mail.deployis.eu with HTTP; Fri, 25 Dec 2009 18:30:49 +0100 (CET) Message-ID: <40504.188.156.82.138.1261762249.squirrel@mail.deployis.eu> In-Reply-To: <200912251214.19788.benny.goemans@belgacom.net> References: <200912251214.19788.benny.goemans@belgacom.net> Date: Fri, 25 Dec 2009 18:30:49 +0100 (CET) From: =?iso-8859-2?Q?G=F3t_Andr=E1s?= To: "Benny Goemans" User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Spam-Score-deployiseu: -23 Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Matrixraid on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 17:33:19 -0000 Hi, I strongly advise against any of these "raid solutions". I got a very rough weekend beacuse of the nvidia raid. Here's the short story. I got our new webserver with S939 Opteron and the matched nvidia chipset. That time FreeBSD 6.1 was the actual, so that was installed. When installing I noticed that the motherboard raid works with FreeBSD so I went with it. It turned out that it's completely transparent so I was happy thinking that a simple solution is not likely to go wrong. On a weekend I went for the planned maintenance to the coloc facility. When the reboot came the motherboard nvidia raid told me that I have a failed Raid1 with one disk. The problem was that after this it refused to boot anymore. Later it turned out that somewhy 2 weeks ago! the nvidia raid dropped one disk and that left in that state (it was mountable, readable quite well etc.) and the other had the actual data. Both disk was replaced then beacause I told myself that at least I'd like to gain something out this huge downtime. Since then gmirror was used and tried what it would do if I take out one this. Gmirror handled it quite well, I got a message in the log about the disk failure and everything went on. With the software raid the nvidia controller or the disk backplane lost one disk after half a year of uptime but a reboot corrected it. (There was a small thread about this that time on a FreeBSD maillist.) On Pén, December 25, 2009 12:14 pm, Benny Goemans wrote: > Hi, > > > I'm running 8.0-release (i386) on a Asus P5WDG2 motherboard with > integrated Intel Matrixraid (software raid) controller. Everything runs > fine in this one. > > Since I've noticed 64 bit support for the Nvidia driver I've been trying > to install the AMD64 8.0 version. During install dmesg shows my hard > drives and raid drives (ar0, ar1) perfectly, just as it does in the i386 > version. But when I enter sysinstall it can't locate my drive(s). It just > doesn't find a single drive, no arN but also no hdaN (which do show up in > dmesg). > > Has anyone seen this behaviour before and is there some kind of solution? > Maybe some parameters to sysinstall, extra kernel modules to load that > are on the install disk or something? > > Kind regards, > > > Benny Goemans > > > ps. I'm currently redownloading the iso file for the cd and will check > its checksum to make sure I don't have some bizarre bad download > _______________________________________________ > 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 owner-freebsd-amd64@FreeBSD.ORG Sat Dec 26 17:40:09 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 061E4106568B for ; Sat, 26 Dec 2009 17:40:09 +0000 (UTC) (envelope-from benny.goemans@belgacom.net) Received: from bente.schedom-europe.net (bente.schedom-europe.net [193.109.184.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6E1F48FC08 for ; Sat, 26 Dec 2009 17:40:07 +0000 (UTC) Received: (qmail 20142 invoked by uid 507); 26 Dec 2009 18:40:07 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bente.schedom-europe.net X-Spam-Level: *********** X-Spam-Status: No, score=11.7 required=15.0 tests=BAYES_99,HELO_LH_HOME, RCVD_IN_PBL,RDNS_DYNAMIC autolearn=disabled version=3.2.5 Received: from ip184.dyn3.bkc3.schedom-europe.net (HELO bennypc.home) (83.101.50.184) by bente.schedom-europe.net with SMTP; 26 Dec 2009 18:40:02 +0100 From: Benny Goemans To: =?iso-8859-2?q?G=F3t_Andr=E1s?= Date: Sat, 26 Dec 2009 18:40:01 +0100 User-Agent: KMail/1.12.4 (FreeBSD/8.0-RELEASE; KDE/4.3.4; i386; ; ) References: <200912251214.19788.benny.goemans@belgacom.net> <40504.188.156.82.138.1261762249.squirrel@mail.deployis.eu> In-Reply-To: <40504.188.156.82.138.1261762249.squirrel@mail.deployis.eu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Message-Id: <200912261840.01861.benny.goemans@belgacom.net> Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Matrixraid on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 17:40:09 -0000 Hi Andr=E1s, I am indeed aware of the risk that these kind of raid solutions bring with= =20 them and if I would do the whole system anew I would just buy a separate ra= id=20 controller. The thing is that there's now around 1TB of data in a raid configuration si= nce=20 one or two years and I can't change raid controllers easily. This is=20 especially hard since it's a tri boot system (windows, freebsd and a test-o= s). But I suppose that the driver is expected to work on amd64 just as it is on= =20 i386, isn't it? After all everything is showing up fine, it just seems to b= e=20 that sysinstall has a problem using it (maybe the kernel but I'll do some m= ore=20 tests to confirm). Regards, Benny Goemans On Friday 25 December 2009 18:30:49 G=F3t Andr=E1s wrote: > Hi, >=20 > I strongly advise against any of these "raid solutions". I got a very > rough weekend beacuse of the nvidia raid. Here's the short story. >=20 > I got our new webserver with S939 Opteron and the matched nvidia chipset. > That time FreeBSD 6.1 was the actual, so that was installed. When > installing I noticed that the motherboard raid works with FreeBSD so I > went with it. It turned out that it's completely transparent so I was > happy thinking that a simple solution is not likely to go wrong. >=20 > On a weekend I went for the planned maintenance to the coloc facility. > When the reboot came the motherboard nvidia raid told me that I have a > failed Raid1 with one disk. The problem was that after this it refused to > boot anymore. Later it turned out that somewhy 2 weeks ago! the nvidia > raid dropped one disk and that left in that state (it was mountable, > readable quite well etc.) and the other had the actual data. >=20 > Both disk was replaced then beacause I told myself that at least I'd like > to gain something out this huge downtime. Since then gmirror was used and > tried what it would do if I take out one this. Gmirror handled it quite > well, I got a message in the log about the disk failure and everything > went on. With the software raid the nvidia controller or the disk > backplane lost one disk after half a year of uptime but a reboot corrected > it. (There was a small thread about this that time on a FreeBSD maillist.) >=20 > On P=E9n, December 25, 2009 12:14 pm, Benny Goemans wrote: > > Hi, > > > > > > I'm running 8.0-release (i386) on a Asus P5WDG2 motherboard with > > integrated Intel Matrixraid (software raid) controller. Everything runs > > fine in this one. > > > > Since I've noticed 64 bit support for the Nvidia driver I've been trying > > to install the AMD64 8.0 version. During install dmesg shows my hard > > drives and raid drives (ar0, ar1) perfectly, just as it does in the i3= 86 > > version. But when I enter sysinstall it can't locate my drive(s). It ju= st > > doesn't find a single drive, no arN but also no hdaN (which do show up = in > > dmesg). > > > > Has anyone seen this behaviour before and is there some kind of solutio= n? > > Maybe some parameters to sysinstall, extra kernel modules to load that > > are on the install disk or something? > > > > Kind regards, > > > > > > Benny Goemans > > > > > > ps. I'm currently redownloading the iso file for the cd and will check > > its checksum to make sure I don't have some bizarre bad download > > _______________________________________________ > > 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" >=20 From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 26 20:13:49 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 548FE106566C for ; Sat, 26 Dec 2009 20:13:49 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from mail.deployis.eu (mail.deployis.eu [217.20.135.253]) by mx1.freebsd.org (Postfix) with ESMTP id D4E598FC0C for ; Sat, 26 Dec 2009 20:13:48 +0000 (UTC) Received: from localhost ([127.0.0.1]:36461 helo=mail.deployis.eu) by mail.deployis.eu with esmtp (Exim 4.69 #1 (Debian)) id 1NOcys-0001NF-SM from ; Sat, 26 Dec 2009 21:11:19 +0100 Received: from 188.157.44.137 (SquirrelMail authenticated user andrej@antiszoc.hu) by mail.deployis.eu with HTTP; Sat, 26 Dec 2009 21:11:18 +0100 (CET) Message-ID: <50505.188.157.44.137.1261858278.squirrel@mail.deployis.eu> In-Reply-To: <200912261840.01861.benny.goemans@belgacom.net> References: <200912251214.19788.benny.goemans@belgacom.net> <40504.188.156.82.138.1261762249.squirrel@mail.deployis.eu> <200912261840.01861.benny.goemans@belgacom.net> Date: Sat, 26 Dec 2009 21:11:18 +0100 (CET) From: =?iso-8859-2?Q?G=F3t_Andr=E1s?= To: "Benny Goemans" User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Spam-Score-deployiseu: -17 Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Matrixraid on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 20:13:49 -0000 Hi, I had this issue on an AMD64 FreeBSD installed machine. My problem was not with the freebsd driver. I assume it was working as written (FreeBSD stuff is quite well documented and working as documented). The real problem came at the reboot. I'd suggest to go with gmirror which is a transparent solution, so you can mount your drives separately also. Imho, take a look at you config and if it's a transparent raid1 setup, just migrate easily to gmirror. For a RAID1 config you won't get much more speed with a real and relatively expensive raid card. Yes, maybe I got paranoid after that hard weekend and also know that intel stuff works much better than nvidia when came to chipsets and the like. But I'd not give my data to a half-solution. Andras On Szo, December 26, 2009 6:40 pm, Benny Goemans wrote: > Hi András, > > > I am indeed aware of the risk that these kind of raid solutions bring > with them and if I would do the whole system anew I would just buy a > separate raid controller. The thing is that there's now around 1TB of data > in a raid configuration since one or two years and I can't change raid > controllers easily. This is especially hard since it's a tri boot system > (windows, freebsd and a test-os). > > > But I suppose that the driver is expected to work on amd64 just as it is > on i386, isn't it? After all everything is showing up fine, it just seems > to be that sysinstall has a problem using it (maybe the kernel but I'll do > some more tests to confirm). > > Regards, > > > Benny Goemans > > > On Friday 25 December 2009 18:30:49 Gót András wrote: > >> Hi, >> >> >> I strongly advise against any of these "raid solutions". I got a very >> rough weekend beacuse of the nvidia raid. Here's the short story. >> >> I got our new webserver with S939 Opteron and the matched nvidia >> chipset. That time FreeBSD 6.1 was the actual, so that was installed. >> When >> installing I noticed that the motherboard raid works with FreeBSD so I >> went with it. It turned out that it's completely transparent so I was >> happy thinking that a simple solution is not likely to go wrong. >> >> On a weekend I went for the planned maintenance to the coloc facility. >> When the reboot came the motherboard nvidia raid told me that I have a >> failed Raid1 with one disk. The problem was that after this it refused >> to boot anymore. Later it turned out that somewhy 2 weeks ago! the >> nvidia raid dropped one disk and that left in that state (it was >> mountable, readable quite well etc.) and the other had the actual data. >> >> Both disk was replaced then beacause I told myself that at least I'd >> like to gain something out this huge downtime. Since then gmirror was >> used and tried what it would do if I take out one this. Gmirror handled >> it quite well, I got a message in the log about the disk failure and >> everything went on. With the software raid the nvidia controller or the >> disk backplane lost one disk after half a year of uptime but a reboot >> corrected it. (There was a small thread about this that time on a >> FreeBSD maillist.) >> >> >> On Pén, December 25, 2009 12:14 pm, Benny Goemans wrote: >> >>> Hi, >>> >>> >>> >>> I'm running 8.0-release (i386) on a Asus P5WDG2 motherboard with >>> integrated Intel Matrixraid (software raid) controller. Everything >>> runs fine in this one. >>> >>> Since I've noticed 64 bit support for the Nvidia driver I've been >>> trying to install the AMD64 8.0 version. During install dmesg shows my >>> hard drives and raid drives (ar0, ar1) perfectly, just as it does in >>> the i386 version. But when I enter sysinstall it can't locate my >>> drive(s). It just doesn't find a single drive, no arN but also no hdaN >>> (which do show up in >>> dmesg). >>> >>> Has anyone seen this behaviour before and is there some kind of >>> solution? Maybe some parameters to sysinstall, extra kernel modules to >>> load that are on the install disk or something? >>> >>> Kind regards, >>> >>> >>> >>> Benny Goemans >>> >>> >>> >>> ps. I'm currently redownloading the iso file for the cd and will >>> check its checksum to make sure I don't have some bizarre bad download >>> _______________________________________________ >>> 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 owner-freebsd-amd64@FreeBSD.ORG Sat Dec 26 20:40:46 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFE4A106568B for ; Sat, 26 Dec 2009 20:40:46 +0000 (UTC) (envelope-from benny.goemans@belgacom.net) Received: from silke.schedom-europe.net (silke.schedom-europe.net [193.109.184.88]) by mx1.freebsd.org (Postfix) with ESMTP id 437AE8FC17 for ; Sat, 26 Dec 2009 20:40:45 +0000 (UTC) Received: (qmail 19933 invoked by uid 507); 26 Dec 2009 21:40:45 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on silke.schedom-europe.net X-Spam-Level: *********** X-Spam-Status: No, score=11.7 required=15.0 tests=BAYES_99,HELO_LH_HOME, RCVD_IN_PBL,RDNS_DYNAMIC autolearn=disabled version=3.2.5 Received: from ip184.dyn3.bkc3.schedom-europe.net (HELO bennypc.home) (83.101.50.184) by silke.schedom-europe.net with SMTP; 26 Dec 2009 21:40:38 +0100 From: Benny Goemans To: =?iso-8859-2?q?G=F3t_Andr=E1s?= Date: Sat, 26 Dec 2009 21:40:38 +0100 User-Agent: KMail/1.12.4 (FreeBSD/8.0-RELEASE; KDE/4.3.4; i386; ; ) References: <200912251214.19788.benny.goemans@belgacom.net> <200912261840.01861.benny.goemans@belgacom.net> <50505.188.157.44.137.1261858278.squirrel@mail.deployis.eu> In-Reply-To: <50505.188.157.44.137.1261858278.squirrel@mail.deployis.eu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Message-Id: <200912262140.38423.benny.goemans@belgacom.net> Cc: freebsd-amd64@freebsd.org Subject: Re: Intel Matrixraid on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 20:40:46 -0000 Hi, well, it's actually 4 disks in a mixed RAID 5 and RAID 0 solution. The data= on=20 the RAID 0 can be easily replaced, the important data and operating systems= =20 are on a RAID 5. On this RAID 5 there are multiple OS's running so there's = no=20 easy solution to migrating. I know the Intel setup may be risky but it's been setup as-is and I really= =20 can't risk changing the setup itself at the moment (reinstalling all OS's=20 etc). And until now it's been working nicely from 6.0-RELEASE up to 8.0- RELEASE, all i386 architecture. Now I just need the AMD64 architecture up-a= nd- running :) So I'm hoping this is some easily fixable thing. I should also be able to=20 supply the necessary debugging info to whoever needs it. Regards, Benny Goemans On Saturday 26 December 2009 21:11:18 G=F3t Andr=E1s wrote: > Hi, >=20 > I had this issue on an AMD64 FreeBSD installed machine. My problem was not > with the freebsd driver. I assume it was working as written (FreeBSD stuff > is quite well documented and working as documented). The real problem came > at the reboot. I'd suggest to go with gmirror which is a transparent > solution, so you can mount your drives separately also. >=20 > Imho, take a look at you config and if it's a transparent raid1 setup, > just migrate easily to gmirror. For a RAID1 config you won't get much more > speed with a real and relatively expensive raid card. >=20 > Yes, maybe I got paranoid after that hard weekend and also know that intel > stuff works much better than nvidia when came to chipsets and the like. > But I'd not give my data to a half-solution. >=20 > Andras >=20 > On Szo, December 26, 2009 6:40 pm, Benny Goemans wrote: > > Hi Andr=E1s, > > > > > > I am indeed aware of the risk that these kind of raid solutions bring > > with them and if I would do the whole system anew I would just buy a > > separate raid controller. The thing is that there's now around 1TB of > > data in a raid configuration since one or two years and I can't change > > raid controllers easily. This is especially hard since it's a tri boot > > system (windows, freebsd and a test-os). > > > > > > But I suppose that the driver is expected to work on amd64 just as it is > > on i386, isn't it? After all everything is showing up fine, it just see= ms > > to be that sysinstall has a problem using it (maybe the kernel but I'll > > do some more tests to confirm). > > > > Regards, > > > > > > Benny Goemans > > > > On Friday 25 December 2009 18:30:49 G=F3t Andr=E1s wrote: > >> Hi, > >> > >> > >> I strongly advise against any of these "raid solutions". I got a very > >> rough weekend beacuse of the nvidia raid. Here's the short story. > >> > >> I got our new webserver with S939 Opteron and the matched nvidia > >> chipset. That time FreeBSD 6.1 was the actual, so that was installed. > >> When > >> installing I noticed that the motherboard raid works with FreeBSD so I > >> went with it. It turned out that it's completely transparent so I was > >> happy thinking that a simple solution is not likely to go wrong. > >> > >> On a weekend I went for the planned maintenance to the coloc facility. > >> When the reboot came the motherboard nvidia raid told me that I have a > >> failed Raid1 with one disk. The problem was that after this it refused > >> to boot anymore. Later it turned out that somewhy 2 weeks ago! the > >> nvidia raid dropped one disk and that left in that state (it was > >> mountable, readable quite well etc.) and the other had the actual data. > >> > >> Both disk was replaced then beacause I told myself that at least I'd > >> like to gain something out this huge downtime. Since then gmirror was > >> used and tried what it would do if I take out one this. Gmirror handled > >> it quite well, I got a message in the log about the disk failure and > >> everything went on. With the software raid the nvidia controller or the > >> disk backplane lost one disk after half a year of uptime but a reboot > >> corrected it. (There was a small thread about this that time on a > >> FreeBSD maillist.) > >> > >> On P=E9n, December 25, 2009 12:14 pm, Benny Goemans wrote: > >>> Hi, > >>> > >>> > >>> > >>> I'm running 8.0-release (i386) on a Asus P5WDG2 motherboard with > >>> integrated Intel Matrixraid (software raid) controller. Everything > >>> runs fine in this one. > >>> > >>> Since I've noticed 64 bit support for the Nvidia driver I've been > >>> trying to install the AMD64 8.0 version. During install dmesg shows my > >>> hard drives and raid drives (ar0, ar1) perfectly, just as it does in > >>> the i386 version. But when I enter sysinstall it can't locate my > >>> drive(s). It just doesn't find a single drive, no arN but also no hdaN > >>> (which do show up in > >>> dmesg). > >>> > >>> Has anyone seen this behaviour before and is there some kind of > >>> solution? Maybe some parameters to sysinstall, extra kernel modules to > >>> load that are on the install disk or something? > >>> > >>> Kind regards, > >>> > >>> > >>> > >>> Benny Goemans > >>> > >>> > >>> > >>> ps. I'm currently redownloading the iso file for the cd and will > >>> check its checksum to make sure I don't have some bizarre bad download > >>> _______________________________________________ > >>> 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" >=20