From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 5 00:14:27 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1D5A16A422 for ; Sun, 5 Mar 2006 00:14:27 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A1FD43D46 for ; Sun, 5 Mar 2006 00:14:25 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FFgtE-0000Mm-Bo; Sat, 04 Mar 2006 19:14:24 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.3/8.13.3/Submit) id k250EOa1001409; Sat, 4 Mar 2006 19:14:24 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Sat, 4 Mar 2006 19:14:24 -0500 (EST) From: "FreeBSD" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 192.168.1.9 X-Mailer: Usermin 1.190 Message-Id: <1141517664.1407@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1141517664" Subject: FreeBSD shutting down unexpectedly 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, 05 Mar 2006 00:14:27 -0000 This is a multi-part message in MIME format. --bound1141517664 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hi everyone, I'm having a problem with my FreeBSD server shutting down for no reason. This started happening recently (within the last month) so I'm not sure if the hardware is dying or if there's another underlying problem. The server is a rackmountable 1U chassis at a remote location connected to an APC UPS. When I lose connectivity and go to physically inspect the server, it's powered off completely as if there was a power outage. However, each time I can confirm that the UPS did not lose power and there were no voltage spikes (the APC can be managed via telnet and SNMP so there are logs I can look at). So far the only way I've been able to reproduce the problem is by running "portsdb -Uu" to update the ports DB after a cvsup of the ports tree. I suppose this is a CPU/disk intensive task so maybe I have a dying hard drive? Running this command used to take about 10 minutes for me, now when I run it about 5 minutes later the box powers off mysteriously. There's nothing in /var/log/messa ges and after I bring it back up, dmesg does not show anything unusual. I setup a console server to monitor this server's console but there was absolutely nothing on the console during the last such "crash". I'm looking for some suggestions on how to troubleshoot this problem, perhaps I can enable crash dump files or some sort of debugging? Here's some output: su-2.05b# 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 5.4-RELEASE #1: Fri Jul 1 18:02:01 EST 2005 *@*.com:/usr/src/sys/i386/compile/CUSTOM ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU - S 1266MHz (1262.30-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b4 Stepping = 4 Features=0x383fbff real memory = 1073676288 (1023 MB) avail memory = 1045422080 (996 MB) ioapic0 irqs 0-23 on motherboard npx0: on motherboard npx0: INT 16 interface 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 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pci0: at device 7.4 (no driver attached) em0: port 0xe400-0xe43f mem 0xdffc0000-0xdffdffff,0xdffe0000-0xdfffffff irq 17 at device 9.0 on pci0 em0: Ethernet address: 00:07:e9:09:d5:b2 em0: Speed:N/A Duplex:N/A fxp0: port 0xe000-0xe03f mem 0xdfe00000-0xdfefffff,0xdff9f000-0xdff9ffff irq 18 at device 14.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:20:ed:69:c8:22 acpi_tz0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 orm0: at iomem 0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1262301687 Hz quality 800 Timecounters tick every 10.000 msec ad0: 78533MB [159560/16/63] at ata0-master UDMA100 ata1-master: DMA limited to UDMA33, non-ATA66 cable or device ad2: 78533MB [159560/16/63] at ata1-master UDMA33 acd0: CDROM at ata1-slave PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted WARNING: /www was not properly dismounted WARNING: /storage was not properly dismounted su-2.05b# df -H Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 5.2G 51M 4.7G 1% / devfs 1.0k 1.0k 0B 100% /dev /dev/ad0s1f 2.1G 16M 1.9G 1% /tmp /dev/ad0s1d 31G 5.9G 23G 21% /usr /dev/ad0s1e 10G 78M 9.5G 1% /var /dev/ad0s1g 29G 13M 26G 0% /www /dev/ad2s1d 80G 10k 73G 0% /storage su-2.05b# uname -a FreeBSD *.com 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Fri Jul 1 18:02:01 EST 2005 *@*.com:/usr/src/sys/i386/compile/CUSTOM i386 Any suggestions would be welcome. Thanks. -Yuri --bound1141517664-- From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 5 03:47:44 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12B9F16A420 for ; Sun, 5 Mar 2006 03:47:44 +0000 (GMT) (envelope-from jfm@shell.reiteration.net) Received: from asmtp-out3.blueyonder.co.uk (asmtp-out3.blueyonder.co.uk [195.188.213.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A6AC43D45 for ; Sun, 5 Mar 2006 03:47:43 +0000 (GMT) (envelope-from jfm@shell.reiteration.net) Received: from [82.34.179.228] (helo=shell.reiteration.net) by asmtp-out3.blueyonder.co.uk with esmtp (Exim 4.52) id 1FFkDe-0002uM-3u for freebsd-hardware@freebsd.org; Sun, 05 Mar 2006 03:47:42 +0000 Received: from localhost ([127.0.0.1] helo=shell.reiteration.net ident=jfm) by shell.reiteration.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FFYBO-000JVW-OI for freebsd-hardware@freebsd.org; Sat, 04 Mar 2006 14:56:34 +0000 Received: (from jfm@localhost) by shell.reiteration.net (8.13.4/8.13.4/Submit) id k24EuYG7074989 for freebsd-hardware@freebsd.org; Sat, 4 Mar 2006 14:56:34 GMT (envelope-from jfm) Date: Sat, 4 Mar 2006 14:56:34 +0000 From: John To: freebsd-hardware@freebsd.org Message-ID: <20060304145634.GA74733@reiteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jfm@shell.reiteration.net X-SA-Exim-Scanned: No (on shell.reiteration.net); SAEximRunCond expanded to false Subject: socket 939 boards with SATA 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, 05 Mar 2006 03:47:44 -0000 Hello list Can anyone recommend a socket 939 board for use with FreeBSD 6? Does SATA work? thanks -- John From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 5 07:56:17 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5809D16A420 for ; Sun, 5 Mar 2006 07:56:17 +0000 (GMT) (envelope-from gcorcoran@rcn.com) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02DAA43D55 for ; Sun, 5 Mar 2006 07:56:13 +0000 (GMT) (envelope-from gcorcoran@rcn.com) Received: from 207-172-241-254.c3-0.tlg-ubr1.atw-tlg.pa.cable.rcn.com (HELO [10.56.78.130]) ([207.172.241.254]) by smtp02.mrf.mail.rcn.net with ESMTP; 05 Mar 2006 02:56:14 -0500 X-IronPort-AV: i="4.02,164,1139202000"; d="scan'208"; a="211285855:sNHT28100096" Message-ID: <440A9B0A.4050303@rcn.com> Date: Sun, 05 Mar 2006 03:02:18 -0500 From: Gary Corcoran User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: FreeBSD References: <1141517664.1407@swaggi.com> In-Reply-To: <1141517664.1407@swaggi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: me@carrollkong.com, freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly 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, 05 Mar 2006 07:56:17 -0000 FreeBSD wrote: > Hi everyone, > > I'm having a problem with my FreeBSD server shutting down for no reason. This started happening recently (within the last month) so I'm not sure if the hardware is dying or if there's another underlying problem. The server is a rackmountable 1U chassis at a remote location connected to an APC UPS. When I lose connectivity and go to physically inspect the server, it's powered off completely as if there was a power outage. However, each time I can confirm that the UPS did not lose power and there were no voltage spikes (the APC can be managed via telnet and SNMP so there are logs I can look at). So far the only way I've been able to reproduce the problem is by running "portsdb -Uu" to update the ports DB after a cvsup of the ports tree. I suppose this is a CPU/disk intensive task so maybe I have a dying hard drive? Running this command used to take about 10 minutes for me, now when I run it about 5 minutes later the box powers off mysteriously. There's nothing in /var/log/me ssa > ges and after I bring it back up, dmesg does not show anything unusual. I setup a console server to monitor this server's console but there was absolutely nothing on the console during the last such "crash". > I'm looking for some suggestions on how to troubleshoot this problem, perhaps I can enable crash dump files or some sort of debugging? Here's some output: > Any suggestions would be welcome. You may have a failing, or underpowered, power supply, which could cause flakiness when you have large amounts of CPU and/or disk activity. Or, sorry to say, you may be yet another victim of the "bad capacitors" that have plagued many motherboards, even from quality makers, during the past few years. Do a google search, or try this site that google just showed me, for what to look for: http://www.badcaps.net/ Gary From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 5 19:23:44 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6857316A420 for ; Sun, 5 Mar 2006 19:23:44 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C391943D46 for ; Sun, 5 Mar 2006 19:23:43 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A56BD.dip.t-dialin.net [84.154.86.189]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k25JNaaK011598; Sun, 5 Mar 2006 20:23:41 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k25JNViR031432; Sun, 5 Mar 2006 20:23:31 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k25JR0sl043971; Sun, 5 Mar 2006 20:27:00 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200603051927.k25JR0sl043971@fire.jhs.private> To: "FreeBSD" In-Reply-To: Message from "FreeBSD" of "Sat, 04 Mar 2006 19:14:24 EST." <1141517664.1407@swaggi.com> Date: Sun, 05 Mar 2006 20:26:59 +0100 From: "Julian H. Stacey" Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly 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, 05 Mar 2006 19:23:44 -0000 > I'm having a problem with my FreeBSD server shutting down for no reason. This started happening recently (within the last month) so I'm not sure if the hardware is dying or if there's another underlying problem. The server is a rackmountable 1U chassis at a remote location connected to an APC UPS. When I lose connectivity and go to physically inspect the server, it's powered off completely as if there was a power outage. However, each time I can confirm that the UPS did not lose power and there were no voltage spikes (the APC can be managed via telnet and SNMP so there are logs I can look at). So far the only way I've been able to reproduce the problem is by running "portsdb -Uu" to update the ports DB after a cvsup of the ports tree. I suppose this is a CPU/disk intensive task so maybe I have a dying hard drive? Running this command used to take about 10 minutes for me, now when I run it about 5 minutes later the box powers off mysteriously. There's nothing in /var/log/messa Please prune your line length ! APC can also be controlled & logged by NUT /usr/ports/sysutils/nut > ges and after I bring it back up, dmesg does not show anything unusual. I setup a console server to monitor this server's console but there was absolutely nothing on the console during the last such "crash". > I'm looking for some suggestions on how to troubleshoot this problem, perhaps I can enable crash dump files or some sort of debugging? Here's some output: Maybe your CPU or chassis fan is sticky/ slow/ dead. You can check your running temps withn other things in /usr/ports/sysutils/ > Any suggestions would be welcome. Good luck. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = meine allergischen Kopfschmerzen. From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 00:51:19 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B34B716A420 for ; Mon, 6 Mar 2006 00:51:19 +0000 (GMT) (envelope-from g_jin@lbl.gov) Received: from smtp107.sbc.mail.mud.yahoo.com (smtp107.sbc.mail.mud.yahoo.com [68.142.198.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 54C9E43D45 for ; Mon, 6 Mar 2006 00:51:19 +0000 (GMT) (envelope-from g_jin@lbl.gov) Received: (qmail 72684 invoked from network); 6 Mar 2006 00:51:18 -0000 Received: from unknown (HELO ?192.168.2.10?) (jinmtb@sbcglobal.net@68.127.175.150 with plain) by smtp107.sbc.mail.mud.yahoo.com with SMTP; 6 Mar 2006 00:51:18 -0000 Message-ID: <440B87C2.3060704@lbl.gov> Date: Sun, 05 Mar 2006 16:52:18 -0800 From: "Jin Guojun [VFFS]" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050108 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: me@carrollkong.com References: <1141517664.1407@swaggi.com> <440A9B0A.4050303@rcn.com> In-Reply-To: <440A9B0A.4050303@rcn.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD , freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly 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, 06 Mar 2006 00:51:19 -0000 Gary Corcoran wrote: > FreeBSD wrote: > >> Hi everyone, >> I'm having a problem with my FreeBSD server shutting down for no >> reason. This started happening recently (within the last month) so >> I'm not sure if the hardware is dying or if there's another >> underlying problem. The server is a rackmountable 1U chassis at a >> remote location connected to an APC UPS. When I lose connectivity and >> go to physically inspect the server, it's powered off completely as >> if there was a power outage. However, each time I can confirm that >> the UPS did not lose power and there were no voltage spikes (the APC >> can be managed via telnet and SNMP so there are logs I can look at). >> So far the only way I've been able to reproduce the problem is by >> running "portsdb -Uu" to update the ports DB after a cvsup of the >> ports tree. I suppose this is a CPU/disk intensive task so maybe I >> have a dying hard drive? Running this command used to take about 10 >> minutes for me, now when I run it about 5 minutes later the box >> powers off mysteriously. There's nothing in /var/log/me > > ssa > >> ges and after I bring it back up, dmesg does not show anything >> unusual. I setup a console server to monitor this server's console >> but there was absolutely nothing on the console during the last such >> "crash". >> I'm looking for some suggestions on how to troubleshoot this problem, >> perhaps I can enable crash dump files or some sort of debugging? >> Here's some output: > > > >> Any suggestions would be welcome. > > > You may have a failing, or underpowered, power supply, which could cause > flakiness when you have large amounts of CPU and/or disk activity. It sound like a power related issue. Another thing to try is to remove the UPS, even though you think it is OK. 5 years ago, we bought 25 APC and more than 7 had some problems. Some of them turned machine off, while monitor meter did not show losing power. APC may have improved their product now, but try to isolate it first. If the server still has the same problem, than the power supply may be degraded (check the fan and temperature). Dying hard drive generally will not cause power shuting down. -Jin From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 02:01:18 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43E8716A420 for ; Mon, 6 Mar 2006 02:01:18 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id E93C543D48 for ; Mon, 6 Mar 2006 02:01:15 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FG52B-0002rz-0g for freebsd-hardware@freebsd.org; Sun, 05 Mar 2006 21:01:15 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.3/8.13.3/Submit) id k2621EVT011033; Sun, 5 Mar 2006 21:01:14 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Sun, 5 Mar 2006 21:01:14 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 192.168.1.9 X-Mailer: Usermin 1.190 In-Reply-To: <440B87C2.3060704@lbl.gov> Message-Id: <1141610474.10989@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1141610474" Subject: Re: FreeBSD shutting down unexpectedly 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, 06 Mar 2006 02:01:18 -0000 This is a multi-part message in MIME format. --bound1141610474 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Jin Guojun [VFFS] wrote .. > Gary Corcoran wrote: > > You may have a failing, or underpowered, power supply, which could cause > > flakiness when you have large amounts of CPU and/or disk activity. > > It sound like a power related issue. Another thing to try is to remove > the UPS, > even though you think it is OK. > 5 years ago, we bought 25 APC and more than 7 had some problems. Some of > them turned machine off, while monitor meter did not show losing power. > APC may have improved their product now, but try to isolate it first. > If the server still has the same problem, than the power supply may be > degraded > (check the fan and temperature). > Dying hard drive generally will not cause power shuting down. > > -Jin Thanks for the suggestions everyone, I will find some time this week to bring down the server and thoroughly inspect the hardware. It's most likely the power supply failing so I will have to look for a replacement. I will update the list once I find the culprit. -Yuri --bound1141610474-- From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 02:06:00 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B42BB16A420 for ; Mon, 6 Mar 2006 02:06:00 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6522943D46 for ; Mon, 6 Mar 2006 02:06:00 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FG56l-0002sv-T6 for freebsd-hardware@freebsd.org; Sun, 05 Mar 2006 21:06:00 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.3/8.13.3/Submit) id k2625xOD011091; Sun, 5 Mar 2006 21:05:59 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Sun, 5 Mar 2006 21:05:59 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 192.168.1.9 X-Mailer: Usermin 1.190 In-Reply-To: <200603051927.k25JR0sl043971@fire.jhs.private> Message-Id: <1141610759.11088@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1141610759" Subject: Re: FreeBSD shutting down unexpectedly 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, 06 Mar 2006 02:06:00 -0000 This is a multi-part message in MIME format. --bound1141610759 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Julian H. Stacey wrote .. > > APC can also be controlled & logged by NUT > /usr/ports/sysutils/nut Looks promising, I will check this out although I'm almost 100% sure the APC UPS is OK (as there are other devices on it). > Maybe your CPU or chassis fan is sticky/ slow/ dead. > > You can check your running temps withn other things in /usr/ports/sysutils/ > > Good luck. Do you know which ports specifically can show running temps? Thanks, -Yuri --bound1141610759-- From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 02:13:24 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE65E16A420 for ; Mon, 6 Mar 2006 02:13:24 +0000 (GMT) (envelope-from rossiya@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AEF743D46 for ; Mon, 6 Mar 2006 02:13:23 +0000 (GMT) (envelope-from rossiya@gmail.com) Received: by nproxy.gmail.com with SMTP id i2so747469nfe for ; Sun, 05 Mar 2006 18:13:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=E6fSwv45MRNvrY3xvQvAQNlMeB1eRctn3Ob7LQNWIW30SvwmyoM8oL1hIPtKPU/7bdSPTLXbSfNKesHCjhkWbeTOGjptfcD/RxNdpC3UskKWLjTnWgWRBc7UBGPbaRLW5vazBcjkaGhOLRDJxjWF4vUK4wmWDTIZ5BEfgrcibp4= Received: by 10.49.11.18 with SMTP id o18mr2190330nfi; Sun, 05 Mar 2006 18:13:22 -0800 (PST) Received: by 10.48.219.7 with HTTP; Sun, 5 Mar 2006 18:13:22 -0800 (PST) Message-ID: <28a99ba50603051813o18b30df3t1df3e3bb9a9a6347@mail.gmail.com> Date: Sun, 5 Mar 2006 18:13:22 -0800 From: MC To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Best USB PCI Card 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, 06 Mar 2006 02:13:24 -0000 Hi I am shopping for a USB2 PCI card to support 4 or more USB hard drives. I thought to get a PCI card rather than an external USB2 hub, which splits the USB2 bandwidth. Looking through the supported hardware of freebsd6.x there's a big list of supported devices, but none that match hardware vendor websites offhand. I see for example the ALi 6+2 port USB 2.0 PCI Card with the ALi M573 chipset and VIA VT6212 4+1 Port USB 2.0 PCI Controller Card with the VIA VT6212 chipset. But these don't match anything on http://www.freebsd.org/releases/6.0R/hardware-i386.html What are the best [most compatible trouble free] USB PCI cards? From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 02:18:44 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1859F16A420 for ; Mon, 6 Mar 2006 02:18:44 +0000 (GMT) (envelope-from dean@bong.com.au) Received: from aramaki.bong.com.au (aramaki.bong.com.au [203.91.232.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0DB943D45 for ; Mon, 6 Mar 2006 02:18:43 +0000 (GMT) (envelope-from dean@bong.com.au) Received: from paynet-gw.penrithcity.nsw.gov.au ([203.91.245.98] helo=[127.0.0.1]) by aramaki.bong.com.au with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FG5J8-0005kq-Rq; Mon, 06 Mar 2006 13:18:47 +1100 Message-ID: <440B9BFF.2010503@bong.com.au> Date: Mon, 06 Mar 2006 13:18:39 +1100 From: Dean Hamstead User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: MC References: <28a99ba50603051813o18b30df3t1df3e3bb9a9a6347@mail.gmail.com> In-Reply-To: <28a99ba50603051813o18b30df3t1df3e3bb9a9a6347@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: Best USB PCI Card 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, 06 Mar 2006 02:18:44 -0000 i would be careful with the theory that the usb pci card supplies N number of completely independent USB 2.0 ports. im not sure that they don't just supply one and then a built in N port hub. just food for thought. Dean MC wrote: > Hi I am shopping for a USB2 PCI card to support 4 or more USB hard drives. > I thought to > get a PCI card rather than an external USB2 hub, which splits the USB2 > bandwidth. > Looking through the supported hardware of freebsd6.x there's a big list of > supported > devices, but none that match hardware vendor websites offhand. I see for > example > the ALi 6+2 port USB 2.0 PCI Card with the ALi M573 chipset and VIA VT6212 > 4+1 > Port USB 2.0 PCI Controller Card with the VIA VT6212 chipset. But these > don't match > anything on http://www.freebsd.org/releases/6.0R/hardware-i386.html > > What are the best [most compatible trouble free] USB PCI cards? > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 06:58:06 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D32FD16A420 for ; Mon, 6 Mar 2006 06:58:06 +0000 (GMT) (envelope-from bsdfan@nurfuerspam.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 195F543D49 for ; Mon, 6 Mar 2006 06:58:05 +0000 (GMT) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail 1079 invoked by uid 0); 6 Mar 2006 06:58:05 -0000 Received: from 84.63.52.204 by www047.gmx.net with HTTP; Mon, 6 Mar 2006 07:58:04 +0100 (MET) Date: Mon, 6 Mar 2006 07:58:04 +0100 (MET) From: "Markus Dolze" To: MC MIME-Version: 1.0 References: <28a99ba50603051813o18b30df3t1df3e3bb9a9a6347@mail.gmail.com> X-Priority: 3 (Normal) X-Authenticated: #931807 Message-ID: <23679.1141628284@www047.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Cc: freebsd-hardware@freebsd.org Subject: Re: Best USB PCI Card 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, 06 Mar 2006 06:58:06 -0000 > --- Ursprüngliche Nachricht --- > Von: MC > An: freebsd-hardware@freebsd.org > Betreff: Best USB PCI Card > Datum: Sun, 5 Mar 2006 18:13:22 -0800 > > Hi I am shopping for a USB2 PCI card to support 4 or more USB hard drives. > I thought to > get a PCI card rather than an external USB2 hub, which splits the USB2 > bandwidth. > Looking through the supported hardware of freebsd6.x there's a big list of > supported > devices, but none that match hardware vendor websites offhand. I see for > example > the ALi 6+2 port USB 2.0 PCI Card with the ALi M573 chipset and VIA VT6212 > 4+1 > Port USB 2.0 PCI Controller Card with the VIA VT6212 chipset. But these > don't match > anything on http://www.freebsd.org/releases/6.0R/hardware-i386.html > > What are the best [most compatible trouble free] USB PCI cards? Hi, I would not use cards with ALi anymore. I got one and had problems with it. When doing high-speed transfers the card resets sometimes. The history of the windows driver lists a lot of problems fixed in the past. I have good experience with a card equipped with a NEC chip. Regards Markus From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 07:41:20 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D632C16A420 for ; Mon, 6 Mar 2006 07:41:20 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd3mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72FC443D45 for ; Mon, 6 Mar 2006 07:41:20 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd5mr6so.prod.shaw.ca (pd5mr6so-qfe3.prod.shaw.ca [10.0.141.182]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IVP005KY40V30F0@l-daemon> for freebsd-hardware@freebsd.org; Mon, 06 Mar 2006 00:41:19 -0700 (MST) Received: from pn2ml2so.prod.shaw.ca ([10.0.121.146]) by pd5mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IVP0035D40VYG90@pd5mr6so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Mon, 06 Mar 2006 00:41:19 -0700 (MST) Received: from soralx.cydem.org ([24.85.63.128]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IVP00G0X40UXXN0@l-daemon> for freebsd-hardware@freebsd.org; Mon, 06 Mar 2006 00:41:19 -0700 (MST) Date: Sun, 05 Mar 2006 23:41:18 -0800 From: soralx@cydem.org In-reply-to: <440B87C2.3060704@lbl.gov> To: freebsd-hardware@freebsd.org Message-id: <200603052341.18723.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <1141517664.1407@swaggi.com> <440A9B0A.4050303@rcn.com> <440B87C2.3060704@lbl.gov> User-Agent: KMail/1.5.4 Cc: g_jin@lbl.gov, freebsd@swaggi.com, me@carrollkong.com Subject: Re: FreeBSD shutting down unexpectedly 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, 06 Mar 2006 07:41:21 -0000 > >> I'm having a problem with my FreeBSD server shutting down for no > >> reason. This started happening recently (within the last month) so > Or, sorry to say, you may be yet another victim of the "bad capacitors" > that have plagued many motherboards, even from quality makers, during > the past few years. Do a google search, or try this site that google > just showed me, for what to look for: http://www.badcaps.net/ or even better: http://en.wikipedia.org/wiki/Capacitor_plague capacitors recently confirmed (by me personally) to be bad (found in Thermaltake PSU and a Gigabyte mainboard): G-Luxon, Choyo, Tayeh. As I mentioned before, bad/failing/questionable power supplies is not something I advise to use in any systemm, if the system and it's data are of any value. Failing capacitor may (though seldom) cause a MOSFET failure, which may possibly be a Source-Drain short circuit. This means that voltage way too high will be applied to components before the transistor lets out some magic smoke, or (current limiting)|(overcurrent shutoff) kicks in. There is another way in which a failing PSU may destroy your data. My old AT server became unstable a month ago (halts, shuts off, etc). So I measured it's power supply's output: +5V was at ~12.5Vdc level, and +12V was as high as 20Vdc. The server couldn't boot, becase somehow the boot record on HDD became corrupted (the rest of data was ok). Turns out the PSU's fan stopped, so it worked at high temperatures for months, which immensely shortened capacitors' life (for electrolytics, the service life roughly halves for every 10*C temperature increase), ending in parametric failure. As you can see, it's always a good idea to replace all power capacitors on mainboard and power supply with quality ones before use (even if new). It cost me ~$30 to get all capacitors > 470uF for a socket478 mainboard and 2 ATX PSUs (I got high-quality, low ESR Nichicon UPL-series caps). So, ensure good cooling, test components before use (especially the PSU), watch for symptoms of hardware failure, avoid poor quality parts, and don't forget about maintenance; these simple rules become automatic very quickly. BTW, by 'good quality parts' I mean not just some brand parts, but devices made for optimum performance/efficiency, not for optimum profit to the brand. Since such components are nearly impossible to find nowadays (for reasonable price), it's a good idea to buy some more-or-less good (well engineered) parts (such as Thermaltake PSU, for example -- not some no-name genius of a Chinese engineer), throw out low quality components (such as power capacitors and fans), and install good quality parts. This will _greatly_ increase stability, service life, and sometimes efficiency. rant { If more people refused to buy crappy devices (many don't even imagine how bad, horribly bad, most non-server grade products are), we wouldn't have manufacturers who try to cut cost by deliberately utilizing (flawed)|(low quality) components. Would you consider spending U$15 (cost of good capacitors) more on a $320 mainboard and get a reliable, stable (better overclocking, too) board that will serve you well for many years (istead of just 0.5 - 3y max)? Would you try to save a few bucks on a $100 power supply to get an unstable, high-ripple PSU which may kill your HDD one day? This applies not only to computer, of course. } > 5 years ago, we bought 25 APC and more than 7 had some problems. Some of > them turned machine off, while monitor meter did not show losing power. Possibly, the UPSes had dead/discharged batteries, so when doing a self-test, would lose power to the load. > Do you know which ports specifically can show running temps? 'ports/sysutils/mbmon' works for me Timestamp: 0x440BC5DB [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 08:07:34 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E267E16A420 for ; Mon, 6 Mar 2006 08:07:34 +0000 (GMT) (envelope-from rossiya@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD91443D48 for ; Mon, 6 Mar 2006 08:07:33 +0000 (GMT) (envelope-from rossiya@gmail.com) Received: by nproxy.gmail.com with SMTP id d4so780052nfe for ; Mon, 06 Mar 2006 00:07:32 -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:references; b=cc2TS2R06wLAlskNnu0MJBB8oLPSx8lgWItbObVOZEWxGu/ra/+Bix9wTWmtl/ueRhRPABz2jj18JQXDm1NBgnp86nv99T1P9MzW1U/QIpf+o//lXiZOMnpnyJJYkQt5rJgxdkMxCKGld1Hxpwp0KsrSiQvR79yFiVl875nD5Kg= Received: by 10.48.238.3 with SMTP id l3mr2276611nfh; Mon, 06 Mar 2006 00:07:32 -0800 (PST) Received: by 10.48.219.7 with HTTP; Mon, 6 Mar 2006 00:07:32 -0800 (PST) Message-ID: <28a99ba50603060007j6efd5e70la51ddce58b786f05@mail.gmail.com> Date: Mon, 6 Mar 2006 00:07:32 -0800 From: MC To: "Markus Dolze" In-Reply-To: <23679.1141628284@www047.gmx.net> MIME-Version: 1.0 References: <28a99ba50603051813o18b30df3t1df3e3bb9a9a6347@mail.gmail.com> <23679.1141628284@www047.gmx.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: Best USB PCI Card 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, 06 Mar 2006 08:07:35 -0000 I saw accounts of the NEC uPD 720100 USB 2.0 controller making troubles for the ehci driver last year this time. Sounds like they may be fixed now. I will try out the card see how it goes. I just installed a qemu gentoo linux for the LVM2 "infinite disk" feature and feed qemu the raw da0 ... da3 USB2 drives for a userspace backup system. When archiving is done, I just quit qemu and the disks can stay off for a week. I didn't have much luck passing the USB2 device to qeum as a USB handoff. But it's not needed as qemu takes disk devices with the -hdb -hdc and -hdd options On 3/5/06, Markus Dolze wrote: > > > --- Urspr=FCngliche Nachricht --- > > Von: MC > > An: freebsd-hardware@freebsd.org > > Betreff: Best USB PCI Card > > Datum: Sun, 5 Mar 2006 18:13:22 -0800 > > > > Hi I am shopping for a USB2 PCI card to support 4 or more USB hard > drives. > > I thought to > > get a PCI card rather than an external USB2 hub, which splits the USB2 > > bandwidth. > > Looking through the supported hardware of freebsd6.x there's a big list > of > > supported > > devices, but none that match hardware vendor websites offhand. I see > for > > example > > the ALi 6+2 port USB 2.0 PCI Card with the ALi M573 chipset and VIA > VT6212 > > 4+1 > > Port USB 2.0 PCI Controller Card with the VIA VT6212 chipset. But thes= e > > don't match > > anything on http://www.freebsd.org/releases/6.0R/hardware-i386.html > > > > What are the best [most compatible trouble free] USB PCI cards? > > Hi, > > I would not use cards with ALi anymore. I got one and had problems with > it. > When doing high-speed transfers the card resets sometimes. The history of > the windows driver lists a lot of problems fixed in the past. > > I have good experience with a card equipped with a NEC chip. > > Regards > Markus > From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 08:48:19 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 805CC16A420 for ; Mon, 6 Mar 2006 08:48:19 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id D106A43D45 for ; Mon, 6 Mar 2006 08:48:18 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k268m4bc019028 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Mar 2006 19:48:07 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k268m4o8001257; Mon, 6 Mar 2006 19:48:04 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k268m13V001256; Mon, 6 Mar 2006 19:48:01 +1100 (EST) (envelope-from peter) Date: Mon, 6 Mar 2006 19:48:01 +1100 From: Peter Jeremy To: soralx@cydem.org Message-ID: <20060306084801.GA826@turion.vk2pj.dyndns.org> References: <1141517664.1407@swaggi.com> <440A9B0A.4050303@rcn.com> <440B87C2.3060704@lbl.gov> <200603052341.18723.soralx@cydem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603052341.18723.soralx@cydem.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: g_jin@lbl.gov, freebsd@swaggi.com, me@carrollkong.com, freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly 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, 06 Mar 2006 08:48:19 -0000 On Sun, 2006-Mar-05 23:41:18 -0800, soralx@cydem.org wrote: >or even better: http://en.wikipedia.org/wiki/Capacitor_plague Good article. >capacitors recently confirmed (by me personally) to be bad (found in >Thermaltake PSU and a Gigabyte mainboard): G-Luxon, Choyo, Tayeh. I've also been a victim of this. Luckily I noticed fairly early and there was very little leakage (which I managed to clean off) and (AFAIK) no permanent damage. >It cost me ~$30 to get all capacitors > 470uF for a socket478 mainboard >and 2 ATX PSUs (I got high-quality, low ESR Nichicon UPL-series caps). Note that if you don't have the skills to replace the capacitors yourself, you need to add the labour cost for a technician (which will probably be somewhat more than the capacitors cost). Note that it's crucial that any goo be completely cleaned off the MB - it will destory the tracks if it's left. >If more people refused to buy crappy devices (many don't even imagine how >bad, horribly bad, most non-server grade products are), we wouldn't have >manufacturers who try to cut cost by deliberately utilizing >(flawed)|(low quality) components. It's not only low quality components, it's also poor thermal design. Heat is the major enemy of electrolytic capacitors. PSUs typically have all the capacitors crammed (and even glued) together, minimising cooling. My (GigaByte) MB has capacitors wedged between toroid inductors (which get quite hot during operation) and squeezed under the CPU heatsink. I also suspect (based on the unused capacitor pads) that manufacturers skimp on both filtering and bypassing. Even if the boards were designed conservatively, the manufacturer can save money by leaving "unnecessary" components out. > Would you consider spending U$15 (cost >of good capacitors) more on a $320 mainboard and get a reliable, stable >(better overclocking, too) board that will serve you well for many years >(istead of just 0.5 - 3y max)? Yes, but I don't have that choice. I can either buy consumer-grade equipment (which is virtually all of similar quality) or I can buy server-grade hardware - for several times as much. -- Peter Jeremy From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 11:45:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9330E16A420 for ; Mon, 6 Mar 2006 11:45:28 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from asmtp-out1.blueyonder.co.uk (asmtp-out1.blueyonder.co.uk [195.188.213.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B9DD43D70 for ; Mon, 6 Mar 2006 11:45:26 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [62.31.10.79] (helo=[192.168.0.2]) by asmtp-out1.blueyonder.co.uk with esmtp (Exim 4.52) id 1FGE9V-0005RM-D7; Mon, 06 Mar 2006 11:45:25 +0000 Message-ID: <440C20D4.6090400@dial.pipex.com> Date: Mon, 06 Mar 2006 11:45:24 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: John References: <20060304145634.GA74733@reiteration.net> In-Reply-To: <20060304145634.GA74733@reiteration.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: socket 939 boards with SATA 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, 06 Mar 2006 11:45:28 -0000 John wrote: >Hello list > >Can anyone recommend a socket 939 board for use with FreeBSD 6? Does >SATA work? > > Asus A8V Deluxe works. I won't go so far as to recommend it - it works just fine and I am happy with it - but it's now 9 months since I bought it and I haven't kept up with any developments in the field. The board is not SLI, for example (no clue if that's supported yet) and has no PCI-E PCI-X PCI-Express or other mind-bending variations none of which I can ever get my head around. It has two SATA RAID chipsets which I do not (yet) use in RAID mode. (SATA disks work just fine as long as you controller is supported - check the hardware compatibility pages on the website and use google). Everything else that I would hope to work on the board (ethernet, sound, serial port) works just fine for me. There are some issues with the ACPI but it does the basic thing of powering the machine off which is all I really care about. This is running 5.4 but I wouldn't expect 6 to break anything fundamental -- there were issues with RAID0 on the VIA controller in 6.0. No idea if they are fixed or not and there was an unofficial patch floating around, if you cared. --Alex From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 6 23:41:54 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70C5016A420 for ; Mon, 6 Mar 2006 23:41:54 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-4.paradise.net.nz (bm-4a.paradise.net.nz [203.96.152.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id E413243D6E for ; Mon, 6 Mar 2006 23:41:47 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-4.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IVQ0087TCHLSF@linda-4.paradise.net.nz> for freebsd-hardware@freebsd.org; Tue, 07 Mar 2006 12:41:45 +1300 (NZDT) Received: from [192.168.1.11] (218-101-29-158.dsl.clear.net.nz [218.101.29.158]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 6EB521AF49C for ; Tue, 07 Mar 2006 12:41:45 +1300 (NZDT) Date: Tue, 07 Mar 2006 12:41:43 +1300 From: Mark Kirkwood To: freebsd-hardware@freebsd.org Message-id: <440CC8B7.4090708@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) Subject: Add warning notes for known quirkly ata chipsets 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, 06 Mar 2006 23:41:54 -0000 Do folks think that amending the ata(4) man page, and adding warnings beside known quirky or broken chipsets is a good idea? I'm thinking of Si 3112 here in particular(!) - the aim being to discourage folks from buying 'em based on the fact they appear in ata(4). I'm happy to draft up something - altho I'd be pretty basic like: Silicon Image: SiI0680, SiI3112 (see NOTES), SiI3114, SiI3512. Notes: .... There have been reports of data corruption and erratic behavior with some chipsets. This seems to be related to deficiencies with the chipset design rather than the driver code. It is recommended to avoid these. A list of known problematic chipsets is: SiI3112,... I don't know any others offhand - but if a) the basic idea seems sensible and b) people mail me with well documented cases, I'd be happy to add 'em! Finally, I'm bringing this up now, as 6.1 is out soon, and it seemed a good time :-) regards Mark From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 7 02:24:35 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6548716A420 for ; Tue, 7 Mar 2006 02:24:35 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id E035143D46 for ; Tue, 7 Mar 2006 02:24:34 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IVQ00K7HK0XVV@linda-1.paradise.net.nz> for freebsd-hardware@freebsd.org; Tue, 07 Mar 2006 15:24:33 +1300 (NZDT) Received: from [192.168.1.11] (218-101-29-158.dsl.clear.net.nz [218.101.29.158]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id F04931478A37 for ; Tue, 07 Mar 2006 15:24:32 +1300 (NZDT) Date: Tue, 07 Mar 2006 15:24:30 +1300 From: Mark Kirkwood In-reply-to: <440CC8B7.4090708@paradise.net.nz> To: freebsd-hardware@freebsd.org Message-id: <440CEEDE.60809@paradise.net.nz> MIME-version: 1.0 Content-type: multipart/mixed; boundary=------------040102090200090609040804 X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <440CC8B7.4090708@paradise.net.nz> Subject: Re: Add warning notes for known quirkly ata chipsets 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, 07 Mar 2006 02:24:35 -0000 This is a multi-part message in MIME format. --------------040102090200090609040804 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mark Kirkwood wrote: > Do folks think that amending the ata(4) man page, and adding warnings > beside known quirky or broken chipsets is a good idea? I'm thinking of > Si 3112 here in particular(!) - the aim being to discourage folks from > buying 'em based on the fact they appear in ata(4). > > I'm happy to draft up something - altho I'd be pretty basic like: A tentative patch, adding a BUGS section instead of lumping it into NOTES (see attached). regards Mark --------------040102090200090609040804 Content-Type: text/plain; name="ata4.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ata4.patch" *** ata.4.orig Tue Mar 7 13:00:17 2006 --- ata.4 Tue Mar 7 15:21:12 2006 *************** *** 135,141 **** .It ServerWorks: ROSB4, CSB5, CSB6. .It Silicon Image: ! SiI0680, SiI3112, SiI3114, SiI3512. .It SiS: SIS180, SIS181, SIS182, SIS5513, SIS530, SIS540, SIS550, SIS620, SIS630, SIS630S, SIS633, SIS635, SIS730, SIS733, SIS735, SIS745, SIS961, SIS962, SIS963, SIS964, SIS965. .It VIA: --- 135,141 ---- .It ServerWorks: ROSB4, CSB5, CSB6. .It Silicon Image: ! SiI0680, SiI3112 (see BUGS), SiI3114, SiI3512. .It SiS: SIS180, SIS181, SIS182, SIS5513, SIS530, SIS540, SIS550, SIS620, SIS630, SIS630S, SIS633, SIS635, SIS730, SIS733, SIS735, SIS745, SIS961, SIS962, SIS963, SIS964, SIS965. .It VIA: *************** *** 216,221 **** --- 216,225 ---- This is useful in hotswap scenarios where disks should always show up as the same numbered device, and not depend on attach order. + .Sh BUGS + There have been reports of data corruption and erratic behavior with some + controllers which seem to be related to deficiencies with the chipset design + rather than the driver code. It is recommended to avoid these: SiI3112. .Sh SEE ALSO .Xr ataraid 4 , .Xr atacontrol 8 , --------------040102090200090609040804-- From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 7 05:54:16 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DA7D16A420 for ; Tue, 7 Mar 2006 05:54:16 +0000 (GMT) (envelope-from vvelox@vvelox.net) Received: from mail07.powweb.com (mail07.powweb.com [66.152.97.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F56543D46 for ; Tue, 7 Mar 2006 05:54:16 +0000 (GMT) (envelope-from vvelox@vvelox.net) Received: from vixen42.vulpes (24-119-205-114.cpe.cableone.net [24.119.205.114]) by mail07.powweb.com (Postfix) with ESMTP id 029A814DF7E for ; Mon, 6 Mar 2006 21:54:15 -0800 (PST) Date: Tue, 7 Mar 2006 00:04:51 -0600 From: "Z.C.B." To: freebsd-hardware@freebsd.org Message-ID: <20060307000451.3a07f9a8@vixen42.vulpes> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Suggestions on remote USB HID device. 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, 07 Mar 2006 05:54:16 -0000 Any one know of a plain old IR USB HID remotes that works nicely with FreeBSD? From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 7 06:38:31 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C785416A420 for ; Tue, 7 Mar 2006 06:38:31 +0000 (GMT) (envelope-from rossiya@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4503943D48 for ; Tue, 7 Mar 2006 06:38:29 +0000 (GMT) (envelope-from rossiya@gmail.com) Received: by nproxy.gmail.com with SMTP id b2so957613nfe for ; Mon, 06 Mar 2006 22:38:28 -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:references; b=N0i1gl3EURDQFUREJVmqGfgFa4UlPt/S4Zmm0vTq8o8Y8hUu2/BlormHuDlULvSdwdkB2L7x3HAt9k8cWQAEgzgH7i3inc+dLrCsB1TNjX98uzAna8fQTtN+YEAin2fmNvVCGgnPPbhl6v/oCWnJov/uvDvaXprdOLstUYDvu6s= Received: by 10.48.207.2 with SMTP id e2mr2807012nfg; Mon, 06 Mar 2006 22:38:27 -0800 (PST) Received: by 10.48.219.7 with HTTP; Mon, 6 Mar 2006 22:38:27 -0800 (PST) Message-ID: <28a99ba50603062238l4b66c51asd945eee95c22bb09@mail.gmail.com> Date: Mon, 6 Mar 2006 22:38:27 -0800 From: MC To: Z.C.B. In-Reply-To: <20060307000451.3a07f9a8@vixen42.vulpes> MIME-Version: 1.0 References: <20060307000451.3a07f9a8@vixen42.vulpes> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: Suggestions on remote USB HID device. 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, 07 Mar 2006 06:38:31 -0000 Have you taken a look at /usr/src/share/misc/pci_vendors or /usr/src/sys/dev/usb/ehci_pci.c ? Lots of stuff listed in there. It might give you ponters worthy of a googl= e or two On 3/6/06, Z.C.B. wrote: > > Any one know of a plain old IR USB HID remotes that works nicely with > FreeBSD? > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.or= g > " > From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 7 21:04:58 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E3AF16A423; Tue, 7 Mar 2006 21:04:58 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id E08BD43D45; Tue, 7 Mar 2006 21:04:55 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.4/8.13.4) with ESMTP id k27L4sc3029973; Tue, 7 Mar 2006 13:04:54 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.4/8.13.4/Submit) with UUCP id k27L4s0u029970; Tue, 7 Mar 2006 13:04:54 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id UAA16737; Tue, 7 Mar 2006 20:58:09 GMT Message-Id: <200603072058.UAA16737@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org Date: Tue, 07 Mar 2006 12:58:09 +0000 From: Dieter Cc: freebsd-amd64@freebsd.org Subject: Re: Add warning notes for known quirkly ata chipsets X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Mar 2006 21:04:58 -0000 > I don't know any others offhand Word is that nforce4 plus Maxtor or Hitachi disks gives data corruption. Nforce4 plus Seagate is said to be okay. http://forums.nvidia.com/lofiversion/index.php?t8171.html I have nforce4-ultra with 4 Seagate 7200.8 SATA drives and have not observed any data corruption. I have have copied many multi-GB files from one disk to another, and afterwards cmp(1) says they are identical. I picked the nforce4-ultra because the other AMD64 chipsets did not have NCQ. I have not had any problems with the nf4 chipset. (But then I don't have any Maxtor or Hitachi disks hooked to it.) On the other hand, I *have* seen data problems with a Maxtor PATA drive on NetBSD/alpha (not a nforce4 chipset, obviously). Read the same sector three times and get three different results. From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 8 01:31:31 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7199916A420 for ; Wed, 8 Mar 2006 01:31:31 +0000 (GMT) (envelope-from vvelox@vvelox.net) Received: from mail07.powweb.com (mail07.powweb.com [66.152.97.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E38C43D45 for ; Wed, 8 Mar 2006 01:31:31 +0000 (GMT) (envelope-from vvelox@vvelox.net) Received: from vixen42.vulpes (24-119-205-114.cpe.cableone.net [24.119.205.114]) by mail07.powweb.com (Postfix) with ESMTP id 0911114DE02; Tue, 7 Mar 2006 17:31:29 -0800 (PST) Date: Tue, 7 Mar 2006 19:42:16 -0600 From: "Z.C.B." To: MC Message-ID: <20060307194216.00e79dad@vixen42.vulpes> In-Reply-To: <28a99ba50603062238l4b66c51asd945eee95c22bb09@mail.gmail.com> References: <20060307000451.3a07f9a8@vixen42.vulpes> <28a99ba50603062238l4b66c51asd945eee95c22bb09@mail.gmail.com> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: Suggestions on remote USB HID device. 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, 08 Mar 2006 01:31:31 -0000 On Mon, 6 Mar 2006 22:38:27 -0800 MC wrote: > Have you taken a look at /usr/src/share/misc/pci_vendors or > /usr/src/sys/dev/usb/ehci_pci.c ? > Lots of stuff listed in there. It might give you ponters worthy of > a google or two I am not looking for a controller. I am looking for a UHID remote that does not have any oddities that would keep it from working with FreeBSD. > On 3/6/06, Z.C.B. wrote: > > > > Any one know of a plain old IR USB HID remotes that works nicely > > with FreeBSD? From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 8 12:48:51 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE1A616A420 for ; Wed, 8 Mar 2006 12:48:51 +0000 (GMT) (envelope-from psyzar@yahoo.co.uk) Received: from web25410.mail.ukl.yahoo.com (web25410.mail.ukl.yahoo.com [217.146.176.228]) by mx1.FreeBSD.org (Postfix) with SMTP id 83BC043D46 for ; Wed, 8 Mar 2006 12:48:46 +0000 (GMT) (envelope-from psyzar@yahoo.co.uk) Received: (qmail 22303 invoked by uid 60001); 8 Mar 2006 12:48:45 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RJHfcPdE4lkwVDlwayM4ZL68YgfoJAqd04GKf0A8CCBLvky92FKh5eSBQyD4e7H75tb9doi+4jjh4zgYQnIXtpkU0YPTG2Sr4yoWWh6belvCrpi+JLEV4gPJ8YxkbM9U/xYgkjF+4Nkc8UaJLe2m34sDFWZdVNl/EHpXSQ0phzU= ; Message-ID: <20060308124845.22301.qmail@web25410.mail.ukl.yahoo.com> Received: from [82.211.112.48] by web25410.mail.ukl.yahoo.com via HTTP; Wed, 08 Mar 2006 12:48:45 GMT Date: Wed, 8 Mar 2006 12:48:45 +0000 (GMT) From: F J To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: HP ProLiant DL320 G4 and FreeBSD 4.11/6.0 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, 08 Mar 2006 12:48:52 -0000 Hi I am trying to install FreeBSD onto a new HP DL320 G4 server. Neither version 4.11 nor 6.0 recognise the disks (SATA) which I believe is a driver issue. The controller is embedded Intel 82801GR SATA. I have disabled the raid option in the bios. I have also played with the "MPS Table Mode" settings, variously set to "Full Table APIC" and "Disabled" as had been suggested. During FreeBSD 6.0, escaping to the loader prompt, lsdev output shows disk0 (BIOS A), disk1 (BIOS C), disk2 (BIOS D). FreeBSD 6.0 boots to the system installation menus but does not recognise any disks so I cannot proceed beyond this point. Has anyone installed on these HP servers? Where can I get the correct drivers? Many thanks Francois ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 8 22:19:53 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7921D16A420 for ; Wed, 8 Mar 2006 22:19:53 +0000 (GMT) (envelope-from mdmadmin@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1614743D46 for ; Wed, 8 Mar 2006 22:19:52 +0000 (GMT) (envelope-from mdmadmin@gmail.com) Received: by xproxy.gmail.com with SMTP id r21so266403wxc for ; Wed, 08 Mar 2006 14:19:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gCXXfFsZCbEVvvpAsnNvZ3O/9Z7cd8srxjgRIn2LJNSgehDfi4x2rfax0Zg0QBFXgW524tueWqXYCuOg8xWyiErCEJC8wJRmQGivvI+zDeaddEVom1GRM5mKrwQjshEVbdz1l7uiQULyHcG2Uo9Sl21KdVHEavfLSaoZ670MYMk= Received: by 10.70.105.2 with SMTP id d2mr1457841wxc; Wed, 08 Mar 2006 14:19:51 -0800 (PST) Received: by 10.70.96.5 with HTTP; Wed, 8 Mar 2006 14:19:51 -0800 (PST) Message-ID: Date: Wed, 8 Mar 2006 23:19:51 +0100 From: "mdma admin" To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: IBM xSeries 205 Install Problems 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, 08 Mar 2006 22:19:53 -0000 I tried to install FreeBSD 4.5-RELEASE Productin (Legacy) on IBM eServer xSeries 205 with P4 2,4GHz HTT, 1G DDR RAM, SCSI HDD (IBM-ESXS - SCSI controller id 0) and SCSI CD (AIC-7892A - SCSI controller id 7) on Adaptec's controller. Both are detected by the OS when booting from CD. I'm able to make partitions with sysinstall as well. But I get following error message after I make partitions and choose what to install (after 1 minute of extracting/copying files). panic non-maskable interrupt service and system reboots. What's going on? I wont to know more about that error, what kind of error, etc. What can I do to fix it? Any suggestion, similar experience, idea? Cheers. Matija From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 05:38:09 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F19D216A420 for ; Thu, 9 Mar 2006 05:38:09 +0000 (GMT) (envelope-from admin@happyatjamos.com) Received: from smtp102.biz.mail.re2.yahoo.com (smtp102.biz.mail.re2.yahoo.com [68.142.229.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 7220343D46 for ; Thu, 9 Mar 2006 05:38:09 +0000 (GMT) (envelope-from admin@happyatjamos.com) Received: (qmail 32872 invoked from network); 9 Mar 2006 05:38:08 -0000 Received: from unknown (HELO ?192.168.11.4?) (admin@happyatjamos.com@61.208.236.55 with plain) by smtp102.biz.mail.re2.yahoo.com with SMTP; 9 Mar 2006 05:38:08 -0000 Message-ID: <440FBF9F.60009@happyatjamos.com> Date: Thu, 09 Mar 2006 14:39:43 +0900 From: "Jarrod @ HappyAtJamos" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Known issues with LAPLINK connection on plip0 ? 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: Thu, 09 Mar 2006 05:38:10 -0000 Hi All, Just wondering if anyone knows of any issues with setting up plip to network 2 PCs under FreeBSD 6.0?? I have 6.0 installed on two laptops, one old Toshiba 1GHz and one VERY old Fujitsu P133. I've followed the steps in the handbook regarding setting up plip0, and ifconfig reports the following: > plip0: flags=108851 mtu 1500 > inet 10.0.0.6 --> 10.0.0.5 netmask 0xff000000 Suggesting that as far as BSD is concerned, things are good. However, ping does not work. I also keep getting this message: > "lp0: Too many errors, Going off-line." on ttyv0. I've searched on Google and found a couple of people having the same issue but haven't found a solution. Can anyone offer any insight on what might be happening here? Thanks kindly! Jarrod. From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 07:38:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8241C16A420 for ; Thu, 9 Mar 2006 07:38:28 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECF1F43D70 for ; Thu, 9 Mar 2006 07:38:19 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd4mr2so.prod.shaw.ca (pd4mr2so-qfe3.prod.shaw.ca [10.0.141.213]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IVU0041FNVUHYA0@l-daemon> for freebsd-hardware@freebsd.org; Thu, 09 Mar 2006 00:38:18 -0700 (MST) Received: from pn2ml7so.prod.shaw.ca ([10.0.121.151]) by pd4mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IVU00E36NVUXPM0@pd4mr2so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Thu, 09 Mar 2006 00:38:18 -0700 (MST) Received: from soralx.cydem.org ([24.85.63.128]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IVU005C7NVUHQL0@l-daemon> for freebsd-hardware@freebsd.org; Thu, 09 Mar 2006 00:38:18 -0700 (MST) Date: Wed, 08 Mar 2006 23:38:02 -0800 From: soralx@cydem.org In-reply-to: <20060306084801.GA826@turion.vk2pj.dyndns.org> To: freebsd-hardware@freebsd.org Message-id: <200603082338.02237.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <1141517664.1407@swaggi.com> <200603052341.18723.soralx@cydem.org> <20060306084801.GA826@turion.vk2pj.dyndns.org> User-Agent: KMail/1.5.4 Cc: g_jin@lbl.gov, peterjeremy@optushome.com.au, me@carrollkong.com Subject: Re: FreeBSD shutting down unexpectedly 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: Thu, 09 Mar 2006 07:38:28 -0000 > >It cost me ~$30 to get all capacitors > 470uF for a socket478 mainboard > >and 2 ATX PSUs (I got high-quality, low ESR Nichicon UPL-series caps). > > Note that if you don't have the skills to replace the capacitors > yourself, you need to add the labour cost for a technician (which will > probably be somewhat more than the capacitors cost). Note that it's > crucial that any goo be completely cleaned off the MB - it will > destory the tracks if it's left. 2 all: This is an important point I forgot to mention. Desoldering the capacitors is actually much harder than it seems, even if you have a solder sucker (desoldering station), because the power layers conduct heat very well, and high temperature burns the laquer/dye layer easily. If you never soldered multi-layer (more than 2) boards before, do not do it yourself, if the mainboard is of any value to you. Practice first. I never destoyed a mainboard myself this way, but I was close a couple times, so I imagine how difficult would it be to an unexperienced person. > It's not only low quality components, it's also poor thermal design. > Heat is the major enemy of electrolytic capacitors. PSUs typically > have all the capacitors crammed (and even glued) together, minimising > cooling. My (GigaByte) MB has capacitors wedged between toroid > inductors (which get quite hot during operation) and squeezed under > the CPU heatsink. Rather, the poor design here lies in the fact that inductors are used which have high resistance (resistance to DC, not impedance) and low surface area; this get them quite hot, and also decreases efficiency of the voltage converter. > > Would you consider spending U$15 (cost > >of good capacitors) more on a $320 mainboard and get a reliable, stable > >(better overclocking, too) board that will serve you well for many years > >(istead of just 0.5 - 3y max)? > > Yes, but I don't have that choice. I can either buy consumer-grade > equipment (which is virtually all of similar quality) or I can > buy server-grade hardware - for several times as much. This is a problem indeed. In any case, this is getting off-topic now. Hopefully, this discussion succeeded in pointion out the quality problem that exists with current consumer-grade hardware, and suggested some ways to solve it (whether globally -- by 'boycotting' bad manufacturers, or locally -- by modifying already purchased hardware). The specific goal was to show that current power devices (power supplies, mainboard converters, etc) are of insufficient quality, and how quality is important in this area. Timestamp: 0x440FCE8F [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 12:25:25 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C22EB16A420 for ; Thu, 9 Mar 2006 12:25:25 +0000 (GMT) (envelope-from judmarc@fastmail.fm) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 579AB43D45 for ; Thu, 9 Mar 2006 12:25:24 +0000 (GMT) (envelope-from judmarc@fastmail.fm) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 63454D3AF7E for ; Thu, 9 Mar 2006 07:24:36 -0500 (EST) Received: from web3.messagingengine.com ([10.202.2.212]) by frontend1.internal (MEProxy); Thu, 09 Mar 2006 07:24:36 -0500 Received: by web3.messagingengine.com (Postfix, from userid 99) id BB284151DD; Thu, 9 Mar 2006 07:24:36 -0500 (EST) Message-Id: <1141907076.25030.256207540@webmail.messagingengine.com> X-Sasl-Enc: 376qPG3PI2uGpEjcAmP9Wr0a5O5nyeAaM3dDGc6+rtqc 1141907076 From: "Jud" To: freebsd-hardware@freebsd.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 5022 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Thu, 09 Mar 2006 07:24:36 -0500 Subject: Fwd: Promise TX2200/2300 SATA RAID Controllers - New Driver/BIOS Problem 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: Thu, 09 Mar 2006 12:25:25 -0000 -Hardware may be a more appropriate list for this followup; the original post was sent to -questions. On Tue, 07 Mar 2006 07:53:28 -0500, "Jud" said: > At the beginning of February, Promise released a new BIOS (version > 2.5.0.3115) for the TX2300 and a new Windows driver (version 2.06.0.311) > for the TX2200/2300. After installing the new BIOS and driver on my > TX2300, neither the BSDINSTALLER iso from early December nor a -CURRENT > installation iso from the end of January recognize my RAID-0 array; the > two drives are seen as ad4 and ad6 rather than ar0. Prior to installing > the new BIOS and driver, the BSDINSTALLER iso did recognize the array as > ar0. > > I'm attempting a reinstall because of an unfortunate concatenation of > two hardware problems. I tried to run glxgears on my Radeon 9500 > (R300), which caused the system to freeze. After a hardware reset, I > ran into the kern/91408 bug. > > I've backed up my Win system and plan to see tonight whether atacontrol > can create ar0 for me. If not, then for the time being I will likely > reflash the BIOS and change the Win driver back to the older versions. Catch-22: atacontrol works fine to create ar0 that can be used for FreeBSD purposes, but on bootup the Promise BIOS shows the array as "Initializing" rather than "Functional." Windows boots, though the Promise WebPAM utility shows array status as "3" (couldn't find the precise meaning of "3" in WebPAM's Help, on the Promise website, or by Googling), which I'm guessing may mean initializing, some degraded level of performance, or an indication of unknown status. Remaking the RAID-0 array so it shows as "Functional" in the new BIOS breaks ar0 in FreeBSD, and it's back to where we started. Looks like going back to the older BIOS and Win driver is currently the only option to create a RAID-0 array that "just works" in FreeBSD. Another oddity: The Promise BIOS allows a stripe size of 128kB, but after running "atacontrol create raid0 250 ad4 ad6," the BIOS shows a stripe size of 64kB (the default) on bootup. Jud From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 16:35:32 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFA6C16A420; Thu, 9 Mar 2006 16:35:32 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A46B543D48; Thu, 9 Mar 2006 16:35:32 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 4DA6A1A4D9B; Thu, 9 Mar 2006 08:35:32 -0800 (PST) Date: Thu, 9 Mar 2006 08:35:32 -0800 From: Alfred Perlstein To: re@freebsd.org, sos@freebsd.org, hardware@freebsd.org Message-ID: <20060309163532.GH23971@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: ATA problems with 5.5-PRERELEASE 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: Thu, 09 Mar 2006 16:35:33 -0000 Hello, we recently began deploying 5.5-PRERELEASE dated March 7th. Across all (7 so far) of our machines we're getting the following error: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=32176383 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15514623 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=34480383 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31408319 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15718783 On FreeBSD 5.4-stable from September we were fine. This is the ata hardware present: atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ad0: 38166MB [77545/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 >From mysql on one of the hosts: 060309 5:28:48 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:29:40 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:30:02 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:30:14 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:30:14 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:34:40 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' #define HA_ERR_RECORD_DELETED 134 /* Intern error-code */ Looks like we were getting corrupt data. Any hints? Can this be looked into please? -- - Alfred Perlstein - CTO Okcupid.com / FreeBSD Hacker / All that jazz - From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 16:45:03 2006 Return-Path: X-Original-To: hardware@FreeBSD.ORG Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C026A16A420; Thu, 9 Mar 2006 16:45:03 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C487743D5A; Thu, 9 Mar 2006 16:45:02 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k29Giw9Q066052; Thu, 9 Mar 2006 17:44:58 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <44105B8A.3050102@deepcore.dk> Date: Thu, 09 Mar 2006 17:44:58 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: Alfred Perlstein References: <20060309163532.GH23971@elvis.mu.org> In-Reply-To: <20060309163532.GH23971@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: re@FreeBSD.ORG, hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA problems with 5.5-PRERELEASE 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: Thu, 09 Mar 2006 16:45:03 -0000 Alfred Perlstein wrote: > Hello, we recently began deploying 5.5-PRERELEASE dated > March 7th. > > Across all (7 so far) of our machines we're getting the following error: > > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=32176383 > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15514623 > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=34480383 > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31408319 > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15718783 > > On FreeBSD 5.4-stable from September we were fine. > > This is the ata hardware present: > > atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x > 3f6,0x1f0-0x1f7 at device 31.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > ad0: 38166MB [77545/16/63] at ata0-master UDMA100 > acd0: CDROM at ata1-master PIO4 > >>From mysql on one of the hosts: > > 060309 5:28:48 [ERROR] Got error 134 when reading table './romatch/profile_acti > ve' > 060309 5:29:40 [ERROR] Got error 134 when reading table './romatch/profile_acti > ve' > 060309 5:30:02 [ERROR] Got error 134 when reading table './romatch/profile_acti > ve' > 060309 5:30:14 [ERROR] Got error 134 when reading table './romatch/profile_acti > ve' > 060309 5:30:14 [ERROR] Got error 134 when reading table './romatch/profile_acti > ve' > 060309 5:34:40 [ERROR] Got error 134 when reading table './romatch/profile_acti > ve' > > #define HA_ERR_RECORD_DELETED 134 /* Intern error-code */ > > Looks like we were getting corrupt data. > > Any hints? Not from this end, I havn't touched ATA in 5.x for well over a year. > Can this be looked into please? I wont be able to unless someone contracts me to do it, sorry but I have to prioritize my sparse spare time... -Søren From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 16:54:41 2006 Return-Path: X-Original-To: hardware@FreeBSD.ORG Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3224C16A420; Thu, 9 Mar 2006 16:54:41 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05A8143D48; Thu, 9 Mar 2006 16:54:40 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E4CF91A4D9A; Thu, 9 Mar 2006 08:54:40 -0800 (PST) Date: Thu, 9 Mar 2006 08:54:40 -0800 From: Alfred Perlstein To: S?ren Schmidt Message-ID: <20060309165440.GI23971@elvis.mu.org> References: <20060309163532.GH23971@elvis.mu.org> <44105B8A.3050102@deepcore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44105B8A.3050102@deepcore.dk> User-Agent: Mutt/1.4.2.1i Cc: re@FreeBSD.ORG, hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATA problems with 5.5-PRERELEASE 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: Thu, 09 Mar 2006 16:54:41 -0000 * S?ren Schmidt [060309 08:45] wrote: > Alfred Perlstein wrote: > >Hello, we recently began deploying 5.5-PRERELEASE dated > >March 7th. > > > >Across all (7 so far) of our machines we're getting the following error: > > > >ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=32176383 > >ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15514623 > >ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=34480383 > > > >Looks like we were getting corrupt data. > > > >Any hints? > > Not from this end, I havn't touched ATA in 5.x for well over a year. > > >Can this be looked into please? > > I wont be able to unless someone contracts me to do it, sorry but I have > to prioritize my sparse spare time... *sigh* I'll keep it mind when deploying from now on. I just think that maybe the 5.5 release notes might include a blurb like: "sorry we broke ata somewhere between 5.4 and 5.5, don't upgrade if you're using IDE hardware." Would that work? -- - Alfred Perlstein - CTO Okcupid.com / FreeBSD Hacker / All that jazz - From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 17:06:26 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2B7B16A420; Thu, 9 Mar 2006 17:06:26 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB2BA43D67; Thu, 9 Mar 2006 17:06:25 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k29H6NWo066359; Thu, 9 Mar 2006 18:06:23 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <4410608F.5030107@deepcore.dk> Date: Thu, 09 Mar 2006 18:06:23 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: Alfred Perlstein References: <20060309163532.GH23971@elvis.mu.org> <44105B8A.3050102@deepcore.dk> <20060309165440.GI23971@elvis.mu.org> In-Reply-To: <20060309165440.GI23971@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: re@freebsd.org, hardware@freebsd.org, sos@freebsd.org Subject: Re: ATA problems with 5.5-PRERELEASE 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: Thu, 09 Mar 2006 17:06:26 -0000 Alfred Perlstein wrote: > * S?ren Schmidt [060309 08:45] wrote: >> Alfred Perlstein wrote: >>> Hello, we recently began deploying 5.5-PRERELEASE dated >>> March 7th. >>> >>> Across all (7 so far) of our machines we're getting the following error: >>> >>> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=32176383 >>> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15514623 >>> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=34480383 >>> >>> Looks like we were getting corrupt data. >>> >>> Any hints? >> Not from this end, I havn't touched ATA in 5.x for well over a year. >> >>> Can this be looked into please? >> I wont be able to unless someone contracts me to do it, sorry but I have >> to prioritize my sparse spare time... > > *sigh* > > I'll keep it mind when deploying from now on. You *really* should use 6.x you know... > I just think that maybe the 5.5 release notes might include > a blurb like: > > "sorry we broke ata somewhere between 5.4 and 5.5, don't > upgrade if you're using IDE hardware." > > Would that work? Ask those that broke it, I havn't been in there since just before 5.3RELEASE and havn't followed what has been changed/added in there. -Søren From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 17:15:47 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0860416A420; Thu, 9 Mar 2006 17:15:47 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDDD843D46; Thu, 9 Mar 2006 17:15:46 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id BDABD1A4D95; Thu, 9 Mar 2006 09:15:46 -0800 (PST) Date: Thu, 9 Mar 2006 09:15:46 -0800 From: Alfred Perlstein To: S?ren Schmidt Message-ID: <20060309171546.GJ23971@elvis.mu.org> References: <20060309163532.GH23971@elvis.mu.org> <44105B8A.3050102@deepcore.dk> <20060309165440.GI23971@elvis.mu.org> <4410608F.5030107@deepcore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4410608F.5030107@deepcore.dk> User-Agent: Mutt/1.4.2.1i Cc: re@freebsd.org, hardware@freebsd.org, sos@freebsd.org Subject: Re: ATA problems with 5.5-PRERELEASE 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: Thu, 09 Mar 2006 17:15:47 -0000 * S?ren Schmidt [060309 09:06] wrote: > Alfred Perlstein wrote: > > > >*sigh* > > > >I'll keep it mind when deploying from now on. > > You *really* should use 6.x you know... Looking into it. > > >I just think that maybe the 5.5 release notes might include > >a blurb like: > > > >"sorry we broke ata somewhere between 5.4 and 5.5, don't > >upgrade if you're using IDE hardware." > > > >Would that work? > > Ask those that broke it, I havn't been in there since just before > 5.3RELEASE and havn't followed what has been changed/added in there. Odd. -- - Alfred Perlstein - CTO Okcupid.com / FreeBSD Hacker / All that jazz - From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 10 10:55:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7283416A420 for ; Fri, 10 Mar 2006 10:55:28 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-5.paradise.net.nz (bm-5a.paradise.net.nz [203.96.152.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0621243D46 for ; Fri, 10 Mar 2006 10:55:27 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-5.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IVW001KUROEWT@linda-5.paradise.net.nz> for freebsd-hardware@freebsd.org; Fri, 10 Mar 2006 23:55:26 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-105.dsl.clear.net.nz [218.101.28.105]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id E12E5FF8798; Fri, 10 Mar 2006 23:55:25 +1300 (NZDT) Date: Fri, 10 Mar 2006 23:55:24 +1300 From: Mark Kirkwood In-reply-to: <1141907076.25030.256207540@webmail.messagingengine.com> To: Jud Message-id: <44115B1C.3020703@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <1141907076.25030.256207540@webmail.messagingengine.com> Cc: freebsd-hardware@freebsd.org Subject: Re: Fwd: Promise TX2200/2300 SATA RAID Controllers - New Driver/BIOS Problem 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: Fri, 10 Mar 2006 10:55:28 -0000 Jud wrote: > Another oddity: The Promise BIOS allows a stripe size of 128kB, but > after running "atacontrol create raid0 250 ad4 ad6," the BIOS shows a > stripe size of 64kB (the default) on bootup. I think you need to do "atacontrol create raid0 256 ad4 ad6" (assuming "250" isn't a typo) - 250 is not a valid stripe size, so I guess the array firmware is falling back on the default of 128. Cheers Mark From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 10 12:00:33 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EAEB16A429 for ; Fri, 10 Mar 2006 12:00:33 +0000 (GMT) (envelope-from judmarc@fastmail.fm) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE94743D60 for ; Fri, 10 Mar 2006 12:00:16 +0000 (GMT) (envelope-from judmarc@fastmail.fm) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 66003D3B184; Fri, 10 Mar 2006 07:00:12 -0500 (EST) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend1.internal (MEProxy); Fri, 10 Mar 2006 07:00:12 -0500 Received: by frontend3.messagingengine.com (Postfix, from userid 99) id 5E0D2104; Fri, 10 Mar 2006 07:00:11 -0500 (EST) Message-Id: <1141992011.7658.256300397@webmail.messagingengine.com> X-Sasl-Enc: UdPrH5XcKNZQ48rLA8p1Q/HnA6R6L9WOxqRh4R2jTh3u 1141992011 From: "Jud" To: "Mark Kirkwood" Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 5022 (F2.72; T1.15; A1.62; B3.04; Q3.03) References: <1141907076.25030.256207540@webmail.messagingengine.com> <44115B1C.3020703@paradise.net.nz> In-Reply-To: <44115B1C.3020703@paradise.net.nz> Date: Fri, 10 Mar 2006 07:00:11 -0500 Cc: freebsd-hardware@freebsd.org Subject: Re: Fwd: Promise TX2200/2300 SATA RAID Controllers - New Driver/BIOS Problem 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: Fri, 10 Mar 2006 12:00:33 -0000 On Fri, 10 Mar 2006 23:55:24 +1300, "Mark Kirkwood" said: > Jud wrote: > > > Another oddity: The Promise BIOS allows a stripe size of 128kB, but > > after running "atacontrol create raid0 250 ad4 ad6," the BIOS shows a > > stripe size of 64kB (the default) on bootup. > > I think you need to do "atacontrol create raid0 256 ad4 ad6" (assuming > "250" isn't a typo) - 250 is not a valid stripe size, so I guess the > array firmware is falling back on the default of 128. Thanks, made the error (all too familiar in my case) of calculating 128,000 bytes = 128kB. Jud From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 11 01:42:44 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EEC916A41F for ; Sat, 11 Mar 2006 01:42:44 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ED8C43DA1 for ; Sat, 11 Mar 2006 01:42:37 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IVX000S8WQYFC@linda-1.paradise.net.nz> for hardware@freebsd.org; Sat, 11 Mar 2006 14:42:34 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-54.dsl.clear.net.nz [218.101.28.54]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 36B8911AEE03 for ; Sat, 11 Mar 2006 14:42:34 +1300 (NZDT) Date: Sat, 11 Mar 2006 14:42:31 +1300 From: Mark Kirkwood To: hardware@freebsd.org Message-id: <44122B07.5070104@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) Cc: Subject: 6.0-RELEASE /dev/pci still has config for uninstalled LAN card 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: Sat, 11 Mar 2006 01:42:44 -0000 I recently did a motherboard swap (removed VIA Apollo 133A board and added VIA Apollo 266 based one). The new board has its own LAN (Intel 82559), so I removed the PCI LAN card (VIA Rhine III based card). I noticed this in the boot up: vr0: port 0xc400-0xc4ff mem 0xf7101000-0xf71010ff irq 11 at device 18.0 on pci0 vr0: MII without any phy! device_attach: vr0 attach returned 6 And pciconf shows: # pciconf -lv .... vr0@pci0:18:0: class=0x020000 card=0x01021106 chip=0x30651106 rev=0x62 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6102 Rhine II PCI Fast Ethernet Controller' class = network subclass = ethernet However it really is not there: # ifconfig vr0 ifconfig: interface vr0 does not exist After swapping the boards, I checked 'reset config data' in the BIOS and everything else has worked great. Is there any way to tell (devfs I guess) to forget this device? Cheers Mark From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 11 01:56:38 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0CBE16A432 for ; Sat, 11 Mar 2006 01:56:37 +0000 (GMT) (envelope-from freebsd@rmnanetworks.com) Received: from rmnanetworks.com (S01060010b53d5228.ed.shawcable.net [68.149.208.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2740F4FC20 for ; Fri, 10 Mar 2006 23:41:09 +0000 (GMT) (envelope-from freebsd@rmnanetworks.com) Received: (qmail 16011 invoked by uid 89); 10 Mar 2006 23:39:46 -0000 Received: by simscan 1.1.0 ppid: 16004, pid: 16007, t: 0.8650s scanners: clamav: 0.87.1/m:34/d:1162 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.rmnanetworks.com X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=HTML_60_70,HTML_MESSAGE autolearn=no version=3.1.0 Received: from unknown (HELO rmnalaptop) (freebsd@rmnanetworks.com@68.149.208.209) by mail.rmnanetworks.com with (RC4-MD5 encrypted) SMTP; 10 Mar 2006 23:39:45 -0000 Message-ID: <006f01c6449b$eca9d2d0$076fa8c0@rmnalaptop> From: "Freesbie" To: Date: Fri, 10 Mar 2006 16:39:50 -0700 MIME-Version: 1.0 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 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: dge-530T 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: Sat, 11 Mar 2006 01:56:38 -0000 Hi, I am using FreeBSD6.0(6.0-RELEASE FreeBSD 6.0-RELEASE #1). I just bought = two dge-530T gigabyte ethernet cards and installed them in my computer. = I have sk compiled into my kernel, but on boot they are not recognized. = Is there any additional steps I need to take? My kernel config = file(PCI-Ethernet Portion) as well as pertaining snippet of dmesg are = below.=20 Thank you for your time in reading this message. Freesbie # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs! device miibus # MII bus support #device bfe # Broadcom BCM440x 10/100 Ethernet #device bge # Broadcom BCM570xx Gigabit Ethernet #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, = 82558) #device lge # Level 1 LXT1001 gigabit Ethernet #device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet = Networking #device pcn # AMD Am79C97x PCI 10/100(precedence = over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS = 7016 device sk # SysKonnect SK-984x & SK-982x gigabit = Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device ti # Alteon Networks Tigon I/II gigabit = Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vge # VIA VT612x gigabit Ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', = ``Cyclone'') Dmesg Snippet pcib1: at device 30.0 on pci0 pci1: on pcib1 pci1: at device 9.0 (no driver attached) pci1: at device 10.0 (no driver attached) pci1: at device 11.0 (no driver attached)