From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 18 01:58:40 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B2E016A41F; Sun, 18 Dec 2005 01:58:40 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B272A43D4C; Sun, 18 Dec 2005 01:58:39 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jBI1wcab072342; Sat, 17 Dec 2005 20:58:38 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jBI1wcYl077044; Sat, 17 Dec 2005 20:58:38 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 37E627302F; Sat, 17 Dec 2005 20:58:38 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051218015838.37E627302F@freebsd-current.sentex.ca> Date: Sat, 17 Dec 2005 20:58:38 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 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: Sun, 18 Dec 2005 01:58:40 -0000 TB --- 2005-12-18 01:14:03 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-18 01:14:03 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-18 01:14:03 - cleaning the object tree TB --- 2005-12-18 01:14:41 - checking out the source tree TB --- 2005-12-18 01:14:41 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-18 01:14:41 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-18 01:20:51 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-18 01:20:51 - cd /src TB --- 2005-12-18 01:20:51 - /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 [...] cc -O2 -pipe -c /src/libexec/rshd/rshd.c cc -O2 -pipe -o rshd rshd.o -lutil -lpam gzip -cn /src/libexec/rshd/rshd.8 > rshd.8.gz ===> libexec/rtld-elf (all) cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/amd64 -I/src/libexec/rtld-elf -elf -fpic -DPIC -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/amd64/rtld_start.S cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/amd64 -I/src/libexec/rtld-elf -elf -fpic -DPIC -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/amd64/reloc.c /src/libexec/rtld-elf/amd64/reloc.c: In function `reloc_non_plt': /src/libexec/rtld-elf/amd64/reloc.c:317: warning: int format, different type arg (arg 3) *** Error code 1 Stop in /src/libexec/rtld-elf. *** Error code 1 Stop in /src/libexec. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-18 01:58:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-18 01:58:37 - ERROR: failed to build world TB --- 2005-12-18 01:58:37 - tinderbox aborted TB --- 1.38 user 6.56 system 2674.55 real From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 18 10:35:17 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1000916A422 for ; Sun, 18 Dec 2005 10:35:17 +0000 (GMT) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id C59DF43D55 for ; Sun, 18 Dec 2005 10:35:11 +0000 (GMT) (envelope-from michiel@boland.org) Received: from brakkenstein.nijmegen.internl.net by neerbosch.nijmegen.internl.net via brakkenstein.nijmegen.internl.net [217.149.193.41] with ESMTP id jBIAZA1D010553 (8.13.2/1.4); Sun, 18 Dec 2005 11:35:10 +0100 (MET) Received: from localhost by brakkenstein.nijmegen.internl.net via mboland@localhost with ESMTP id jBIAZAvR029802 (8.13.2/2.02); Sun, 18 Dec 2005 11:35:10 +0100 (MET) X-Authentication-Warning: brakkenstein.nijmegen.internl.net: mboland owned process doing -bs Date: Sun, 18 Dec 2005 11:35:10 +0100 (MET) From: Michiel Boland To: Valery In-Reply-To: <439D354D.1000007@vslash.com> Message-ID: References: <439D354D.1000007@vslash.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: Supported Hardwre : Sun X2100 ? 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, 18 Dec 2005 10:35:17 -0000 On Mon, 12 Dec 2005, Valery wrote: > Dear all, > a simple question, is the recent Sun X2100 Servers > family (AMD Opteron 148,152,175 / SATA) planned to be > supported, or simply, does FreeBSD 6.x run whithout > trouble on this kind of system ? 6.x installs and runs just fine on an x2100. As long as you don't use the NVIDIA NIC. Luckily, these boxes have a Broadcom as well. Cheers Michiel From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 18 10:44:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7937916A41F for ; Sun, 18 Dec 2005 10:44:36 +0000 (GMT) (envelope-from valery@vslash.com) Received: from mail.vslash.com (bgl93-1-82-67-185-6.fbx.proxad.net [82.67.185.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A259243D46 for ; Sun, 18 Dec 2005 10:44:35 +0000 (GMT) (envelope-from valery@vslash.com) Received: from [192.168.0.22] (oxe.intranet.vslash.com [192.168.0.22]) by mail.vslash.com (Postfix) with ESMTP id 0D1DD8441B; Sun, 18 Dec 2005 11:44:26 +0100 (CET) Message-ID: <43A53D82.9040305@vslash.com> Date: Sun, 18 Dec 2005 11:44:18 +0100 From: Valery User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050420 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michiel Boland References: <439D354D.1000007@vslash.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: Supported Hardwre : Sun X2100 ? 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, 18 Dec 2005 10:44:36 -0000 Many thanks for these informations, B.R. Valéry Michiel Boland wrote: > On Mon, 12 Dec 2005, Valery wrote: > >> Dear all, >> a simple question, is the recent Sun X2100 Servers >> family (AMD Opteron 148,152,175 / SATA) planned to be >> supported, or simply, does FreeBSD 6.x run whithout >> trouble on this kind of system ? > > > 6.x installs and runs just fine on an x2100. As long as you don't use > the NVIDIA NIC. Luckily, these boxes have a Broadcom as well. > > Cheers > Michiel > From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 18 22:27:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E92BE16A433 for ; Sun, 18 Dec 2005 22:27:43 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACAB643D62 for ; Sun, 18 Dec 2005 22:27:41 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.40] ([213.112.167.88] [213.112.167.88]) by mxfep01.bredband.com with ESMTP id <20051218222740.WBLB4422.mxfep01.bredband.com@[192.168.245.40]>; Sun, 18 Dec 2005 23:27:40 +0100 Message-ID: <43A5E25C.6080909@bredband.net> Date: Sun, 18 Dec 2005 23:27:40 +0100 From: Lars Tunkrans User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.12) Gecko/20051118 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michiel Boland References: <439D354D.1000007@vslash.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: Supported Hardwre : Sun X2100 ? 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, 18 Dec 2005 22:27:44 -0000 Michiel Boland wrote: > On Mon, 12 Dec 2005, Valery wrote: > >> Dear all, >> a simple question, is the recent Sun X2100 Servers >> family (AMD Opteron 148,152,175 / SATA) planned to be >> supported, or simply, does FreeBSD 6.x run whithout >> trouble on this kind of system ? > > > 6.x installs and runs just fine on an x2100. As long as you don't use > the NVIDIA NIC. Luckily, these boxes have a Broadcom as well. > > Cheers > Michiel Did you try Björn Zeeb's latest patch ? http://sources.zabbadoz.net/freebsd/patchset/nve-20051209-01.diff From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 19 03:08:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68F4C16A41F; Mon, 19 Dec 2005 03:08:50 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from stimpy.forestinformatics.com (cvo-cr1-200-239.peak.org [69.59.200.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 606FD43D58; Mon, 19 Dec 2005 03:08:49 +0000 (GMT) (envelope-from jeff.hamann@forestinformatics.com) Received: from mothra (rodan [192.168.0.11]) by stimpy.forestinformatics.com (8.12.9/8.12.9) with SMTP id jBJ38kOo057579; Sun, 18 Dec 2005 19:08:46 -0800 (PST) (envelope-from jeff.hamann@forestinformatics.com) Message-ID: <004301c60449$865f3cf0$0c00a8c0@mothra> From: "Jeff D. Hamann" To: Date: Sun, 18 Dec 2005 19:08:40 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on stimpy.forestinformatics.com Cc: freebsd-amd64@freebsd.org Subject: acpi_perf0: invalid _PSS package? 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, 19 Dec 2005 03:08:50 -0000 I've been noticing this message on startup (using dmesg) acpi_perf0: invalid _PSS package and can't figure out what it is, what it's for and why there are so many? FreeBSD bobby.somewhere.com 6.0-RELEASE FreeBSD 6.0-RELEASE #2: Sun Nov 27 14:07:55 PST 2005 hamannj@bobby.somewhere.com:/usr/obj/usr/src/sys/GENERIC amd64 and bobby# dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #2: Sun Nov 27 14:07:55 PST 2005 hamannj@bobby.forestinformatics.com:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1995.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1576271872 (1503 MB) avail memory = 1511051264 (1441 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 0 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 10 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 5 on acpi0 pci_link5: irq 10 on acpi0 pci_link6: irq 5 on acpi0 pci_link7: irq 5 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.5 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 2.7 (no driver attached) ohci0: mem 0xfbefc000-0xfbefcfff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfbefd000-0xfbefdfff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xfbefe000-0xfbefefff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfbeff000-0xfbefffff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered pci0: at device 4.0 (no driver attached) atapci1: port 0xa800-0xa807,0xa400-0xa403,0xa000-0xa007,0x9800-0x9803,0x9400-0x940f,0x9000-0x907f irq 17 at device 5.0 on pci0 ata2: on atapci1 ata3: on atapci1 pcib2: at device 6.0 on pci0 pci2: on pcib2 pcib3: at device 7.0 on pci0 pci3: on pcib3 rl0: port 0x8800-0x88ff mem 0xfbefb800-0xfbefb8ff irq 17 at device 10.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:11:95:24:60:b3 acpi_button0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc7fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1995009076 Hz quality 800 Timecounters tick every 1.000 msec ad0: 190782MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA66 Trying to mount root from ufs:/dev/ad0s1a bobby# From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 19 08:47:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA98A16A41F for ; Mon, 19 Dec 2005 08:47:34 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E19743D5E for ; Mon, 19 Dec 2005 08:47:33 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 5E08C1FFAD1; Mon, 19 Dec 2005 09:47:27 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C15C61FFAD0; Mon, 19 Dec 2005 09:47:24 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 31086444F6B; Mon, 19 Dec 2005 08:43:35 +0000 (UTC) Date: Mon, 19 Dec 2005 08:43:35 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Lars Tunkrans In-Reply-To: <43A5E25C.6080909@bredband.net> Message-ID: <20051219084011.L23668@maildrop.int.zabbadoz.net> References: <439D354D.1000007@vslash.com> <43A5E25C.6080909@bredband.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1004305553-1134981815=:23668" X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Michiel Boland , freebsd-amd64@freebsd.org Subject: Re: Supported Hardwre : Sun X2100 ? 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, 19 Dec 2005 08:47:35 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1004305553-1134981815=:23668 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 18 Dec 2005, Lars Tunkrans wrote: > Michiel Boland wrote: > >> 6.x installs and runs just fine on an x2100. As long as you don't use th= e=20 >> NVIDIA NIC. Luckily, these boxes have a Broadcom as well. > > Did you try Bj=F6rn Zeeb's latest patch ? > > http://sources.zabbadoz.net/freebsd/patchset/nve-20051209-01.diff Prefered one (which got comitted to HEAD): http://sources.zabbadoz.net/freebsd/patchset/nve-20051211-01.diff it's still not ideal because the NF Professional seem to be able to work w/o the 4GB limit in contigmalloc. --=20 Bjoern A. Zeeb=09=09=09=09bzeeb at Zabbadoz dot NeT --0-1004305553-1134981815=:23668-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 19 09:59:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B7A716A41F; Mon, 19 Dec 2005 09:59:53 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F81F43D66; Mon, 19 Dec 2005 09:59:53 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EoHo3-0006DO-00; Mon, 19 Dec 2005 10:59:47 +0100 Date: Mon, 19 Dec 2005 10:59:46 +0100 To: "Jeff D. Hamann" Message-ID: <20051219095946.GA6233@poupinou.org> References: <004301c60449$865f3cf0$0c00a8c0@mothra> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004301c60449$865f3cf0$0c00a8c0@mothra> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: acpi_perf0: invalid _PSS package? 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, 19 Dec 2005 09:59:53 -0000 On Sun, Dec 18, 2005 at 07:08:40PM -0800, Jeff D. Hamann wrote: > I've been noticing this message on startup (using dmesg) > > acpi_perf0: invalid _PSS package > > and can't figure out what it is, what it's for and why there are so many? It's related to powernow somehow. The powernow driver use ACPI in order to get the needed configuration information. Unfortunately, some BIOS provide buggy _PSS packages. It's likely harmless since other _PSS packages are OK. But to be sure, it would help if you provide a dump of the acpi tables somewhere on the web, or, if you can't, send them privately to me. An acpidump -d -t will give us this information. Note that the kernel log flood is already fixed under -current. This will be MFC'ed soon to RELENG_6. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 19 10:32:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC24C16A41F for ; Mon, 19 Dec 2005 10:32:14 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29CF143D6A for ; Mon, 19 Dec 2005 10:32:11 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so1378458wra for ; Mon, 19 Dec 2005 02:32:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VpB9lmBW8oKaGm5P45jmYVV/JvcJ20jhM6CLH8EH0Vmv0EwjYaGX4lHaqWipHvwE2BqwAK2rwTYCTJV3BNcsuB7xghvepG7TLlljUC2idqJBMOcB/3pyAbk6zv45VM06ssPPairBzqxsUsIMLAyBM+rT6j5u2w9F3KGI0dNgjBQ= Received: by 10.54.118.18 with SMTP id q18mr806686wrc; Mon, 19 Dec 2005 02:32:11 -0800 (PST) Received: by 10.54.131.9 with HTTP; Mon, 19 Dec 2005 02:32:11 -0800 (PST) Message-ID: <1d6d20bc0512190232v5591adabw@mail.gmail.com> Date: Mon, 19 Dec 2005 18:32:11 +0800 From: Jia-Shiun Li To: freebsd-amd64@freebsd.org In-Reply-To: <20051205174356.GA76476@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051201182200.29630.qmail@web32911.mail.mud.yahoo.com> <20051205174356.GA76476@dragon.NUXI.org> Cc: pfgshield-freebsd@yahoo.com Subject: Re: options VESA --> where is it ? 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, 19 Dec 2005 10:32:14 -0000 2005/12/6, David O'Brien : > SuSE Linux has nice high-res console when running on amd64 machines. > Figuring out the techniques they use may be helpful. If you mean VESA framebuffer driver, the comment in linux/drivers/video/vesafb.c says that it enters graphics mode at boot time while still in real mode. Jia-Shiun. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 19 11:02:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED73716A41F for ; Mon, 19 Dec 2005 11:02:27 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B21B543D7F for ; Mon, 19 Dec 2005 11:02:10 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBJB26EC011117 for ; Mon, 19 Dec 2005 11:02:06 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBJB25O9011111 for freebsd-amd64@freebsd.org; Mon, 19 Dec 2005 11:02:05 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 19 Dec 2005 11:02:05 GMT Message-Id: <200512191102.jBJB25O9011111@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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, 19 Dec 2005 11:02:28 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step o [2005/11/17] amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMP o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/20] amd64/87748 amd64 can't initialize X o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre o [2005/11/24] amd64/89501 amd64 System crashes on install using ftp on lo o [2005/11/24] amd64/89503 amd64 Cant Boot Installation Disk o [2005/11/25] amd64/89546 amd64 [geom] GEOM error o [2005/11/25] amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o [2005/11/25] amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o [2005/12/05] amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem o [2005/12/12] amd64/90303 amd64 Marvell 88E8111 Gigabit LAN PHY driver 58 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 [ti] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 [bge] [patch] FreeBSD 5.4 released versio o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins 15 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 19 16:52:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 054EA16A41F for ; Mon, 19 Dec 2005 16:52:25 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A01E43D46 for ; Mon, 19 Dec 2005 16:52:24 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 793E2B80F for ; Mon, 19 Dec 2005 11:52:23 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: <439D354D.1000007@vslash.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8B64F00A-C0E8-449A-88DA-57BC4716C893@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 19 Dec 2005 11:52:22 -0500 To: freebsd-amd64 List X-Mailer: Apple Mail (2.746.2) Subject: Re: Supported Hardwre : Sun X2100 ? 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, 19 Dec 2005 16:52:25 -0000 On Dec 18, 2005, at 5:35 AM, Michiel Boland wrote: > 6.x installs and runs just fine on an x2100. As long as you don't > use the NVIDIA NIC. Luckily, these boxes have a Broadcom as well. Thanks for this note -- at least this part of my plans will work... Any ideas about the X4100? From the specs it should work except for the built-in disk and controller, but it is quite an expensive thing to buy if it doesn't work... I plan to plug an external RAID to it so it doesn't matter that the internal disk doesn't work. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 08:33:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C543C16A420 for ; Tue, 20 Dec 2005 08:33:02 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1C2943D5F for ; Tue, 20 Dec 2005 08:33:00 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: by nproxy.gmail.com with SMTP id p48so462650nfa for ; Tue, 20 Dec 2005 00:32:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=fvUBa6YK2VLfOH/hYUd/sVa5WJDuAzakWFt3AUY5FOEVnq9xkL/NfXFN2xc8LdPHh3+dV8In3cK8wjsP7guX7uJBrr7Wweiys2zFDvJC/GG4R/SwRG8PPIYXT+wnLohI9uJHBObNSM3hfNt/p1p746IfI5TneaFxKTn0gdR+bpA= Received: by 10.48.240.13 with SMTP id n13mr290968nfh; Tue, 20 Dec 2005 00:32:59 -0800 (PST) Received: by 10.48.215.13 with HTTP; Tue, 20 Dec 2005 00:32:59 -0800 (PST) Message-ID: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> Date: Tue, 20 Dec 2005 09:32:59 +0100 From: spil oss To: bug-followup@FreeBSD.org, funkblaster@mail.ru, pav@FreeBSD.org, freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 08:33:02 -0000 Hi All, After installing 6-RELEASE using ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0-RELEA= SE-i386-disc1.iso nve is giving me the device timeouts (as I expected) http://www.nl.freebsd.org/platforms/amd64/motherboards.html reports nve being fine in 6-BETA5 though. After timeout (64) the network was gone. Is this a problem that was introduced after BETA5 (from other reports on nve that seems unlikely) Spil. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 09:07:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80B5716A41F; Tue, 20 Dec 2005 09:07:29 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05BB743D49; Tue, 20 Dec 2005 09:07:28 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 6114E1FFAD2; Tue, 20 Dec 2005 10:07:26 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C42BF1FFAD4; Tue, 20 Dec 2005 10:07:23 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 537F5444F6B; Tue, 20 Dec 2005 09:04:02 +0000 (UTC) Date: Tue, 20 Dec 2005 09:04:01 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: spil oss In-Reply-To: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> Message-ID: <20051220090125.T23668@maildrop.int.zabbadoz.net> References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: pav@FreeBSD.org, funkblaster@mail.ru, freebsd-amd64@freebsd.org, bug-followup@FreeBSD.org Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 09:07:29 -0000 On Tue, 20 Dec 2005, spil oss wrote: > Hi All, > > After installing 6-RELEASE using > ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0-RELEASE-i386-disc1.iso > nve is giving me the device timeouts (as I expected) > http://www.nl.freebsd.org/platforms/amd64/motherboards.html reports > nve being fine in 6-BETA5 though. I doubt that nve really worked on this board for 6.x . > After timeout (64) the network was gone. > Is this a problem that was introduced after BETA5 (from other reports > on nve that seems unlikely) could you try http://sources.zabbadoz.net/freebsd/patchset/nve-20051211-01.diff It'll be merged to RELENG_6 soon. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 09:31:09 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D83D16A41F for ; Tue, 20 Dec 2005 09:31:09 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F00F43D96 for ; Tue, 20 Dec 2005 09:30:54 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBK9UpEk022857 for ; Tue, 20 Dec 2005 07:30:52 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Tue, 20 Dec 2005 07:30:48 -0200 User-Agent: KMail/1.8.3 References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> In-Reply-To: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512200730.48613.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 09:31:09 -0000 On Tuesday 20 December 2005 06:32, spil oss wrote: > After installing 6-RELEASE using > ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0-REL= EA >SE-i386-disc1.iso nve is giving me the device timeouts (as I expected) > http://www.nl.freebsd.org/platforms/amd64/motherboards.html reports > nve being fine in 6-BETA5 though. > > After timeout (64) the network was gone. I have similar problems with R-6 amd64 but with sk and fxp driver without any reason I get such events=20 sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN and fxp0: DMA timeout fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff for sure the HUB is Ok and no other physical problem the sk error ocurres normally in idle hours and the fxp anytime when the sk event happens the traffic goes still through when the fxp error appears traffic stops on that interface and the IF statu= s=20 change to=20 status: active=20 media Ethernet autoselect (none) the xl I have installed do not give any problem at all this is an ASUS A8V with amd64 processor, I thought this could be an acpi=20 problem because the dsdt is giving lots of errors when compiling it, indeed= =20 it does not compile at all. I do not have this problems with the same HW and 5.4-R Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 09:44:13 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06DE216A41F for ; Tue, 20 Dec 2005 09:44:13 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 435BC43D67 for ; Tue, 20 Dec 2005 09:44:11 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: by nproxy.gmail.com with SMTP id p48so466641nfa for ; Tue, 20 Dec 2005 01:44:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r6Spvr9lotZGpLT7u2hY4m0ejF8yNv4FcgUMwx8bRG+N7SFM0m06l/X2+8c+0znAhB9zm4oJ/T+KueduIzSCqWIaZyfp9HW84j2+VHbYNfhJ6wl47HLgyb7sntQEEVcNAezjZjYbYks/u5IRbCwk8Hn48A425E/bFakIVkNY/2Y= Received: by 10.48.225.15 with SMTP id x15mr167898nfg; Tue, 20 Dec 2005 01:44:09 -0800 (PST) Received: by 10.48.215.13 with HTTP; Tue, 20 Dec 2005 01:44:09 -0800 (PST) Message-ID: <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> Date: Tue, 20 Dec 2005 10:44:09 +0100 From: spil oss To: JoaoBR In-Reply-To: <200512200730.48613.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> <200512200730.48613.joao@matik.com.br> Cc: freebsd-amd64@freebsd.org Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 09:44:13 -0000 Jo=E3o, As for the sk, I think you're running into a different problem which I'm told has something to do with Interrupt-routing. For my ancient 3com 3c575 the workaround was to use polling on the card (although I'm hoping for a fix as polling takes too much resource on that ancient laptop). This does require a kernel with polling support. See http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/87114 Maybe it helps someone here if you list the specific model/version of the NIC that uses this SysKonnect driver. Have you tried booting with acpi disabled? Spil. On 12/20/05, JoaoBR wrote: > On Tuesday 20 December 2005 06:32, spil oss wrote: > > After installing 6-RELEASE using > > ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0-R= ELEA > >SE-i386-disc1.iso nve is giving me the device timeouts (as I expected) > > http://www.nl.freebsd.org/platforms/amd64/motherboards.html reports > > nve being fine in 6-BETA5 though. > > > > After timeout (64) the network was gone. > > > I have similar problems with R-6 amd64 but with sk and fxp driver > > without any reason I get such events > > sk0: link state changed to UP > sk0: watchdog timeout > sk0: link state changed to DOWN > > and > > fxp0: DMA timeout > fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > for sure the HUB is Ok and no other physical problem > the sk error ocurres normally in idle hours and the fxp anytime > > when the sk event happens the traffic goes still through > > when the fxp error appears traffic stops on that interface and the IF sta= tus > change to > status: active > media Ethernet autoselect (none) > > the xl I have installed do not give any problem at all > > this is an ASUS A8V with amd64 processor, I thought this could be an acpi > problem because the dsdt is giving lots of errors when compiling it, inde= ed > it does not compile at all. > > I do not have this problems with the same HW and 5.4-R > > Jo=E3o > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada seg= ura. > Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br > _______________________________________________ > 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 Tue Dec 20 09:52:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B5CC16A422 for ; Tue, 20 Dec 2005 09:52:28 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16E6A43D5A for ; Tue, 20 Dec 2005 09:52:26 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id A8F491FFACC; Tue, 20 Dec 2005 10:52:25 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 230511FFAD5; Tue, 20 Dec 2005 10:52:23 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id E7C90444F6B; Tue, 20 Dec 2005 09:48:06 +0000 (UTC) Date: Tue, 20 Dec 2005 09:48:06 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: JoaoBR In-Reply-To: <200512200730.48613.joao@matik.com.br> Message-ID: <20051220094016.I23668@maildrop.int.zabbadoz.net> References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> <200512200730.48613.joao@matik.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 09:52:28 -0000 On Tue, 20 Dec 2005, JoaoBR wrote: > I have similar problems with R-6 amd64 but with sk and fxp driver or HEAD (for sk(4)). > without any reason I get such events > > sk0: link state changed to UP > sk0: watchdog timeout > sk0: link state changed to DOWN I get them too but do you actually have any interruption? Can you try to find out the delta T (time difference) between the DOWN and the next UP message? It's sometimes days here. > when the sk event happens the traffic goes still through Yes, that's the strange thing. I can see these messages on my serial console log in the other term next to the one I am working on such a machine with ssh. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 09:57:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4A2B16A41F for ; Tue, 20 Dec 2005 09:57:27 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 015B443D53 for ; Tue, 20 Dec 2005 09:57:26 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id A834C1FFAD3; Tue, 20 Dec 2005 10:57:25 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id D7C981FFBF8; Tue, 20 Dec 2005 10:57:22 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 9D3AB444F6B; Tue, 20 Dec 2005 09:51:47 +0000 (UTC) Date: Tue, 20 Dec 2005 09:51:47 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: spil oss In-Reply-To: <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> Message-ID: <20051220094927.F23668@maildrop.int.zabbadoz.net> References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> <200512200730.48613.joao@matik.com.br> <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-45361522-1135072307=:23668" X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 09:57:27 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-45361522-1135072307=:23668 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 20 Dec 2005, spil oss wrote: > Jo=E3o, > > As for the sk, I think you're running into a different problem which > I'm told has something to do with Interrupt-routing. For my ancient > 3com 3c575 the workaround was to use polling on the card (although I'm > hoping for a fix as polling takes too much resource on that ancient > laptop). This does require a kernel with polling support. > See http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/87114 > Maybe it helps someone here if you list the specific model/version of > the NIC that uses this SysKonnect driver. sk(4) doesn't have poling support imho. but reading this could you try =09sysctl dev.skc.0.int_mod=3D200 (change the 0 to whatever it is for you) I am trying to find a spare machine and see if that is going to help. It had been the default before. --=20 Bjoern A. Zeeb=09=09=09=09bzeeb at Zabbadoz dot NeT --0-45361522-1135072307=:23668-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 10:02:35 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6E4616A41F for ; Tue, 20 Dec 2005 10:02:35 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54FA443D64 for ; Tue, 20 Dec 2005 10:02:32 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBKA2Vwp024018 for ; Tue, 20 Dec 2005 08:02:31 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Tue, 20 Dec 2005 08:02:28 -0200 User-Agent: KMail/1.8.3 References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> <200512200730.48613.joao@matik.com.br> <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> In-Reply-To: <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512200802.28549.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: www/86888: new motherboard for the 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: Tue, 20 Dec 2005 10:02:36 -0000 On Tuesday 20 December 2005 07:44, spil oss wrote: > Jo=E3o, > > As for the sk, I think you're running into a different problem which > I'm told has something to do with Interrupt-routing. For my ancient > 3com 3c575 the workaround was to use polling on the card (although I'm > hoping for a fix as polling takes too much resource on that ancient > laptop). This does require a kernel with polling support. > See http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/87114 > Maybe it helps someone here if you list the specific model/version of > the NIC that uses this SysKonnect driver. > > Have you tried booting with acpi disabled? > The Asus A8V does not boot with acpi disabled and polling did not made any= =20 difference and I believe sk do not support polling The IF is onboard and probed as: skc0: port 0xb400-0xb4ff mem 0xfa500000-0xfa503f= ff=20 irq 17 at device 10.0 on pci0 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 thanks, Jo=E3o > Spil. > > On 12/20/05, JoaoBR wrote: > > On Tuesday 20 December 2005 06:32, spil oss wrote: > > > After installing 6-RELEASE using > > > ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0= =2DR > > >ELEA SE-i386-disc1.iso nve is giving me the device timeouts (as I > > > expected) http://www.nl.freebsd.org/platforms/amd64/motherboards.html > > > reports nve being fine in 6-BETA5 though. > > > > > > After timeout (64) the network was gone. > > > > I have similar problems with R-6 amd64 but with sk and fxp driver > > > > without any reason I get such events > > > > sk0: link state changed to UP > > sk0: watchdog timeout > > sk0: link state changed to DOWN > > > > and > > > > fxp0: DMA timeout > > fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > > > for sure the HUB is Ok and no other physical problem > > the sk error ocurres normally in idle hours and the fxp anytime > > > > when the sk event happens the traffic goes still through > > > > when the fxp error appears traffic stops on that interface and the IF > > status change to > > status: active > > media Ethernet autoselect (none) > > > > the xl I have installed do not give any problem at all > > > > this is an ASUS A8V with amd64 processor, I thought this could be an ac= pi > > problem because the dsdt is giving lots of errors when compiling it, > > indeed it does not compile at all. > > > > I do not have this problems with the same HW and 5.4-R > > > > Jo=E3o > > > > > > > > > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > segura. Service fornecido pelo Datacenter Matik=20 > > https://datacenter.matik.com.br > > _______________________________________________ > > 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" > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > segura. Service fornecido pelo Datacenter Matik=20 > https://datacenter.matik.com.br =2D-=20 Atenciosamente Infomatik Internet Technology (18)3551.8155 (18)8112.7007 http://info.matik.com.br A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 13:51:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DF5116A41F for ; Tue, 20 Dec 2005 13:51:20 +0000 (GMT) (envelope-from ewinter@west.bsn.com) Received: from lobo.ewinter.org (host-62-245-151-69.customer.m-online.net [62.245.151.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id F28D943D66 for ; Tue, 20 Dec 2005 13:51:17 +0000 (GMT) (envelope-from ewinter@west.bsn.com) Received: from lobo.ewinter.org (localhost [127.0.0.1]) by lobo.ewinter.org (8.13.4/8.13.4) with ESMTP id jBKDku9Q033103; Tue, 20 Dec 2005 14:46:56 +0100 (CET) (envelope-from ewinter@west.bsn.com) Received: (from ewinter@localhost) by lobo.ewinter.org (8.13.4/8.13.4/Submit) id jBKDktC0033102; Tue, 20 Dec 2005 14:46:55 +0100 (CET) (envelope-from ewinter) Date: Tue, 20 Dec 2005 14:46:54 +0100 From: "Ernst W. Winter" To: JoaoBR Message-ID: <20051220134654.GA32960@lobo.ewinter.org> References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> <200512200730.48613.joao@matik.com.br> <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> <200512200802.28549.joao@matik.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512200802.28549.joao@matik.com.br> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 6.0-STABLE FreeBSD 6.0-STABLE User-Agent: mutt-ng/devel (FreeBSD) Cc: freebsd-amd64@freebsd.org Subject: Re: www/86888: new motherboard for the amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 13:51:20 -0000 On Tue, 20 Dec 2005, JoaoBR wrote: > On Tuesday 20 December 2005 07:44, spil oss wrote: > > Jo?o, > > > > As for the sk, I think you're running into a different problem which > > I'm told has something to do with Interrupt-routing. For my ancient > > 3com 3c575 the workaround was to use polling on the card (although I'm > > hoping for a fix as polling takes too much resource on that ancient > > laptop). This does require a kernel with polling support. > > See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/87114 > > Maybe it helps someone here if you list the specific model/version of > > the NIC that uses this SysKonnect driver. > > > > Have you tried booting with acpi disabled? > > > > The Asus A8V does not boot with acpi disabled and polling did not > made any difference and I believe sk do not support polling > > The IF is onboard and probed as: > > skc0: port 0xb400-0xb4ff mem > 0xfa500000-0xfa503fff irq 17 at device 10.0 on pci0 > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > sk0: on skc0 > > > thanks, Jo?o > > well what version of 6.0 do you have? I found that once you sup to the latest this problem dissapeared with my MB as it is the same as yours and here the output when booting, I keep it short as I have other NIC as well: -----------------------------Snip------------------------------------- Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-STABLE #5: Tue Dec 6 21:20:19 CET 2005 ewinter@lobo.ewinter.org:/usr/obj/usr/src/sys/lobo ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.58-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 2147155968 (2047 MB) avail memory = 2065616896 (1969 MB) [...] skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) sk0: on skc0 sk0: Ethernet address: 00:11:2f:d2:a9:dd miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xb000-0xb07f mem 0xfac00000-0xfac0 007f irq 18 at device 13.0 on pci0 miibus1: on xl0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:75:74:c7:df and here the ifconfig: lobo ewinter 502-->ifconfig sk0: flags=8843 mtu 1500 inet6 fe80::211:2fff:fed2:a9dd%sk0 prefixlen 64 scopeid 0x1 inet 192.168.1.44 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:11:2f:d2:a9:dd media: Ethernet autoselect (100baseTX ) status: active xl0: flags=8802 mtu 1500 options=9 ether 00:04:75:74:c7:df media: Ethernet autoselect (none) status: no carrier plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 -----------------------------Snip------------------------------------- the xl0 is not used and just a spare as I used it with 5.4 as I had problems with the skc driver. If you want the full output or config, then mail me and I will send it to you or post it here if anyone is interested. Ernst > > > Spil. > > > > On 12/20/05, JoaoBR wrote: > > > On Tuesday 20 December 2005 06:32, spil oss wrote: > > > > After installing 6-RELEASE using > > > > ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0-R > > > >ELEA SE-i386-disc1.iso nve is giving me the device timeouts (as I > > > > expected) http://www.nl.freebsd.org/platforms/amd64/motherboards.html > > > > reports nve being fine in 6-BETA5 though. > > > > > > > > After timeout (64) the network was gone. > > > > > > I have similar problems with R-6 amd64 but with sk and fxp driver > > > > > > without any reason I get such events > > > > > > sk0: link state changed to UP > > > sk0: watchdog timeout > > > sk0: link state changed to DOWN > > > > > > and > > > > > > fxp0: DMA timeout > > > fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > > fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > > > > > for sure the HUB is Ok and no other physical problem > > > the sk error ocurres normally in idle hours and the fxp anytime > > > > > > when the sk event happens the traffic goes still through > > > > > > when the fxp error appears traffic stops on that interface and the IF > > > status change to > > > status: active > > > media Ethernet autoselect (none) > > > > > > the xl I have installed do not give any problem at all > > > > > > this is an ASUS A8V with amd64 processor, I thought this could be an acpi > > > problem because the dsdt is giving lots of errors when compiling it, > > > indeed it does not compile at all. > > > > > > I do not have this problems with the same HW and 5.4-R > > > > > > Jo?o > > > > > > > > > > > > > > > > > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > > segura. Service fornecido pelo Datacenter Matik > > > https://datacenter.matik.com.br > > > _______________________________________________ > > > 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" > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > segura. Service fornecido pelo Datacenter Matik > > https://datacenter.matik.com.br > > -- > > Atenciosamente > > Infomatik Internet Technology > (18)3551.8155 (18)8112.7007 > http://info.matik.com.br > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. > Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br > _______________________________________________ > 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 Tue Dec 20 14:50:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77FD016A41F; Tue, 20 Dec 2005 14:50:26 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D660E43D46; Tue, 20 Dec 2005 14:50:25 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 9735AB832; Tue, 20 Dec 2005 16:50:23 +0200 (EET) Received: (nullmailer pid 48878 invoked by uid 1002); Tue, 20 Dec 2005 14:50:23 -0000 Date: Tue, 20 Dec 2005 16:50:23 +0200 From: Vasil Dimov To: Jia-Shiun Li Message-ID: <20051220145023.GA48817@qlovarnika.bg.datamax> References: <20051201182200.29630.qmail@web32911.mail.mud.yahoo.com> <20051205174356.GA76476@dragon.NUXI.org> <1d6d20bc0512190232v5591adabw@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <1d6d20bc0512190232v5591adabw@mail.gmail.com> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 Cc: pfgshield-freebsd@yahoo.com, freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 14:50:26 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 19, 2005 at 06:32:11PM +0800, Jia-Shiun Li wrote: > 2005/12/6, David O'Brien : > > SuSE Linux has nice high-res console when running on amd64 machines. > > Figuring out the techniques they use may be helpful. >=20 > If you mean VESA framebuffer driver, the comment in > linux/drivers/video/vesafb.c > says that it enters graphics mode at boot time while still in real mode. >=20 Some time ago I pondered switching the video mode at early boot time and wondered if it would be less work to do... --=20 Vasil Dimov --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFDqBouFw6SP/bBpCARAl+yAJ9RMNSAZqlud6zij5RX2q4OVipndgCfWhBx zJL40LW6/ggFuGm9foVt+C8= =mS5q -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 15:48:59 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3FD216A420; Tue, 20 Dec 2005 15:48:59 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89FF843D77; Tue, 20 Dec 2005 15:48:52 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id 163F56C2C1F; Tue, 20 Dec 2005 16:48:49 +0100 (CET) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12206-02-4; Tue, 20 Dec 2005 16:48:48 +0100 (CET) Received: from rambutan.pingpong.net (rambutan.pingpong.net [192.168.1.187]) by melon.pingpong.net (Postfix) with ESMTP id 9D8336C2C1D; Tue, 20 Dec 2005 16:48:48 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by rambutan.pingpong.net (8.13.4/8.13.4) with ESMTP id jBKFmmex089814; Tue, 20 Dec 2005 16:48:48 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Tue, 20 Dec 2005 16:48:48 +0100 From: Palle Girgensohn To: Vitaliy Skakun , freebsd-java@freebsd.org Message-ID: <665935C9D6097C207056D277@rambutan.pingpong.net> In-Reply-To: <806128ad0512200629s7cd0fd74w@mail.gmail.com> References: <5CAF2984AB1A9F00A265DD12@rambutan.pingpong.net> <806128ad0512200629s7cd0fd74w@mail.gmail.com> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Cc: amd64@freebsd.org Subject: Re: SEGV on jdk 1.5.0 @ 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: Tue, 20 Dec 2005 15:49:00 -0000 --On tisdag, december 20, 2005 16.29.29 +0200 Vitaliy Skakun wrote: > Hi! > > 2005/12/20, Palle Girgensohn : >> >> Hi! >> >> I have experienced two crashes pof the in the last 24 hours. This is on >> freebsd-6.0-release @ amd64 with latest jdk-1.5.0p2_2 >> >> [skipped] > > Just my 2 cents: > > I tried running Jboss 4.0.3SP1 with the following > - platform EM64T > - RELENG_6 of ~ 2 weeks ago dating, amd64 > - JDK 1.5.0p2_2 > > and noticed that it works slow, even visually. Then I switched to i386 on > the same hardware and noticed that JBoss starts ~2 times faster, visually > works also faster. BTW buildworld works ~1.35 times faster.(Sorry, I do > not have benchmark results now.) > > My conclusion was - still to use FreeBSD.i386 on EM64T hardware for JBoss > server. Umm, OK. :( We do use EM64T hardware, it is a Dell 2850. With i386, I only get approx 2GB out of the four installed - that's why I tried installing amd64. We use just tomcat, not the entire jboss, but it does seem to be rather slow, indeed. Does anyone else have experience with this? /Palle From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 16:07:32 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A3C916A42A; Tue, 20 Dec 2005 16:07:32 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from e0-a11.b1.lan.prg.vol.cz (e0-a11.b1.lan.prg.vol.cz [195.122.204.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D3DA43D49; Tue, 20 Dec 2005 16:07:17 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from pav.hide.vol.cz (localhost [127.0.0.1]) by e0-a11.b1.lan.prg.vol.cz (8.13.4/8.13.4) with ESMTP id jBKG7BLq082432; Tue, 20 Dec 2005 17:07:11 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by pav.hide.vol.cz (8.13.4/8.13.4/Submit) id jBKG7AAQ082431; Tue, 20 Dec 2005 17:07:10 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: pav.hide.vol.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: spil oss In-Reply-To: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YzTj8yi10acCvf1U0/Wk" Date: Tue, 20 Dec 2005 17:07:10 +0100 Message-Id: <1135094830.79395.19.camel@pav.hide.vol.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Cc: funkblaster@mail.ru, freebsd-amd64@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: www/86888: new motherboard for the amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 16:07:33 -0000 --=-YzTj8yi10acCvf1U0/Wk Content-Type: text/plain; charset=ISO8859-2 Content-Transfer-Encoding: quoted-printable spil oss p=ED=B9e v =FAt 20. 12. 2005 v 09:32 +0100: > Hi All, >=20 > After installing 6-RELEASE using > ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.0/6.0-REL= EASE-i386-disc1.iso > nve is giving me the device timeouts (as I expected) > http://www.nl.freebsd.org/platforms/amd64/motherboards.html reports > nve being fine in 6-BETA5 though. >=20 > After timeout (64) the network was gone. > Is this a problem that was introduced after BETA5 (from other reports > on nve that seems unlikely) Sad to hear that. I updated the motherboards page to note this. --=20 Pav Lucistnik Is this a dagger which I see before me, its handle towards my hand? Come, let me clutch thee! I have thee not, and yet I see thee still. --=-YzTj8yi10acCvf1U0/Wk Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDqCwuntdYP8FOsoIRAvA3AJ43YxmHyeudcWlSKk4eqJT0ximv/QCeP1xD Vo2dtfZW37LCf3R10iqL4Yk= =mgKp -----END PGP SIGNATURE----- --=-YzTj8yi10acCvf1U0/Wk-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 16:43:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D41B516A431 for ; Tue, 20 Dec 2005 16:43:27 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4F8243D8C for ; Tue, 20 Dec 2005 16:43:23 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.6] (unknown [192.168.1.6]) by yertle.kcilink.com (Postfix) with ESMTP id 846EBB80F for ; Tue, 20 Dec 2005 11:43:19 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <8B64F00A-C0E8-449A-88DA-57BC4716C893@khera.org> References: <439D354D.1000007@vslash.com> <8B64F00A-C0E8-449A-88DA-57BC4716C893@khera.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5EA6582C-9F0E-4402-A30A-317AC2376DEB@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 20 Dec 2005 11:43:16 -0500 To: freebsd-amd64 List X-Mailer: Apple Mail (2.746.2) Subject: Re: Supported Hardwre : Sun X2100 ? 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, 20 Dec 2005 16:43:27 -0000 On Dec 19, 2005, at 11:52 AM, Vivek Khera wrote: > Any ideas about the X4100? In bad form I reply to myself... Sun has told me that FreeBSD will boot on the X4100 but they do not support it and they have a "no-return policy" so there's no way to check without putting up some bucks and crossing fingers... unless someone out there can post a dmesg from a freebsd 6.0 boot...? please, pretty please? From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 17:54:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B86A16A41F for ; Tue, 20 Dec 2005 17:54:19 +0000 (GMT) (envelope-from groot@kde.org) Received: from hex.athame.co.uk (salama58.adsl.netsonic.fi [81.17.207.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F3443D5D for ; Tue, 20 Dec 2005 17:54:17 +0000 (GMT) (envelope-from groot@kde.org) Received: from localhost.athame.co.uk ([127.0.0.1] helo=hex.athame.co.uk) by hex.athame.co.uk with esmtp (Exim 4.54 (FreeBSD)) id 1Eolgm-000Okl-KE for freebsd-amd64@freebsd.org; Tue, 20 Dec 2005 19:54:16 +0200 Received: from localhost (adridg@localhost) by hex.athame.co.uk (8.13.4/8.13.1/Submit) with ESMTP id jBKHsFtO095152 for ; Tue, 20 Dec 2005 19:54:16 +0200 (EET) (envelope-from groot@kde.org) X-Authentication-Warning: hex.athame.co.uk: adridg owned process doing -bs Date: Tue, 20 Dec 2005 19:54:14 +0200 (EET) From: Adriaan de Groot X-X-Sender: adridg@hex.athame.co.uk To: freebsd-amd64@freebsd.org Message-ID: <20051220195122.W94851@hex.athame.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Asus A8N-VM CSM 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, 20 Dec 2005 17:54:19 -0000 A while back I asked about experiences with the Asus A8N-VM CSM, a micro-ATX nForce4 + onboard GF 6150 combo -- noone had worked with it. So I bought one anyway, and much to my surprise, 5.1-R amd64 booted on it! Way! That's what was on the spare HDD I had, hence that particular test. More than "it boots" I have not looked into, but I'll PR it to the motherboards list when I'm done checking. Of particular interest is whether XOrg supports the video .. the binary drivers are out, no? [ade] From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 20 23:07:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69CE316A41F for ; Tue, 20 Dec 2005 23:07:57 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA81143D5C for ; Tue, 20 Dec 2005 23:07:56 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id AB3F8F7C5 for ; Tue, 20 Dec 2005 16:07:53 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 6F6D4F7BB for ; Tue, 20 Dec 2005 16:07:53 -0700 (MST) Date: Tue, 20 Dec 2005 16:07:52 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051220160752.0f6dcc43.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Tyan TA26, LSI 320-1, and FBSD6.0 Strangeness 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, 20 Dec 2005 23:07:57 -0000 Hello List: I'm having a tough time w/a Tyan TA26, 320-1 and 6.0-RELEASE that I'm hoping y'all may be able to shed some light on. I create logical drives and install FBSD just fine. Then cvsup, buildworld, buildkernel, installkernel. Upon reboot the system drives (mirror) are in degraded mode and the raid0 drive (swap) is offline. MegaRAID is unable to rebuild the arrays. I've called LSI support and they're mystified as well. Details: A) Hardware: 1) Tyan Transport TA-26 2U Barebones Server Latest Tyan BIOS Rev. 3.04 b20 2) Dual AMD Opteron 246 3) 2 GB ECC Registered RAM (Corsair- Memtest runs ad infinitum w/o reporting any errors.) 4) LSL MegaRAID 320-1 --Confirmed latest LSI Firmware 5) Fujitsu MAT3073NC 80 pin, 73.5 GB, U320-SCSI, 10K RPM Hard Drives B) Configuration 1) Array 1 consists of 2 hard drives in slots 1 & 5 respecitvely w/2 logical drives configured: a) Logical Drive 1- RAID1 Mirror, 64K stripe size. b) Logical Drive 2- RAID0, 128K stripe size 2) Array 2 a) Logical Drive 3- RAID5 data array, 128K stripe size 3) Operating System- FreeBSD-6.0-RELEASE 4) Mainboard BIOS config- disable onboard Adaptec, SATA, etc. Plug & Play OS set to "NO" C) How to Replicate: 1) create arrays, logical drives, and perform FreeBSD base install. a) Logical Drive 1 system drive b) Logical Drive 2- swap c) Logical Drive 2- data storage 2) cvsup FreeBSD source code 3) buildworld, buildkernel, and installkernel 6) reboot The logical drives 1 & 2 will now be offline and degraded mode and DMESG reports IO errors. Logical Drive 1- Degraded Logical Drive 2- Offline 7) Boot into single user mode anyways, installworld, mergemaster, and reboot. 8) Boot into LSI MegaRAID utilities a) Objects>physical drives- drive in slot 1 will be failed b) Try to rebuild- fails w/Error c) Sometimes I get a partial rebuild before the error by going through the rebuild menu. d) No media errors, etc. reported. At this point you're basically hosed and unable to recover. My understanding is that even if for some strange reason FBSD is overwriting something on Physical Drive 1 that the MegaRAID should still be able to rebuild from data on Physical Drive 5. D) History: 1) Upon first encounter LSI tech support concluded that I had a defective RAID card and rma'd. Then same problems with new card. 2) After much testing and discussion w/Tyan support conclusion was that Slot 1 on the Tyan backplane was defective. Also possibly pci-riser as it exhibited signs of physical damage. Tyan RMA's the machine. 3) Now I am stil having same problem. Moving hd's around doesn't help. Not a HD issue as they work fine in another machine. E) Present Status: Interestingly enough, I am able to FORCE Physical Drive 1 back online and then "Check Consistency". Presently 21% complete so don't know if it will choke on error on not yet. LSI support is planning to investigate further but I am informed that their test lab is under remodling at the moment and it won't be for at least a couple weeks. In the meantime any insights/help from the list would be appreciated. All of this hardware is pretty well supported for some time now on FBSD. Am I on crack and missing the obvious here or what? TIA-- -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 04:10:50 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C40116A41F; Wed, 21 Dec 2005 04:10:50 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB4543D58; Wed, 21 Dec 2005 04:10:48 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jBL4AkCH049511; Tue, 20 Dec 2005 23:10:47 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jBL4AlVm045380; Tue, 20 Dec 2005 23:10:47 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 918A27302F; Tue, 20 Dec 2005 23:10:46 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051221041046.918A27302F@freebsd-current.sentex.ca> Date: Tue, 20 Dec 2005 23:10:46 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 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, 21 Dec 2005 04:10:50 -0000 TB --- 2005-12-21 03:01:31 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-21 03:01:31 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-21 03:01:31 - cleaning the object tree TB --- 2005-12-21 03:02:07 - checking out the source tree TB --- 2005-12-21 03:02:07 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-21 03:02:07 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-21 03:08:04 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-21 03:08:04 - cd /src TB --- 2005-12-21 03:08:04 - /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 [...] cc -O2 -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -o newsyslog newsyslog.o ptimes.o gzip -cn /src/usr.sbin/newsyslog/newsyslog.8 > newsyslog.8.gz gzip -cn /src/usr.sbin/newsyslog/newsyslog.conf.5 > newsyslog.conf.5.gz ===> usr.sbin/nfsd (all) cc -O2 -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 -c /src/usr.sbin/nfsd/nfsd.c /src/usr.sbin/nfsd/nfsd.c: In function `main': /src/usr.sbin/nfsd/nfsd.c:666: warning: passing arg 3 of `accept' from incompatible pointer type /src/usr.sbin/nfsd/nfsd.c:688: warning: passing arg 3 of `accept' from incompatible pointer type *** Error code 1 Stop in /src/usr.sbin/nfsd. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-21 04:10:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-21 04:10:46 - ERROR: failed to build world TB --- 2005-12-21 04:10:46 - tinderbox aborted TB --- 1.23 user 6.71 system 4155.06 real From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 06:10:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9885E16A41F for ; Wed, 21 Dec 2005 06:10:21 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86BAE43D60 for ; Wed, 21 Dec 2005 06:10:20 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 58E68F7C5 for ; Tue, 20 Dec 2005 23:10:19 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 35AFAF7BB for ; Tue, 20 Dec 2005 23:10:19 -0700 (MST) Date: Tue, 20 Dec 2005 23:10:18 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051220231018.5b383a39.kgunders@teamcool.net> In-Reply-To: <20051220160752.0f6dcc43.kgunders@teamcool.net> References: <20051220160752.0f6dcc43.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Tyan TA26, LSI 320-1, and FBSD6.0 Strangeness 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: Wed, 21 Dec 2005 06:10:21 -0000 On Tue, 20 Dec 2005 16:07:52 -0700 Ken Gunderson wrote: > Hello List: > > I'm having a tough time w/a Tyan TA26, 320-1 and 6.0-RELEASE that > I'm hoping y'all may be able to shed some light on. I create logical > drives and install FBSD just fine. Then cvsup, buildworld, > buildkernel, installkernel. Upon reboot the system drives (mirror) are > in degraded mode and the raid0 drive (swap) is offline. MegaRAID is > unable to rebuild the arrays. I've called LSI support and they're > mystified as well. [big snippage] > E) Present Status: > > Interestingly enough, I am able to FORCE Physical Drive 1 back online > and then "Check Consistency". Presently 21% complete so don't know if > it will choke on error on not yet. Update- The consistency check did complete w/o any errors and rebooting all logical drives are once again in "Optimal" state. For sake of completeness heres the dmesg: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE-p1 #0: Tue Dec 20 15:48:15 EST 2005 kgunders@portia.musicalartists.org:/usr/obj/usr/src/sys/PORTIA Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 244 (1794.11-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2147418112 (2047 MB) avail memory = 2063020032 (1967 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 15 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 9 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci3 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci3 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci3: at device 6.0 (no driver attached) fxp0: port 0xbc00-0xbc3f mem 0xfeafb000-0xfeafbfff,0xfeaa0000-0xfeabffff irq 18 at device 8.0 on pci3 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:2f:8e:98 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfc9b0000-0xfc9bffff,0xfc9a0000-0xfc9affff irq 24 at device 9.0 on pci2 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:2f:8e:d0 bge1: mem 0xfc9e0000-0xfc9effff,0xfc9d0000-0xfc9dffff irq 25 at device 9.1 on pci2 miibus2: on bge1 brgphy1: on miibus2 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:2f:8e:d1 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 amr0: mem 0xff4f0000-0xff4fffff irq 29 at device 4.0 on pci1 amr0: Firmware 1L37, BIOS G119, 64MB RAM pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 amrd0: on amr0 amrd0: 66036MB (135241728 sectors) RAID 1 (optimal) amrd1: on amr0 amrd1: 8198MB (16789504 sectors) RAID 0 (optimal) amrd2: on amr0 amrd2: 140270MB (287272960 sectors) RAID 5 (optimal) SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/amrd0s1a bge0: link state changed to UP -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 08:53:34 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D0AC16A41F for ; Wed, 21 Dec 2005 08:53:34 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2765D43D46 for ; Wed, 21 Dec 2005 08:53:34 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 365EC213E5 for ; Wed, 21 Dec 2005 08:53:33 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 88101-05-2 for ; Wed, 21 Dec 2005 08:53:24 +0000 (GMT) Received: from [192.168.0.90] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 4B00820C43 for ; Wed, 21 Dec 2005 08:53:24 +0000 (GMT) Message-ID: <43A91804.4090301@jetnet.co.uk> Date: Wed, 21 Dec 2005 08:53:24 +0000 From: David Reid User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051216) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD AMD64 Mailing List X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: Subject: how to get more info #2 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: Wed, 21 Dec 2005 08:53:34 -0000 Following on from my last attempt to get more information on why my box keeps rebooting, it was suggested that the lack of panics was a function of running under X. Off list it was suggested I try remote debugging via firewire, something I have now done. The panic showed up in vm_map_entry_splay as a page fault. The function was called following a trap 0xc. I tried to get into gdb to get more information but it complained about a lack of remote debuggers. As I'm still new to the remote debugging thing does anyone have any pointers/suggestions for how to extract more information next time it crashes and what sort of information I should post? Thanks, david From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 09:19:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9B6216A41F for ; Wed, 21 Dec 2005 09:19:36 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D94F143D46 for ; Wed, 21 Dec 2005 09:19:35 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBL9JWkf078553; Wed, 21 Dec 2005 07:19:34 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: "Bjoern A. Zeeb" Date: Wed, 21 Dec 2005 07:19:28 -0200 User-Agent: KMail/1.8.3 References: <5fbf03c20512200032w38d571d9u266ba3f77f93344f@mail.gmail.com> <5fbf03c20512200144l48aee31dm578c111ac352cec6@mail.gmail.com> <20051220094927.F23668@maildrop.int.zabbadoz.net> In-Reply-To: <20051220094927.F23668@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512210719.28497.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: www/86888: new motherboard for the 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: Wed, 21 Dec 2005 09:19:36 -0000 On Tuesday 20 December 2005 07:51, Bjoern A. Zeeb wrote: > but reading this could you try > sysctl dev.skc.0.int_mod=3D200 Hi good tip, with it my sk up/down message went away. thank you Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 16:19:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0198C16A425 for ; Wed, 21 Dec 2005 16:19:31 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id D20BD43D66 for ; Wed, 21 Dec 2005 16:19:25 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 4296153 for multiple; Wed, 21 Dec 2005 11:20:59 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id jBLGJJDP016736; Wed, 21 Dec 2005 11:19:20 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Wed, 21 Dec 2005 11:16:20 -0500 User-Agent: KMail/1.8.2 References: <43A91804.4090301@jetnet.co.uk> In-Reply-To: <43A91804.4090301@jetnet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512211116.21392.jhb@freebsd.org> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: how to get more info #2 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: Wed, 21 Dec 2005 16:19:32 -0000 On Wednesday 21 December 2005 03:53 am, David Reid wrote: > Following on from my last attempt to get more information on why my box > keeps rebooting, it was suggested that the lack of panics was a function > of running under X. Off list it was suggested I try remote debugging > via firewire, something I have now done. > > The panic showed up in vm_map_entry_splay as a page fault. The function > was called following a trap 0xc. > > I tried to get into gdb to get more information but it complained about > a lack of remote debuggers. > > As I'm still new to the remote debugging thing does anyone have any > pointers/suggestions for how to extract more information next time it > crashes and what sort of information I should post? Compile KDB and DDB into the kernel. You can then use 'tr' in ddb to get a stack trace. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 21 18:47:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CD1C16A41F; Wed, 21 Dec 2005 18:47:45 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9439543D6B; Wed, 21 Dec 2005 18:47:38 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jBLIlYTV018725; Wed, 21 Dec 2005 10:47:34 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jBLIlYi4018723; Wed, 21 Dec 2005 10:47:34 -0800 (PST) (envelope-from jmg) Date: Wed, 21 Dec 2005 10:47:33 -0800 From: John-Mark Gurney To: John Baldwin Message-ID: <20051221184733.GF19490@funkthat.com> Mail-Followup-To: John Baldwin , freebsd-amd64@freebsd.org References: <43A91804.4090301@jetnet.co.uk> <200512211116.21392.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512211116.21392.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-amd64@freebsd.org Subject: Re: how to get more info #2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2005 18:47:45 -0000 John Baldwin wrote this message on Wed, Dec 21, 2005 at 11:16 -0500: > On Wednesday 21 December 2005 03:53 am, David Reid wrote: > > Following on from my last attempt to get more information on why my box > > keeps rebooting, it was suggested that the lack of panics was a function > > of running under X. Off list it was suggested I try remote debugging > > via firewire, something I have now done. > > > > The panic showed up in vm_map_entry_splay as a page fault. The function > > was called following a trap 0xc. > > > > I tried to get into gdb to get more information but it complained about > > a lack of remote debuggers. > > > > As I'm still new to the remote debugging thing does anyone have any > > pointers/suggestions for how to extract more information next time it > > crashes and what sort of information I should post? > > Compile KDB and DDB into the kernel. You can then use 'tr' in ddb to get a > stack trace. add option GDB if you want to try to use gdb w/ it too. Though ddb is usually enough for basic stuff like getting a back trace like jhb said above... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 00:33:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29F9E16A41F for ; Thu, 22 Dec 2005 00:33:30 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78C1F43D92 for ; Thu, 22 Dec 2005 00:33:18 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 49F73F7CE for ; Wed, 21 Dec 2005 17:33:12 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 121F3F7C5 for ; Wed, 21 Dec 2005 17:33:12 -0700 (MST) Date: Wed, 21 Dec 2005 17:33:11 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051221173311.1fb1670b.kgunders@teamcool.net> In-Reply-To: <20051220231018.5b383a39.kgunders@teamcool.net> References: <20051220160752.0f6dcc43.kgunders@teamcool.net> <20051220231018.5b383a39.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Tyan TA26, LSI 320-1, and FBSD6.0 Strangeness 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, 22 Dec 2005 00:33:30 -0000 On Tue, 20 Dec 2005 23:10:18 -0700 Ken Gunderson wrote: > On Tue, 20 Dec 2005 16:07:52 -0700 > Ken Gunderson wrote: > > > Hello List: > > > > I'm having a tough time w/a Tyan TA26, 320-1 and 6.0-RELEASE that > > I'm hoping y'all may be able to shed some light on. I create logical > > drives and install FBSD just fine. Then cvsup, buildworld, > > buildkernel, installkernel. Upon reboot the system drives (mirror) are > > in degraded mode and the raid0 drive (swap) is offline. MegaRAID is > > unable to rebuild the arrays. I've called LSI support and they're > > mystified as well. > > [big snippage] > > > E) Present Status: > > > > Interestingly enough, I am able to FORCE Physical Drive 1 back online > > and then "Check Consistency". Presently 21% complete so don't know if > > it will choke on error on not yet. > > Update- > > The consistency check did complete w/o any errors and rebooting all > logical drives are once again in "Optimal" state. For sake of > completeness heres the dmesg: [more snippage] Yet another follow up on my own post... Update Redoux: 1) Using the amr driver from 7-CURRENT yields same results. 2) Did some testing playing musical hard drive slots. IF I do NOT use slot 1 (# on Tyan Backplane starts w/1) and use the EXACT same raid config for the mirror usings, e.g. slots 2 & 3, then all works as normally expected. So it would seem that Tyan and/or LSI have something Foobarred? Or that for some reason FBSD is overwriting directly to disk on slot 1 (i.e. da0) even though it's not technically there? Bizarre hardware issues. My raison d'etre... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 04:31:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C71EC16A41F for ; Thu, 22 Dec 2005 04:31:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6AEB43D5A for ; Thu, 22 Dec 2005 04:30:55 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBM4UpFm065998; Wed, 21 Dec 2005 21:30:54 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43AA2BFB.3050408@samsco.org> Date: Wed, 21 Dec 2005 21:30:51 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20051220160752.0f6dcc43.kgunders@teamcool.net> <20051220231018.5b383a39.kgunders@teamcool.net> <20051221173311.1fb1670b.kgunders@teamcool.net> In-Reply-To: <20051221173311.1fb1670b.kgunders@teamcool.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Tyan TA26, LSI 320-1, and FBSD6.0 Strangeness 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, 22 Dec 2005 04:31:02 -0000 Ken Gunderson wrote: > On Tue, 20 Dec 2005 23:10:18 -0700 > Ken Gunderson wrote: > > >>On Tue, 20 Dec 2005 16:07:52 -0700 >>Ken Gunderson wrote: >> >> >>>Hello List: >>> >>>I'm having a tough time w/a Tyan TA26, 320-1 and 6.0-RELEASE that >>>I'm hoping y'all may be able to shed some light on. I create logical >>>drives and install FBSD just fine. Then cvsup, buildworld, >>>buildkernel, installkernel. Upon reboot the system drives (mirror) are >>>in degraded mode and the raid0 drive (swap) is offline. MegaRAID is >>>unable to rebuild the arrays. I've called LSI support and they're >>>mystified as well. >> >>[big snippage] >> >> >>>E) Present Status: >>> >>>Interestingly enough, I am able to FORCE Physical Drive 1 back online >>>and then "Check Consistency". Presently 21% complete so don't know if >>>it will choke on error on not yet. >> >>Update- >> >>The consistency check did complete w/o any errors and rebooting all >>logical drives are once again in "Optimal" state. For sake of >>completeness heres the dmesg: > > > [more snippage] > > Yet another follow up on my own post... > > Update Redoux: > > 1) Using the amr driver from 7-CURRENT yields same results. > > 2) Did some testing playing musical hard drive slots. IF I do NOT > use slot 1 (# on Tyan Backplane starts w/1) and use the EXACT same raid > config for the mirror usings, e.g. slots 2 & 3, then all works as > normally expected. > > So it would seem that Tyan and/or LSI have something Foobarred? Or > that for some reason FBSD is overwriting directly to disk on slot 1 > (i.e. da0) even though it's not technically there? > > Bizarre hardware issues. My raison d'etre... > There is no way for FreeBSD to directly access disks attached to the RAID controller. All reads and writes to the array are bounded by the controller, and there simply is no way to get around that. With a certain amount of advanced hacking it would be possible to corrupt the disks with the amr_cam module, but even that is disabled with 7-CURRENT. What I'd actually suspect is that the backplane and/or slot connector is bad, so bad that simple parity detection cannot catch it. Some controllers allow you to run scans on individual disks from within a controlled environment, like the BIOS. I don't recall if the LSI cards have this feature, but if they do then they could almost certainly verify this. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 09:06:41 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3369016A41F for ; Thu, 22 Dec 2005 09:06:41 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7358443D53 for ; Thu, 22 Dec 2005 09:06:40 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 189E6F7CE; Thu, 22 Dec 2005 02:06:39 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id BBB9FF7C5; Thu, 22 Dec 2005 02:06:38 -0700 (MST) Date: Thu, 22 Dec 2005 02:06:37 -0700 From: Ken Gunderson To: Scott Long Message-Id: <20051222020637.6d099d40.kgunders@teamcool.net> In-Reply-To: <43AA2BFB.3050408@samsco.org> References: <20051220160752.0f6dcc43.kgunders@teamcool.net> <20051220231018.5b383a39.kgunders@teamcool.net> <20051221173311.1fb1670b.kgunders@teamcool.net> <43AA2BFB.3050408@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: Tyan TA26, LSI 320-1, and FBSD6.0 Strangeness 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, 22 Dec 2005 09:06:41 -0000 On Wed, 21 Dec 2005 21:30:51 -0700 Scott Long wrote: > Ken Gunderson wrote: > > > On Tue, 20 Dec 2005 23:10:18 -0700 > > Ken Gunderson wrote: > > > > > >>On Tue, 20 Dec 2005 16:07:52 -0700 > >>Ken Gunderson wrote: > >> > >> > >>>Hello List: > >>> > >>>I'm having a tough time w/a Tyan TA26, 320-1 and 6.0-RELEASE that > >>>I'm hoping y'all may be able to shed some light on. I create logical > >>>drives and install FBSD just fine. Then cvsup, buildworld, > >>>buildkernel, installkernel. Upon reboot the system drives (mirror) are > >>>in degraded mode and the raid0 drive (swap) is offline. MegaRAID is > >>>unable to rebuild the arrays. I've called LSI support and they're > >>>mystified as well. > >> > >>[big snippage] > >> > >> > >>>E) Present Status: > >>> > >>>Interestingly enough, I am able to FORCE Physical Drive 1 back online > >>>and then "Check Consistency". Presently 21% complete so don't know if > >>>it will choke on error on not yet. > >> > >>Update- > >> > >>The consistency check did complete w/o any errors and rebooting all > >>logical drives are once again in "Optimal" state. For sake of > >>completeness heres the dmesg: > > > > > > [more snippage] > > > > Yet another follow up on my own post... > > > > Update Redoux: > > > > 1) Using the amr driver from 7-CURRENT yields same results. > > > > 2) Did some testing playing musical hard drive slots. IF I do NOT > > use slot 1 (# on Tyan Backplane starts w/1) and use the EXACT same raid > > config for the mirror usings, e.g. slots 2 & 3, then all works as > > normally expected. > > > > So it would seem that Tyan and/or LSI have something Foobarred? Or > > that for some reason FBSD is overwriting directly to disk on slot 1 > > (i.e. da0) even though it's not technically there? > > > > Bizarre hardware issues. My raison d'etre... > > > > There is no way for FreeBSD to directly access disks attached to the > RAID controller. All reads and writes to the array are bounded by the > controller, and there simply is no way to get around that. With a > certain amount of advanced hacking it would be possible to corrupt the > disks with the amr_cam module, but even that is disabled with 7-CURRENT. > What I'd actually suspect is that the backplane and/or slot connector is > bad, so bad that simple parity detection cannot catch it. Well, I told y'all it was BIZARRE .... The blackplane and/or connector issue was the conclusion last time around. So that machine was RMA'd by Tyan. The replacement was reportedly double checked by Tyan tech prior to being shipped. Now I'm seeing same with 2nd machine. And to make matters even more interesting... I've subsequently confirmed on yet a 3rd. I've done some additional testing w/7-CURRENT amr driver w/one of the mirrored hd's back in slot #1. If I just grab amr from cvs and build an SMP kernel I can boot into the new kernel just fine. If I then buildworld and reboot w/o proceeding any further then I get degraded arrary that I can't rebuild, e.g: $ dmesg |grep amr amr0: mem 0xff4f0000-0xff4fffff irq 29 at device 4.0 on pci1 amr0: delete logical drives supported by controller amr0: Firmware 1L37, BIOS G119, 64MB RAM amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 66036MB (135241728 sectors) RAID 1 (degraded) amrd1: on amr0 amrd1: 8198MB (16789504 sectors) RAID 0 (offline) amrd2: on amr0 amrd2: 140270MB (287272960 sectors) RAID 5 (optimal) amrd1: I/O error - 0x1 Trying to mount root from ufs:/dev/amrd0s1a So this would indicate there _might_ be something amis w/the amr driver that only pops up under a bit of I/O load, e.g. buildworld. But if this were the case then why would it only show up when using Slot 1? Other possibility is that there is something just plain broken at the hardware/ firmware level with either the LSI card or the Tyan unit. I'd lean more towards the latter since the LSI 320-1 had been on the market for a long time now and widely deployed. Especially compared to the Tyan TA-26. So it seems like the odds alone would point more towards the Tyan. The good news is that LSI seems quite interested in further investigation (wish I could say the same for Tyan). Bad news is that their lab is undergoing remodeling. Or so I am told. > Some controllers allow you to run scans on individual disks from within > a controlled environment, like the BIOS. I don't recall if the LSI > cards have this feature, but if they do then they could almost certainly > verify this. The 320-1 does not. Or at least not that I've found. Maybe there's some top secret proceedure somewhere I don't know about... I can only do consistency checks at logical drive level. -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 10:40:13 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2708D16A41F for ; Thu, 22 Dec 2005 10:40:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 485A843D60 for ; Thu, 22 Dec 2005 10:40:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBMAeAjC074534 for ; Thu, 22 Dec 2005 10:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBMAeAlQ074533; Thu, 22 Dec 2005 10:40:10 GMT (envelope-from gnats) Resent-Date: Thu, 22 Dec 2005 10:40:10 GMT Resent-Message-Id: <200512221040.jBMAeAlQ074533@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, ted Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7D9E16A420 for ; Thu, 22 Dec 2005 10:36:49 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 647BF43D67 for ; Thu, 22 Dec 2005 10:36:49 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jBMAanga091462 for ; Thu, 22 Dec 2005 10:36:49 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jBMAanpj091461; Thu, 22 Dec 2005 10:36:49 GMT (envelope-from nobody) Message-Id: <200512221036.jBMAanpj091461@www.freebsd.org> Date: Thu, 22 Dec 2005 10:36:49 GMT From: ted To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/90798: asking if motherboard is compatible 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, 22 Dec 2005 10:40:13 -0000 >Number: 90798 >Category: amd64 >Synopsis: asking if motherboard is compatible >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Thu Dec 22 10:40:09 GMT 2005 >Closed-Date: >Last-Modified: >Originator: ted >Release: freebsd 6.0 >Organization: microsoft >Environment: n/a >Description: motherboard: manufacturer: nec computers international model: MS-7168 1.0 chipset: ATI Radeon RS480 rev 10 southbridge: ATI SB400 Bios AMI version: 080012 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 11:20:07 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E29F16A41F for ; Thu, 22 Dec 2005 11:20:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D7BD43D53 for ; Thu, 22 Dec 2005 11:20:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBMBK6Wu076251 for ; Thu, 22 Dec 2005 11:20:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBMBK6lF076250; Thu, 22 Dec 2005 11:20:06 GMT (envelope-from gnats) Date: Thu, 22 Dec 2005 11:20:06 GMT Message-Id: <200512221120.jBMBK6lF076250@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= Cc: Subject: Re: amd64/90798: asking if motherboard is compatible X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 11:20:07 -0000 The following reply was made to PR amd64/90798; it has been noted by GNATS. From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= To: bug-followup@FreeBSD.org, ted@hotmail.com Cc: Subject: Re: amd64/90798: asking if motherboard is compatible Date: Thu, 22 Dec 2005 12:16:56 +0100 Please send this kind of questions to the mailinglists 'questions' and/or 'amd64'. See also http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL Björn From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 13:51:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 179A616A41F for ; Thu, 22 Dec 2005 13:51:28 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 530B243D4C for ; Thu, 22 Dec 2005 13:51:27 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBMDpR1d046055 for ; Thu, 22 Dec 2005 11:51:27 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Thu, 22 Dec 2005 11:51:24 -0200 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512221151.25834.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: make depend fails releng_6 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, 22 Dec 2005 13:51:28 -0000 Hi make depend fails with a funny msg some idea? Or am I doing something worng here? Jo=E3o =2E..... function-growth=3D1000 -mcmodel=3Dkernel -mno-red-zone -mfpmath=3D387 -mn= o-sse=20 =2Dmno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tabl= es=20 =2Dffreestanding rm -f .depend mv .newdep .depend cd ../../../modules;=20 MAKEOBJDIRPREFIX=3D/usr/src/sys/amd64/compile/wipgw-64/modules=20 KMODDIR=3D/boot/kernel MODULES_OVERRIDE=3D"acpi splash bridge if_bridge"=20 MACHINE=3Damd64 KERNBUILDDIR=3D"/usr/src/sys/amd64/compile/wipgw-64" make = obj =3D=3D=3D> acpi (obj) "Makefile", line 4: "ACPI can only be compiled into the kernel on the amd64= =20 and ia64 platforms" *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/amd64/compile/wipgw-64. ######## uname -a ######## =46reeBSD gw64.matik.com.br 6.0-RELEASE FreeBSD 6.0-RELEASE #1: Tue Dec 20= =20 07:54:20 BRST 2005 =20 joao@gw64.matik.com.br:/usr/src/sys/amd64/compile/wipgw-64 amd64 ####### make.conf ####### CPUTYPE=3Dathlon64 PERL_VER=3D5.8.7 PERL_VERSION=3D5.8.7 MODULES_OVERRIDE=3Dacpi splash bridge if_bridge DOC_LANG=3Den_US.ISO8859-1 A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 14:33:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FD7616A41F for ; Thu, 22 Dec 2005 14:33:59 +0000 (GMT) (envelope-from bjoern.koenig@spray.se) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B71443D7F for ; Thu, 22 Dec 2005 14:33:50 +0000 (GMT) (envelope-from bjoern.koenig@spray.se) Received: from eurystheus.local (port-212-202-39-231.dynamic.qsc.de [212.202.39.231]) by efacilitas.de (Postfix) with ESMTP id 2D5784CBA7; Thu, 22 Dec 2005 15:42:17 +0100 (CET) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id B411E5285C; Thu, 22 Dec 2005 15:32:25 +0100 (CET) Message-ID: <43AAB951.6050604@spray.se> Date: Thu, 22 Dec 2005 15:33:53 +0100 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: JoaoBR References: <200512221151.25834.joao@matik.com.br> In-Reply-To: <200512221151.25834.joao@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: make depend fails releng_6 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, 22 Dec 2005 14:33:59 -0000 JoaoBR schrieb: > [...] > "Makefile", line 4: "ACPI can only be compiled into the kernel on the amd64 > and ia64 platforms" > *** Error code 1 > > [...] > MODULES_OVERRIDE=acpi splash bridge if_bridge > [...] The error message wants to tell you that you can't create an ACPI module. It have to be compiled into the kernel. Björn From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 14:36:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47F2516A41F for ; Thu, 22 Dec 2005 14:36:57 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A58A43D5C for ; Thu, 22 Dec 2005 14:36:56 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id D1BE2B832; Thu, 22 Dec 2005 16:36:55 +0200 (EET) Received: (nullmailer pid 29464 invoked by uid 1002); Thu, 22 Dec 2005 14:36:55 -0000 Date: Thu, 22 Dec 2005 16:36:55 +0200 From: Vasil Dimov To: JoaoBR Message-ID: <20051222143655.GB29372@qlovarnika.bg.datamax> References: <200512221151.25834.joao@matik.com.br> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <200512221151.25834.joao@matik.com.br> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 Cc: freebsd-amd64@freebsd.org Subject: Re: make depend fails releng_6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 14:36:57 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 22, 2005 at 11:51:24AM -0200, JoaoBR wrote: > =3D=3D=3D> acpi (obj) > "Makefile", line 4: "ACPI can only be compiled into the kernel on the amd= 64=20 > and ia64 platforms" > *** Error code 1 =2E.. > ####### > make.conf > ####### =2E.. > MODULES_OVERRIDE=3Dacpi splash bridge if_bridge You are requesting to build acpi as a module, which is not possible on amd64 --=20 Vasil Dimov --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFDqroHFw6SP/bBpCARAm79AKCAZFifu6BDh2uSrbbrRfLiB0KxWACfb50i jw392+nwaUW3JpsVZWZcywM= =qrSj -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 15:40:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D12F16A41F; Thu, 22 Dec 2005 15:40:36 +0000 (GMT) (envelope-from yuri@irfu.se) Received: from colibri.its.uu.se (colibri.its.UU.SE [130.238.4.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4844043D5E; Thu, 22 Dec 2005 15:40:34 +0000 (GMT) (envelope-from yuri@irfu.se) Received: by colibri.its.uu.se (Postfix, from userid 211) id 45402458; Thu, 22 Dec 2005 16:40:32 +0100 (NFT) Received: from colibri.its.uu.se(127.0.0.1) by colibri.its.uu.se via virus-scan id s14351; Thu, 22 Dec 05 16:40:18 +0100 Received: from hq.irfu.se (hq.irfu.se [130.238.30.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by colibri.its.uu.se (Postfix) with ESMTP id C0C38169; Thu, 22 Dec 2005 16:40:18 +0100 (NFT) Received: from ice.irfu.se (ice.irfu.se [130.238.30.157]) (authenticated bits=0) by hq.irfu.se (8.13.4/8.13.4) with ESMTP id jBMFeFu2095559 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 22 Dec 2005 16:40:15 +0100 (CET) (envelope-from yuri@irfu.se) From: Yuri Khotyaintsev Organization: Swedish Institute of Space Physics To: freebsd-amd64@freebsd.org, freebsd-stable@freebsd.org Date: Thu, 22 Dec 2005 16:40:14 +0100 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512221640.14676.yuri@irfu.se> X-Spam-Status: No, score=-1.4 required=7.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on hq.irfu.se Cc: Subject: Fatal trap 9: general protection fault while in kernel mode 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, 22 Dec 2005 15:40:36 -0000 I have updated kernel/world today on the system which was running without a= ny=20 problems since I installed it (old kernel is from November 28) and i got th= is=20 panic 10 minutes after boot (dmesg is attached below). The system is runnin= g=20 =46reeBSD/amd64 6-STABLE, SMP. [root@xx][/usr/obj/usr/src/sys/DB]# kgdb kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= =20 Undefined symbol "ps_pglobal_lookup"] 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 condition= s. 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: kernel trap 9 with interrupts disabled =46atal trap 9: general protection fault while in kernel mode cpuid =3D 3; apic id =3D 07 instruction pointer =3D 0x8:0xffffffff803b9754 stack pointer =3D 0x10:0xffffffffb35e0ab0 frame pointer =3D 0x10:0xffffff000002b3c0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 40 (irq34: mpt0) trap number =3D 9 panic: general protection fault cpuid =3D 3 Uptime: 2h2m14s Dumping 4095 MB (3 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 3583MB (917184 pages) 3567 3551 3535 3519 3503 3487 3471 3455 34= 39=20 3423 3407 3391 3375 3359 3343 3327 3311 3295 3279 3263 3247 3231 3215 3199= =20 3183 3167 3151 3135 3119 3103 3087 3071 3055 3039 3023 3007 2991 2975 2959= =20 2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719= =20 2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479= =20 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239= =20 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999= =20 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759= =20 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519= =20 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279= =20 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039= =20 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 7= 35=20 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431= =20 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127= =20 111 95 79 63 47 31 15 ... ok chunk 2: 512MB (131072 pages) 497 481 465 449 433 417 401 385 369 353 337= =20 321 305 289 273 257 241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); (kgdb) where #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff8025f637 in boot (howto=3D260)=20 at /usr/src/sys/kern/kern_shutdown.c:399 #3 0xffffffff8025fc95 in panic (fmt=3D0xffffff011f66f980 "@=EF=BF=BD\037\0= 01") at /usr/src/sys/kern/kern_shutdown.c:555 #4 0xffffffff803c918a in trap_fatal (frame=3D0xffffff011f66f980,=20 eva=3D18446742979019789120) at /usr/src/sys/amd64/amd64/trap.c:660 #5 0xffffffff803c960e in trap (frame=3D {tf_rdi =3D -1099511450688, tf_rsi =3D 0, tf_rdx =3D -2143527384, tf_= rcx =3D 0,=20 tf_r8 =3D -1099511451648, tf_r9 =3D 9223372036854775807, tf_rax =3D 18, tf_= rbx =3D=20 =2D1099498667008, tf_rbp =3D -1099511450688, tf_r10 =3D 0, tf_r11 =3D -1094= 689762496,=20 tf_r12 =3D -1099511146240, tf_r13 =3D 18, tf_r14 =3D -1094689818240, tf_r15= =3D=20 =2D1285682416, tf_trapno =3D 9, tf_addr =3D 0, tf_flags =3D -2145094526, tf= _err =3D 0,=20 tf_rip =3D -2143578284, tf_cs =3D 8, tf_rflags =3D 65606, tf_rsp =3D -12856= 82496,=20 tf_ss =3D 16}) at /usr/src/sys/amd64/amd64/trap.c:469 #6 0xffffffff803b71bb in calltrap ()=20 at /usr/src/sys/amd64/amd64/exception.S:168 #7 0xffffffff803b9754 in intr_execute_handlers (isrc=3D0xffffff000002b3c0, iframe=3D0xffffffffb35e0b10) at /usr/src/sys/amd64/amd64/intr_machdep.c= :213 #8 0xffffffff803bbdd1 in lapic_handle_intr (cookie=3D0xffffff000002b3c0, f= rame=3D {if_rdi =3D -1094689818240, if_rsi =3D -1094689818240, if_rdx =3D 582= , if_rcx=20 =3D 0, if_r8 =3D -1285681904, if_r9 =3D 9223372036854775807, if_rax =3D 0, = if_rbx =3D=20 =2D1094689818240, if_rbp =3D 0, if_r10 =3D 0, if_r11 =3D -1094689762496, if= _r12 =3D=20 =2D1099511148288, if_r13 =3D -1094689818240, if_r14 =3D 0, if_r15 =3D -1094= 689762496,=20 if_rip =3D -2143566227, if_cs =3D 8, if_rflags =3D 582, if_rsp =3D -1285682= 224, if_ss=20 =3D 16}) at /usr/src/sys/amd64/amd64/local_apic.c:612 #9 0xffffffff803b76bd in Xapic_isr2 () at apic_vector.S:133 #10 0xffffffff803bc66d in spinlock_exit () at cpufunc.h:391 #11 0xffffffff80247952 in ithread_loop (arg=3D0xffffff0000075100) at /usr/src/sys/kern/kern_intr.c:597 #12 0xffffffff802462d4 in fork_exit (callout=3D0xffffffff802475fe=20 , arg=3D0xffffff0000075100, frame=3D0xffffffffb35e0c50)=20 at /usr/src/sys/kern/kern_fork.c:789 =2D--Type to continue, or q to quit--- #13 0xffffffff803b751e in fork_trampoline ()=20 at /usr/src/sys/amd64/amd64/exception.S:394 #14 0x0000000000000000 in ?? () Previous frame identical to this frame (corrupt stack?) Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. =46reeBSD 6.0-STABLE #4: Thu Dec 22 12:13:33 CET 2005 root@xx.irfu.se:/usr/obj/usr/src/sys/DB Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.71-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf43 Stepping =3D 3 =46eatures=3D0xbfebfbff =46eatures2=3D0x641d> AMD Features=3D0x20100800 Hyperthreading: 2 logical CPUs real memory =3D 4831838208 (4608 MB) avail memory =3D 4134555648 (3943 MB) ACPI APIC Table: =46reeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 !=3D expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 !=3D expected base 56 ioapic3: Changing APIC ID to 11 ioapic3: WARNING: intbase 96 !=3D expected base 88 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard ioapic3 irqs 96-119 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 mpt0: port 0xec00-0xecff mem=20 0xfe9f0000-0xfe9fffff,0xfe9e0000-0xfe9effff irq 34 at device 5.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=3D1.2.12.0 mpt0: Unhandled Event Notify Frame. Event 0xa. mpt1: port 0xe800-0xe8ff mem=20 0xfe9d0000-0xfe9dffff,0xfe9c0000-0xfe9cffff irq 33 at device 5.1 on pci2 mpt1: [GIANT-LOCKED] mpt1: MPI Version=3D1.2.12.0 mpt1: Unhandled Event Notify Frame. Event 0xa. pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: at device 4.0 on pci0 pci4: on pcib4 pcib5: at device 5.0 on pci0 pci5: on pcib5 pcib6: at device 0.0 on pci5 pci6: on pcib6 em0: port=20 0xdcc0-0xdcff mem 0xfe6e0000-0xfe6fffff irq 64 at device 7.0 on pci6 em0: Ethernet address: 00:14:22:19:2c:56 pcib7: at device 0.2 on pci5 pci7: on pcib7 em1: port=20 0xccc0-0xccff mem 0xfe4e0000-0xfe4fffff irq 65 at device 8.0 on pci7 em1: Ethernet address: 00:14:22:19:2c:57 pcib8: at device 6.0 on pci0 pci8: on pcib8 pcib9: at device 0.0 on pci8 pci9: on pcib9 mpt2: port 0xbc00-0xbcff mem=20 0xfe1e0000-0xfe1fffff,0xfe1c0000-0xfe1dffff irq 106 at device 4.0 on pci9 mpt2: [GIANT-LOCKED] mpt2: MPI Version=3D1.2.9.0 mpt2: Unhandled Event Notify Frame. Event 0xa. mpt2: Capabilities: ( RAID-1E RAID-1 SAFTE ) mpt2: 0 Active Volumes (1 Max) mpt2: 0 Hidden Drive Members (6 Max) mpt3: port 0xb800-0xb8ff mem=20 0xfe1a0000-0xfe1bffff,0xfe180000-0xfe19ffff irq 107 at device 4.1 on pci9 mpt3: [GIANT-LOCKED] mpt3: MPI Version=3D1.2.9.0 mpt3: Unhandled Event Notify Frame. Event 0xa. mpt3: Capabilities: ( RAID-1E RAID-1 SAFTE ) mpt3: 0 Active Volumes (1 Max) mpt3: 0 Hidden Drive Members (6 Max) pcib10: at device 0.2 on pci8 pci10: on pcib10 uhci0: port 0x9ce0-0x9cff irq 1= 6=20 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x9cc0-0x9cdf irq 1= 9=20 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x9ca0-0x9cbf irq 1= 8=20 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfeb00000-0xfeb003ff irq 23= at=20 device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 2 ports with 2 removable, self powered pcib11: at device 30.0 on pci0 pci11: on pcib11 pci11: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port=20 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model VersaPad, device ID 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acp= i0 sio0: type 16550A orm0: at iomem=20 0xc0000-0xcafff,0xcb000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd0fff,0xec000-0xe= ffff=20 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle ses0 at mpt0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device=20 ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device=20 da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing= =20 Enabled da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) da2 at mpt3 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-3 device=20 da2: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing= =20 Enabled da2: 1667498MB (3415035904 512 byte sectors: 255H 63S/T 212576C) da1 at mpt2 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-3 device=20 da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing= =20 Enabled da1: 1667498MB (3415035904 512 byte sectors: 255H 63S/T 212576C) SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled,= =20 default to deny, logging disabled reboot after panic: general protection fault writing core to vmcore.0 em0: link state changed to UP em1: link state changed to UP =2D-=20 Dr. Yuri Khotyaintsev Institutet f=C3=B6r rymdfysik (IRF), Uppsala From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 15:48:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6CC216A41F for ; Thu, 22 Dec 2005 15:48:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A26D43D58 for ; Thu, 22 Dec 2005 15:47:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBMFlsWE069009; Thu, 22 Dec 2005 08:47:57 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43AACAAA.40501@samsco.org> Date: Thu, 22 Dec 2005 08:47:54 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20051220160752.0f6dcc43.kgunders@teamcool.net> <20051220231018.5b383a39.kgunders@teamcool.net> <20051221173311.1fb1670b.kgunders@teamcool.net> <43AA2BFB.3050408@samsco.org> <20051222020637.6d099d40.kgunders@teamcool.net> In-Reply-To: <20051222020637.6d099d40.kgunders@teamcool.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Tyan TA26, LSI 320-1, and FBSD6.0 Strangeness 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, 22 Dec 2005 15:48:04 -0000 Ken Gunderson wrote: > On Wed, 21 Dec 2005 21:30:51 -0700 > Scott Long wrote: > > >>Ken Gunderson wrote: >> >> >>>On Tue, 20 Dec 2005 23:10:18 -0700 >>>Ken Gunderson wrote: >>> >>> >>> >>>>On Tue, 20 Dec 2005 16:07:52 -0700 >>>>Ken Gunderson wrote: >>>> >>>> >>>> >>>>>Hello List: >>>>> >>>>>I'm having a tough time w/a Tyan TA26, 320-1 and 6.0-RELEASE that >>>>>I'm hoping y'all may be able to shed some light on. I create logical >>>>>drives and install FBSD just fine. Then cvsup, buildworld, >>>>>buildkernel, installkernel. Upon reboot the system drives (mirror) are >>>>>in degraded mode and the raid0 drive (swap) is offline. MegaRAID is >>>>>unable to rebuild the arrays. I've called LSI support and they're >>>>>mystified as well. >>>> >>>>[big snippage] >>>> >>>> >>>> >>>>>E) Present Status: >>>>> >>>>>Interestingly enough, I am able to FORCE Physical Drive 1 back online >>>>>and then "Check Consistency". Presently 21% complete so don't know if >>>>>it will choke on error on not yet. >>>> >>>>Update- >>>> >>>>The consistency check did complete w/o any errors and rebooting all >>>>logical drives are once again in "Optimal" state. For sake of >>>>completeness heres the dmesg: >>> >>> >>>[more snippage] >>> >>>Yet another follow up on my own post... >>> >>>Update Redoux: >>> >>>1) Using the amr driver from 7-CURRENT yields same results. >>> >>>2) Did some testing playing musical hard drive slots. IF I do NOT >>>use slot 1 (# on Tyan Backplane starts w/1) and use the EXACT same raid >>>config for the mirror usings, e.g. slots 2 & 3, then all works as >>>normally expected. >>> >>>So it would seem that Tyan and/or LSI have something Foobarred? Or >>>that for some reason FBSD is overwriting directly to disk on slot 1 >>>(i.e. da0) even though it's not technically there? >>> >>>Bizarre hardware issues. My raison d'etre... >>> >> >>There is no way for FreeBSD to directly access disks attached to the >>RAID controller. All reads and writes to the array are bounded by the >>controller, and there simply is no way to get around that. With a >>certain amount of advanced hacking it would be possible to corrupt the >>disks with the amr_cam module, but even that is disabled with 7-CURRENT. >>What I'd actually suspect is that the backplane and/or slot connector is >>bad, so bad that simple parity detection cannot catch it. > > > Well, I told y'all it was BIZARRE .... > > The blackplane and/or connector issue was the conclusion last time > around. So that machine was RMA'd by Tyan. The replacement was > reportedly double checked by Tyan tech prior to being shipped. Now I'm > seeing same with 2nd machine. And to make matters even more > interesting... I've subsequently confirmed on yet a 3rd. > > I've done some additional testing w/7-CURRENT amr driver w/one of the > mirrored hd's back in slot #1. If I just grab amr from cvs and > build an SMP kernel I can boot into the new kernel just fine. > > If I then buildworld and reboot w/o proceeding any further then I get > degraded arrary that I can't rebuild, e.g: > > $ dmesg |grep amr > amr0: mem 0xff4f0000-0xff4fffff irq 29 at > device 4.0 on pci1 amr0: delete logical drives supported by controller > amr0: Firmware 1L37, BIOS G119, 64MB RAM > amr0: delete logical drives supported by controller > amrd0: on amr0 > amrd0: 66036MB (135241728 sectors) RAID 1 (degraded) > amrd1: on amr0 > amrd1: 8198MB (16789504 sectors) RAID 0 (offline) > amrd2: on amr0 > amrd2: 140270MB (287272960 sectors) RAID 5 (optimal) > amrd1: I/O error - 0x1 > Trying to mount root from ufs:/dev/amrd0s1a > > So this would indicate there _might_ be something amis w/the amr driver > that only pops up under a bit of I/O load, e.g. buildworld. But if this > were the case then why would it only show up when using Slot 1? > The driver in 7-CURRENT was tested under extreme I/O load for 2 weeks before being committed to the tree. > Other possibility is that there is something just plain broken at the > hardware/ firmware level with either the LSI card or the Tyan unit. I'd > lean more towards the latter since the LSI 320-1 had been on the market > for a long time now and widely deployed. Especially compared to the > Tyan TA-26. So it seems like the odds alone would point more towards > the Tyan. > > The good news is that LSI seems quite interested in further > investigation (wish I could say the same for Tyan). Bad news is that > their lab is undergoing remodeling. Or so I am told. > > >>Some controllers allow you to run scans on individual disks from within >>a controlled environment, like the BIOS. I don't recall if the LSI >>cards have this feature, but if they do then they could almost certainly >>verify this. > > > The 320-1 does not. Or at least not that I've found. Maybe there's > some top secret proceedure somewhere I don't know about... I can only > do consistency checks at logical drive level. > Would it be at all possible to substitute a different controller card, even a plain SCSI one, and hook the backplane up to it? Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 15:58:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3004116A41F for ; Thu, 22 Dec 2005 15:58:45 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A3D43D5D for ; Thu, 22 Dec 2005 15:58:43 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBMFwhaa051240 for ; Thu, 22 Dec 2005 13:58:43 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Thu, 22 Dec 2005 13:58:42 -0200 User-Agent: KMail/1.8.3 References: <200512221151.25834.joao@matik.com.br> <43AAB951.6050604@spray.se> In-Reply-To: <43AAB951.6050604@spray.se> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512221358.42229.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: make depend fails releng_6 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, 22 Dec 2005 15:58:45 -0000 On Thursday 22 December 2005 12:33, Bj=F6rn K=F6nig wrote: > JoaoBR schrieb: > > [...] > > "Makefile", line 4: "ACPI can only be compiled into the kernel on the > > amd64 and ia64 platforms" > > *** Error code 1 > > > > [...] > > MODULES_OVERRIDE=3Dacpi splash bridge if_bridge > > [...] > > The error message wants to tell you that you can't create an ACPI > module. It have to be compiled into the kernel. > I see but still funny because I understood here that the "acpi can only be= =20 compiled into the kernel on amd64 and ia64 platforms" as if I had another=20 platform, this messages says nothing about a module probably something like=20 "you can not compile acpi as module on amd64" would be a clear statement. thank's, Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 20:10:24 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B7F16A41F for ; Thu, 22 Dec 2005 20:10:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C43143D66 for ; Thu, 22 Dec 2005 20:10:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBMKA7EX014116 for ; Thu, 22 Dec 2005 20:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBMKA7cJ014115; Thu, 22 Dec 2005 20:10:07 GMT (envelope-from gnats) Date: Thu, 22 Dec 2005 20:10:07 GMT Message-Id: <200512222010.jBMKA7cJ014115@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Denis Lemire Cc: Subject: Re: amd64/76336: racoon/setkey -D cases instant "Fatal Trap 12: Page fault while in kernel mode" on 5.3-RELEASE-P4 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Denis Lemire List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 20:10:24 -0000 The following reply was made to PR amd64/76336; it has been noted by GNATS. From: Denis Lemire To: bug-followup@FreeBSD.org, matthew@sorbs.net Cc: Subject: Re: amd64/76336: racoon/setkey -D cases instant "Fatal Trap 12: Page fault while in kernel mode" on 5.3-RELEASE-P4 Date: Thu, 22 Dec 2005 13:00:13 -0700 Issue is still present in FreeBSD 6.0-p1/amd64. Hoping this is fixed soon. = :( From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 22 22:11:28 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C098416A41F for ; Thu, 22 Dec 2005 22:11:28 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 216CF43D5D for ; Thu, 22 Dec 2005 22:11:10 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBMMB2Ea079787 for ; Fri, 23 Dec 2005 00:11:02 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 03325-11-2 for ; Fri, 23 Dec 2005 00:10:59 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBMM7gbe079699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 23 Dec 2005 00:07:43 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jBMM7qHO030924 for amd64@FreeBSD.org; Fri, 23 Dec 2005 00:07:52 +0200 (EET) (envelope-from ru) Date: Fri, 23 Dec 2005 00:07:52 +0200 From: Ruslan Ermilov To: amd64@FreeBSD.org Message-ID: <20051222220752.GB45319@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: Subject: Updating i386 in-place to 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: Thu, 22 Dec 2005 22:11:28 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi there, Yesterday, I was playing updating the i386 6.0-STABLE in-place to amd64 (the system was initially running on i386 core, then the disk was moved to the Opteron server). It succeeded, but there were some fun. The idea I had is to: 1) cross-build world and kernel 2) install kernel 3) install32 4) reboot 5) install world 6) update /etc etc. 7) remove i386 dust 1-3 went fine. On reboot, I was hoping that COMPAT_IA32 would be enough to run shell, make and mount* tools. I booted into single user. When it asked me to press ENTER for /bin/sh, I did this; it failed with SIGBUS. I have waited some seconds, and when it asked it again, this time it worked (I verified several times, and it always worked like this). i386 mount(8) did NOT work, so I had to use the "rescue" binary from /usr/obj to NFS mount /usr/src. After that, I fooled make(1) into thinking it runs on i386 and did an install of cross-built amd64 world (env MACHINE_ARCH=3Di386 MACHINE=3Di386 TARGET_ARCH=3Damd64 make installworld). This worked. I then updated /etc etc. from i386 to amd64 (by hand), and now I'm running a native amd64 world+kernel. P.S. It would be nice to be able to run i386 world under the amd64 kernel, but a lot of things don't just work (of course mainly syscalls). P.P.S. It would be nice to win a prize. :-) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDqyO4qRfpzJluFF4RAprdAJ9HkB0oJKA103w/PHmJ3o/OmkSHQQCfXJUy a5SPDGK5UuWNwaZkRoSVYec= =BXJN -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 10:54:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACFE716A41F for ; Fri, 23 Dec 2005 10:54:26 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7DCF43D58 for ; Fri, 23 Dec 2005 10:54:25 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRY003RI6IFS9D0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 23 Dec 2005 11:59:03 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRY00DHS6F5BE50@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 23 Dec 2005 11:57:06 +0100 (CET) Date: Fri, 23 Dec 2005 11:54:24 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH To: freebsd-amd64@freebsd.org Message-id: <20051223115424.2606720c.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: amd64 motherboards: GA-K8NF-9 needs notes 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, 23 Dec 2005 10:54:26 -0000 Hello, The Gigabyte GA-K8NF-9 motherboard is listed in the amd64 motherboards page. But the 'Notes' field is empty. If you look at the provided dmesg, you will see that the submitter has many comments on things that doesn't work (look under "Fixes"). IMHO, these comments should be put in the notes field. I just got a K8NF-9 and installed FreeBSD 6.0-release / amd64 on it. As I expected, nve didn't work, so I put in another network card until I get the machine upgraded to -stable. Currently busy doing just that. :-) BTW, should I snd-pr an update for this motherboard once I get the update done? -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 11:20:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F2116A41F for ; Fri, 23 Dec 2005 11:20:11 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BA5A43D5C for ; Fri, 23 Dec 2005 11:20:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 5A6AC1FFAD0; Fri, 23 Dec 2005 12:20:08 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id A048E1FFACD; Fri, 23 Dec 2005 12:20:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id AE69644487E; Fri, 23 Dec 2005 11:19:27 +0000 (UTC) Date: Fri, 23 Dec 2005 11:19:27 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Torfinn Ingolfsen In-Reply-To: <20051223115424.2606720c.torfinn.ingolfsen@broadpark.no> Message-ID: <20051223111740.Q1898@maildrop.int.zabbadoz.net> References: <20051223115424.2606720c.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 motherboards: GA-K8NF-9 needs notes 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, 23 Dec 2005 11:20:12 -0000 On Fri, 23 Dec 2005, Torfinn Ingolfsen wrote: Hi, > I just got a K8NF-9 and installed FreeBSD 6.0-release / amd64 on it. As > I expected, nve didn't work, so I put in another network card until I > get the machine upgraded to -stable. Currently busy doing just that. :-) The patch you need is not yet in stable. I will MFC it later today or the next days (a bit busy because of christmas ahead;) Until then you can get it from http://sources.zabbadoz.net/freebsd/patchset/nve-20051211-01.diff Greetings Bjoern -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 12:03:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6C3B16A420 for ; Fri, 23 Dec 2005 12:03:16 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1D4843D45 for ; Fri, 23 Dec 2005 12:03:12 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRY006JM9P13O90@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 23 Dec 2005 13:07:49 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRY00AX29LRY2J1@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 23 Dec 2005 13:05:51 +0100 (CET) Date: Fri, 23 Dec 2005 13:03:10 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20051223111740.Q1898@maildrop.int.zabbadoz.net> To: freebsd-amd64@freebsd.org Message-id: <20051223130310.1c127541.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20051223115424.2606720c.torfinn.ingolfsen@broadpark.no> <20051223111740.Q1898@maildrop.int.zabbadoz.net> Subject: Re: amd64 motherboards: GA-K8NF-9 needs notes 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, 23 Dec 2005 12:03:17 -0000 On Fri, 23 Dec 2005 11:19:27 +0000 (UTC) "Bjoern A. Zeeb" wrote: > The patch you need is not yet in stable. I will MFC it later today or > the next days (a bit busy because of christmas ahead;) > > Until then you can get it from > http://sources.zabbadoz.net/freebsd/patchset/nve-20051211-01.diff Ah! Thanks for telling me. I will get it, no worries. Focus on you christmas preparations, FreeBSD can wait. BTW, Merry Christmass, Happy Holidays, Seasons Greetings and so on to all you people who read this list! -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 13:08:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 459B416A41F for ; Fri, 23 Dec 2005 13:08:16 +0000 (GMT) (envelope-from lima@accuhosting.com) Received: from accuhosting.com (smtp01.accuhosting.com [200.122.141.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF7E243D58 for ; Fri, 23 Dec 2005 13:08:14 +0000 (GMT) (envelope-from lima@accuhosting.com) Received: from 201-0-8-208.dsl.telesp.net.br ([201.0.8.208] helo=morbid.accuhosting.com) by accuhosting.com with asmtp (Exim 4.34) id 1Epmed-0003Hn-UR for freebsd-amd64@freebsd.org; Fri, 23 Dec 2005 07:08:17 -0600 Date: Fri, 23 Dec 2005 11:08:17 -0200 From: Marcelo Lima To: freebsd-amd64@freebsd.org Message-ID: <20051223110817.3ba67c7d@morbid.accuhosting.com> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: base64 Subject: hardware 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, 23 Dec 2005 13:08:16 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpIaSBhbGws IA0KDQptZXJyeSBjaHJpc3RpbWFzcyBmb3IgYWxsDQoNCmFuZCBtYXJ2ZWxsIHl1a29uIGV0aGVy bmV0LCBicm9hZGNvbSB3aXJlbGVzcz8NCkkgaGF2ZSBub3RlYm9vayBnYXRld2F5IG14NzUxNSwg Zm9yIG5ldHdvcmsgSSB1c2UgdXNiIHdpcmVsZXNzIGJlY2F1c2UNCm9uYm9hcmQgd2lyZWxlc3Mg KGJyb2FkY29tKSBmcmVlYnNkIGRvbid0IHJlZ29uaXNlLCBtYXJ2ZWxsDQpldGhlcm5ldCB0b28g OigNCg0Kbm9uZTRAcGNpMjowOjA6IGNsYXNzPTB4MDIwMDAwIGNhcmQ9MHgyMDNkMTYxZiBjaGlw PTB4NDM1MTExYWIgcmV2PTB4MTANCmhkcj0weDAwIHZlbmRvciAgID0gJ01hcnZlbGwgU2VtaWNv bmR1Y3RvciAoV2FzOiBHYWxpbGVvIFRlY2hub2xvZ3kNCkx0ZCknIGRldmljZSAgID0gJzg4RTgw MzYgWXVrb24gUENJLUUgRmFzdCBFdGhlcm5ldCBDb250cm9sbGVyJw0KICAgIGNsYXNzICAgID0g bmV0d29yaw0KICAgIHN1YmNsYXNzID0gZXRoZXJuZXQNCg0Kbm9uZTVAcGNpMzo3OjA6IGNsYXNz PTB4MDI4MDAwIGNhcmQ9MHgwNDQ5MTRlNCBjaGlwPTB4NDMxODE0ZTQgcmV2PTB4MDINCmhkcj0w eDAwIHZlbmRvciAgID0gJ0Jyb2FkY29tIENvcnBvcmF0aW9uJw0KICAgIGNsYXNzICAgID0gbmV0 d29yaw0KDQpJIGhhdmUgc291cmNlIGNvZGUgYXQgbWFydmVsIHl1a29uIGV0aGVybmV0IGZvciBp Mzg2IGJ1dCBJIG5vdA0KZGV2ZWxvcGVyIGhlaGVoZQ0KDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRV UkUtLS0tLQ0KVmVyc2lvbjogR251UEcgdjEuNC4yIChGcmVlQlNEKQ0KDQppRDhEQlFGRHEvYkZ4 VUVVVmJoQyswZ1JBZ2k0QUtEZ0UxNzFtN2kzT0p4cnNEU2JFYWZDMnJzTjVBQ2VKUHlWDQo4ekJV a3p6V0Q0M0I5cXhHVm5pQTk0az0NCj1wRDJQDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0N Cg== From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 14:44:28 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 406E316A41F; Fri, 23 Dec 2005 14:44:28 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75DB443D8A; Fri, 23 Dec 2005 14:44:20 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.142] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.13.4/8.13.4) with ESMTP id jBNEiEXK070978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Dec 2005 08:44:17 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Message-ID: <43AC0D3F.5050902@palisadesys.com> Date: Fri, 23 Dec 2005 08:44:15 -0600 From: Guy Helmer User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <20051222220752.GB45319@ip.net.ua> In-Reply-To: <20051222220752.GB45319@ip.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-From: ghelmer@palisadesys.com Cc: amd64@freebsd.org Subject: Re: Updating i386 in-place to 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, 23 Dec 2005 14:44:28 -0000 Ruslan Ermilov wrote: >Hi there, > >Yesterday, I was playing updating the i386 6.0-STABLE in-place to >amd64 (the system was initially running on i386 core, then the >disk was moved to the Opteron server). It succeeded, but there >were some fun. The idea I had is to: > >1) cross-build world and kernel >2) install kernel >3) install32 >4) reboot >5) install world >6) update /etc etc. >7) remove i386 dust > >1-3 went fine. On reboot, I was hoping that COMPAT_IA32 would be >enough to run shell, make and mount* tools. I booted into single >user. When it asked me to press ENTER for /bin/sh, I did this; >it failed with SIGBUS. I have waited some seconds, and when it >asked it again, this time it worked (I verified several times, and >it always worked like this). i386 mount(8) did NOT work, so I >had to use the "rescue" binary from /usr/obj to NFS mount /usr/src. >After that, I fooled make(1) into thinking it runs on i386 and >did an install of cross-built amd64 world (env MACHINE_ARCH=i386 >MACHINE=i386 TARGET_ARCH=amd64 make installworld). This worked. >I then updated /etc etc. from i386 to amd64 (by hand), and now >I'm running a native amd64 world+kernel. > >P.S. It would be nice to be able to run i386 world under the >amd64 kernel, but a lot of things don't just work (of course >mainly syscalls). > >P.P.S. It would be nice to win a prize. :-) > > >Cheers, > > Wow, I'm impressed. I was trying to do an automated, in-place i386 to amd64 upgrade (without source, though) back in August and never got to the point of successfully booting an amd64 kernel running i386 binaries. I did get a good idea, though, that I never followed up on: Matthew Fuller suggested hijacking the swap partition for a temporary amd64 root partition (message id 20050809124756.GA27425@over-yonder.net). Guy Helmer From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 14:59:21 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED7D416A41F; Fri, 23 Dec 2005 14:59:21 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B7AF43D60; Fri, 23 Dec 2005 14:59:21 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-222-80-189.jan.bellsouth.net [68.222.80.189]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 50ACDDE; Fri, 23 Dec 2005 08:59:20 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 75D2561C21; Fri, 23 Dec 2005 08:59:19 -0600 (CST) Date: Fri, 23 Dec 2005 08:59:19 -0600 From: "Matthew D. Fuller" To: Guy Helmer Message-ID: <20051223145919.GH63497@over-yonder.net> References: <20051222220752.GB45319@ip.net.ua> <43AC0D3F.5050902@palisadesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43AC0D3F.5050902@palisadesys.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: amd64@freebsd.org Subject: Re: Updating i386 in-place to 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, 23 Dec 2005 14:59:22 -0000 On Fri, Dec 23, 2005 at 08:44:15AM -0600 I heard the voice of Guy Helmer, and lo! it spake thus: > Ruslan Ermilov wrote: > > >Yesterday, I was playing updating the i386 6.0-STABLE in-place to > >amd64 (the system was initially running on i386 core, then the disk > >was moved to the Opteron server). It succeeded, but there were > >some fun. The idea I had is to: > > Wow, I'm impressed. I was trying to do an automated, in-place i386 > to amd64 upgrade (without source, though) back in August and never > got to the point of successfully booting an amd64 kernel running > i386 binaries. I did get a good idea, though, that I never followed > up on: Matthew Fuller suggested hijacking the swap partition for a > temporary amd64 root partition (message id > 20050809124756.GA27425@over-yonder.net). Yeah, I like the extra safety margin that gave. I had a known-good i386 partition to boot while I made sure the amd64 one booted, and then a known-good (and pure) amd64 one to fall back on if I screwed up blatting the amd64 stuff over the real partitions. And it gave me an excuse to track down all the loader variables that needed to be set to boot off a different partition, which I've now re-forgotten (2 of 'em, I think, needed to be changed?) I never managed to get the amd64 kernel to load anything i386 in the boot path, either init (for multiuser) or sh (for single-user). This was 5.4, I think (maybe 5.3). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 19:53:45 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64DF916A41F for ; Fri, 23 Dec 2005 19:53:45 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44DF843D7C for ; Fri, 23 Dec 2005 19:53:30 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBNJrOfJ017382; Fri, 23 Dec 2005 21:53:24 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 20423-01; Fri, 23 Dec 2005 21:53:21 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBNJZUUD016890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Dec 2005 21:35:30 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jBNJZdhV032371; Fri, 23 Dec 2005 21:35:39 +0200 (EET) (envelope-from ru) Date: Fri, 23 Dec 2005 21:35:39 +0200 From: Ruslan Ermilov To: "Matthew D. Fuller" Message-ID: <20051223193539.GA31874@ip.net.ua> References: <20051222220752.GB45319@ip.net.ua> <43AC0D3F.5050902@palisadesys.com> <20051223145919.GH63497@over-yonder.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <20051223145919.GH63497@over-yonder.net> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: amd64@freebsd.org Subject: Re: Updating i386 in-place to 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, 23 Dec 2005 19:53:45 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 23, 2005 at 08:59:19AM -0600, Matthew D. Fuller wrote: > On Fri, Dec 23, 2005 at 08:44:15AM -0600 I heard the voice of > Guy Helmer, and lo! it spake thus: > > Ruslan Ermilov wrote: > >=20 > > >Yesterday, I was playing updating the i386 6.0-STABLE in-place to > > >amd64 (the system was initially running on i386 core, then the disk > > >was moved to the Opteron server). It succeeded, but there were > > >some fun. The idea I had is to: > > > > Wow, I'm impressed. I was trying to do an automated, in-place i386 > > to amd64 upgrade (without source, though) back in August and never > > got to the point of successfully booting an amd64 kernel running > > i386 binaries. I did get a good idea, though, that I never followed > > up on: Matthew Fuller suggested hijacking the swap partition for a > > temporary amd64 root partition (message id > > 20050809124756.GA27425@over-yonder.net). >=20 > Yeah, I like the extra safety margin that gave. I had a known-good > i386 partition to boot while I made sure the amd64 one booted, and > then a known-good (and pure) amd64 one to fall back on if I screwed up > blatting the amd64 stuff over the real partitions. And it gave me an > excuse to track down all the loader variables that needed to be set to > boot off a different partition, which I've now re-forgotten (2 of 'em, > I think, needed to be changed?) >=20 Nope, just one, always visible with kenv(1) when I forget it: vfs.root.mountfrom=3D"ufs:/dev/ad0a" Or "boot -a" in loader(8). > I never managed to get the amd64 > kernel to load anything i386 in the boot path, either init (for > multiuser) or sh (for single-user). This was 5.4, I think (maybe > 5.3). >=20 Well, this "somehow" works now. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDrFGLqRfpzJluFF4RAoH8AJ9LDZInGPjXA2RlD9KT9EHpsZfMgQCcCyYQ auDE3GsOtqrC+RMS2sWp4Bg= =mCMc -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 20:03:45 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74BDC16A41F; Fri, 23 Dec 2005 20:03:45 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE83643D5C; Fri, 23 Dec 2005 20:03:44 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-222-80-189.jan.bellsouth.net [68.222.80.189]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 1651EDE; Fri, 23 Dec 2005 14:03:44 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 31FC661C21; Fri, 23 Dec 2005 14:03:43 -0600 (CST) Date: Fri, 23 Dec 2005 14:03:43 -0600 From: "Matthew D. Fuller" To: Ruslan Ermilov Message-ID: <20051223200343.GJ63497@over-yonder.net> References: <20051222220752.GB45319@ip.net.ua> <43AC0D3F.5050902@palisadesys.com> <20051223145919.GH63497@over-yonder.net> <20051223193539.GA31874@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051223193539.GA31874@ip.net.ua> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: amd64@freebsd.org Subject: Re: Updating i386 in-place to 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, 23 Dec 2005 20:03:45 -0000 On Fri, Dec 23, 2005 at 09:35:39PM +0200 I heard the voice of Ruslan Ermilov, and lo! it spake thus: > > Nope, just one, always visible with kenv(1) when I forget it: > > vfs.root.mountfrom="ufs:/dev/ad0a" I think I had to mess with currdev and/or loaddev as well, to get it to boot of ad0s1b. > Well, this "somehow" works now. Yeah, it might be farther along enough in RELENG_6 to get a leg up. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 21:44:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11DBF16A41F; Fri, 23 Dec 2005 21:44:42 +0000 (GMT) (envelope-from groot@kde.org) Received: from multi.science.ru.nl (multi.science.ru.nl [131.174.16.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E37A43D68; Fri, 23 Dec 2005 21:44:40 +0000 (GMT) (envelope-from groot@kde.org) Received: from [83.116.148.63] (helo=[10.0.0.155]) (authen=adridg) by multi.science.ru.nl (8.13.5/5.7) with ESMTP id jBNLiVLe013846; Fri, 23 Dec 2005 22:44:31 +0100 (MET) From: Adriaan de Groot To: freebsd-acpi@freebsd.org Date: Fri, 23 Dec 2005 22:44:36 +0100 User-Agent: KMail/1.8.2 References: <200512221155.04352.groot@kde.org> In-Reply-To: <200512221155.04352.groot@kde.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512232244.37363.groot@kde.org> X-Spam-Score: -0.276 () BAYES_40 X-Scanned-By: MIMEDefang 2.48 on 131.174.16.159 Cc: freebsd-amd64@freebsd.org Subject: Re: Bad characters in Asus A8N-VM CSM 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, 23 Dec 2005 21:44:42 -0000 On Thursday 22 December 2005 11:55, Adriaan de Groot wrote: > I just picked up an Asus A8N-VM CSM motherboard. It's a nForce 430 + GFor= ge > 6150 integrated mini-ATX job, amd64, very 1337 and new. That means trouble > :) I knew that when buying it, and know now that it really needs work to > get it working at all. > > ACPI-0397: *** Error: NSSearchAndEnter: Bad character in ACPI Name: > 43035350 ACPI-0381: *** Error: Looking up [0x43035350] (NON-ASCII) > in namespace, AE_BAD_CHARACTER [Following up on myself, for documentation purposes, and CCing -amd64 to wa= rn=20 off potential users there as well.] Well, an instructive but unproductive evening yields the following: 1) Default BIOS (rev. 0403) and FBSD 5.1 amd64 boots, produces ACPI warning= =20 messages above and works normally (no NIC, no SATA tried). 2) Newest BIOS (rev. 0506) and FBSD 5.1 amd64 boots and then page faults in= =20 kernel mode in vm_pageq_enqueue right after GEOM adds ad0. ACPI warning is= =20 still there. 3) I didn't try 6-STABLE with the newest BIOS, since having busted ACPI the= re=20 means you can't get _anything_ done. =46rom the booted 5.1 environment I got an ACPI dump and after hacking utmi= sc.c=20 in contrib/dev/acpica to accept a broken character 0x03, I got a disassembl= y.=20 The bad character is in 0x43035350, which from the looks of the IASL should= =20 have been PSSC (0x43535350) but somehow isn't. It's in one of the processor= =20 sections (the other has a Name(PSSC, 0x0A) ). Elsewhere in the IASL there's some undefined symbols ending in _HFZF (sorry= , I=20 don't have the machine under scrutiny on or functional at this very moment)= ,=20 which I suppose is semi-normal, and then a totally weird-ass Return( While(Local1) { ... }) This chokes the compiler, of course. I suspect that it should read Return(0x00) While (Local1) ... or so, but this suggests yet more broken ACPI tables. Over in Linux land, http://www.nvnews.net/vbulletin/showthread.php?t=3D6059= 6=20 shows that with some effort and the latest of the latest everything, it is= =20 possible to get a functioning machine. If I can create a barely legal ASL=20 file that compiles, I'll have to try out what's described in "11.16.5.3=20 Overriding the Default AML " of the handbook. Until then (or someone more competent than myself deals with the issues), I= 'd=20 suggest avoiding this board entirely. [ade] From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 24 04:19:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E1A316A41F for ; Sat, 24 Dec 2005 04:19:49 +0000 (GMT) (envelope-from vikashb@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DE9343D46 for ; Sat, 24 Dec 2005 04:19:47 +0000 (GMT) (envelope-from vikashb@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so227405uge for ; Fri, 23 Dec 2005 20:19:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=utaju3FQvAjn/cRQzt97gv9eucMbbgroNvvNsYKN5cTE3jN5voZqtNJn7F1/sa4iac0l/kmT/mz0E6XZwUFFKSATtm8BstNQSAbFdzjHlJIhJErVOreYRaaJtaTxzaYoc+BDb6aWHGYlnxMAzuP2Qg1ovKbDPFJ0ycgXiGhKqJQ= Received: by 10.66.225.5 with SMTP id x5mr1102157ugg; Fri, 23 Dec 2005 20:19:46 -0800 (PST) Received: from winxp ( [196.209.60.150]) by mx.gmail.com with ESMTP id q1sm1792795uge.2005.12.23.20.19.35; Fri, 23 Dec 2005 20:19:44 -0800 (PST) Message-ID: <000b01c60841$4536bef0$080a0a0a@winxp> From: "Vikash" To: Date: Sat, 24 Dec 2005 06:19:36 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Subject: biostar GeForce 6100-M9 motherboard 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, 24 Dec 2005 04:19:49 -0000 Greetings, If this is the incorrect list, please refer me to the correct list. I have a biostar GeForce 6100-M9 motherboard with an AMD Athlon 64 Processor 3500+ cpu (http://www.biostar.com.tw/products/mainboard/board.php?name=GeForce%206100-M9) i have managed to install 6.0-RELEASE and upgraded to 6.0-STABLE: the on board lan is not detected and the ata controller is marked as generic the verbose dmesg is bellow: please advise as to how i can help to get the ata working at better than umda33 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-STABLE #0: Sat Dec 24 02:36:46 SAST 2005 root@supernova2.my.domain:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8097b000. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193245 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2210077283 Hz CPU: AMD Athlon(tm) 64 Processor 3500+ (2210.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 1055850496 (1006 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000a78000 - 0x000000003d12ffff, 1013678080 bytes (247480 pages) avail memory = 1007902720 (961 MB) APIC: CPU 0 has ACPI ID 0 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: high MADT: Interrupt override: source 14, irq 14 ioapic0: intpin 14 trigger: edge ioapic0: intpin 14 polarity: high MADT: Interrupt override: source 15, irq 15 ioapic0: intpin 15 trigger: edge ioapic0: intpin 15 polarity: high lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high MADT: Ignoring local NMI routed to ACPI CPU 1 ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050010 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device mem: io: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80006804 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=050000] [hdr=80] is there (id=02f110de) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 10 func 0 acpi0: Power Button (fixed) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR AcpiOsDerivePciId: bus 0 dev 5 func 0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 5 7 9 10 11 14 15 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 5 7 9 10 11 14 15 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 5 7 9 10 11 14 15 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 5 7 9 10 11 14 15 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 5 7 9 10 11 14 15 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 5 7 9 10 11 14 15 pci_link8: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link9: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link9: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link9: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 5 7 9 10 11 14 15 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 5 7 9 10 11 14 15 pci_link10: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link11: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 14 15 pci_link11: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 14 15 pci_link11: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link12: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link12: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link12: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link13: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 5 7 9 10 11 14 15 pci_link13: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 5 7 9 10 11 14 15 pci_link13: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link14: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link14: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link14: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link15: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 5 7 9 10 11 14 15 pci_link15: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 5 7 9 10 11 14 15 pci_link15: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link16: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 14 15 pci_link16: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 14 15 pci_link16: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link17: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link17: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link17: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link18: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 14 15 pci_link18: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 14 15 pci_link18: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 14 15 pci_link19: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link19: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link19: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link20: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link20: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link20: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 17 pci_link21: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link21: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link21: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 18 pci_link22: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link22: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link22: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 19 pci_link23: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link23: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link23: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link24: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link24: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link24: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link25: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link25: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link25: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link26: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link26: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link26: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 16 pci_link27: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link27: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link28: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link29: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link30: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link31: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link32: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link32: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link32: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link33: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link33: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link33: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link34: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link34: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link34: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link35: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link35: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link35: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link36: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link36: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link36: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link37: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link37: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link37: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link38: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link38: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 pci_link38: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 21 22 23 acpi0: reservation of 1bf00000, 100000 (3) failed acpi0: reservation of 2bf00000, 100000 (3) failed acpi0: reservation of 3bf00000, 100000 (3) failed ACPI timer: 1/2 1/2 1/2 1/2 1/2 1/1 1/2 1/2 1/2 1/2 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x10de, dev=0x02f1, revid=0xa2 bus=0, slot=0, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02fa, revid=0xa2 bus=0, slot=0, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0100, statreg=0x4020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02fe, revid=0xa2 bus=0, slot=0, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02f8, revid=0xa2 bus=0, slot=0, func=3 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02f9, revid=0xa2 bus=0, slot=0, func=4 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02ff, revid=0xa2 bus=0, slot=0, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x027f, revid=0xa2 bus=0, slot=0, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0102, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x027e, revid=0xa2 bus=0, slot=0, func=7 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02fc, revid=0xa1 bus=0, slot=2, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02fd, revid=0xa1 bus=0, slot=3, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x02fb, revid=0xa1 bus=0, slot=4, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0242, revid=0xa2 bus=0, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 32, base fb000000, size 24, enabled map[14]: type 3, range 64, base d0000000, size 28, enabled map[1c]: type 1, range 64, base fc000000, size 24, enabled pcib0: matched entry for 0.5.INTA (src \\_SB_.PCI0.APC7:0) pci_link25: Picked IRQ 16 with weight 0 pcib0: slot 5 INTA routed to irq 16 via \\_SB_.PCI0.APC7 found-> vendor=0x10de, dev=0x0270, revid=0xa2 bus=0, slot=9, func=0 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0261, revid=0xa2 bus=0, slot=10, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0264, revid=0xa2 bus=0, slot=10, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 00001c00, size 6, enabled map[24]: type 4, range 32, base 00001c40, size 6, enabled pcib0: matched entry for 0.10.INTA (src \\_SB_.PCI0.APCS:0) pci_link34: Picked IRQ 20 with weight 0 pcib0: slot 10 INTA routed to irq 20 via \\_SB_.PCI0.APCS found-> vendor=0x10de, dev=0x0272, revid=0xa2 bus=0, slot=10, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0400, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x026d, revid=0xa2 bus=0, slot=11, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fe02f000, size 12, enabled pcib0: matched entry for 0.11.INTA (src \\_SB_.PCI0.APCF:0) pci_link27: Picked IRQ 21 with weight 0 pcib0: slot 11 INTA routed to irq 21 via \\_SB_.PCI0.APCF found-> vendor=0x10de, dev=0x026e, revid=0xa2 bus=0, slot=11, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fe02e000, size 8, enabled found-> vendor=0x10de, dev=0x0265, revid=0xa1 bus=0, slot=13, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000f400, size 4, enabled found-> vendor=0x10de, dev=0x0266, revid=0xa1 bus=0, slot=14, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type 4, range 32, base 000009f0, size 3, enabled map[14]: type 4, range 32, base 00000bf0, size 2, enabled map[18]: type 4, range 32, base 00000970, size 3, enabled map[1c]: type 4, range 32, base 00000b70, size 2, enabled map[20]: type 4, range 32, base 0000e000, size 4, enabled map[24]: type 1, range 32, base fe02d000, size 12, enabled pcib0: matched entry for 0.14.INTA (src \\_SB_.PCI0.APSI:0) pci_link38: Picked IRQ 22 with weight 0 pcib0: slot 14 INTA routed to irq 22 via \\_SB_.PCI0.APSI found-> vendor=0x10de, dev=0x026f, revid=0xa2 bus=0, slot=16, func=0 class=06-04-01, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x026b, revid=0xa2 bus=0, slot=16, func=2 class=04-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=c, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000dc00, size 8, enabled map[14]: type 4, range 32, base 0000d800, size 8, enabled map[18]: type 1, range 32, base fe02c000, size 12, enabled pcib0: matched entry for 0.16.INTC (src \\_SB_.PCI0.APCJ:0) pci_link30: Picked IRQ 23 with weight 0 pcib0: slot 16 INTC routed to irq 23 via \\_SB_.PCI0.APCJ found-> vendor=0x10de, dev=0x0269, revid=0xa1 bus=0, slot=20, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fe02b000, size 12, enabled map[14]: type 4, range 32, base 0000d400, size 3, enabled pcib0: matched entry for 0.20.INTA (src \\_SB_.PCI0.APCH:0) pci_link29: Picked IRQ 20 with weight 1 pcib0: slot 20 INTA routed to irq 20 via \\_SB_.PCI0.APCH found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xa000-0xafff pcib1: memory decode 0xfd700000-0xfd7fffff pcib1: prefetched decode 0xfde00000-0xfdefffff pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.XVRC - AE_NOT_FOUND pci1: on pcib1 pci1: physical bus=1 pcib2: at device 3.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0x9000-0x9fff pcib2: memory decode 0xfdd00000-0xfddfffff pcib2: prefetched decode 0xfdc00000-0xfdcfffff pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.XVRB - AE_NOT_FOUND pci2: on pcib2 pci2: physical bus=2 pcib3: at device 4.0 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xb000-0xbfff pcib3: memory decode 0xfd900000-0xfd9fffff pcib3: prefetched decode 0xfd800000-0xfd8fffff pcib3: could not get PCI interrupt routing table for \\_SB_.PCI0.XVRA - AE_NOT_FOUND pci3: on pcib3 pci3: physical bus=3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 21 at device 11.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02f000 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff at device 11.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe02e000 pcib0: matched entry for 0.11.INTB (src \\_SB_.PCI0.APCL:0) pci_link35: Picked IRQ 21 with weight 1 pcib0: slot 11 INTB routed to irq 21 via \\_SB_.PCI0.APCL ehci0: [GIANT-LOCKED] usb1: waiting for BIOS to give up control usb1: timed out waiting for BIOS usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf400-0xf40f at device 13.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf400 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=50 ata0: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 ata0: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 ata0: stat0=0x90 err=0x90 lsb=0x90 msb=0x90 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=50 devices=0x3 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=60 ostat1=70 ata1: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata1: stat1=0x30 err=0x30 lsb=0x30 msb=0x30 ata1: reset tp2 stat0=20 stat1=30 devices=0x0 ata1: [MPSAFE] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 22 at device 14.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe000 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata2: reset tp1 mask=03 ostat0=7f ostat1=7f ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat0=0x7f err=0xff lsb=0xff msb=0xff ata2: stat1=0x7f err=0xff lsb=0xff msb=0xff ata2: reset tp2 stat0=ff stat1=ff devices=0x0 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata3: reset tp1 mask=03 ostat0=7f ostat1=7f ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat0=0x7f err=0xff lsb=0xff msb=0xff ata3: stat1=0x7f err=0xff lsb=0xff msb=0xff ata3: reset tp2 stat0=ff stat1=ff devices=0x0 ata3: [MPSAFE] pcib4: at device 16.0 on pci0 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0xc000-0xcfff pcib4: memory decode 0xfdb00000-0xfdbfffff pcib4: prefetched decode 0xfda00000-0xfdafffff pcib4: Subtractively decoded bridge. pci4: on pcib4 pci4: physical bus=4 found-> vendor=0x10ec, dev=0x8139, revid=0x10 bus=4, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000cc00, size 8, enabled pcib4: (null) requested I/O range 0xcc00-0xccff: in range map[14]: type 1, range 32, base fdbff000, size 8, enabled pcib4: (null) requested memory range 0xfdbff000-0xfdbff0ff: good pcib4: matched entry for 4.6.INTA (src \\_SB_.PCI0.APC3:0) pci_link21: Picked IRQ 18 with weight 0 pcib4: slot 6 INTA routed to irq 18 via \\_SB_.PCI0.APC3 re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xcc00 pcib4: rl0 requested I/O range 0xcc00-0xccff: in range pcib4: rl0 requested I/O range 0xcc00-0xccff: in range rl0: port 0xcc00-0xccff mem 0xfdbff000-0xfdbff0ff irq 18 at device 6.0 on pci4 pcib4: rl0 requested I/O range 0xcc00-0xccff: in range miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: bpf attached rl0: Ethernet address: 00:08:a1:48:50:1b rl0: [MPSAFE] pci0: at device 16.2 (no driver attached) pci0: at device 20.0 (no driver attached) acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] sio0: irq maps: 0xc21 0xc31 0xc21 0xc21 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: using extended I/O port range ppc0: SPP ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ ex_isa_identify() atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 1: ioport 0x1c00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0xc21 0xc21 0xc21 0xc21 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered linprocfs registered lapic: Divisor 2, Frequency 100457653 hz Timecounter "TSC" frequency 2210077283 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 wire ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ad0: 76319MB at ata0-master UDMA33 ad0: 156301488 sectors [155061C/16H/63S] 16 sectors/interrupt 1 depth queue ad0: nVidia check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed fdc0: output ready timeout ad1: 239372MB at ata0-slave UDMA33 ad1: 490234752 sectors [486344C/16H/63S] 16 sectors/interrupt 1 depth queue ad1: nVidia check1 failed ad1: Adaptec check1 failed ad1: LSI (v3) check1 failed ad1: LSI (v2) check1 failed ad1: FreeBSD check1 failed ATA PseudoRAID loaded ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 18 (PCI IRQ 18) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout GEOM: new disk ad0 GEOM: new disk ad1 Trying to mount root from ufs:/dev/ad0s1a start_init: trying /sbin/init fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout rl0: link state changed to UP From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 24 09:12:33 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DC8816A41F for ; Sat, 24 Dec 2005 09:12:33 +0000 (GMT) (envelope-from groot@kde.org) Received: from hex.athame.co.uk (salama58.adsl.netsonic.fi [81.17.207.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E9A443D5C for ; Sat, 24 Dec 2005 09:12:32 +0000 (GMT) (envelope-from groot@kde.org) Received: from localhost.athame.co.uk ([127.0.0.1] helo=hex.athame.co.uk) by hex.athame.co.uk with esmtp (Exim 4.54 (FreeBSD)) id 1Eq5S2-000Nio-C8; Sat, 24 Dec 2005 11:12:30 +0200 Received: from localhost (adridg@localhost) by hex.athame.co.uk (8.13.4/8.13.1/Submit) with ESMTP id jBO9CTAZ091187; Sat, 24 Dec 2005 11:12:30 +0200 (EET) (envelope-from groot@kde.org) X-Authentication-Warning: hex.athame.co.uk: adridg owned process doing -bs Date: Sat, 24 Dec 2005 11:12:29 +0200 (EET) From: Adriaan de Groot X-X-Sender: adridg@hex.athame.co.uk To: Vikash In-Reply-To: <000b01c60841$4536bef0$080a0a0a@winxp> Message-ID: <20051224110448.F90902@hex.athame.co.uk> References: <000b01c60841$4536bef0$080a0a0a@winxp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: biostar GeForce 6100-M9 motherboard 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, 24 Dec 2005 09:12:33 -0000 On Sat, 24 Dec 2005, Vikash wrote: > I have a biostar GeForce 6100-M9 motherboard with an AMD Athlon 64 Processor > 3500+ cpu > (http://www.biostar.com.tw/products/mainboard/board.php?name=GeForce%206100-M9) That's an nForce 410 + GeForce 6100; similar to the Asus A8N-VM. The nForce4 flavors are problematic at best. > i have managed to install 6.0-RELEASE and upgraded to 6.0-STABLE: Well, that's a lot more than I manage with the A8N-VM (but that has a totally broken BIOS on top of a weird chipset). > the on board lan is not detected and the ata controller is marked as generic > the verbose dmesg is bellow: > > please advise as to how i can help to get the ata working at better than > umda33 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: bpf attached > rl0: Ethernet address: 00:08:a1:48:50:1b > rl0: [MPSAFE] It's peculiar that that doesn't work; it looks detected to _me_. Otherwise, check the archives of this list for references to nve(4). > ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 wire > ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire > ad0: 76319MB at ata0-master UDMA33 > ad0: 156301488 sectors [155061C/16H/63S] 16 sectors/interrupt 1 depth queue Again, problem with newish chipsets. I can't recall any report of SATA working really well w/ nForce4 chipsets on this list. [ade] From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 24 12:28:35 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FBE616A420 for ; Sat, 24 Dec 2005 12:28:35 +0000 (GMT) (envelope-from vikashb@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 560F943D5F for ; Sat, 24 Dec 2005 12:28:34 +0000 (GMT) (envelope-from vikashb@gmail.com) Received: by zproxy.gmail.com with SMTP id z6so185616nzd for ; Sat, 24 Dec 2005 04:28:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:cc:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=oZmZ8eACee6oWks5Wt2CKPxRTUoJU5uN2miJSeSkiuXNTn1LWWbpBJH1nMO9gOe7ZTGB3c3SIrFnXmmK5XCY8mHTHXnqt3EAdQHj1H/6bodXPnoXMhsN9PhvGNiKSPfT/hxYwyGZs1Apu28ILf3+9ZtD10crUXro2NuwIJCGvLk= Received: by 10.64.199.7 with SMTP id w7mr1985904qbf; Sat, 24 Dec 2005 04:28:32 -0800 (PST) Received: from winxp ( [196.209.60.150]) by mx.gmail.com with ESMTP id q18sm1718391qbq.2005.12.24.04.28.29; Sat, 24 Dec 2005 04:28:32 -0800 (PST) Message-ID: <000701c60885$91959610$080a0a0a@winxp> From: "Vikash" To: "Adriaan de Groot" References: <000b01c60841$4536bef0$080a0a0a@winxp> <20051224110448.F90902@hex.athame.co.uk> Date: Sat, 24 Dec 2005 14:28:31 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Cc: freebsd-amd64@freebsd.org Subject: Re: biostar GeForce 6100-M9 motherboard 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, 24 Dec 2005 12:28:35 -0000 ----- Original Message ----- From: "Adriaan de Groot" To: "Vikash" Cc: Sent: Saturday, December 24, 2005 11:12 AM Subject: Re: biostar GeForce 6100-M9 motherboard >> rlphy0: on miibus0 >> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> rl0: bpf attached >> rl0: Ethernet address: 00:08:a1:48:50:1b >> rl0: [MPSAFE] > > It's peculiar that that doesn't work; it looks detected to _me_. > Otherwise, check the archives of this list for references to nve(4). > this is a nic that i installed in order to upgrade to -STABLE > Again, problem with newish chipsets. I can't recall any report of SATA > working really well w/ nForce4 chipsets on this list. > > [ade] Show I get a new motherboard while I wait for the 'catch' up ? Vikash From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 24 14:20:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAE2C16A41F for ; Sat, 24 Dec 2005 14:20:22 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 004CF43D49 for ; Sat, 24 Dec 2005 14:20:21 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IS0001Q7APODW20@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sat, 24 Dec 2005 15:25:00 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IS0007XKAMDOWM0@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sat, 24 Dec 2005 15:23:01 +0100 (CET) Date: Sat, 24 Dec 2005 15:20:20 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20051224110448.F90902@hex.athame.co.uk> To: freebsd-amd64@freebsd.org Message-id: <20051224152020.524e8aa3.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <000b01c60841$4536bef0$080a0a0a@winxp> <20051224110448.F90902@hex.athame.co.uk> Subject: Re: biostar GeForce 6100-M9 motherboard 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, 24 Dec 2005 14:20:22 -0000 On Sat, 24 Dec 2005 11:12:29 +0200 (EET) Adriaan de Groot wrote: > On Sat, 24 Dec 2005, Vikash wrote: > > I have a biostar GeForce 6100-M9 motherboard with an AMD Athlon 64 > > Processor 3500+ cpu > > (http://www.biostar.com.tw/products/mainboard/board.php?name=GeForc > > e%206100-M9) > > That's an nForce 410 + GeForce 6100; similar to the Asus A8N-VM. The > nForce4 flavors are problematic at best. Apparantly, some are better than others: I have a Gigabyte K8NF-9, see http://www.giga-byte.com/MotherBoard/Products/Products_GA-K8NF-9.htm > > the on board lan is not detected and the ata controller is marked as > > generic the verbose dmesg is bellow: My ata controller is detected ok: tingo@kg-fil$ dmesg | grep ata atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd000-0xd00f mem 0xf8002000-0xf8002fff irq 21 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xe400-0xe40f mem 0xf8003000-0xf8003fff irq 22 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 ad0: 39265MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA33 ad4: 238474MB at ata2-master SATA150 ad6: 238475MB at ata3-master SATA150 ad8: 238475MB at ata4-master SATA150 ad10: 238475MB at ata5-master SATA150 The (P)ATA disk and CD-ROM work, I haven't tested the SATA disks yet. > Again, problem with newish chipsets. I can't recall any report of SATA > working really well w/ nForce4 chipsets on this list. We'll find out, I plan to test the sata disks during the holidays. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 24 14:22:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2116C16A41F for ; Sat, 24 Dec 2005 14:22:28 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AB1C43D49 for ; Sat, 24 Dec 2005 14:22:27 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IS0001P8AT6DZ20@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sat, 24 Dec 2005 15:27:06 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IS0007HRAPVOQM0@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sat, 24 Dec 2005 15:25:07 +0100 (CET) Date: Sat, 24 Dec 2005 15:22:26 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20051223111740.Q1898@maildrop.int.zabbadoz.net> To: freebsd-amd64@freebsd.org Message-id: <20051224152226.3e9bf3c2.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20051223115424.2606720c.torfinn.ingolfsen@broadpark.no> <20051223111740.Q1898@maildrop.int.zabbadoz.net> Subject: Re: amd64 motherboards: GA-K8NF-9 needs notes 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, 24 Dec 2005 14:22:28 -0000 On Fri, 23 Dec 2005 11:19:27 +0000 (UTC) "Bjoern A. Zeeb" wrote: > The patch you need is not yet in stable. I will MFC it later today or > the next days (a bit busy because of christmas ahead;) Just for later reference; with that patch my nve seems to work well. I haven't done any stress testing, just normal use. -- Regards, Torfinn Ingolfsn, Norway