From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 29 08:22:30 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6DD3106568F for ; Sun, 29 Nov 2009 08:22:30 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id B0B1B8FC17 for ; Sun, 29 Nov 2009 08:22:30 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.70 (FreeBSD)) (envelope-from ) id 1NEf38-00081u-8F for freebsd-hardware@freebsd.org; Sun, 29 Nov 2009 08:22:30 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id BF7492C57D33 for ; Sun, 29 Nov 2009 17:22:29 +0900 (JST) Date: Sun, 29 Nov 2009 17:22:29 +0900 Message-ID: From: Randy Bush To: freebsd-hardware User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: hptraidconf for freebsd X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2009 08:22:30 -0000 where did htpraidconf go? i used to have it but it seems to have flown the coop from ports. i have a 2340 which needs a bit of attention. randy From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 29 10:04:35 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95633106566B for ; Sun, 29 Nov 2009 10:04:35 +0000 (UTC) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id E7A258FC12 for ; Sun, 29 Nov 2009 10:04:34 +0000 (UTC) Received: (qmail 8654 invoked by uid 89); 29 Nov 2009 10:04:32 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (78.111.72.187) by avocado.salatschuessel.net with SMTP; 29 Nov 2009 10:04:32 -0000 Date: Sun, 29 Nov 2009 11:04:32 +0100 From: Oliver Lehmann To: freebsd-hardware@freebsd.org Message-Id: <20091129110432.204016c2.lehmann@ans-netz.de> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Hardware Support for new MB X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2009 10:04:35 -0000 Hi, I'd like to upgrade my Athlon64 3500+ system to a new intel i7 1366 system. I tend between aa MSI and an ASRock board: http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=170&prod_no=1796 http://www.asrock.com/mb/overview.asp?Model=X58%20Extreme&s=1366 I wonder if FreeBSD supports Audio: - ALC690 (ASRock) - ALC88S / ALC889 (MSI) LAN: - RTL 8111DL (ASRock) - RTL 8111C (MSI) SATA - ICH10R Southbridge I guess since the ICH10R also can do AHCI this is at least supported by the new (and old) ahci driver. But what about sound and LAN? RTL8111C I was able to found in if_re.c but RTL8111DL? Unfortunally I was not able to find the device IDs of this devices to look them up in the FreeBSD drivers - not even in the Windows drivers :( -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 29 21:47:00 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6388D106566B for ; Sun, 29 Nov 2009 21:47:00 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id 187FB8FC1A for ; Sun, 29 Nov 2009 21:46:59 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 9so709460qwb.7 for ; Sun, 29 Nov 2009 13:46:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=vN7Fx1pJ60hkiIfXztWoTE+kDZQmn1vdbKLua8N399I=; b=j+8kE6ETOr+QXz9rlrreoUWFD7hLnCA+n1y8fGjJusekyBVujGe6oD+xwx4ltj4OgJ +ARe8h6hZtUQrqQnq62hEVgGpirCI9QGG3aO41bSWMsRv1FrBM1vZkhu3CMyaCc3wUO6 wJ3DNNECgfjgXtWJTMhoigxSPlyJX45eYxm1o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=UqcbLMQqyDMWuEPAUeyi3/1CEGI+lcXgERcaTpf6PdXCXpsNow5+whT+6YULljIfPd argrZugzvuT10cwdp9VcnMsAi00HAgGrxUpju6p7Q6wCjoqHLJkvoPtHJqqY/TnTZ3zg jvkfcNFL+lIqTw7m0AI+M0a8v6roibokxkepk= Received: by 10.224.50.11 with SMTP id x11mr1715838qaf.248.1259531219476; Sun, 29 Nov 2009 13:46:59 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 2sm9741934qwi.37.2009.11.29.13.46.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 29 Nov 2009 13:46:58 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 29 Nov 2009 13:46:32 -0800 From: Pyun YongHyeon Date: Sun, 29 Nov 2009 13:46:32 -0800 To: Oliver Lehmann Message-ID: <20091129214632.GC1128@michelle.cdnetworks.com> References: <20091129110432.204016c2.lehmann@ans-netz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091129110432.204016c2.lehmann@ans-netz.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: Hardware Support for new MB X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2009 21:47:00 -0000 On Sun, Nov 29, 2009 at 11:04:32AM +0100, Oliver Lehmann wrote: > Hi, > > I'd like to upgrade my Athlon64 3500+ system to a new intel i7 1366 > system. I tend between aa MSI and an ASRock board: > > http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=170&prod_no=1796 > http://www.asrock.com/mb/overview.asp?Model=X58%20Extreme&s=1366 > > I wonder if FreeBSD supports > > Audio: > - ALC690 (ASRock) > - ALC88S / ALC889 (MSI) > > LAN: > - RTL 8111DL (ASRock) > - RTL 8111C (MSI) > > SATA > - ICH10R Southbridge > > I guess since the ICH10R also can do AHCI this is at least supported by > the new (and old) ahci driver. > But what about sound and LAN? RTL8111C I was able to found in if_re.c but > RTL8111DL? Unfortunally I was not able to find the device IDs of this I'm not sure but generally I could make it work if you can give me the output value of Tx config register. Normally the value is printed by re(4) even if re(4) does not recognize the controller. > devices to look them up in the FreeBSD drivers - not even in the Windows > drivers :( > RealTek tends to use the same PCI device id for a family so knowing the PCI device id does not help. From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 30 01:05:16 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A36751065692 for ; Mon, 30 Nov 2009 01:05:16 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8DE738FC13 for ; Mon, 30 Nov 2009 01:05:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id 938A15C1A for ; Mon, 30 Nov 2009 01:44:26 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by localhost (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-GVmkK87Pw3 for ; Mon, 30 Nov 2009 01:44:23 +0100 (CET) Received: from [192.168.166.29] (unknown [210.188.173.245]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id 1B93C5C19 for ; Mon, 30 Nov 2009 01:44:21 +0100 (CET) Message-ID: <4B13159D.9010504@darkbsd.org> Date: Mon, 30 Nov 2009 09:45:17 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig38C5DAA0566C2E0944718F3C" Subject: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2009 01:05:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig38C5DAA0566C2E0944718F3C Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, did anyone have the opportunity to test operation with a MV88SX6081 SATA controller on FreeBSD 8.0 ? My amd64 dual-Opteron (using 4G ECC RAM) system just works fine with it on FreeBSD 7.2, but can't handle any high-speed disk I/O when booting with a FreeBSD 8.0 kernel. I have two controllers as follow : atapci1@pci0:17:4:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x608111ab= rev=3D0x09 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device =3D 'MV88SX6081 8-port SATA II PCI-X Controller' class =3D mass storage subclass =3D SCSI atapci2@pci0:18:4:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x608111ab= rev=3D0x09 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device =3D 'MV88SX6081 8-port SATA II PCI-X Controller' class =3D mass storage subclass =3D SCSI http://www.supermicro.com/products/accessories/addon/AOC-SAT2-MV8.cfm On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O bursts (confirmed with zpool iostat), before totally freezing down and locking the ZFS pool (the system is still up and only ZFS based file systems are unusable in this state), probably to avoid data corruption. Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)" error message showing up, on a random hard disk. I already gave the hard disks a thorough check and they work just fine. On FreeBSD 7.2-STABLE, the scrub proceeds nicely and the I/O peaks at 300MB/s (confirmed with zpool iostat) on the pool without a hitch. I could also confirm that attempts at booting a FreeBSD 8.0-RELEASE kernel did not damage my ZFS pool checksums or anything. Therefore, I am inclined to think the motherboard/memory (a "TYAN Thunder K8WE S2895") would be at fault here, and that "something" in FreeBSD 8.0 brings out this very specific problem, but I would first like to hear about any tests of the aforementioned controller on FreeBSD 8.0 on another environment before upgrading the hardware. Thanks in advance for your time, P.S. : Here is the dmesg trace for FreeBSD 8.0. Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-RELEASE #8: Wed Nov 25 03:48:44 JST 2009 darksoul@eirei-no-za.yomi.darkbsd.org:/usr/storage/tech/eirei-no-za.yomi.= darkbsd.org/usr/obj/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src= /sys/DARK-2009KERN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual Core AMD Opteron(tm) Processor 275 (2210.20-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x20f12 Stepping =3D 2 Features=3D0x178bfbff Features2=3D0x1 AMD Features=3D0xe2500800 AMD Features2=3D0x3 real memory =3D 5100273664 (4864 MB) avail memory =3D 4109283328 (3918 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 2 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard ioapic3 irqs 32-55 on motherboard kbd1 at kbdmux0 iscsi: version 2.1.0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 nfsmb0: port 0xa000-0xa03f,0xa040-0xa07f at device 1.1 on pci0 smbus0: on nfsmb0 smb0: on smbus0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 smb1: on smbus1 ohci0: mem 0xdd800000-0xdd800fff irq 20 at device 2.0 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 6.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcib1: at device 9.0 on pci0 pci1: on pcib1 vgapci0: port 0x2000-0x207f mem 0xde000000-0xde7fffff,0xdd900000-0xdd90ffff at device 4.0 on pci1 pcib2: at device 14.0 on pci0 pci2: on pcib2 amdtemp0: on hostb3 amdtemp1: on hostb7 pcib3: port 0xcf8-0xcff on acpi0 pci16: on pcib3 pcib4: at device 10.0 on pci16 pci17: on pcib4 atapci1: port 0x3000-0x30ff mem 0xde900000-0xde9fffff,0xdec00000-0xdeffffff irq 24 at device 4.0 on pci17= atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] ata9: on atapci1 ata9: [ITHREAD] pcib5: at device 11.0 on pci16 pci18: on pcib5 atapci2: port 0x4000-0x40ff mem 0xdf400000-0xdf4fffff,0xdf000000-0xdf3fffff irq 28 at device 4.0 on pci18= atapci2: [ITHREAD] ata10: on atapci2 ata10: [ITHREAD] ata11: on atapci2 ata11: [ITHREAD] ata12: on atapci2 ata12: [ITHREAD] ata13: on atapci2 ata13: [ITHREAD] ata14: on atapci2 ata14: [ITHREAD] ata15: on atapci2 ata15: [ITHREAD] ata16: on atapci2 ata16: [ITHREAD] ata17: on atapci2 ata17: [ITHREAD] em0: port 0x4400-0x443f mem 0xdf500000-0xdf51ffff irq 29 at device 9.0 on pci18 em0: [FILTER] em0: Ethernet address: 00:07:e9:0f:a3:80 em1: port 0x4440-0x447f mem 0xdf520000-0xdf53ffff irq 30 at device 9.1 on pci18 em1: [FILTER] em1: Ethernet address: 00:07:e9:0f:a3:81 pcib6: port 0xcf8-0xcff on acpi0 pci128: on pcib6 pci128: at device 0.0 (no driver attached) pci128: at device 1.0 (no driver attached) pcib7: at device 14.0 on pci128 pci129: on pcib7 pcib8: at device 0.0 on pci129 pci130: on pcib8 em2: port 0x5000-0x503f mem 0xdfb40000-0xdfb5ffff,0xdfb00000-0xdfb3ffff irq 48 at device 4.0 on pci130 em2: [FILTER] em2: Ethernet address: 00:0e:0c:70:7d:1e em3: port 0x5040-0x507f mem 0xdfb60000-0xdfb7ffff,0xdfb80000-0xdfbbffff irq 49 at device 4.1 on pci130 em3: [FILTER] em3: Ethernet address: 00:0e:0c:70:7d:1f pcib9: at device 0.2 on pci129 pci131: on pcib9 atrtc0: port 0x70-0x71 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 uart0: [FILTER] fdc1: port 0-0x5,0 on acpi0 fdc1: cannot reserve interrupt line device_attach: fdc1 attach returned 6 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 cpu2: on acpi0 powernow2: on cpu2 cpu3: on acpi0 powernow3: on cpu3 fdc1: port 0-0x5,0 on acpi0 fdc1: cannot reserve interrupt line device_attach: fdc1 attach returned 6 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0= ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=3D0" to /boot/loader.conf. ZFS filesystem version 13 ZFS storage pool version 13 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 3823MB at ata0-master UDMA33 ugen0.1: at usbus0 uhub0: on usbus0= ad1: FAILURE - SET_MULTI status=3D51 error=3D4 ad1: 61136MB at ata0-slave UDMA133 ad4: 1430799MB at ata2-master SATA300 ad6: 1430799MB at ata3-master SATA300 ad8: 1430799MB at ata4-master SATA300 ad10: 1430799MB at ata5-master SATA300 uhub0: 10 ports with 10 removable, self powered ad12: FAILURE - SET_MULTI status=3D51 error=3D4= ad12: 61136MB at ata6-master SATA300 ad14: 1430799MB at ata7-master SATA300 ad16: 1430799MB at ata8-master SATA300 ad18: 1430799MB at ata9-master SATA300 ad20: 1430799MB at ata10-master SATA300 ad22: 1430799MB at ata11-master SATA300 ad24: 1430799MB at ata12-master SATA300 ad26: 1430799MB at ata13-master SATA300 ad28: 1430799MB at ata14-master SATA300 ugen0.2: at usbus0 uhub1: on usb= us0 ad30: 1430799MB at ata15-master SATA300 ad32: 1430799MB at ata16-master SATA300 ad34: 1430799MB at ata17-master SATA300 SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! Root mount waiting for: usbus0 uhub1: 3 ports with 2 removable, bus powered ugen0.3: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 Trying to mount root from zfs:prana P.P.S. : Here is the FreeBSD 7.2-STABLE dmesg trace. Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #3: Thu Aug 6 20:59:13 JST 2009 darksoul@eirei-no-za.yomi.darkbsd.org:/usr/storage/tech/eirei-no-za.yomi.= darkbsd.org/usr/obj/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src= /sys/DARK-2009KERN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual Core AMD Opteron(tm) Processor 275 (2210.20-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x20f12 Stepping =3D 2 Features=3D0x178bfbff Features2=3D0x1 AMD Features=3D0xe2500800 AMD Features2=3D0x3 Cores per package: 2 usable memory =3D 4282880000 (4084 MB) avail memory =3D 4110327808 (3919 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard ioapic3 irqs 32-55 on motherboard kbd1 at kbdmux0 smbios0: at iomem 0xf7850-0xf786e on motherboard= smbios0: Version: 2.33 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 nfsmb0: port 0xa000-0xa03f,0xa040-0xa07f at device 1.1 on pci0 smbus0: on nfsmb0 smb0: on smbus0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 smb1: on smbus1 ohci0: mem 0xdd800000-0xdd800fff irq 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 6.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcib1: at device 9.0 on pci0 pci1: on pcib1 vgapci0: port 0x2000-0x207f mem 0xde000000-0xde7fffff,0xdd900000-0xdd90ffff at device 4.0 on pci1 pcib2: at device 14.0 on pci0 pci2: on pcib2 amdtemp0: on hostb3 amdtemp1: on hostb7 pcib3: port 0xcf8-0xcff on acpi0 pci16: on pcib3 pcib4: at device 10.0 on pci16 pci17: on pcib4 atapci1: port 0x3000-0x30ff mem 0xde900000-0xde9fffff,0xdec00000-0xdeffffff irq 24 at device 4.0 on pci17= atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] ata9: on atapci1 ata9: [ITHREAD] pcib5: at device 11.0 on pci16 pci18: on pcib5 atapci2: port 0x4000-0x40ff mem 0xdf400000-0xdf4fffff,0xdf000000-0xdf3fffff irq 28 at device 4.0 on pci18= atapci2: [ITHREAD] ata10: on atapci2 ata10: [ITHREAD] ata11: on atapci2 ata11: [ITHREAD] ata12: on atapci2 ata12: [ITHREAD] ata13: on atapci2 ata13: [ITHREAD] ata14: on atapci2 ata14: [ITHREAD] ata15: on atapci2 ata15: [ITHREAD] ata16: on atapci2 ata16: [ITHREAD] ata17: on atapci2 ata17: [ITHREAD] em0: port 0x4400-0x443f mem 0xdf500000-0xdf51ffff irq 29 at device 9.0 on pci18 em0: [FILTER] em0: Ethernet address: 00:07:e9:0f:a3:80 em1: port 0x4440-0x447f mem 0xdf520000-0xdf53ffff irq 30 at device 9.1 on pci18 em1: [FILTER] em1: Ethernet address: 00:07:e9:0f:a3:81 pcib6: port 0xcf8-0xcff on acpi0 pci128: on pcib6 pci128: at device 0.0 (no driver attached) pci128: at device 1.0 (no driver attached) pcib7: at device 14.0 on pci128 pci129: on pcib7 pcib8: at device 0.0 on pci129 pci130: on pcib8 em2: port 0x5000-0x503f mem 0xdfb40000-0xdfb5ffff,0xdfb00000-0xdfb3ffff irq 48 at device 4.0 on pci13= 0 em2: [FILTER] em2: Ethernet address: 00:0e:0c:70:7d:1e em3: port 0x5040-0x507f mem 0xdfb60000-0xdfb7ffff,0xdfb80000-0xdfbbffff irq 49 at device 4.1 on pci13= 0 em3: [FILTER] em3: Ethernet address: 00:0e:0c:70:7d:1f pcib9: at device 0.2 on pci129 pci131: on pcib9 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] fdc0: port 0-0x5,0 on acpi0 fdc0: cannot reserve interrupt line device_attach: fdc0 attach returned 6 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 cpu2: on acpi0 powernow2: on cpu2 cpu3: on acpi0 powernow3: on cpu3 fdc0: port 0-0x5,0 on acpi0 fdc0: cannot reserve interrupt line device_attach: fdc0 attach returned 6 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0= ppc0: cannot reserve I/O port range sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled uhub1: on uhu= b0 uhub1: 3 ports with 2 removable, bus powered ukbd0: on uhub1 kbd2 at ukbd0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec ad0: DMA limited to UDMA33, device found non-ATA66 cable ZFS filesystem version 13 ZFS storage pool version 13 ad0: 3823MB at ata0-master UDMA33 ad1: FAILURE - SET_MULTI status=3D51 error=3D4 ad1: 61136MB at ata0-slave UDMA133 ad4: 1430799MB at ata2-master SATA300 ad6: 1430799MB at ata3-master SATA300 ad8: 1430799MB at ata4-master SATA300 ad10: 1430799MB at ata5-master SATA300 ad12: FAILURE - SET_MULTI status=3D51 error=3D4= ad12: 61136MB at ata6-master SATA300 ad14: 1430799MB at ata7-master SATA300 ad16: 1430799MB at ata8-master SATA300 ad18: 1430799MB at ata9-master SATA300 ad20: 1430799MB at ata10-master SATA300 ad22: 1430799MB at ata11-master SATA300 ad24: 1430799MB at ata12-master SATA300 ad26: 1430799MB at ata13-master SATA300 ad28: 1430799MB at ata14-master SATA300 ad30: 1430799MB at ata15-master SATA300 ad32: 1430799MB at ata16-master SATA300 ad34: 1430799MB at ata17-master SATA300 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from zfs:prana The full pciconf -lv output : none0@pci0:0:0:0: class=3D0x058000 card=3D0x289510f1 chip=3D0x005e10de rev=3D0xa4 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 Memory Controller' class =3D memory isab0@pci0:0:1:0: class=3D0x060100 card=3D0x289510f1 chip=3D0x005110de rev=3D0xb1 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 ISA Bridge' class =3D bridge subclass =3D PCI-ISA nfsmb0@pci0:0:1:1: class=3D0x0c0500 card=3D0x289510f1 chip=3D0x005210de rev=3D0xa2 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 SMBus' class =3D serial bus subclass =3D SMBus ohci0@pci0:0:2:0: class=3D0x0c0310 card=3D0x289510f1 chip=3D0x005a10de rev=3D0xa2 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 USB Controller' class =3D serial bus subclass =3D USB atapci0@pci0:0:6:0: class=3D0x01018a card=3D0x289510f1 chip=3D0x005310de rev=3D0xf3 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 Parallel ATA Controller' class =3D mass storage subclass =3D ATA pcib1@pci0:0:9:0: class=3D0x060401 card=3D0x00000000 chip=3D0x005c10de rev=3D0xa2 hdr=3D0x01 vendor =3D 'Nvidia Corp' device =3D 'nForce4 PCI Bridge' class =3D bridge subclass =3D PCI-PCI pcib2@pci0:0:14:0: class=3D0x060400 card=3D0x00000000 chip=3D0x005d10de rev=3D0xa3 hdr=3D0x01 vendor =3D 'Nvidia Corp' device =3D 'nForce4 PCIe Bridge' class =3D bridge subclass =3D PCI-PCI hostb0@pci0:0:24:0: class=3D0x060000 card=3D0x00000000 chip=3D0x11001022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport Technology Configuration' class =3D bridge subclass =3D HOST-PCI hostb1@pci0:0:24:1: class=3D0x060000 card=3D0x00000000 chip=3D0x11011022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) Address Map' class =3D bridge subclass =3D HOST-PCI hostb2@pci0:0:24:2: class=3D0x060000 card=3D0x00000000 chip=3D0x11021022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller'= class =3D bridge subclass =3D HOST-PCI hostb3@pci0:0:24:3: class=3D0x060000 card=3D0x00000000 chip=3D0x11031022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous Control' class =3D bridge subclass =3D HOST-PCI hostb4@pci0:0:25:0: class=3D0x060000 card=3D0x00000000 chip=3D0x11001022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport Technology Configuration' class =3D bridge subclass =3D HOST-PCI hostb5@pci0:0:25:1: class=3D0x060000 card=3D0x00000000 chip=3D0x11011022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) Address Map' class =3D bridge subclass =3D HOST-PCI hostb6@pci0:0:25:2: class=3D0x060000 card=3D0x00000000 chip=3D0x11021022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller'= class =3D bridge subclass =3D HOST-PCI hostb7@pci0:0:25:3: class=3D0x060000 card=3D0x00000000 chip=3D0x11031022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous Control' class =3D bridge subclass =3D HOST-PCI vgapci0@pci0:1:4:0: class=3D0x030000 card=3D0x63261039 chip=3D0x63261039 rev=3D0x0b hdr=3D0x00 vendor =3D 'Silicon Integrated Systems (SiS)' device =3D 'SiS6326 GUI Accelerator' class =3D display subclass =3D VGA pcib4@pci0:16:10:0: class=3D0x060400 card=3D0x00000000 chip=3D0x74501022 rev=3D0x13 hdr=3D0x01 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'PCI-X Bridge (AMD-8131)' class =3D bridge subclass =3D PCI-PCI ioapic0@pci0:16:10:1: class=3D0x080010 card=3D0x289510f1 chip=3D0x7451102= 2 rev=3D0x01 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'PCI-X IOAPIC (AMD-8131)' class =3D base peripheral subclass =3D interrupt controller pcib5@pci0:16:11:0: class=3D0x060400 card=3D0x00000000 chip=3D0x74501022 rev=3D0x13 hdr=3D0x01 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'PCI-X Bridge (AMD-8131)' class =3D bridge subclass =3D PCI-PCI ioapic1@pci0:16:11:1: class=3D0x080010 card=3D0x289510f1 chip=3D0x7451102= 2 rev=3D0x01 hdr=3D0x00 vendor =3D 'Advanced Micro Devices (AMD)' device =3D 'PCI-X IOAPIC (AMD-8131)' class =3D base peripheral subclass =3D interrupt controller atapci1@pci0:17:4:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x608111ab= rev=3D0x09 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device =3D 'MV88SX6081 8-port SATA II PCI-X Controller' class =3D mass storage subclass =3D SCSI atapci2@pci0:18:4:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x608111ab= rev=3D0x09 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device =3D 'MV88SX6081 8-port SATA II PCI-X Controller' class =3D mass storage subclass =3D SCSI em0@pci0:18:9:0: class=3D0x020000 card=3D0x10128086 chip=3D0x10128086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Dual Port Gigabit Ethernet Controller (Fiber) (82546E= B)' class =3D network subclass =3D ethernet em1@pci0:18:9:1: class=3D0x020000 card=3D0x10128086 chip=3D0x10128086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Dual Port Gigabit Ethernet Controller (Fiber) (82546E= B)' class =3D network subclass =3D ethernet none1@pci0:128:0:0: class=3D0x058000 card=3D0x289510f1 chip=3D0x005e10de rev=3D0xa4 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 Memory Controller' class =3D memory none2@pci0:128:1:0: class=3D0x058000 card=3D0x289510f1 chip=3D0x00d310de rev=3D0xb1 hdr=3D0x00 vendor =3D 'Nvidia Corp' device =3D 'nForce4 Memory Controller' class =3D memory pcib7@pci0:128:14:0: class=3D0x060400 card=3D0x00000000 chip=3D0x005d10de= rev=3D0xa3 hdr=3D0x01 vendor =3D 'Nvidia Corp' device =3D 'nForce4 PCIe Bridge' class =3D bridge subclass =3D PCI-PCI pcib8@pci0:129:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x03408086 rev=3D0x09 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '41210 [Lanai] Serial to Parallel PCI Bridge A-segment= Bridge' class =3D bridge subclass =3D PCI-PCI pcib9@pci0:129:0:2: class=3D0x060400 card=3D0x00000000 chip=3D0x03418086 rev=3D0x09 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '41210 [Lanai] Serial to Parallel PCI Bridge B-segment= Bridge' class =3D bridge subclass =3D PCI-PCI em2@pci0:130:4:0: class=3D0x020000 card=3D0x108a8086 chip=3D0x108a8086 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/1000 P' class =3D network subclass =3D ethernet em3@pci0:130:4:1: class=3D0x020000 card=3D0x108a8086 chip=3D0x108a8086 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/1000 P' class =3D network subclass =3D ethernet Here is my ZFS pool status : pool: prana state: ONLINE scrub: scrub completed after 10h37m with 0 errors on Fri Nov 27 09:12:08 2009 config: NAME STATE READ WRITE CKSUM prana ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad16 ONLINE 0 0 0 ad30 ONLINE 0 0 0 ad28 ONLINE 0 0 0 ad18 ONLINE 0 0 0 ad14 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad26 ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad20 ONLINE 0 0 0 ad22 ONLINE 0 0 0 ad24 ONLINE 0 0 0 ad32 ONLINE 0 0 0 ad34 ONLINE 0 0 0 cache ad12 ONLINE 0 0 0 ad1 ONLINE 0 0 0 errors: No known data errors --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enig38C5DAA0566C2E0944718F3C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksTFZ0ACgkQ24Ql8u6TF2PUOgCg7KUXSA/SgrbEen3j+WK+Ql08 f/EAnjMy0PAfsHog7U6re2Rl3L07jjTV =dqQs -----END PGP SIGNATURE----- --------------enig38C5DAA0566C2E0944718F3C-- From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 30 05:05:19 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E53B6106566C for ; Mon, 30 Nov 2009 05:05:19 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-11.ptldor.fios.verizon.net [98.108.131.11]) by mx1.freebsd.org (Postfix) with ESMTP id 45A0C8FC0C for ; Mon, 30 Nov 2009 05:05:18 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 90C91B64F; Sun, 29 Nov 2009 20:41:51 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id FAA11837; Mon, 30 Nov 2009 05:01:11 GMT Message-Id: <200911300501.FAA11837@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org Date: Sun, 29 Nov 2009 21:01:11 PST From: Dieter Subject: Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2009 05:05:20 -0000 In message <4B13159D.9010504@darkbsd.org>, Stephane LAPIE writes: > On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O > bursts (confirmed with zpool iostat), before totally freezing down and > locking the ZFS pool (the system is still up and only ZFS based file > systems are unusable in this state), probably to avoid data corruption. > Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)" > error message showing up, on a random hard disk. And there are these, which you didn't mention: > ad1: FAILURE - SET_MULTI status=3D51 error=3D4 > ad12: FAILURE - SET_MULTI status=3D51 error=3D4 (No, I don't know what that means, sorry.) > ad18: 1430799MB at ata9-master SATA300 > ad20: 1430799MB at ata10-master SATA300 How old is the SD1A disk? As you may know, Seagate had various troubles with the .11 firmware. I have some of the ST31500341AS CC1H and mine are new enough that they are supposed to be ok. > Therefore, I am inclined to think the motherboard/memory (a "TYAN > Thunder K8WE S2895") would be at fault here, I have been told that Tyan does a good job with memory, although even assuming that's true it could still be a memory problem. My Tyan board has a memory scrubbing feature that can be turned on in firmware, but I've never tried it. Also, you could try rotating the SIMMs and see if anything changes. From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 30 09:39:38 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC3261065670 for ; Mon, 30 Nov 2009 09:39:38 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6F8668FC0A for ; Mon, 30 Nov 2009 09:39:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id 0811D5C1A for ; Mon, 30 Nov 2009 10:38:33 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by localhost (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ttONlFjDJPWy for ; Mon, 30 Nov 2009 10:38:30 +0100 (CET) Received: from [192.168.166.29] (unknown [210.188.173.245]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id DAE445C19 for ; Mon, 30 Nov 2009 10:38:29 +0100 (CET) Message-ID: <4B1392CF.5090600@darkbsd.org> Date: Mon, 30 Nov 2009 18:39:27 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 CC: freebsd-hardware@freebsd.org References: <200911300501.FAA11837@sopwith.solgatos.com> In-Reply-To: <200911300501.FAA11837@sopwith.solgatos.com> X-Enigmail-Version: 0.96.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6087BC6BF4C85283A10BB7E9" Subject: Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2009 09:39:39 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6087BC6BF4C85283A10BB7E9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dieter wrote: > In message <4B13159D.9010504@darkbsd.org>, Stephane LAPIE writes: >=20 >> On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O >> bursts (confirmed with zpool iostat), before totally freezing down and= >> locking the ZFS pool (the system is still up and only ZFS based file >> systems are unusable in this state), probably to avoid data corruption= =2E >> Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)" >> error message showing up, on a random hard disk. >=20 > And there are these, which you didn't mention: >> ad1: FAILURE - SET_MULTI status=3D3D51 error=3D3D4 >> ad12: FAILURE - SET_MULTI status=3D3D51 error=3D3D4 > (No, I don't know what that means, sorry.) Ah, actually I do have an idea as to what these are about : These two disks are SSDs I'm using in my ZFS pool as cache devices. So I guess this is the kind of error that says "I tried to use an access mode this device was not designed for". In the same fashion, I also get such error messages when trying SMART checks on ad0, which is a flash card. ad0: FAILURE - SMART status=3D51 error=3D4 So, I think these could safely be discarded under "not a normal disk device". (Unless I'm completely mistaken about this...) >> ad18: 1430799MB at ata9-master SATA300 >> ad20: 1430799MB at ata10-master SATA300 >=20 > How old is the SD1A disk? As you may know, Seagate had various trouble= s > with the .11 firmware. I have some of the ST31500341AS CC1H and mine a= re > new enough that they are supposed to be ok. I bought all these disks at roughly the same time around April, but strangely got an odd one in the lot and didn't bother to change it. =46rom what I checked with the Seagate page about the firmware issues, SD1A is not affected. I also have three spare disks in a drawer in case a problem occurs. >> Therefore, I am inclined to think the motherboard/memory (a "TYAN >> Thunder K8WE S2895") would be at fault here, >=20 > I have been told that Tyan does a good job with memory, although even > assuming that's true it could still be a memory problem. My Tyan > board has a memory scrubbing feature that can be turned on in > firmware, but I've never tried it. Also, you could try rotating the > SIMMs and see if anything changes. The memory is brand new, from Corsair. I tried swapping the sticks (while still using the same slots) and strangely enough, some combinations just... don't boot at all. Also, completely unrelated to the SATA controller, some quirks on this motherboard (though at BIOS level) have been annoying me quite a lot : - Booting FreeBSD from anything besides an IDE device has a 80% chance of freezing the computer at BTX level. - Sometimes the Option ROMs (this including the VGA card) are not loaded properly because of an "out of memory" problem at BIOS level. However, once the system is booted, it can go on for several months. (Though, I have witnessed one "Fatal error 12: Page fault"-type kernel panic in six months) Thanks again for your time. --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enig6087BC6BF4C85283A10BB7E9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksTks8ACgkQ24Ql8u6TF2Ps2QCg6zykzph7734ce5FRBuNlq6RO pywAoICo2amL7L+UHiXbACpjEsYQYjnC =ouSv -----END PGP SIGNATURE----- --------------enig6087BC6BF4C85283A10BB7E9-- From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 05:21:55 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F1191068414 for ; Tue, 1 Dec 2009 05:21:14 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-11.ptldor.fios.verizon.net [98.108.131.11]) by mx1.freebsd.org (Postfix) with ESMTP id 3BD3E8FC14 for ; Tue, 1 Dec 2009 05:21:13 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 4D7DFB64F; Mon, 30 Nov 2009 20:57:11 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id CAA08303; Tue, 1 Dec 2009 02:31:32 GMT Message-Id: <200912010231.CAA08303@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org In-reply-to: Your message of "Mon, 30 Nov 2009 18:39:27 +0900." <4B1392CF.5090600@darkbsd.org> Date: Mon, 30 Nov 2009 18:31:32 PST From: Dieter Subject: Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 05:21:55 -0000 In message <4B1392CF.5090600@darkbsd.org>, Stephane LAPIE writes: > >> Therefore, I am inclined to think the motherboard/memory (a "TYAN > >> Thunder K8WE S2895") would be at fault here, > >=20 > > I have been told that Tyan does a good job with memory, although even > > assuming that's true it could still be a memory problem. My Tyan > > board has a memory scrubbing feature that can be turned on in > > firmware, but I've never tried it. Also, you could try rotating the > > SIMMs and see if anything changes. > > The memory is brand new, from Corsair. I tried swapping the sticks > (while still using the same slots) and strangely enough, some > combinations just... don't boot at all. That sounds like a major clue that you probably have a very bad stick of memory (probably a hard error). I would try booting with just 1 stick at a time (or whatever the minimum is for your board) and isolate the bad stick. Most likely with 7.2 something landed on the bad location that doesn't actually get used, but with 8.0 something disk related lands there. > Also, completely unrelated to the SATA controller, some quirks on this > motherboard (though at BIOS level) have been annoying me quite a lot : > - Booting FreeBSD from anything besides an IDE device has a 80% chance > of freezing the computer at BTX level. > - Sometimes the Option ROMs (this including the VGA card) are not loaded > properly because of an "out of memory" problem at BIOS level. > > However, once the system is booted, it can go on for several months. > (Though, I have witnessed one "Fatal error 12: Page fault"-type kernel > panic in six months) Let me guess, "Phoenix - AwardBIOS"? On mine they can't even spell the name of the board correctly: "TYAN Tomact K8E BIOS V1.00 022105" (should be Tomcat) Such quality control. Mine hangs in boot if I have 2 JMB363 cards in the 2 PCIe x1 slots. Moved one to the x16 slot and it boots. I've been blaming the JMB363 cards but maybe the Phoenix AwardBIOS is the problem child? Most of the time one of the cards doesn't do it's display the drives and give me 5.1 nanoseconds to hit some control character to enter a setup-a-raid thingy. And frequently FreeBSD doesn't see one of the controllers and thus doesn't make it to multiuser. I'd expect these events to be correlated but oddly they don't seem to be. Sometimes it takes several reboots to get all the controllers seen. I haven't seen an "out of memory" message, but the way things fly by perhaps I just missed it. It always works correctly the first time after a power cycle, so my theory is that the expansion cards aren't getting reset properly. I have a firewire PCI card that got into a funky mode and rebooting didn't fix it but a power cycle did. Tyan is supposed to be tier 1 but they aren't doing themselves any favors with that pathetic excuse for firmware. From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 05:47:14 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B34111065A4F for ; Tue, 1 Dec 2009 05:47:14 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 40E2B8FC15 for ; Tue, 1 Dec 2009 05:47:13 +0000 (UTC) Received: by bwz5 with SMTP id 5so3185587bwz.3 for ; Mon, 30 Nov 2009 21:47:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=NCxG4PwJhMXg4Y4G5RCXKWkoYQp5t+rfyv+sETOyRlc=; b=T51ZRhD/84v2AeYhCLFGi9TjPx1yeEj+rEF+OMDK1MIBnqufYk7Kf9IEPHzNpLA+GD xSP2tQrBRTOX7vVgEZTbNNEJ+zWVRiuaQJ8DxDm2qqAE+qn5Tm+JPKhLq02nCVOdghZc SEhXzb5VgW1C2Sc+Fhpv9gAPcrs3PI/LIka4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=b7nw1JLWNC5cYkddK55G9MR7bZ19b9+s1njqLMRG602wfhcnJfDoyWhA4MIKoYax0+ Q0HG9RnNDltHxOETvlvmptUOPlj+OmSBIZE3M1kqDABcaE9Ulid6Gl0R12rGXyIAhPoP yBeDRLJOybcCbrpCjIp1yElJUQZ8BOznUZFrM= Received: by 10.204.154.92 with SMTP id n28mr2385499bkw.5.1259646432890; Mon, 30 Nov 2009 21:47:12 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 15sm1738904fxm.2.2009.11.30.21.47.12 (version=SSLv3 cipher=RC4-MD5); Mon, 30 Nov 2009 21:47:12 -0800 (PST) Sender: Alexander Motin Message-ID: <4B14ADDE.4060705@FreeBSD.org> Date: Tue, 01 Dec 2009 07:47:10 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Oliver Lehmann References: <1259500985.00188343.1259489403@10.7.7.3> In-Reply-To: <1259500985.00188343.1259489403@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: Hardware Support for new MB X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 05:47:14 -0000 Oliver Lehmann wrote: > I wonder if FreeBSD supports > > Audio: > - ALC690 (ASRock) > - ALC88S / ALC889 (MSI) > > SATA > - ICH10R Southbridge > > I guess since the ICH10R also can do AHCI this is at least supported by > the new (and old) ahci driver. It is supported by both old ata(4) drives, and new ahci(4). I've recently tested it in my lab. > But what about sound? All Realtek HDA codecs are supported fine. There can be some surprises from motherboard vendor, but usually they work out of the box. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 06:08:58 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 422771065672 for ; Tue, 1 Dec 2009 06:08:58 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id BBAAE8FC0C for ; Tue, 1 Dec 2009 06:08:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id E49425C1A for ; Tue, 1 Dec 2009 07:07:50 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by localhost (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKkeiSM9+BH0 for ; Tue, 1 Dec 2009 07:07:48 +0100 (CET) Received: from [192.168.166.29] (unknown [210.188.173.245]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id 6B9DD5C19 for ; Tue, 1 Dec 2009 07:07:47 +0100 (CET) Message-ID: <4B14B2EE.8030103@darkbsd.org> Date: Tue, 01 Dec 2009 15:08:46 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <200912010231.CAA08303@sopwith.solgatos.com> In-Reply-To: <200912010231.CAA08303@sopwith.solgatos.com> X-Enigmail-Version: 0.96.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig161B22FC463FC37BAC1C8293" Subject: Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 06:08:58 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig161B22FC463FC37BAC1C8293 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dieter wrote: > That sounds like a major clue that you probably have a very bad stick > of memory (probably a hard error). I would try booting with just 1 sti= ck > at a time (or whatever the minimum is for your board) and isolate the b= ad > stick. >=20 > Most likely with 7.2 something landed on the bad location that doesn't > actually get used, but with 8.0 something disk related lands there. I'll try that the next time I have a chance to reboot that server. > Let me guess, "Phoenix - AwardBIOS"? =2E..The very one. As per kenv output : smbios.bios.reldate=3D"11/18/2008" smbios.bios.vendor=3D"Phoenix Technologies Ltd." smbios.bios.version=3D"2004Q3" smbios.chassis.maker=3D"TYAN Computer Corp" smbios.memory.enabled=3D"2097152" smbios.planar.maker=3D"Tyan Computer Corporation" smbios.planar.product=3D"S2895" smbios.planar.serial=3D"0123456789" smbios.planar.version=3D"TYAN Thunder K8WE S2895" smbios.socket.enabled=3D"2" smbios.socket.populated=3D"2" smbios.system.maker=3D"TYAN Computer Corp." smbios.system.product=3D"S2895" smbios.system.serial=3D"0123456789" smbios.system.version=3D"TYAN Thunder K8WE S2895" smbios.version=3D"2.33" > On mine they can't even spell the name of the board correctly: > "TYAN Tomact K8E BIOS V1.00 022105" > (should be Tomcat) Such quality control. Ouch. > Mine hangs in boot if I have 2 JMB363 cards in the 2 PCIe x1 slots. > Moved one to the x16 slot and it boots. I've been blaming the > JMB363 cards but maybe the Phoenix AwardBIOS is the problem child? In my case I guess that would be it. I have never seen FreeBSD freeze on BTX level when loading from media, on any other computer. > Most of the time one of the cards doesn't do it's display the drives > and give me 5.1 nanoseconds to hit some control character to > enter a setup-a-raid thingy. And frequently FreeBSD doesn't see > one of the controllers and thus doesn't make it to multiuser. I'd I also happen to have these ones, but with my Intel NICs (no way I'm using the Marvell default ones, I get lost interrupt messages all over the place when I crank up network I/O a bit) > expect these events to be correlated but oddly they don't seem to be. > Sometimes it takes several reboots to get all the controllers seen. > I haven't seen an "out of memory" message, but the way things fly by > perhaps I just missed it. It always works correctly the first time > after a power cycle, so my theory is that the expansion cards aren't > getting reset properly. I have a firewire PCI card that got into > a funky mode and rebooting didn't fix it but a power cycle did. Just for the recall, it's more like "Could not load Option ROM" (I recall it was because it was out of memory buffers for these, but I don't have the exact message text available at hand), and it pops up randomly ; sometimes as you said, full power cycles do help. Sometimes they don't. > Tyan is supposed to be tier 1 but they aren't doing themselves > any favors with that pathetic excuse for firmware. Definitely not... --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enig161B22FC463FC37BAC1C8293 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksUsu4ACgkQ24Ql8u6TF2OluQCeJJ5M/vhkl21cxP7zripVmqK3 0KsAoIs5RyKDSDMf5DOAK/XPlD/ZGGDG =PFh0 -----END PGP SIGNATURE----- --------------enig161B22FC463FC37BAC1C8293-- From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 12:13:56 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 837D9106566B for ; Tue, 1 Dec 2009 12:13:56 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 0E82B8FC16 for ; Tue, 1 Dec 2009 12:13:55 +0000 (UTC) Received: by bwz5 with SMTP id 5so3377757bwz.3 for ; Tue, 01 Dec 2009 04:13:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=VP5ufh95+LoJnp/CLFMcrxW2tIEvgKkoNWvC2XM8pJE=; b=hj3LZ8QcvD4GGwKFGL8A0hYM5FQBRu4h+B6HEeqeHC6dXY16nw09L2Pb3tMW3UKL9L FrdWLNQKilD5i6m6q/aKLlqiecdZ9nT7CBBwOx7R6IuGy21UOQt0o+bLb9VaBLBsd/rj n2QHbTIkhprncxhADT+oMKJT7VzeE/FM+TsGo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=YQ81RnV+HATZLjA3t+aB/1q94SmpXyOARbQjRNwBcMTUaDI7hcv/0ROcuJt0pIWQwO qsnguVNo563MgVwlfKXHFcJ9TlpOsWIc/FDiZfT6dSyW/g+ccSoCjQURi3b4Ash+k9zP 74wTqOOVlmX0wdOxDPpFBIAzJajgI/BSwqSC4= Received: by 10.204.29.22 with SMTP id o22mr861626bkc.78.1259669635033; Tue, 01 Dec 2009 04:13:55 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 14sm21309fxm.3.2009.12.01.04.13.54 (version=SSLv3 cipher=RC4-MD5); Tue, 01 Dec 2009 04:13:54 -0800 (PST) Sender: Alexander Motin Message-ID: <4B150880.9070503@FreeBSD.org> Date: Tue, 01 Dec 2009 14:13:52 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Stephane LAPIE References: <1259569383.00188602.1259557802@10.7.7.3> <1259587382.00188660.1259574004@10.7.7.3> In-Reply-To: <1259587382.00188660.1259574004@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 12:13:56 -0000 Stephane LAPIE wrote: > Dieter wrote: >> In message <4B13159D.9010504@darkbsd.org>, Stephane LAPIE writes: >> And there are these, which you didn't mention: >>> ad1: FAILURE - SET_MULTI status=3D51 error=3D4 >>> ad12: FAILURE - SET_MULTI status=3D51 error=3D4 >> (No, I don't know what that means, sorry.) > > Ah, actually I do have an idea as to what these are about : These two > disks are SSDs I'm using in my ZFS pool as cache devices. So I guess > this is the kind of error that says "I tried to use an access mode this > device was not designed for". It is probably result of bug in ata(4) code. It was fixed recently by r199749. It is not critical when drive operates in DMA mode. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 16:45:31 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0C63106566B for ; Tue, 1 Dec 2009 16:45:31 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 5DAA78FC1C for ; Tue, 1 Dec 2009 16:45:30 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Tue, 1 Dec 2009 11:45:31 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B154905.8020400@greatbaysoftware.com> Date: Tue, 01 Dec 2009 11:49:09 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4B0ABD27.2080501@greatbaysoftware.com> In-Reply-To: <4B0ABD27.2080501@greatbaysoftware.com> X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: No "boot0" menu on Soekris, net5501 vs net4521 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 16:45:31 -0000 Charles Owens wrote: > Hello, > > We're working with two different Soekris models (net5501 and net4521), > working withFreeBSD 7.1 (nanobsd). We've found that the two models > exhibit different boot behavior. Summary: the 4521 works fine, and > the 5501 doesn't seem right. Here's what we see when we boot either: > > net4521 (BIOS ver 1.33) -- > > * "boot0" menu appears (letting you pick either of two FreeBSD slices) > * OS loads properly from chosen or default slice > > > net5501 (BIOS ver 1.33c) -- > > * "boot0" menu does _not_ appear. > * system boots directly to slice 1 or 2, as chosen via BIOS option > BootPartition > > > Have others seen this behavior? For our application, we really need > the 5501 to boot just like the 4521. Is this a bug (in BIOS, I'm > guessing), or am I doing something wrong? It seems like there should > be a way to clear the BootPartition setting, or set it to "MBR" or > somesuch. > Issue resolved. The syntax for resetting the BootPartition parameter in BIOS was non-obvious (to me). This can be accomplished with: set BootPartition=Disabled ... my thanks to maintainer of wiki: http://wiki.soekris.info/What_do_all_those_BIOS_settings_do%3F ... Charles Owens Great Bay Software From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 1 19:16:55 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABDD2106566C for ; Tue, 1 Dec 2009 19:16:55 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 505B08FC08 for ; Tue, 1 Dec 2009 19:16:54 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Tue, 1 Dec 2009 14:16:54 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B156C80.7090706@greatbaysoftware.com> Date: Tue, 01 Dec 2009 14:20:32 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4B070F07.8010600@greatbaysoftware.com> In-Reply-To: <4B070F07.8010600@greatbaysoftware.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Subject: USB bus setup error with PAE (was USB keyboard flaky with PAE kernel, 7.1) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 19:16:55 -0000 Charles Owens wrote: > Howdy, > > I'm still digging into it, put preliminary testing is showing that > with a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only > occasionally, if you're lucky. This flakiness is being seen with > several different server models that we support (HP and IBM, all Xeon > based). If we boot a non-PAE kernel then the USB keyboard is rock solid. My initial report was entirely too broad --- an unrelated problem was confusing things. I can now report that this problem appears limited to only the IBM System x3550 M2. With a PAE-enabled kernel initialization of some of the USB buses fails. From an external perspective, this results in the rear USB port being non-functional, while the two front USB ports work fine. For some reason, though, when booting the same PAE kernel from a CD none of the USB ports function. In previous posting ( http://docs.freebsd.org/cgi/mid.cgi?4B0D14CB.1010000 ) I included output of usbdevs and boot log when running the PAE-enabled kernel. Note the "root hub error" messages in boot log. Below I'll repeat the same info when running a non-PAE kernel. Any thoughts as to what the story is here... and suggestions for resolution? Thanks in advance. [root@dmz55 /usr/home/muck]# usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, Comfort Curve Keyboard 2000(0x00dd), Microsoft(0x045e), rev 1.73 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, RNDIS/CDC ETHER(0x4010), IBM(0x04b3), rev 2.15 Controller /dev/usb4: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb5: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb6: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: high speed, power 2 mA, config 2, IBM Composite Device-0(0x4012), IBM(0x04b3), rev 0.00 port 2 powered port 3 powered port 4 powered port 5 powered port 6 addr 3: high speed, power 450 mA, config 1, product 0x1a00(0x1a00), vendor 0x2001(0x2001), rev 10.01 Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE-p8 #0: Wed Nov 18 11:22:57 EST 2009 muck@dmz55.greatbaysoftware.com:/usr/obj/usr/src/sys/DMZ55 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (2000.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5 Features=0xbfebfbff Features2=0x9ce3bd AMD Features=0x28100000 AMD Features2=0x1 Cores per package: 8 Logical CPUs per core: 2 real memory = 2137583616 (2038 MB) avail memory = 2081480704 (1985 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "HPET" frequency 14318180 Hz quality 900 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 28 at device 1.0 on pci0 pci11: on pcib1 pci11: at device 0.0 (no driver attached) pci11: at device 0.1 (no driver attached) pcib2: irq 29 at device 2.0 on pci0 pci16: on pcib2 pci16: at device 0.0 (no driver attached) pci16: at device 0.1 (no driver attached) pcib3: irq 24 at device 3.0 on pci0 pci21: on pcib3 pcib4: irq 30 at device 7.0 on pci0 pci26: on pcib4 pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 17.0 (no driver attached) pci0: at device 17.1 (no driver attached) pci0: at device 20.0 (no driver attached) pci0: at device 20.1 (no driver attached) pci0: at device 20.2 (no driver attached) pci0: at device 20.3 (no driver attached) pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) pci0: at device 22.2 (no driver attached) pci0: at device 22.3 (no driver attached) pci0: at device 22.4 (no driver attached) pci0: at device 22.5 (no driver attached) pci0: at device 22.6 (no driver attached) pci0: at device 22.7 (no driver attached) uhci0: port 0x20a0-0x20bf irq 17 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2080-0x209f irq 18 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0x9ba21400-0x9ba217ff irq 19 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 6 ports with 6 removable, self powered pcib5: irq 16 at device 28.0 on pci0 pci1: on pcib5 mpt0: port 0x1000-0x10ff mem 0x9b910000-0x9b913fff,0x9b900000-0x9b90ffff irq 16 at device 0.0 on pci1 mpt0: [ITHREAD] mpt0: MPI Version=1.5.20.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (14 Max) pcib6: irq 16 at device 28.4 on pci0 pci6: on pcib6 pcib7: irq 16 at device 0.0 on pci6 pci7: on pcib7 vgapci0: mem 0x9a000000-0x9affffff,0x9b800000-0x9b803fff,0x9b000000-0x9b7fffff irq 16 at device 0.0 on pci7 uhci2: port 0x2060-0x207f irq 17 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb3: on uhci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered uhci3: port 0x2040-0x205f irq 18 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0x2020-0x203f irq 19 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered ehci1: mem 0x9ba21000-0x9ba213ff irq 17 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub6: on usb6 uhub6: 6 ports with 6 removable, self powered ukbd0: on uhub6 kbd2 at ukbd0 ums0: on uhub6 ums0: X report 0x0002 not supported device_attach: ums0 attach returned 6 ums0: on uhub6 ums0: 3 buttons and Z dir. umass0: on uhub6 umass1: on uhub6 axe0: on uhub6 axe0: AX88172, bufsz 1536, boundary 64 miibus0: on axe0 rlphy0: PHY 3 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto axe0: WARNING: using obsoleted if_watchdog interface axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag axe0: Ethernet address: 00:80:c8:38:15:ff pcib8: at device 30.0 on pci0 pci31: on pcib8 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20f0-0x20ff,0x20e0-0x20ef irq 16 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci1: port 0x2108-0x210f,0x2124-0x2127,0x2100-0x2107,0x2120-0x2123,0x20d0-0x20df,0x20c0-0x20cf irq 21 at device 31.5 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 p4tcc3: on cpu3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd1: on uhub0 kbd3 at ukbd1 uhid0: on uhub0 cdce0: on uhub3 cdce0: faking MAC address cdce0: WARNING: using obsoleted IFF_NEEDSGIANT flag cdce0: Ethernet address: 2a:00:00:00:00:00 Timecounters tick every 1.000 msec acd0: CDRW at ata0-master UDMA33 da0 at mpt0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing Enabled da0: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) da1 at mpt0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-5 device da1: 300.000MB/s transfers da1: Command Queueing Enabled da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! da2 at umass-sim1 bus 1 target 0 lun 0 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 40.000MB/s transfers da3 at umass-sim1 bus 1 target 0 lun 1 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/da0s1a Charles Owens Great Bay Software| www.GreatBaySoftware.com From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 2 15:03:31 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 015FD106566B for ; Wed, 2 Dec 2009 15:03:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C8D748FC1B for ; Wed, 2 Dec 2009 15:03:30 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 845E446B23; Wed, 2 Dec 2009 10:03:30 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id D76C28A020; Wed, 2 Dec 2009 10:03:29 -0500 (EST) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 2 Dec 2009 09:43:15 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <4B070F07.8010600@greatbaysoftware.com> <4B156C80.7090706@greatbaysoftware.com> In-Reply-To: <4B156C80.7090706@greatbaysoftware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912020943.15200.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 02 Dec 2009 10:03:29 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Charles Owens Subject: Re: USB bus setup error with PAE (was USB keyboard flaky with PAE kernel, 7.1) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2009 15:03:31 -0000 On Tuesday 01 December 2009 2:20:32 pm Charles Owens wrote: > Charles Owens wrote: > > Howdy, > > > > I'm still digging into it, put preliminary testing is showing that > > with a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only > > occasionally, if you're lucky. This flakiness is being seen with > > several different server models that we support (HP and IBM, all Xeon > > based). If we boot a non-PAE kernel then the USB keyboard is rock solid. > > My initial report was entirely too broad --- an unrelated problem was > confusing things. I can now report that this problem appears limited to > only the IBM System x3550 M2. With a PAE-enabled kernel initialization > of some of the USB buses fails. From an external perspective, this > results in the rear USB port being non-functional, while the two front > USB ports work fine. For some reason, though, when booting the same PAE > kernel from a CD none of the USB ports function. > > In previous posting ( > http://docs.freebsd.org/cgi/mid.cgi?4B0D14CB.1010000 ) I included output > of usbdevs and boot log when running the PAE-enabled kernel. Note the > "root hub error" messages in boot log. > > Below I'll repeat the same info when running a non-PAE kernel. > > Any thoughts as to what the story is here... and suggestions for > resolution? Thanks in advance. Would you be able to test an 8.0 kernel with PAE enabled? 8.0 has a completely rewritten USB stack, so there is a chance that the bug in 7 might not be present in 8. You can also try posting on freebsd-usb@ since the folks working on the USB drivers tend to hang out on that list. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 2 15:59:20 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E10A106566B; Wed, 2 Dec 2009 15:59:20 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id DC3F08FC18; Wed, 2 Dec 2009 15:59:19 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Wed, 2 Dec 2009 10:59:19 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B168FB2.6020509@greatbaysoftware.com> Date: Wed, 02 Dec 2009 11:02:58 -0500 From: Charles Owens MIME-Version: 1.0 To: John Baldwin References: <4B070F07.8010600@greatbaysoftware.com> <4B156C80.7090706@greatbaysoftware.com> <200912020943.15200.jhb@freebsd.org> In-Reply-To: <200912020943.15200.jhb@freebsd.org> X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: USB bus setup error with PAE (was USB keyboard flaky with PAE kernel, 7.1) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2009 15:59:20 -0000 John Baldwin wrote: > On Tuesday 01 December 2009 2:20:32 pm Charles Owens wrote: > >> Charles Owens wrote: >> >>> Howdy, >>> >>> I'm still digging into it, put preliminary testing is showing that >>> with a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only >>> occasionally, if you're lucky. This flakiness is being seen with >>> several different server models that we support (HP and IBM, all Xeon >>> based). If we boot a non-PAE kernel then the USB keyboard is rock solid. >>> >> My initial report was entirely too broad --- an unrelated problem was >> confusing things. I can now report that this problem appears limited to >> only the IBM System x3550 M2. With a PAE-enabled kernel initialization >> of some of the USB buses fails. From an external perspective, this >> results in the rear USB port being non-functional, while the two front >> USB ports work fine. For some reason, though, when booting the same PAE >> kernel from a CD none of the USB ports function. >> >> In previous posting ( >> http://docs.freebsd.org/cgi/mid.cgi?4B0D14CB.1010000 ) I included output >> of usbdevs and boot log when running the PAE-enabled kernel. Note the >> "root hub error" messages in boot log. >> >> Below I'll repeat the same info when running a non-PAE kernel. >> >> Any thoughts as to what the story is here... and suggestions for >> resolution? Thanks in advance. >> > > Would you be able to test an 8.0 kernel with PAE enabled? 8.0 has a > completely rewritten USB stack, so there is a chance that the bug in 7 might > not be present in 8. You can also try posting on freebsd-usb@ since the folks > working on the USB drivers tend to hang out on that list. > Good suggestions... I'll proceed with both. Thanks, Charles