From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 01:12:33 2004 Return-Path: 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 D989816A4CE for ; Mon, 19 Apr 2004 01:12:33 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB80E43D53 for ; Mon, 19 Apr 2004 01:12:32 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i3J8CSXi059944 for ; Mon, 19 Apr 2004 12:12:30 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <001801c425e5$9f3a19a0$0c00a8c0@artem> From: "Artem Koutchine" To: Date: Mon, 19 Apr 2004 12:09:17 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 08:12:34 -0000 Hi! I am trying to install an escalde 7506-4LP into 32 PCI slot on Asustek P2B-DS motherboard with dual PIII 550Mhz CPUs. I have installed the card and inisialized RAID 5 array (3 drives). The in inserted the FreeBSD installed disk (5.2-RC2) and tried installing it. During kernel boot i see message like: twe0: <3ware Storage Controller> port 0xb800-0xb80f mem 0xe0000000-0xe07fff= ff,0xe0800000-0xe080000f irq 5 at device 11.0 on pci0 twe0: PCI parity error: Reseat card, move card or buggy device present. (this line is repeated many times). I have searched google and maillist archived and have found that other people have met this error message, but there is nowhere clear explanation why it is happening. Some people say it should be just ignored. Is it so? Please help, i need to get this box running this week. Regards, Artem Kuchin From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 03:03:56 2004 Return-Path: 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 430A516A512 for ; Mon, 19 Apr 2004 03:03:56 -0700 (PDT) Received: from myn.rcast.u-tokyo.ac.jp (spam002.ecc.u-tokyo.ac.jp [133.11.50.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 5078E43D60 for ; Mon, 19 Apr 2004 03:03:53 -0700 (PDT) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from gin.myn.rcast.u-tokyo.ac.jp ( [157.82.72.158]) by spam002.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.5) with ESMTP id for ; Mon, 19 Apr 2004 19:03:51 +0900 Date: Mon, 19 Apr 2004 19:03:44 +0900 Message-ID: From: Hiroharu Tamaru To: "Artem Koutchine" In-Reply-To: <001801c425e5$9f3a19a0$0c00a8c0@artem> References: <001801c425e5$9f3a19a0$0c00a8c0@artem> User-Agent: User-Agent: Wanderlust/2.10.0 (Venus) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-IP: 157.82.72.158 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 10:03:56 -0000 Hi, there. I got a few people asking me the same thing recently, so I'll reply you on the ML to keep it archived. At Mon, 19 Apr 2004 12:09:17 +0400, Artem Koutchine wrote: > I am trying to install an escalde 7506-4LP into 32 PCI slot > on Asustek P2B-DS motherboard with dual PIII 550Mhz > CPUs. I have installed the card and inisialized RAID 5 array > (3 drives). The in inserted the FreeBSD installed disk (5.2-RC2) > and tried installing it. During kernel boot i see message like: > > twe0: <3ware Storage Controller> port 0xb800-0xb80f mem 0xe0000000-0xe07fff= > ff,0xe0800000-0xe080000f irq 5 at device 11.0 on pci0 > twe0: PCI parity error: Reseat card, move card or buggy device present. > (this line is repeated many times). > > I have searched google and maillist archived and have found that other > people have met this error message, but there is nowhere clear explanation > why it is happening. Some people say it should be just ignored. Is it so? This is the original message I wrote back then: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware I couldn't confirm if it were safe to ignore the message or not, but I never had any trouble with it for the 1+ year that I ran the system. That includes mail alarting and rebuilding the array through the 3dmd utility. I use to run JBOD, mirroring and RAID5 on that card. After that, I upgraded the M/B to a P4 system (an ordinary 32-bit-PCI Intel 845 setup) and (naturally) I no longer have any warnings. The warning message was annoying and bloating the logs, so I simply patched the driver not to log that particular message, and instead just count it in a sysctl MIB. As far as I remember, the rate at which this counter counts was really stable for an uptime of more than one month. The patch is against 4-stable of those days, and is attached below for your reference. With this patch, do a 'sysctl hw.twe.twe_pe_discard=1' to shut the message up, and check 'sysctl hw.twe.twe_pe' to see how many PE counts you got. Hope it helps. Hiroharu Tamaru. diff -ru sys/dev/twe-/twe.c sys/dev/twe/twe.c --- sys/dev/twe-/twe.c Tue May 21 21:33:16 2002 +++ sys/dev/twe/twe.c Tue May 21 21:47:34 2002 @@ -38,6 +38,8 @@ #define TWE_DEFINE_TABLES #include +extern int twe_pe_discard; + /* * Command submission. */ @@ -1595,13 +1597,17 @@ if ((status_reg & TWE_STATUS_UNEXPECTED_BITS) != 0) { if (time_second > (lastwarn[1] + 5)) { + if (!(twe_pe_discard && (status_reg & TWE_STATUS_PCI_PARITY_ERROR))) { twe_printf(sc, "unexpected status bit(s) %b\n", status_reg & TWE_STATUS_UNEXPECTED_BITS, TWE_STATUS_BITS_DESCRIPTION); lastwarn[1] = time_second; + } } result = 1; if (status_reg & TWE_STATUS_PCI_PARITY_ERROR) { + if (!twe_pe_discard) { twe_printf(sc, "PCI parity error: Reseat card, move card or buggy device present."); + } twe_clear_pci_parity_error(sc); } if (status_reg & TWE_STATUS_PCI_ABORT) { diff -ru sys/dev/twe-/twe_freebsd.c sys/dev/twe/twe_freebsd.c --- sys/dev/twe-/twe_freebsd.c Tue May 21 21:33:16 2002 +++ sys/dev/twe/twe_freebsd.c Tue May 21 21:40:21 2002 @@ -45,6 +45,7 @@ #include #include +#include static devclass_t twe_devclass; @@ -58,6 +59,13 @@ #define TWED_BIO_OUT #endif +int twe_pe_discard = 0; +unsigned int twe_pe = 0; + +SYSCTL_NODE(_hw, OID_AUTO, twe, CTLFLAG_RW, 0, "Twe RAID Driver mgmt"); +SYSCTL_INT(_hw_twe, OID_AUTO, pe_discard, CTLFLAG_RW, &twe_pe_discard, 0, "no msg for parity error"); +SYSCTL_UINT(_hw_twe, OID_AUTO, pe, CTLFLAG_RD, &twe_pe, 0, "parity error count"); + /******************************************************************************** ******************************************************************************** Control device interface @@ -520,6 +528,7 @@ { TWE_CONTROL(sc, TWE_CONTROL_CLEAR_PARITY_ERROR); pci_write_config(sc->twe_dev, PCIR_STATUS, TWE_PCI_CLEAR_PARITY_ERROR, 2); + ++ twe_pe; } /******************************************************************************** From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 03:18:33 2004 Return-Path: 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 D020A16A4CE for ; Mon, 19 Apr 2004 03:18:33 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171ED43D5A for ; Mon, 19 Apr 2004 03:18:33 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i3JAIVXg061264; Mon, 19 Apr 2004 14:18:31 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <003c01c425f7$3a3d6b30$0c00a8c0@artem> From: "Artem Koutchine" To: "Hiroharu Tamaru" References: <001801c425e5$9f3a19a0$0c00a8c0@artem> Date: Mon, 19 Apr 2004 14:15:11 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 10:18:33 -0000 > > twe0: <3ware Storage Controller> port 0xb800-0xb80f mem 0xe0000000-0xe07fff= > > ff,0xe0800000-0xe080000f irq 5 at device 11.0 on pci0 > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > (this line is repeated many times). > This is the original message I wrote back then: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware > > I couldn't confirm if it were safe to ignore the message or > not, but I never had any trouble with it for the 1+ year > that I ran the system. That includes mail alarting and > rebuilding the array through the 3dmd utility. I use to run > JBOD, mirroring and RAID5 on that card. Thank you for replying. I just installed FreeBSD on that dual P2B-DS MB with 2 P3 550Mhz CPUs and run top. What i saw scred me. I saw 50% CPU LOAD on interupts. Nothing really was running, The system is just installed and it was my first login (as root). I thinj this 50% interupts load is somehow related to the error message. But this is just a guess. Is there any way to be make it sure? Artem From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 03:54:54 2004 Return-Path: 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 2623C16A4CE for ; Mon, 19 Apr 2004 03:54:54 -0700 (PDT) Received: from myn.rcast.u-tokyo.ac.jp (spam002.ecc.u-tokyo.ac.jp [133.11.50.195]) by mx1.FreeBSD.org (Postfix) with SMTP id C846643D5A for ; Mon, 19 Apr 2004 03:54:52 -0700 (PDT) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from gin.myn.rcast.u-tokyo.ac.jp ( [157.82.72.158]) by spam002.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.5) with ESMTP id for ; Mon, 19 Apr 2004 19:54:51 +0900 Date: Mon, 19 Apr 2004 19:54:50 +0900 Message-ID: From: Hiroharu Tamaru To: "Artem Koutchine" In-Reply-To: <003c01c425f7$3a3d6b30$0c00a8c0@artem> References: <001801c425e5$9f3a19a0$0c00a8c0@artem> <003c01c425f7$3a3d6b30$0c00a8c0@artem> User-Agent: User-Agent: Wanderlust/2.10.0 (Venus) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-IP: 157.82.72.158 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 10:54:54 -0000 At Mon, 19 Apr 2004 14:15:11 +0400, Artem Koutchine wrote: > > > > twe0: <3ware Storage Controller> port 0xb800-0xb80f mem 0xe0000000-0xe07fff= > > > ff,0xe0800000-0xe080000f irq 5 at device 11.0 on pci0 > > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > > (this line is repeated many times). > > This is the original message I wrote back then: > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware > > > > I couldn't confirm if it were safe to ignore the message or > > not, but I never had any trouble with it for the 1+ year > > that I ran the system. That includes mail alarting and > > rebuilding the array through the 3dmd utility. I use to run > > JBOD, mirroring and RAID5 on that card. > > Thank you for replying. I just installed FreeBSD on > that dual P2B-DS MB with 2 P3 550Mhz CPUs and > run top. What i saw scred me. I saw 50% CPU LOAD on > interupts. Nothing really was running, The system is just > installed and it was my first login (as root). I thinj this > 50% interupts load is somehow related to the error message. > But this is just a guess. Is there any way to be make it sure? I can't remember well, but PRINTING warnings could well had been the reason. Try my patch, and see if suppressing the printf's themselves could save the CPU. If not, well, it could be scheduler related, and you might want to try 4-stable instead. IIRC, my system was working without any noticable load while the logging was turned off (using my patch). I don't remember well about how loaded it was with the logging turned on. Oh, here I found a note I wrote back then. It reads: Updateing the BIOS changed this 'error' rate. On P2B-DS, The original BIOS with 4.5-PRELEASE kernel panic'ed. BIOS 1.13 beta 1 gave some 12 err/sec rate where as BIOS 1.13 beta 7 gave 0.9 err/sec. See if your BIOS is most recent as well. Hiroharu Tamaru From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 04:42:23 2004 Return-Path: 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 20FD316A4CE for ; Mon, 19 Apr 2004 04:42:23 -0700 (PDT) Received: from mail.creativenet.de (mail.creativenet.de [194.162.37.11]) by mx1.FreeBSD.org (Postfix) with SMTP id D336643D1D for ; Mon, 19 Apr 2004 04:42:21 -0700 (PDT) (envelope-from thorolf@grid.einherjar.de) Received: (qmail 11056 invoked by uid 1014); 19 Apr 2004 11:42:50 -0000 Received: from thorolf@grid.einherjar.de by 2-1ha-de by uid 1002 with qmail-scanner-1.20 (clamscan: 0.67. Clear:RC:1(194.162.37.1):. Processed in 0.065117 secs); 19 Apr 2004 11:42:50 -0000 Received: from unknown (HELO thorolf.host) (194.162.37.1) by mail.creativenet.de with SMTP; 19 Apr 2004 11:42:50 -0000 Date: Mon, 19 Apr 2004 13:42:20 +0200 (CEST) From: Thorolf X-X-Sender: thorolf@thorolf.host To: freebsd-hardware@freebsd.org Message-ID: <20040419133922.B585@thorolf.host> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Prism GT / Netgear WG511 (fwd) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 11:42:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello list, I have new Netgear WG511 pcmcia WLANcard, I have made ndis driver, but this card doesn't work. Did someone know, how can I bring this card to work? thorolf# uname -v FreeBSD 5.2-CURRENT #1: Sat Apr 17 14:52:32 CEST 2004 root@thorolf.host:/usr/src/sys/i386/compile/THoR # boot -v output pci1: driver added found-> vendor=0x1260, dev=0x3890, revid=0x01 bus=2, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0298, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 ndis0: mem 0x88000000-0x88001fff irq 11 at device 0.0 on cardbus0 ndis0: [GIANT-LOCKED] can't re-use a leaf (BusType)! ndis0: NDIS API version: 5.0 ndis0: bpf attached ndis0: Ethernet address: 00:09:5b:98:1e:bb ndis0: bpf attached ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps # ifconfig output before ifconfig up ndis0: flags=8802 mtu 1500 ether 00:09:5b:98:1e:bb media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel -1 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 # ifconfig ndis0 up # dmesg output ndis0: set mclist failed: 6 ndis0: set filter failed: 6 ndis0: set mclist failed: 6 ndis0: set filter failed: 6 ndis0: set mclist failed: 6 ndis0: set filter failed: 6 ndis0: couldn't retrieve channel info: 28 thorolf# ifconfig ndis0 channel 10 ssid "my_net" ndis0: flags=8843 mtu 1500 inet6 fe80::209:5bff:fe98:1ebb%ndis0 prefixlen 64 scopeid 0x4 ether 00:09:5b:98:1e:bb media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel 10 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 # sysctl -a | grep ndis hw.ndis0.PlatformID: 0 hw.ndis0.VendorDesc: NETGEAR WG511 54 Mbps Wireless PC Card hw.ndis0.FWFileName: WG511DCB.arm hw.ndis0.BusType: 5 hw.ndis0.DeviceVxDs: WG511ICB.sys hw.ndis0.CardBusBridgeLatencyTimer: 32 hw.ndis0.CardBusBridgeCacheLineSize: 8 hw.ndis0.PRISMIOC: 1 hw.ndis0.SilentInstall: 1 hw.ndis0.SSID: NETGEAR hw.ndis0.DefaultSSID: NETGEAR hw.ndis0.LanExpress: IL00 hw.ndis0.11dMode: 0 hw.ndis0.Band: 1 hw.ndis0.BandPreference: 0 hw.ndis0.CountryCode: GB hw.ndis0.DSFreq: 2457000 hw.ndis0.RTSThresh: 2347 hw.ndis0.FragThresh: 2346 hw.ndis0.PSMode: 1 hw.ndis0.ShortRetryLimit: 7 hw.ndis0.LongRetryLimit: 4 hw.ndis0.ConfigProfile: 1 hw.ndis0.NitroMode: 1 hw.ndis0.Environment: 1 hw.ndis0.NdisVersion: 0x00050001 hw.ndis0.InterruptNumber: 11 hw.ndis0.NumCoalesce: UNSET hw.ndis0.NumTcb: UNSET hw.ndis0.PciCacheLineSize: UNSET hw.ndis0.PciLatencyTimer: UNSET hw.ndis0.NumMgmtBuffers: UNSET hw.ndis0.NetworkType: UNSET hw.ndis0.WepReq: UNSET hw.ndis0.DefaultKeyId: UNSET hw.ndis0.RunningWin9X: UNSET hw.ndis0.DataRate: UNSET hw.ndis0.activeScan: UNSET hw.ndis0.ignoreFilterError: UNSET hw.ndis0.EnableRadio: UNSET hw.ndis0.LongPreamble: UNSET hw.ndis0.NonERPMode: UNSET hw.ndis0.LongSlot: UNSET hw.ndis0.SoftReset: UNSET hw.ndis0.NitroTime: UNSET hw.ndis0.DefaultKeys: UNSET hw.ndis0.EsarHpsSap: UNSET hw.ndis0.ProfileID: UNSET hw.ndis0.DomainCode: UNSET thorolf# head /sys/modules/if_ndis/ndis_driver_data.h /* * Generated from /tmp/Driver/NETWG511.inf and /tmp/Driver/WG511ICB.sys (57786 bytes) */ thorolf# wicontrol -i ndis0 -L NIC serial number: [ ] Station name: [ thorolf.host ] SSID for IBSS creation: [ my_net ] Current netname (SSID): [ ] Desired netname (SSID): [ my_net ] Current BSSID: [ 00:00:00:00:00:00 ] Channel list: [ ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff 3fff ] IBSS channel: [ 10 ] Current channel: [ 10 ] Comms quality/signal/noise: [ 0 0 0 ] Promiscuous mode: [ Off ] Intersil-Prism2 based card: [ 1 ] Port type (1=BSS, 3=ad-hoc): [ 1 ] MAC address: [ 00:09:5b:98:1e:bb ] TX rate (selection): [ 0 ] TX rate (actual speed): [ 0 ] RTS/CTS handshake threshold: [ 2312 ] Create IBSS: [ Off ] Access point density: [ 1 ] Power Mgmt (1=on, 0=off): [ 0 ] Max sleep time: [ 100 ] WEP encryption: [ Off ] TX encryption key: [ 1 ] Encryption keys: [ ][ ][ ][ ] Available APs: Regards, Rafal Lesniak PS. sorry for my poor english ;-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iQCVAwUBQIO7H+2ijGMJcqkLAQJCBQQAib+UFvePwAY/QMLCP8Fp9v3smtb5xUwX zimaK3U+8tg+7rPyOilf48DmApXVfV63vVLX7j5X+QFTsL0nW0FuTAXStcdmWiBn ZfBYmyuYrsXC71QML7OsOpJdJdlPyqfJ6Ll3PoHJcCL447TJE0Kf0PqVi6k7ss6u WAYeqNo1Fxs= =INIX -----END PGP SIGNATURE----- From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 05:50:14 2004 Return-Path: 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 E4BD516A4CF for ; Mon, 19 Apr 2004 05:50:14 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BD9443D53 for ; Mon, 19 Apr 2004 05:50:14 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i3JCo8Xg063225; Mon, 19 Apr 2004 16:50:12 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <00c201c4260c$6acf2580$0c00a8c0@artem> From: "Artem Koutchine" To: "Hiroharu Tamaru" References: <001801c425e5$9f3a19a0$0c00a8c0@artem><003c01c425f7$3a3d6b30$0c00a8c0@artem> Date: Mon, 19 Apr 2004 16:46:59 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 12:50:15 -0000 > > > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > > > (this line is repeated many times). > > > This is the original message I wrote back then: > > > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware > > > > > > I couldn't confirm if it were safe to ignore the message or > > > not, but I never had any trouble with it for the 1+ year > > > that I ran the system. That includes mail alarting and > > > rebuilding the array through the 3dmd utility. I use to run > > > JBOD, mirroring and RAID5 on that card. > > > > Thank you for replying. I just installed FreeBSD on > > that dual P2B-DS MB with 2 P3 550Mhz CPUs and > > run top. What i saw scred me. I saw 50% CPU LOAD on > > interupts. Nothing really was running, The system is just > > installed and it was my first login (as root). I thinj this > > 50% interupts load is somehow related to the error message. > > But this is just a guess. Is there any way to be make it sure? > > I can't remember well, but PRINTING warnings could well had > been the reason. Try my patch, and see if suppressing the > printf's themselves could save the CPU. If not, well, it > could be scheduler related, and you might want to try > 4-stable instead. Did the patch. The message are gone now. However, i still have about 50% of cpu power wasted on interupts and i have not idea what is going on and how to figure out what is geenrated so many interupts and why. Maybe i should first do CVSup to 5-CURRENT (i am running 5.2-RC2). Please, someone comment on this. Best regards, Artem From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 09:33:13 2004 Return-Path: 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 02E2316A4CE for ; Mon, 19 Apr 2004 09:33:13 -0700 (PDT) Received: from myn.rcast.u-tokyo.ac.jp (spam003.ecc.u-tokyo.ac.jp [133.11.50.196]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F42B43D4C for ; Mon, 19 Apr 2004 09:33:07 -0700 (PDT) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from md002.ecc.u-tokyo.ac.jp ( [133.11.50.202]) by spam003.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.5) with ESMTP id for ; Tue, 20 Apr 2004 01:33:05 +0900 Received: from amulet.amuletic.net (YahooBB219001110002.bbtec.net [219.1.110.2]) by md002.ecc.u-tokyo.ac.jp (MOS 3.4.5-GR) with ESMTP id ACP48898 (AUTH via LOGINBEFORESMTP); Tue, 20 Apr 2004 01:33:04 +0900 (JST) Date: Tue, 20 Apr 2004 01:32:50 +0900 Message-ID: From: Hiroharu Tamaru To: "Artem Koutchine" In-Reply-To: <00c201c4260c$6acf2580$0c00a8c0@artem> References: <001801c425e5$9f3a19a0$0c00a8c0@artem> <003c01c425f7$3a3d6b30$0c00a8c0@artem> <00c201c4260c$6acf2580$0c00a8c0@artem> User-Agent: User-Agent: Wanderlust/2.10.0 (Venus) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-IP: 133.11.50.202 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 16:33:13 -0000 At Mon, 19 Apr 2004 16:46:59 +0400, Artem Koutchine wrote: > > > > > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > > > > (this line is repeated many times). > > > > This is the original message I wrote back then: > > > > > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware > > > > > > > > I couldn't confirm if it were safe to ignore the message or > > > > not, but I never had any trouble with it for the 1+ year > > > > that I ran the system. That includes mail alarting and > > > > rebuilding the array through the 3dmd utility. I use to run > > > > JBOD, mirroring and RAID5 on that card. > > > > > > Thank you for replying. I just installed FreeBSD on > > > that dual P2B-DS MB with 2 P3 550Mhz CPUs and > > > run top. What i saw scred me. I saw 50% CPU LOAD on > > > interupts. Nothing really was running, The system is just > > > installed and it was my first login (as root). I thinj this > > > 50% interupts load is somehow related to the error message. > > > But this is just a guess. Is there any way to be make it sure? > > > > I can't remember well, but PRINTING warnings could well had > > been the reason. Try my patch, and see if suppressing the > > printf's themselves could save the CPU. If not, well, it > > could be scheduler related, and you might want to try > > 4-stable instead. > > Did the patch. The message are gone now. However, i still have > about 50% of cpu power wasted on interupts and i have not idea > what is going on and how to figure out what is geenrated so many > interupts and why. Maybe i should first do CVSup to 5-CURRENT > (i am running 5.2-RC2). > And which BIOS version have you? I'd try differrent BIOS versions before cvsup'ing, since BIOS did change the interrupt rates in my case. Have a look at the counter and see how fast you are getting the PE interrupts. sysctl hw.twe.twe_pe ; sleep 10 ; sysctl hw.twe.twe_pe Then flash some other BIOS (maybe the latest one :) ), and see if the rates change. Since, in my case, it was 20/sec -> 0.9/sec, that certainly would give you more CPU cycles to spare... -- Hiroharu Tamaru From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 09:41:49 2004 Return-Path: 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 695B616A4CE for ; Mon, 19 Apr 2004 09:41:49 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8137143D49 for ; Mon, 19 Apr 2004 09:41:48 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i3JGfkXg066032; Mon, 19 Apr 2004 20:41:46 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <014501c4262c$c4535a70$0c00a8c0@artem> From: "Artem Koutchine" To: "Hiroharu Tamaru" References: <001801c425e5$9f3a19a0$0c00a8c0@artem><003c01c425f7$3a3d6b30$0c00a8c0@artem><00c201c4260c$6acf2580$0c00a8c0@artem> Date: Mon, 19 Apr 2004 20:38:35 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 16:41:49 -0000 > > > > > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > > > > > (this line is repeated many times). > > > > > This is the original message I wrote back then: > > > > > > > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware > > > > > > > > > > I couldn't confirm if it were safe to ignore the message or > > > > > not, but I never had any trouble with it for the 1+ year > > > > > that I ran the system. That includes mail alarting and > > > > > rebuilding the array through the 3dmd utility. I use to run > > > > > JBOD, mirroring and RAID5 on that card. > > > > > > > > Thank you for replying. I just installed FreeBSD on > > > > that dual P2B-DS MB with 2 P3 550Mhz CPUs and > > > > run top. What i saw scred me. I saw 50% CPU LOAD on > > > > interupts. Nothing really was running, The system is just > > > > installed and it was my first login (as root). I thinj this > > > > 50% interupts load is somehow related to the error message. > > > > But this is just a guess. Is there any way to be make it sure? > > > > > > I can't remember well, but PRINTING warnings could well had > > > been the reason. Try my patch, and see if suppressing the > > > printf's themselves could save the CPU. If not, well, it > > > could be scheduler related, and you might want to try > > > 4-stable instead. > > > > Did the patch. The message are gone now. However, i still have > > about 50% of cpu power wasted on interupts and i have not idea > > what is going on and how to figure out what is geenrated so many > > interupts and why. Maybe i should first do CVSup to 5-CURRENT > > (i am running 5.2-RC2). > > > > And which BIOS version have you? > I'd try differrent BIOS versions before cvsup'ing, > since BIOS did change the interrupt rates in my case. > > Have a look at the counter and see how fast you are > getting the PE interrupts. > > sysctl hw.twe.twe_pe ; sleep 10 ; sysctl hw.twe.twe_pe > > Then flash some other BIOS (maybe the latest one :) ), and > see if the rates change. Since, in my case, it was 20/sec > -> 0.9/sec, that certainly would give you more CPU cycles > to spare... I am using the latest BIOS which i could get from www.asus.com.tw (version 1013). The rate is actyally well below 20/sec. I think (i didn't measure) it is about 3 to 5 errors per second. But error rate and interupts rate are different things and it may or maynot be related. Artem From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 10:05:38 2004 Return-Path: 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 27DCC16A4CE for ; Mon, 19 Apr 2004 10:05:38 -0700 (PDT) Received: from mwinf0401.wanadoo.fr (smtp4.wanadoo.fr [193.252.22.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B943343D46 for ; Mon, 19 Apr 2004 10:05:37 -0700 (PDT) (envelope-from solo1607@postmark.net) Received: from postmark.net (ARouen-106-1-4-206.w217-128.abo.wanadoo.fr [217.128.253.206]) by mwinf0401.wanadoo.fr (SMTP Server) with ESMTP id 31FA9580069F for ; Mon, 19 Apr 2004 19:05:34 +0200 (CEST) Message-ID: <408406E2.90409@postmark.net> Date: Mon, 19 Apr 2004 19:05:38 +0200 From: solo1607 User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Philips KEYRING 007 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 17:05:38 -0000 Hi I'm running FreeBSD 4.9 and I can't make work my Philips KEYRING 007. It's a tiny digital camera, connecting as USB mass storage. When I connect it, it's not attached to daX device. All I get is : umass0: Philips KEYRING 007, rev 1.10/1.00, addr 2 My other USB key and my MMC drive are attached to da0, and they have the same version string "rev 1.10/1.00, addr 2". Anyone knows if that device is supported at all under FreeBSD, and if so, in which release ? Thank you. From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 13:25:36 2004 Return-Path: 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 C9A4F16A4CE for ; Mon, 19 Apr 2004 13:25:36 -0700 (PDT) Received: from web61309.mail.yahoo.com (web61309.mail.yahoo.com [216.155.196.152]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E21D43D66 for ; Mon, 19 Apr 2004 13:25:36 -0700 (PDT) (envelope-from richard_bejtlich@yahoo.com) Message-ID: <20040419202516.45433.qmail@web61309.mail.yahoo.com> Received: from [208.235.153.34] by web61309.mail.yahoo.com via HTTP; Mon, 19 Apr 2004 13:25:16 PDT Date: Mon, 19 Apr 2004 13:25:16 -0700 (PDT) From: Richard Bejtlich To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: FreeBSD with SATA on Dell PowerEdge 750 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 20:25:36 -0000 Hello, Is anyone using FreeBSD 5.x on the Dell PowerEdge 750 with SATA? I saw the earlier thread about a PE 750 with SCSI controller.[0] I'm considering the same box, except with the onboard SATA for non-RAID applications. The PE 750 is reported to have an Intel 7210 chipset.[1] This seems to be paired with the Intel 6300ESB I/O controller.[2] I just noticed mail on freebsd-current discussing this very device.[3] A quick check of the CVS tree shows recent mention of this device in places like src/sys/dev/ata/ata-chipset.c.[4] Can anyone report their findings with this hardware? Thank you, Richard http://www.taosecurity.com [0] http://lists.freebsd.org/mailman/htdig/freebsd-hardware/2004-April/001456.html [1] http://www.dell.com/downloads/global/products/pedge/en/750_specs.pdf [2] http://www.intel.com/design/chipsets/E7210/ [3] http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025032.html [4] http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/ata/ata-chipset.c?rev=1.68&content-type=text/plain __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 15:58:06 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id AD12B16A4CF; Mon, 19 Apr 2004 15:58:06 -0700 (PDT) In-Reply-To: <20040419133922.B585@thorolf.host> from Thorolf at "Apr 19, 2004 01:42:20 pm" To: thorolf@grid.einherjar.de (Thorolf) Date: Mon, 19 Apr 2004 15:58:06 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040419225806.AD12B16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-hardware@freebsd.org Subject: Re: Prism GT / Netgear WG511 (fwd) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 22:58:06 -0000 >Hello list, >I have new Netgear WG511 pcmcia WLANcard, >I have made ndis driver, but this card doesn't work. >Did someone know, how can I bring this card to work? [...] >thorolf# ifconfig ndis0 channel 10 ssid "my_net" Ok, stop right there. You have failed to provide important information in your post. Please listen carefully: you can have either a BSS network (with an access point) or an ad-hoc network (bunch of computers talking in a stand alone cell). You did not specify what kind of net you are trying to use, and it is impossible for anyone to just guess. Next time you ask a question, remember that little things which you think are basic have a big impact on your problems, and you make life hard for people when you don't bother to mention them. Setting the channel for a BSS network has no meaning. It only matters for ad-hoc networks. If you are trying to connect to an access point, DO NOT TRY FIDDLING WITH THE CHANNEL SETTING. Just leave it alone. For a BSS network (with an access point), do the following: # ifconfig ndis0 ssid "my_net" media autoselect For an ad-hoc network (bunch of computers in stand-alone cell): # ifconfig ndis0 ssid "my_net" mediaopt adhoc Only set the channel for ad-hoc if the default channel setting does not work: # ifconfig ndis0 ssid "my_net" mediaopt adhoc channel 10 You should also scan for nearby networks to make sure the net you want to connect to is in range: # ifconfig ndis0 up # wicontrol -i ndis0 -l If the SSID scan shows you a list of nets, then the driver is working correctly. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 16:15:59 2004 Return-Path: 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 8446116A4CE; Mon, 19 Apr 2004 16:15:59 -0700 (PDT) Received: from wsip-24-234-162-196.lv.lv.cox.net (wsip-24-234-162-196.lv.lv.cox.net [24.234.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0382D43D41; Mon, 19 Apr 2004 16:15:57 -0700 (PDT) (envelope-from mjpelletier@mjpelletier.com) Received: from pc1 (wsip-24-234-216-141.lv.lv.cox.net [24.234.216.141]) (authenticated bits=0)i3JNQhZS001178 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 19 Apr 2004 16:26:44 -0700 (PDT) (envelope-from mjpelletier@mjpelletier.com) Message-ID: <013801c42665$3d06ba60$8dd8ea18@pc1> From: "Michael J. Pelletier" To: "Thorolf" , "Bill Paul" References: <20040419225806.AD12B16A4CF@hub.freebsd.org> Date: Mon, 19 Apr 2004 16:22:52 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Scanned-By: MIMEDefang 2.40 cc: freebsd-hardware@freebsd.org Subject: Best wireless gear? Any suggestins? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 23:15:59 -0000 I have a quick question for you guys. I am thinking about a wireless solution. I do not need a wireless router really more of a wireless bridge setup. I will need to connect a laptop on the wireless network work as well a another wireless bridge (muliple rj45 ports on the wireless bridge). My environment is as follows 1 FreeBSD firewall (4.9) with three interfaces 1st interface goes to the cable modem (ISP access and firewalled) 2nd interface goes to a bunch of Winblows Servers (2000 mostly) and FreeBSD servers 3rd interface will be for the wireless network. This is the interface that will connect to the wireless bridge. On the wireless network, I will need a wireless bridge that has muliple rj45 interfaces (for my XBOX) and a seperate PCMCIA card for a laptop... Any thought about the best wireless gear for this and FreeBSD? Michael ----- Original Message ----- From: "Bill Paul" To: "Thorolf" Cc: Sent: Monday, April 19, 2004 3:58 PM Subject: Re: Prism GT / Netgear WG511 (fwd) > > > >Hello list, > > >I have new Netgear WG511 pcmcia WLANcard, > >I have made ndis driver, but this card doesn't work. > >Did someone know, how can I bring this card to work? > > [...] > > >thorolf# ifconfig ndis0 channel 10 ssid "my_net" > > Ok, stop right there. You have failed to provide important information > in your post. Please listen carefully: you can have either a BSS > network (with an access point) or an ad-hoc network (bunch of computers > talking in a stand alone cell). You did not specify what kind of net > you are trying to use, and it is impossible for anyone to just guess. > Next time you ask a question, remember that little things which you > think are basic have a big impact on your problems, and you make life > hard for people when you don't bother to mention them. > > Setting the channel for a BSS network has no meaning. It only matters > for ad-hoc networks. If you are trying to connect to an access point, > DO NOT TRY FIDDLING WITH THE CHANNEL SETTING. Just leave it alone. > > For a BSS network (with an access point), do the following: > > # ifconfig ndis0 ssid "my_net" media autoselect > > For an ad-hoc network (bunch of computers in stand-alone cell): > > # ifconfig ndis0 ssid "my_net" mediaopt adhoc > > Only set the channel for ad-hoc if the default channel setting does > not work: > > # ifconfig ndis0 ssid "my_net" mediaopt adhoc channel 10 > > You should also scan for nearby networks to make sure the net you want > to connect to is in range: > > # ifconfig ndis0 up > # wicontrol -i ndis0 -l > > If the SSID scan shows you a list of nets, then the driver is > working correctly. > > -Bill > > -- > ============================================================================ = > -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > wpaul@windriver.com | Wind River Systems > ============================================================================ = > you're just BEGGING to face the moose > ============================================================================ = > _______________________________________________ > 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 Apr 19 16:24:06 2004 Return-Path: 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 B889416A4CE for ; Mon, 19 Apr 2004 16:24:06 -0700 (PDT) Received: from pr93.lublin.sdi.tpnet.pl (pr93.lublin.sdi.tpnet.pl [217.97.36.93]) by mx1.FreeBSD.org (Postfix) with SMTP id 44F1A43D2F for ; Mon, 19 Apr 2004 16:24:05 -0700 (PDT) (envelope-from michal@pasternak.w.lub.pl) Received: (qmail 51055 invoked by uid 1001); 19 Apr 2004 23:24:04 -0000 Date: Tue, 20 Apr 2004 01:24:04 +0200 From: Michal Pasternak To: freebsd-hardware@freebsd.org Message-ID: <20040419232404.GA50973@pasternak.w.lub.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Subject: Software RAID 0 with IDE HDs on 5.2.1 workstation - should I? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Michal Pasternak List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 23:24:06 -0000 Hello, in my workstation I happen to have: ad0: 76319MB [155061/16/63] at ata0-master UDMA100 that's an IDE 80GB Caviar (7200 rpm, 8 MB cache). As the HD is pretty cheap, I've started to wonder if buying another one to setup RAID-0 stripe would be any sense. What do you think? Mobo is ASUS A7V600 (with VIA 8237 UDMA 133 controller); I generally use this box to do some development (which includes building sometimes large quantities of packages from source); I really appreciate comments from users FreeBSD, that tried similar configurations (raid-0 on ide). Take care, -- mp From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 20 02:59:26 2004 Return-Path: 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 9B85616A4CE for ; Tue, 20 Apr 2004 02:59:26 -0700 (PDT) Received: from mwinf0903.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDC3543D31 for ; Tue, 20 Apr 2004 02:59:25 -0700 (PDT) (envelope-from solo1607@postmark.net) Received: from postmark.net (ARouen-106-1-4-206.w217-128.abo.wanadoo.fr [217.128.253.206]) by mwinf0903.wanadoo.fr (SMTP Server) with ESMTP id 4DFAF180059B; Tue, 20 Apr 2004 11:59:24 +0200 (CEST) Message-ID: <4084F481.6070001@postmark.net> Date: Tue, 20 Apr 2004 11:59:29 +0200 From: solo1607 User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "John L.Utz III" References: <408406E2.90409@postmark.net> <86llkr2srp.wl%john@utzweb.net> In-Reply-To: <86llkr2srp.wl%john@utzweb.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Philips KEYRING 007 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2004 09:59:26 -0000 John L.Utz III wrote: > Hi, > > At Mon, 19 Apr 2004 19:05:38 +0200, > solo1607 wrote: > >>Hi >> >>I'm running FreeBSD 4.9 and I can't make work my Philips KEYRING 007. >>It's a tiny digital camera, connecting as USB mass storage. > > > I have a Logitech Pocket Digital, which oem's SMaL's camera platform. > > >>When I connect it, it's not attached to daX device. All I get is : >>umass0: Philips KEYRING 007, rev 1.10/1.00, addr 2 > > >>My other USB key and my MMC drive are attached to da0, and they have the >>same version string "rev 1.10/1.00, addr 2". Anyone knows if that device >>is supported at all under FreeBSD, and if so, in which release ? > > > if it shows up as a umass, cant you just mount it, something like > > mount /mnt /dev/umass0 ? > > >>Thank you. > > > HTH > > johnu > umass0 is not a device in /dev, it's just the USB kernel layer, configurable through camcontrol. To be mounted it needs to be attached to another device : /dev/daX. da privodes Direct Access disks support, also used for SCSI disks. When i try things like camcontrol rescan 0 or camcontrol rescan 0:0:0 when my camera is plugged in, it just freezes the kernel. Once my computer even rebooted by itself as if I had pressed the reset button ! > At least you see yours as a umass! > > How did you get that far? All i get is ugen :-( > > ugen0: SMaL Pocket Digital Camera, rev 1.10/0.00, addr 2 My camera is supposed to connect as USB mass storage. It works well under Windows... For most digital cameras, you need a special driver, but i can't help you, i never tried to configure one. solo From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 20 06:34:46 2004 Return-Path: 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 37AEF16A4CE for ; Tue, 20 Apr 2004 06:34:46 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 023E543D58 for ; Tue, 20 Apr 2004 06:34:45 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i3KDYfXi073387 for ; Tue, 20 Apr 2004 17:34:42 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <010501c426db$cc281a10$0c00a8c0@artem> From: "Artem Koutchine" To: Date: Tue, 20 Apr 2004 17:31:29 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: ACPI floods CPUs with interrupts X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2004 13:34:46 -0000 I have installed FreeBSd 5.2-RC2 on ASUS P2B-DS with 3ware raid controller and DUAL PIII (slot2) 550Mhz. Updated motherboard bios to the latest bios and after patching the twe driver, so it does not show the "PCI parity erro" several times a second. (I think it is related to the fact that 3ware 7506 controller is pci 2.2 while p2b is pci 2.1). After that i did top and saw that 50% of cpu power is wasted on interrupts. I did sysstat and :vmstat. It showed that 46700 interrupts per second were generated by acpi on irq 20. So, i booted without acpi and got 100% cpu idle. The question is: How ACPI can generate IRQs? I thought it is just some kind of interface and protocol standard, not a real hardware part which can rise irq. Why does it generate so many irqs? May it be related to the PCI parity error on twe? Artem From owner-freebsd-hardware@FreeBSD.ORG Thu Apr 22 06:12:52 2004 Return-Path: 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 25F1C16A4CE for ; Thu, 22 Apr 2004 06:12:52 -0700 (PDT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 040D043D48 for ; Thu, 22 Apr 2004 06:12:52 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6655 invoked from network); 22 Apr 2004 13:12:51 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Apr 2004 13:12:51 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i3MDCmru006281; Thu, 22 Apr 2004 09:12:48 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 22 Apr 2004 09:13:02 -0400 User-Agent: KMail/1.6 References: <010501c426db$cc281a10$0c00a8c0@artem> In-Reply-To: <010501c426db$cc281a10$0c00a8c0@artem> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Message-Id: <200404220913.02440.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Artem Koutchine Subject: Re: ACPI floods CPUs with interrupts X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2004 13:12:52 -0000 On Tuesday 20 April 2004 09:31 am, Artem Koutchine wrote: > I have installed FreeBSd 5.2-RC2 on ASUS P2B-DS > with 3ware raid controller and DUAL PIII (slot2) 550Mhz. > Updated motherboard bios to > the latest bios and after patching the twe driver, so it does not > show the "PCI parity erro" several times a second. (I think > it is related to the fact that 3ware 7506 controller is pci 2.2 > while p2b is pci 2.1). After that i did top and saw that > 50% of cpu power is wasted on interrupts. I did > sysstat and :vmstat. It showed that 46700 interrupts per > second were generated by acpi on irq 20. So, i booted without > acpi and got 100% cpu idle. The question is: > How ACPI can generate IRQs? I thought it is just some kind > of interface and protocol standard, not > a real hardware part which > can rise irq. Why does it generate so many irqs? May it be related > to the PCI parity error on twe? It is because the ACPI interrupt is programmed incorrectly (due to a buggy BIOS) and is treated as edge triggered when it is actually level triggered. You can try updating to -current to see if that fixes it. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Thu Apr 22 06:54:07 2004 Return-Path: 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 0035416A4CE; Thu, 22 Apr 2004 06:54:06 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFB7843D5D; Thu, 22 Apr 2004 06:54:05 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i3MDs3Xg092253; Thu, 22 Apr 2004 17:54:04 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <009f01c42870$deadb230$0c00a8c0@artem> From: "Artem Koutchine" To: "John Baldwin" , References: <010501c426db$cc281a10$0c00a8c0@artem> <200404220913.02440.jhb@FreeBSD.org> Date: Thu, 22 Apr 2004 17:51:09 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: ACPI floods CPUs with interrupts X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2004 13:54:07 -0000 > On Tuesday 20 April 2004 09:31 am, Artem Koutchine wrote: > > I have installed FreeBSd 5.2-RC2 on ASUS P2B-DS > > with 3ware raid controller and DUAL PIII (slot2) 550Mhz. > > Updated motherboard bios to > > the latest bios and after patching the twe driver, so it does not > > show the "PCI parity erro" several times a second. (I think > > it is related to the fact that 3ware 7506 controller is pci 2.2 > > while p2b is pci 2.1). After that i did top and saw that > > 50% of cpu power is wasted on interrupts. I did > > sysstat and :vmstat. It showed that 46700 interrupts per > > second were generated by acpi on irq 20. So, i booted without > > acpi and got 100% cpu idle. The question is: > > How ACPI can generate IRQs? I thought it is just some kind > > of interface and protocol standard, not > a real hardware part which > > can rise irq. Why does it generate so many irqs? May it be related > > to the PCI parity error on twe? > > It is because the ACPI interrupt is programmed incorrectly (due to a buggy > BIOS) and is treated as edge triggered when it is actually level triggered. > You can try updating to -current to see if that fixes it. Cvsupped -current today and built world and installed new kernel. Now it actually detects the interrupt storm and does what it calles 'thottling' to the source of the interrupts. Now i get only 9000 ints per second and it eats abouts 10% of the CPU. I still do not consider it a good idea and i cannot update bios because the latest update was in 2002 and since then asus made no changed to it. So i just did hint.acpi.0.disabled="1" and disabled acpi. Now i have all 100% of cpu to do something usefull. ACPI is a good thing but it is totally broken on all motherboards. Too bad. Artem From owner-freebsd-hardware@FreeBSD.ORG Thu Apr 22 17:36:13 2004 Return-Path: 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 F3DF716A4CE for ; Thu, 22 Apr 2004 17:36:12 -0700 (PDT) Received: from e2kcn1.ad.uky.edu (e2kcn1.ad.uky.edu [128.163.2.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ED3143D31 for ; Thu, 22 Apr 2004 17:36:10 -0700 (PDT) (envelope-from Jon.Reckner@uky.edu) Received: from e2kbe1.ad.uky.edu ([128.163.2.94]) by e2kcn1.ad.uky.edu with Microsoft SMTPSVC(5.0.2195.5329); Thu, 22 Apr 2004 20:36:09 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Date: Thu, 22 Apr 2004 20:36:08 -0400 Message-ID: <7E5005789BF1AD40BB8C736937FFA3FA90238B@e2kbe1.ad.uky.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Rocket Raid 454 - HPT374 Thread-Index: AcQoyvgqcTEL8jyTSfGcWQRMyJCBug== From: "Reckner, Jonathan G" To: X-OriginalArrivalTime: 23 Apr 2004 00:36:09.0726 (UTC) FILETIME=[F8E1A9E0:01C428CA] Subject: Rocket Raid 454 - HPT374 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Apr 2004 00:36:13 -0000 SGFzIGFueW9uZSBzdWNjZXNzZnVsbHkgZ290dGVuIGEgSGlnaHBvaW50IFJvY2tldCBSYWlkIDQ1 NCB3aXRoIHRoZSBocHQzNzQgY2hpcCB0byB3b3JrIGluIEZyZWVCU0Q/IEkgaGF2ZSB0cmllZCB2 ZXJzaW9ucyA1LjIuMSwgNC45LCBhbmQgNC43LiBDdXJyZW50bHkgSSBhbSB1c2luZyBGcmVlQlNE IDQuNyBidXQgSSB3b3VsZCBsaWtlIHRvIGdldCB0aGlzIGNhcmQgd29ya2luZyBpbiA0LjkuIEkg YW0gdXNpbmcgdGhlIGZpbGVzIHN1cHBsaWVkIGJ5IGhpZ2hwb2ludCBodHRwOi8vd3d3LmhpZ2hw b2ludC10ZWNoLmNvbS9ycjQ1NF9kb3duLmh0bQ0KIA0KQXR0YWNoZWQgaXMgbXkgY3VycmVudCBk bWVzZyBhZnRlciBsb2FkaW5nIHRoZSBocHQzNzQua28gZm9yIDQuNyBhdCBib290LiBJZiBhbnlv bmUgY2FuIHNoZWQgc29tZSBsaWdodCBvbiBwb3NzaWJseSB3aHkgSSBhbSBub3QgZ2V0dGluZyBh IGRldmljZSBmb3IgdGhlIHJhaWQgYXJyYXkgSSBoYXZlIGl0IHNldHVwIGFzIGEgbWlycm9yIHVz aW5nIHR3byBpZGVudGljYWwgV2VzdGVybiBkaWdpdGFsIDEyMEdCIGRyaXZlcy4gYm90aCBkcml2 ZXMgYXJlIHNob3dpbmcgdXAgaW4gdGhlIGRtZXNnIGFkNCBhbmQgYWQ2LiBJIHdvdWxkIHJlYWxs eSBhcHByZWNpYXRlIHNvbWUgcG9pbnRlcnMgb3IgaW5zdHJ1Y3Rpb25zIG9uIGhvdyB0byBnZXQg dGhpcyByYWlkIGFycmF5IHRvIHdvcmsgcHJvcGVybHkgYmVjYXVzZSBzbyBmYXIgdGhlIGluc3Ry dWN0aW9ucyBzdXBwbGllZCBieSBoaWdocG9pbnQgZGlkIG5vdCB3b3JrIGZvciBtZQ0KIA0KdGh4 DQpKb24NCg== From owner-freebsd-hardware@FreeBSD.ORG Fri Apr 23 11:08:09 2004 Return-Path: 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 DBCDB16A4CE for ; Fri, 23 Apr 2004 11:08:09 -0700 (PDT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id B307343D4C for ; Fri, 23 Apr 2004 11:08:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19374 invoked from network); 23 Apr 2004 18:08:09 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Apr 2004 18:08:09 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i3NI7v6C001779; Fri, 23 Apr 2004 14:08:06 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Artem Koutchine" Date: Fri, 23 Apr 2004 13:49:13 -0400 User-Agent: KMail/1.6 References: <010501c426db$cc281a10$0c00a8c0@artem> <200404220913.02440.jhb@FreeBSD.org> <009f01c42870$deadb230$0c00a8c0@artem> In-Reply-To: <009f01c42870$deadb230$0c00a8c0@artem> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Message-Id: <200404231349.13468.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-hardware@FreeBSD.org Subject: Re: ACPI floods CPUs with interrupts X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Apr 2004 18:08:10 -0000 On Thursday 22 April 2004 09:51 am, Artem Koutchine wrote: > > On Tuesday 20 April 2004 09:31 am, Artem Koutchine wrote: > > > I have installed FreeBSd 5.2-RC2 on ASUS P2B-DS > > > with 3ware raid controller and DUAL PIII (slot2) 550Mhz. > > > Updated motherboard bios to > > > the latest bios and after patching the twe driver, so it does not > > > show the "PCI parity erro" several times a second. (I think > > > it is related to the fact that 3ware 7506 controller is pci 2.2 > > > while p2b is pci 2.1). After that i did top and saw that > > > 50% of cpu power is wasted on interrupts. I did > > > sysstat and :vmstat. It showed that 46700 interrupts per > > > second were generated by acpi on irq 20. So, i booted without > > > acpi and got 100% cpu idle. The question is: > > > How ACPI can generate IRQs? I thought it is just some kind > > > of interface and protocol standard, not > a real hardware part which > > > can rise irq. Why does it generate so many irqs? May it be related > > > to the PCI parity error on twe? > > > > It is because the ACPI interrupt is programmed incorrectly (due to a > > buggy BIOS) and is treated as edge triggered when it is actually level > > triggered. You can try updating to -current to see if that fixes it. > > Cvsupped -current today and built world and installed new kernel. Now it > actually detects the interrupt storm and does what it calles 'thottling' to > the source of the interrupts. Now i get only 9000 ints per second and it > eats abouts 10% of the CPU. I still do not consider it a good idea and i > cannot update bios because the latest update was in 2002 and since then > asus made no changed to it. So i just did hint.acpi.0.disabled="1" and > disabled acpi. Now i have all 100% of cpu to do something usefull. ACPI is > a good thing but it is totally broken on all motherboards. Too bad. ACPI is not totally broken on all motherboards. Can you try adding 'hw.acpi.force_sci_lo=1' to /boot/loader.conf and rebooting to see if it works better? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org