From owner-freebsd-current@FreeBSD.ORG Sun May 16 02:37:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D64B16A4CE for ; Sun, 16 May 2004 02:37:38 -0700 (PDT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2A6343D58 for ; Sun, 16 May 2004 02:37:36 -0700 (PDT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i4G9Z1Xq025066 for freebsd-current@freebsd.org.checked; (8.12.8/vak/2.1) Sun, 16 May 2004 13:35:01 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (rik.cronyx.ru [172.22.4.1]) by hanoi.cronyx.ru with ESMTP id i4G9XHF2025006; (8.12.8/vak/2.1) Sun, 16 May 2004 13:33:17 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <40A73401.5010703@cronyx.ru> Date: Sun, 16 May 2004 13:27:29 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: Marcel Moolenaar References: <40A26162.9030607@cronyx.ru> <20040512.200542.09569104.imp@bsdimp.com> <20040513155109.GB6572@dhcp01.pn.xcllnt.net> <40A4E2CB.2000007@cronyx.ru> <20040515041301.O22881@gamplex.bde.org> <40A537C8.1010407@cronyx.ru> <20040515190413.GB9900@dhcp01.pn.xcllnt.net> In-Reply-To: <20040515190413.GB9900@dhcp01.pn.xcllnt.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Sio & Puc memory mapped X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 09:37:38 -0000 Marcel Moolenaar: [...] > >--- asytest.c~ Fri May 14 11:50:10 2004 >+++ asytest.c Sat May 15 11:31:03 2004 >@@ -152,6 +152,7 @@ > } > > opt = chan[i].old_options; >+ cfmakeraw (&opt); > cfsetspeed (&opt, baud); > opt.c_cflag = CREAD | CS8; > opt.c_lflag &= ~ICANON; >@@ -198,7 +199,7 @@ > for (c=chan; c if (c->fd > 0) { > if (c->ready_to_transmit) { >- s = write (c->fd, tbuf+it, IOSZ); >+ s = write (c->fd, tbuf+it, IOSZ-it); > if (s <= 0) { > if (s < 0) { > if (errno != EAGAIN) > > Works good with my card. Thanks! >The first (the cfmakeraw() insertion) may be related to uart(4) not >setting proper defaults, but may also be related to uart(4) setting >different *valid* defaults. The second is a genuine test program bug > The only I can say that this test works fine with sio(4), cx(4), and under linux kernels before 2.6 with serial. So this requires additional investigation. >triggered by write() doing partial writes. This bug too may be the >result of uart(4) not setting the right defaults, but since the test >program doesn't assume complete writes the bug is primarily in the >test program by virtue of allowing partial writes. > > rik From owner-freebsd-current@FreeBSD.ORG Sun May 16 02:46:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3030016A4CE for ; Sun, 16 May 2004 02:46:49 -0700 (PDT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05A0643D46 for ; Sun, 16 May 2004 02:46:48 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i4G9kd5v024719; Sun, 16 May 2004 19:46:39 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i4G9kaLS012643; Sun, 16 May 2004 19:46:38 +1000 Date: Sun, 16 May 2004 19:46:37 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Julian Elischer In-Reply-To: <20040510162831.X1105@gamplex.bde.org> Message-ID: <20040516190430.O798@gamplex.bde.org> References: <20040510162831.X1105@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD current users Subject: Re: exit1()/scheduler question.. possible typo? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 09:46:49 -0000 On Mon, 10 May 2004, Bruce Evans wrote: > On Sun, 9 May 2004, Julian Elischer wrote: > > > in exit1 there is an assertion to test that the exiting process > > is not init. (proc 1 by tradition..) > > > > yes later, nearly at the end we see: > > > > /* > > * Allow the scheduler to adjust the priority of the > > * parent when a kseg is exiting. > > */ > > if (p->p_pid != 1) > > sched_exit(p->p_pptr, td); > > > > > > firstly, the comment is wrong but, the question comes.. > > "if init can not get here then why have the test?" > > ... > > I get the impression that possibly this should be p->p_pptr->p_ppid > p_pid > > but I don't know enough about ULE to know if that makes sense. > > > > (maybe it should be (p->p_pptr != initproc) > > My version already used initproc here and elsewhere, but was missing the > fix for the LHS. I tried using (p->p_pptr != initproc), but this broke load averages and thus caused problems like sendmail refusing to run. We were depending on the bug to get sched_exit() called unconditionally. The call must now always be made, because one of the things that sched_exit() does for the 4BSD scheduler is decrement the load average counter. The nearby call to cpu_sched_exit() is also bogus: % cpu_sched_exit(td); /* XXXKSE check if this should be in thread_exit */ % /* % * Allow the scheduler to adjust the priority of the % * parent when a kseg is exiting. % */ % if (p->p_pid != 1) % sched_exit(p->p_pptr, p); Scheduling is not cpu-specific, and if it were then it should be done by sched_exit() calling cpu_sched_exit(). In practice, cpu_sched_exit() is null for all arches except sparc64. For sparc64, it does things related to exiting but unrelated to scheduling. ISTR you asking about sparc64's cpu_sched_exit() separately. On i386's, things related to exiting are done in cpu_exit() and cpu_thread_exit(). This seem to be the right places to do such things. However, things are misplaced internally there. The debugger registers are per-thread, so they should only be reset in cpu_thread_exit(). The first senetence of the nearby comment on the call to thread_exit() is also bogus: % /* % * Make sure the scheduler takes this thread out of its tables etc. % * This will also release this thread's reference to the ucred. % * Other thread parts to release include pcb bits and such. % */ % thread_exit(); This call to thread_exit() doesn't do anything related to scheduling, since p->p_numthreads is 1. Bruce From owner-freebsd-current@FreeBSD.ORG Sun May 16 02:50:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B56CF16A4CE for ; Sun, 16 May 2004 02:50:49 -0700 (PDT) Received: from st68.arena.ne.jp (st68.arena.ne.jp [203.138.213.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 4236E43D4C for ; Sun, 16 May 2004 02:50:47 -0700 (PDT) (envelope-from eyes@navi.org) Received: (qmail 23877 invoked by SAV 20040515.9); 16 May 2004 18:50:45 +0900 Received: from unknown (HELO localhost) (220.221.66.250) by st68.arena.ne.jp (203.138.213.118) with SMTP; 16 May 2004 18:50:45 +0900 Date: Sun, 16 May 2004 18:52:18 +0900 From: Hiroyuki Aizu To: current@freebsd.org Message-Id: <20040516185218.2a1d27a2.eyes@navi.org> Organization: navi.org X-Mailer: Sylpheed version 0.9.9-gtk2-20040229 (GTK+ 2.4.1; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: CardBus (PCI ?) resource allocation problem report. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 09:50:49 -0000 Hi I have trouble with IEEE1394 CardBus card on 5-current. I think it is CardBus(PCI ?) resource allocation problem. I'll figure out this. The card cannot attached on 5-current as below message. (with hw.cardbus.debug=1 and hw.cardbus.cis_debug=1) ------------------------------------------------------------------------- cardbus1: Expecting link target, got 0x42 cardbus1: Resource not specified in CIS: id=10, size=800 cardbus1: Resource not specified in CIS: id=14, size=4000 cardbus1: Resource not specified in CIS: id=18, size=800 cardbus1: Non-prefetchable memory at 88008000-8800cfff fwohci0: mem 0x8800c000-0x8800c7ff,0x88008000-0x8800bfff,0x8800c800-0x8800cfff irq 10 at device 0.0 on cardbus1 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version ff.ff (ROM=1) fwohci0: invalid OHCI version fwohci0: fwohci_init failed with err=6 device_probe_and_attach: fwohci0 attach returned 5 cbb1: CardBus card activation failed ------------------------------------------------------------------------- Next, I was patched to /sys/dev/cardbus/cardbus_cis.c like below. (Yes, this is very dirty hack. Just for trouble shooting.) ------------------------------------------------------------------------- --- cardbus_cis.c.orig Mon Apr 12 04:22:25 2004 +++ cardbus_cis.c Sun May 16 17:23:03 2004 @@ -993,6 +993,9 @@ cardbus_add_map(device_t cbdev, device_t static void cardbus_pickup_maps(device_t cbdev, device_t child) { +#if 1 + cardbus_add_map(cbdev, child, PCIR_BAR(0)); +#else struct cardbus_devinfo *dinfo = device_get_ivars(child); int reg; @@ -1003,6 +1006,7 @@ cardbus_pickup_maps(device_t cbdev, devi */ for (reg = 0; reg < dinfo->pci.cfg.nummaps; reg++) cardbus_add_map(cbdev, child, PCIR_BAR(reg)); +#endif } int ------------------------------------------------------------------------- The card works fine on patched kernel like below. ------------------------------------------------------------------------- cardbus1: Expecting link target, got 0x42 cardbus1: Resource not specified in CIS: id=10, size=800 cardbus1: Non-prefetchable memory at 88001000-880017ff fwohci0: mem 0x88001000-0x880017ff irq 10 at device 0.0 on cardbus1 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:40:26:01:04:04:4e:ef fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ------------------------------------------------------------------------- >From difference between two debug messages, I think it is problem that kernel allocate non-requested resource from driver. It has side effects in this case. In the PCI firewire driver reqests I/O memory that specified with rid = 0x10 like this. (from /sys/dev/firewire/fwohci_pci.c) rid = PCI_CBMEM; /* (= PCIR_BAR(0) = 0x10) */ sc->bsr = bus_alloc_resource_any(self, SYS_RES_MEMORY, &rid, RF_ACTIVE); But 5-curret kernel allocates all memory resource (rid = 0x10, 0x14, 0x18). fwohci0: mem 0x8800c000-0x8800c7ff,0x88008000-0x8800bfff,0x8800c800-0x8800cfff irq 10 at device 0.0 on cardbus1 With my patch, it prevent add surplus resource to resource list. (Yes I know, this is not real solution.) # And, I don't know why the IEEE1394 card does not works with all memory # resouces allocated... From owner-freebsd-current@FreeBSD.ORG Sun May 16 04:34:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBED816A4CF for ; Sun, 16 May 2004 04:34:48 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3A2E43D45 for ; Sun, 16 May 2004 04:34:47 -0700 (PDT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i4GBYfDv088964 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sun, 16 May 2004 13:34:43 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i4GBYEUi014912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 May 2004 13:34:15 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id i4GBYENe041154; Sun, 16 May 2004 13:34:14 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id i4GBYCsj041153; Sun, 16 May 2004 13:34:12 +0200 (CEST) (envelope-from ticso) Date: Sun, 16 May 2004 13:34:12 +0200 From: Bernd Walter To: "Marc G. Fournier" Message-ID: <20040516113411.GK70900@cicely12.cicely.de> References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040515233728.Q30269@ganymede.hub.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on cicely12.cicely.de cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 11:34:50 -0000 On Sat, May 15, 2004 at 11:41:41PM -0300, Marc G. Fournier wrote: > 'k ... fsck just started spewing messages to the screen, which is nice > cause now I know its actually doing something: You can always siginfo (CTRL-T) to get information on current progress. fsck delays response to the next check boundary, but reply is still quick enough to be usefull. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Sun May 16 04:52:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75DBC16A4CE for ; Sun, 16 May 2004 04:52:13 -0700 (PDT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E01943D4C for ; Sun, 16 May 2004 04:52:07 -0700 (PDT) (envelope-from peter.schuller@infidyne.com) Received: from scode.mine.nu ([83.226.138.17] [83.226.138.17]) by mxfep01.bredband.com with ESMTP id <20040516115204.SGMW2575.mxfep01.bredband.com@scode.mine.nu>; Sun, 16 May 2004 13:52:04 +0200 Received: from localhost (localhost [127.0.0.1]) by scode.mine.nu (Postfix) with ESMTP id 9B6CE1503BE; Sun, 16 May 2004 13:54:48 +0200 (CEST) From: Peter Schuller To: freebsd-current@freebsd.org Date: Sun, 16 May 2004 13:54:46 +0200 User-Agent: KMail/1.6 References: <20040515220258.H920@ganymede.hub.org> In-Reply-To: <20040515220258.H920@ganymede.hub.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405161354.46932.peter.schuller@infidyne.com> Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 11:52:13 -0000 > In 5.x, if I'm not mistaken, fsck's are backgrounded on reboot, so that > the system comes up faster ... but: A word of warning: This does not hold true for the root partition. If your root partition is small, no problem. Otherwise you will still have to wait for that to be fsck:ed. -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org From owner-freebsd-current@FreeBSD.ORG Sun May 16 05:01:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CB9616A4CE for ; Sun, 16 May 2004 05:01:36 -0700 (PDT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05EF243D54 for ; Sun, 16 May 2004 05:01:35 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i4GC1K4u004043; Sun, 16 May 2004 22:01:20 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i4GC1HLS027061; Sun, 16 May 2004 22:01:18 +1000 Date: Sun, 16 May 2004 22:01:18 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Roman Kurakin In-Reply-To: <40A73401.5010703@cronyx.ru> Message-ID: <20040516210256.W866@gamplex.bde.org> References: <40A26162.9030607@cronyx.ru> <20040512.200542.09569104.imp@bsdimp.com><40A4E2CB.2000007@cronyx.ru> <20040515041301.O22881@gamplex.bde.org> <40A537C8.1010407@cronyx.ru> <40A73401.5010703@cronyx.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Marcel Moolenaar Subject: Re: Sio & Puc memory mapped X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 12:01:36 -0000 On Sun, 16 May 2004, Roman Kurakin wrote: > Marcel Moolenaar: > [...] > > > > >--- asytest.c~ Fri May 14 11:50:10 2004 > >+++ asytest.c Sat May 15 11:31:03 2004 > >@@ -152,6 +152,7 @@ > > } > > > > opt = chan[i].old_options; > >+ cfmakeraw (&opt); > > cfsetspeed (&opt, baud); > > opt.c_cflag = CREAD | CS8; > > opt.c_lflag &= ~ICANON; > > ... > > >The first (the cfmakeraw() insertion) may be related to uart(4) not > >setting proper defaults, but may also be related to uart(4) setting > >different *valid* defaults. The second is a genuine test program bug > > > The only I can say that this test works fine with sio(4), cx(4), > and under linux kernels before 2.6 with serial. So this requires > additional investigation. Programs certainly need to initialize all of the termios state that they care about, but the uart driver uses poorly chosen defaults which can't be changed at runtime and are particularly unsuitable for simple test programs. The only fundamentally broken thing in the uart driver's defaults is that they have echos enabled, so an echo war results if 2 ports driven by the uart driver are connected and one of them happens to send a character before an ioctl can be done to set a useable state. Bruce From owner-freebsd-current@FreeBSD.ORG Sat May 15 07:42:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61F5616A4CE; Sat, 15 May 2004 07:42:58 -0700 (PDT) Received: from smtp.tznet.com (smtp.tznet.com [66.170.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6FC443D2F; Sat, 15 May 2004 07:42:56 -0700 (PDT) (envelope-from scottp@tznet.com) Received: from mail.tznet.com (mail.tznet.com [66.170.64.2]) by smtp.tznet.com (8.12.11/8.12.10) with ESMTP id i4FEghmD037313; Sat, 15 May 2004 09:42:44 -0500 (CDT) Date: Sat, 15 May 2004 09:42:42 -0500 (CDT) From: Scott Pilz To: Brian Fundakowski Feldman In-Reply-To: <200405151414.i4FEEY8e077866@green.homeunix.org> Message-ID: <20040515092439.K35345@mail.tznet.com> References: <200405151414.i4FEEY8e077866@green.homeunix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-T-Net-Virus-Scan: 66.170.64.6: Clean X-Mailman-Approved-At: Sun, 16 May 2004 05:19:39 -0700 cc: current@freebsd.org cc: Jiri Mikulas Subject: Re: hostap TX fix in 5.x [Fwd: Re: wi hostap speed] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2004 14:42:58 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian, try this exact setup on 5.x - this is for the hostap side, the client side can be anything compatible. . . The card is of course, a PRISM 2.5 chipset. To be more specific, a Demarc PRISM 200mw PCMCIA (www.demarc.com). In case there is any question, I've also tried non Demarc cards (still PRISM 2.5) ranging from 30mw to 200mw. The hardware varies - from a P133 to a AMD1.8, doesn't make any bit of difference. I've tried nearly all the public firmware releases for this chipset. The one I'm on right now (that I'll use in this example) Primary 1.1.1, Station 1.7.4.. See output below: dmesg output: wi0: 802.11 address: 00:60:b3:..:..:.. wi0: using RF:PRISM2.5 MAC:ISL3873 wi0: Intersil Firmware: Primary (1.1.1), Station (1.7.4) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps The setup of the system doesn't seem to matter either. I have tried with BRIDGE(4) enabled between the interfaces, I've tried setting the system up to be a router (and route the packets to someplace else), and just for testing, I've tried not having the system route packets or bridge packets, instead just ftp directly from the associated client to the hostap station itself - the speeds do not change. Everything works - the bridging, the routing, the ftping to the station, but the speeds are less than half of what they should be during downloads - upload FROM client TO station works at full 500+KB/sec. (in this example, I'll use 192.168.0.1 for the hostap station and .2 for the client) ifconfig 192.168.0.1 netmask 255.255.255.0 media DS/11Mbps mediaopt hostap ssid test channel 1 stationname test-system Obviously the channel will be up to you, as well as the IP address of the system. I've also used media DS/2Mbps as well as media autoselect - DS/11Mbps gets the better speeds typically (well, what you could call 'better' compared to the other settings, but not full speeds like in FBSD-4.x). I tested this with WEP, long long ago, but I don't currently run it. The type of traffic does not matter. I have tried FTP, I've tried java web-based "speed test" type software, I've tried downloading in browsers from associated stations, again - it doesn't matter. The speeds do not change. At average, the maximum speed is about 160-170KB/sec. Again, using this exact same setup line-for-line, booting with BSD 4.x (and throwing in older firmware as 4.x does not support this PRISM 2.5 firmware) gets full 500+KB/sec up and down. I've gone as far as .. I want to say, flash version 1.3.6 on the PRISM 2.5 card, no change at all. If you figure this out, you're better than I am :)...Short of re-writing the wi driver I'm out of ideas. Scott On Sat, 15 May 2004, Brian Fundakowski Feldman wrote: > Scott Pilz wrote: > > Brian, speeds are limited to under 180KBytes/sec while in hostap > > mode. Take any 5.x box with the wi drivers and a prism 2.5 based card (in > > order for hostap to work properly). Set it up to be an access point > > (mediaopt hostap, doesn't matter what you use for media, I have used both > > autoselect, 11Mbps, etc.) Use any radio equipment to connect to the access > > point (from Lucent to Tranzeo to SmartBridges, you name it, doesn't matter > > as long as it's 802.11b compatible obviously).. You'll get a maximum > > DOWNLOAD of about 180Kbps if you're lucky.. Upload works fine at > > 500+Kbps.. Now, take that exact same setup without changing anything on a > > 4.9 system - download speeds (to the client radio) are back up to 500+ > > Kbps. > > > > This is just off the top of my head, but there was some major > > reconstruction in wi(4) from 4.9 to 5.x. It's been broken since day one > > since the first release of 5.x.. so looking at 'what changed' in CVS > > probably won't help you. My guess is that it's not going to be easily > > found. Bless anyone who wants to look into this - as this has been a real > > nightmare. > > What are you testing with to get those figures? I will try this out at work > on Monday where I have umpteen boxes and PRISM 2.x cards if you can give me > even more exact reproduction steps. If you don't say anything I'm just > going to try netperf TCP stream tests on a non-WEP hostap network. > > -- > Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ > <> green@FreeBSD.org \ The Power to Serve! \ > Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFApixj2REUg6gjWxgRAtW7AJ4/4+VQJKk4aNZ47CLP7lts/s0RegCg85di m1EXEpWGTMQFuSklbXngzYo= =z2vm -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat May 15 10:38:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 121D216A4CE for ; Sat, 15 May 2004 10:38:54 -0700 (PDT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.62.205.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9125E43D41 for ; Sat, 15 May 2004 10:38:53 -0700 (PDT) (envelope-from forrie@forrie.com) Received: from [192.168.1.92] (i-92.forrie.net [192.168.1.92] (may be forged)) by forrie.com with ESMTP id i4FHcgnt071239verify=NO) for ; Sat, 15 May 2004 13:38:46 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <40A655A2.5010706@forrie.com> Date: Sat, 15 May 2004 13:38:42 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.6 (X11/20040514) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean X-Mailman-Approved-At: Sun, 16 May 2004 05:19:39 -0700 Subject: dmesg for ATA devices (SATA) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 May 2004 17:38:54 -0000 I adjusted my BIOS (SOYO Dragon Platinum) to enable only the Primary IDE + SATA and now I can see all drives on FreeBSD-5-CURRENT. However, the dmesg output looks a little weird: ad2: 76319MB [155061/16/63] at ata1-master SATA150 ad3: 76319MB [155061/16/63] at ata1-slave SATA150 ad4: 76319MB [155061/16/63] at ata2-master SATA150 ad6: 76319MB [155061/16/63] at ata3-master SATA150 All 4 drives are plugged in to the Silicon Image controller (4 ports). I'm of course happy to install a PCI-based SATA controller, once I'm certain about which is best recommended for FreeBSD-5. The jury seems out on Highpoint and Promise. Anyone care to comment? The dmesg output should probably read master/slave master/slave... ? Thanks. From owner-freebsd-current@FreeBSD.ORG Sat May 15 19:28:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D083916A4CF for ; Sat, 15 May 2004 19:28:49 -0700 (PDT) Received: from tulxmail03.pennwell.net (tulxmail03.pennwell.net [205.157.161.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A15A43D48 for ; Sat, 15 May 2004 19:28:48 -0700 (PDT) (envelope-from BarryB@pennnet.com) Received: from tulxmail02.pennwell.net ([205.157.176.5]) by tulxmail03.pennwell.net with Microsoft SMTPSVC(5.0.2195.6713); Sat, 15 May 2004 21:28:45 -0500 Received: from tulxmail04.pennwell.net ([205.157.161.23]) by tulxmail02.pennwell.net with Microsoft SMTPSVC(5.0.2195.6713); Sat, 15 May 2004 21:28:46 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 15 May 2004 21:28:05 -0500 Message-ID: <6E2CE2DCE0840149A978BD93F24FA443F1B62E@tulxmail04.pennwell.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: acpidump problem after recent commit Importance: normal Priority: normal thread-index: AcQ61K4VPzgiZv0rRFKprgxHDUa+lQ== From: "Barry Boone" To: X-OriginalArrivalTime: 16 May 2004 02:28:46.0520 (UTC) FILETIME=[83BEDB80:01C43AED] X-Mailman-Approved-At: Sun, 16 May 2004 05:22:31 -0700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: acpidump problem after recent commit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 02:28:49 -0000 My system is no longer able to use acpidump, and instead now issues the message: =20 sysctl machdep.acpi_root does not point to RSDP =20 I am tracking current, and this broke right after the changes in acpidump in the last couple days. =20 Let me know if you need more information=20 =20 If you would prefer not to receive further commercial email messages = from PennWell, please reply to the original email and type "Unsubscribe" = in the subject line. Or, if you prefer, you can write to us at:=20 =20 PennWell Corporation=20 c/o Email Unsubscribe=20 1421 South Sheridan Road=20 Tulsa, Oklahoma 74112 USA =20 =20 PennWell provides business-to-business information and events for the = oil & gas, electric power, water, electronics, semiconductor, = contamination control, optoelectronics, fiber optics, computer graphics, = enterprise storage, information technology, fire, EMS, and dental = markets.=20 =20 From owner-freebsd-current@FreeBSD.ORG Sun May 16 07:12:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC11D16A4CE for ; Sun, 16 May 2004 07:12:04 -0700 (PDT) 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 57C9A43D6D for ; Sun, 16 May 2004 07:11:59 -0700 (PDT) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i4GEBII9081922; Sun, 16 May 2004 16:11:23 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <40A77686.6010807@DeepCore.dk> Date: Sun, 16 May 2004 16:11:18 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.5 (X11/20040329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Aldrich References: <40A655A2.5010706@forrie.com> In-Reply-To: <40A655A2.5010706@forrie.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: dmesg for ATA devices (SATA) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 14:12:04 -0000 Forrest Aldrich wrote: > I adjusted my BIOS (SOYO Dragon Platinum) to enable only the Primary IDE > + SATA and now I can see all drives on FreeBSD-5-CURRENT. However, the > dmesg output looks a little weird: > > ad2: 76319MB [155061/16/63] at ata1-master SATA150 > ad3: 76319MB [155061/16/63] at ata1-slave SATA150 > ad4: 76319MB [155061/16/63] at ata2-master SATA150 > ad6: 76319MB [155061/16/63] at ata3-master SATA150 > > All 4 drives are plugged in to the Silicon Image controller (4 ports). Looks a bit wierd, but as I said last time I need a *full* dmesg to be able to tell. > I'm of course happy to install a PCI-based SATA controller, once I'm > certain about which is best recommended for FreeBSD-5. The jury seems > out on Highpoint and Promise. Anyone care to comment? Promise is the choice IMO. > The dmesg output should probably read master/slave master/slave... ? Depends on controller type and setup, from the above 4 lines noone can tell you what you should have. -- -Søren From owner-freebsd-current@FreeBSD.ORG Sun May 16 08:37:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79ABE16A4CE for ; Sun, 16 May 2004 08:37:11 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E421C43D49 for ; Sun, 16 May 2004 08:37:10 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i4GFYRC9061629; Sun, 16 May 2004 08:34:27 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) i4GFYR8e014012; Sun, 16 May 2004 08:34:27 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i4GFYKSq014011; Sun, 16 May 2004 08:34:20 -0700 (PDT) (envelope-from marcel) Date: Sun, 16 May 2004 08:34:20 -0700 From: Marcel Moolenaar To: Bruce Evans Message-ID: <20040516153420.GA13929@dhcp01.pn.xcllnt.net> References: <40A26162.9030607@cronyx.ru> <20040512.200542.09569104.imp@bsdimp.com> <20040513155109.GB6572@dhcp01.pn.xcllnt.net> <40A4E2CB.2000007@cronyx.ru> <20040515041301.O22881@gamplex.bde.org> <40A537C8.1010407@cronyx.ru> <20040515190413.GB9900@dhcp01.pn.xcllnt.net> <40A73401.5010703@cronyx.ru> <20040516210256.W866@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040516210256.W866@gamplex.bde.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Roman Kurakin Subject: Re: Sio & Puc memory mapped X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 15:37:11 -0000 On Sun, May 16, 2004 at 10:01:18PM +1000, Bruce Evans wrote: > > *snip*. The only fundamentally broken thing in the uart driver's > defaults is that they have echos enabled, so an echo war results if 2 > ports driven by the uart driver are connected and one of them happens > to send a character before an ioctl can be done to set a useable state. The uart(4) driver uses TTYDEF_xFLAG from Are the TTY defaults in that header wrong or are those merely a good general set of defaults that one may need to tweak in ones particular case (e.g. depending on the device or depending on the open mode)? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Sun May 16 09:30:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9202E16A4CE for ; Sun, 16 May 2004 09:30:44 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE09743D1D for ; Sun, 16 May 2004 09:30:43 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i4GGUeTE059591; Sun, 16 May 2004 11:30:40 -0500 (CDT) (envelope-from dan) Date: Sun, 16 May 2004 11:30:40 -0500 From: Dan Nelson To: Michael Hamburg Message-ID: <20040516163039.GE29158@dan.emsphone.com> References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 16:30:44 -0000 In the last episode (May 16), Michael Hamburg said: > On May 15, 2004, at 10:41 PM, Marc G. Fournier wrote: > >On Sat, 15 May 2004, Michael Hamburg wrote: > >>On May 15, 2004, at 9:08 PM, Marc G. Fournier wrote: > >>>I'm seriously considering putting 5.x onto my next server, to take > >>>advantage of, if nothing else, the reduction in the GIANT LOCK > >>>reliance ... one "concern" I have is how fsck works in 5.x ... > >>> > >>>Right now, on 4.x, I have an fsck running that has been going for > >>>~3hrs now: > >>> > >>># date; ps aux | grep fsck > >>>Sat May 15 22:04:00 ADT 2004 > >>>root 40 99.0 4.5 185756 185796 p0 R+ 6:55PM 164:01.60 fsck -y /dev/da0s1h > >>> > >>>and is in Phase 4 ... > >>> > >>>In 5.x, if I'm not mistaken, fsck's are backgrounded on reboot, so > >>>that the system comes up faster ... but: > >>> > >>>a. wouldn't that slow down the fsck itself, since all the > >>>processes on the machine would be using CPU/memory? > >> > >>Yes. You can probably renice it or something, though, and it > >>wouldn't take that much longer. Fsck takes very little CPU; it's almost all disk I/O, and bgfsck tries to throttle its load if it thinks that there's too much disk load. > You don't need much space unless you have high turnover -- the > default extra space in FFS that you can't allocate anyway should be > plenty, but as far as I can tell, if you do run out of space, Very > Bad Things Happen (tm). Just what those Very Bad Things are probably > depends on the release. The only Vary Bad Thing that I've ever seen happen is processes start returning ENOSPC even though df claims there's lots to spare. As soon as the fsck finishes you get your space back. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun May 16 09:44:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5705316A4CE for ; Sun, 16 May 2004 09:44:23 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8946143D39 for ; Sun, 16 May 2004 09:44:22 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4GGnZu6097846; Sun, 16 May 2004 10:49:35 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A79A54.3090703@freebsd.org> Date: Sun, 16 May 2004 10:44:04 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> In-Reply-To: <20040516163039.GE29158@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 16:44:23 -0000 Dan Nelson wrote: > In the last episode (May 16), Michael Hamburg said: > >>On May 15, 2004, at 10:41 PM, Marc G. Fournier wrote: >> >>>On Sat, 15 May 2004, Michael Hamburg wrote: >>> >>>>On May 15, 2004, at 9:08 PM, Marc G. Fournier wrote: >>>> >>>>>I'm seriously considering putting 5.x onto my next server, to take >>>>>advantage of, if nothing else, the reduction in the GIANT LOCK >>>>>reliance ... one "concern" I have is how fsck works in 5.x ... >>>>> >>>>>Right now, on 4.x, I have an fsck running that has been going for >>>>>~3hrs now: >>>>> >>>>># date; ps aux | grep fsck >>>>>Sat May 15 22:04:00 ADT 2004 >>>>>root 40 99.0 4.5 185756 185796 p0 R+ 6:55PM 164:01.60 fsck -y /dev/da0s1h >>>>> >>>>>and is in Phase 4 ... >>>>> >>>>>In 5.x, if I'm not mistaken, fsck's are backgrounded on reboot, so >>>>>that the system comes up faster ... but: >>>>> >>>>>a. wouldn't that slow down the fsck itself, since all the >>>>>processes on the machine would be using CPU/memory? >>>> >>>>Yes. You can probably renice it or something, though, and it >>>>wouldn't take that much longer. > > > Fsck takes very little CPU; it's almost all disk I/O, and bgfsck tries > to throttle its load if it thinks that there's too much disk load. > Actually, bgfsck unconditionally inserts a delay into every 8th i/o operation to try to keep from saturating the disks. Unfortunately this isn't terribly sophisticated and it results in bgfsck taking an eternity whether the system is idle, loaded, or reniced. A _really_ nice TODO item for FreeBSD 6.0 would be a real I/O scheduler. There are plenty of papers on it, some even focused on FreeBSD. Any volunteers? Scott From owner-freebsd-current@FreeBSD.ORG Sun May 16 10:04:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3929A16A4CE; Sun, 16 May 2004 10:04:43 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A904C43D46; Sun, 16 May 2004 10:04:42 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i4GH4f3a026050; Sun, 16 May 2004 12:04:41 -0500 (CDT) (envelope-from dan) Date: Sun, 16 May 2004 12:04:41 -0500 From: Dan Nelson To: Scott Long Message-ID: <20040516170441.GA80376@dan.emsphone.com> References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> <40A79A54.3090703@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40A79A54.3090703@freebsd.org> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 17:04:43 -0000 In the last episode (May 16), Scott Long said: > Actually, bgfsck unconditionally inserts a delay into every 8th i/o > operation to try to keep from saturating the disks. Unfortunately > this isn't terribly sophisticated and it results in bgfsck taking an > eternity whether the system is idle, loaded, or reniced. See http://dan.allantgroup.com/FreeBSD/fsck_ffs.diff for a patch that removes the delay if it's at the minimum value, and more fairly calculates disk wait time. This cuts bgfsck time from ~4 hours to 20 minutes on my 36gb /usr. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun May 16 10:13:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35A3E16A4CF for ; Sun, 16 May 2004 10:13:56 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2EA643D45 for ; Sun, 16 May 2004 10:13:55 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4GHJ9u6098002; Sun, 16 May 2004 11:19:09 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A7A143.7070907@freebsd.org> Date: Sun, 16 May 2004 11:13:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> <40A79A54.3090703@freebsd.org> <20040516170441.GA80376@dan.emsphone.com> In-Reply-To: <20040516170441.GA80376@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 17:13:56 -0000 Dan Nelson wrote: > In the last episode (May 16), Scott Long said: > >>Actually, bgfsck unconditionally inserts a delay into every 8th i/o >>operation to try to keep from saturating the disks. Unfortunately >>this isn't terribly sophisticated and it results in bgfsck taking an >>eternity whether the system is idle, loaded, or reniced. > > > See http://dan.allantgroup.com/FreeBSD/fsck_ffs.diff for a patch that > removes the delay if it's at the minimum value, and more fairly > calculates disk wait time. This cuts bgfsck time from ~4 hours to 20 > minutes on my 36gb /usr. > Looks like a reasonable fix. Do you want it reviewed and committed? Scott From owner-freebsd-current@FreeBSD.ORG Sun May 16 10:36:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AA6416A4CE; Sun, 16 May 2004 10:36:52 -0700 (PDT) Received: from avgw.bjut.edu.cn (avgw.bjut.edu.cn [202.112.78.85]) by mx1.FreeBSD.org (Postfix) with SMTP id 32AB343D39; Sun, 16 May 2004 10:36:51 -0700 (PDT) (envelope-from delphij@frontfree.net) Received: from beastie.frontfree.net ([218.107.145.7]) by avgw.bjut.edu.cn (SAVSMTP 3.1.5.43) with SMTP id M2004051701363411673 ; Mon, 17 May 2004 01:36:37 +0800 Received: from localhost (localhost [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 2E53D11C74; Mon, 17 May 2004 01:36:41 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00754-01; Mon, 17 May 2004 01:36:40 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id D04A211C53; Mon, 17 May 2004 01:36:39 +0800 (CST) Date: Mon, 17 May 2004 01:36:39 +0800 From: Xin LI To: Scott Long Message-ID: <20040516173639.GA628@frontfree.net> References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> <40A79A54.3090703@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <40A79A54.3090703@freebsd.org> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-CURRENT FreeBSD 5.2-CURRENT #33: Mon Apr 26 15:10:21 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: freebsd-current@freebsd.org cc: Dan Nelson cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 17:36:52 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 16, 2004 at 10:44:04AM -0600, Scott Long wrote: [snip] > A _really_ nice TODO item for FreeBSD 6.0 would be a real I/O scheduler. > There are plenty of papers on it, some even focused on FreeBSD. Any > volunteers? That is really attractive item to do... BTW. Scott, do we have a TODO list = for 6.0? IIRC there used to be one in p4, however it seems that p4 is no longer accessable through web. Shall we maintain another (might be more formal one) in www/? Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAp6anOfuToMruuMARApopAJ4mz1vr4Xakt+gmvREE0MRdoGoCrQCfVF2Z l7AD46bViQI9FPTd4abyfUM= =/23/ -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-current@FreeBSD.ORG Sun May 16 10:40:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4306616A4CE; Sun, 16 May 2004 10:40:10 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB07D43D3F; Sun, 16 May 2004 10:40:09 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i4GHdsHH004331; Sun, 16 May 2004 12:39:54 -0500 (CDT) (envelope-from dan) Date: Sun, 16 May 2004 12:39:54 -0500 From: Dan Nelson To: Scott Long Message-ID: <20040516173954.GB80376@dan.emsphone.com> References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> <40A79A54.3090703@freebsd.org> <20040516170441.GA80376@dan.emsphone.com> <40A7A143.7070907@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40A7A143.7070907@freebsd.org> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 17:40:10 -0000 In the last episode (May 16), Scott Long said: > Dan Nelson wrote: > >In the last episode (May 16), Scott Long said: > > > >>Actually, bgfsck unconditionally inserts a delay into every 8th i/o > >>operation to try to keep from saturating the disks. Unfortunately > >>this isn't terribly sophisticated and it results in bgfsck taking > >>an eternity whether the system is idle, loaded, or reniced. > > > >See http://dan.allantgroup.com/FreeBSD/fsck_ffs.diff for a patch > >that removes the delay if it's at the minimum value, and more fairly > >calculates disk wait time. This cuts bgfsck time from ~4 hours to > >20 minutes on my 36gb /usr. > > Looks like a reasonable fix. Do you want it reviewed and committed? Sure. I don't remember why I bumped up the max wait time to 2.5 sec, though. That's probably too long. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sun May 16 10:45:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA75216A4CE for ; Sun, 16 May 2004 10:45:31 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D46043D31 for ; Sun, 16 May 2004 10:45:31 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i4GHoku6098150; Sun, 16 May 2004 11:50:46 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40A7A8AB.2000707@freebsd.org> Date: Sun, 16 May 2004 11:45:15 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> <40A79A54.3090703@freebsd.org> <20040516170441.GA80376@dan.emsphone.com> <40A7A143.7070907@freebsd.org> <20040516173954.GB80376@dan.emsphone.com> In-Reply-To: <20040516173954.GB80376@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 17:45:31 -0000 Dan Nelson wrote: > In the last episode (May 16), Scott Long said: > >>Dan Nelson wrote: >> >>>In the last episode (May 16), Scott Long said: >>> >>> >>>>Actually, bgfsck unconditionally inserts a delay into every 8th i/o >>>>operation to try to keep from saturating the disks. Unfortunately >>>>this isn't terribly sophisticated and it results in bgfsck taking >>>>an eternity whether the system is idle, loaded, or reniced. >>> >>>See http://dan.allantgroup.com/FreeBSD/fsck_ffs.diff for a patch >>>that removes the delay if it's at the minimum value, and more fairly >>>calculates disk wait time. This cuts bgfsck time from ~4 hours to >>>20 minutes on my 36gb /usr. >> >>Looks like a reasonable fix. Do you want it reviewed and committed? > > > Sure. I don't remember why I bumped up the max wait time to 2.5 sec, > though. That's probably too long. > Maybe you were seeing effects of the syncer daemon? It can easily generate 2+ seconds of i/o on a flush. Scott From owner-freebsd-current@FreeBSD.ORG Sun May 16 12:13:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8523916A4CE; Sun, 16 May 2004 12:13:47 -0700 (PDT) Received: from herring.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CAA843D2F; Sun, 16 May 2004 12:13:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [10.0.0.2]) by herring.rabson.org (8.12.11/8.12.11) with ESMTP id i4GJDY6W001294; Sun, 16 May 2004 20:13:34 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 16 May 2004 20:13:33 +0100 User-Agent: KMail/1.6.1 References: <20040425094940.A50968@xorpc.icir.org> In-Reply-To: <20040425094940.A50968@xorpc.icir.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405162013.33894.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on herring.rabson.org X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: Luigi Rizzo cc: current@freebsd.org cc: net@freebsd.org Subject: Re: new arp code snapshot for review... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 19:13:47 -0000 On Sunday 25 April 2004 17:49, Luigi Rizzo wrote: > Here is a snapshot of the new arp code that i have been working on > lately, based a on Andre's ideas. (I say 'ARP' for brevity, what i > mean is the layer3-to-layer2 address translation code -- arp, aarp, > nd6 all fit in the category). Sorry for the delay but I've only just had reason to look at the arp code since I've recently been working on an implementation of rfc2734 IP over firewire. In your patch, you assume that the size of the link-level address is always six bytes. This assumption is not valid - from the looks of the existing arp code, people went to great lengths to avoid making this assumption throughout the networking code. For IP over firewire, the link-level address is sixteen bytes. Other link types have various sizes. You must use ifp->if_addrlen in the generic code to cope with this correctly. From owner-freebsd-current@FreeBSD.ORG Sun May 16 12:13:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8523916A4CE; Sun, 16 May 2004 12:13:47 -0700 (PDT) Received: from herring.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CAA843D2F; Sun, 16 May 2004 12:13:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [10.0.0.2]) by herring.rabson.org (8.12.11/8.12.11) with ESMTP id i4GJDY6W001294; Sun, 16 May 2004 20:13:34 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 16 May 2004 20:13:33 +0100 User-Agent: KMail/1.6.1 References: <20040425094940.A50968@xorpc.icir.org> In-Reply-To: <20040425094940.A50968@xorpc.icir.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405162013.33894.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on herring.rabson.org X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: Luigi Rizzo cc: current@freebsd.org cc: net@freebsd.org Subject: Re: new arp code snapshot for review... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 19:13:47 -0000 On Sunday 25 April 2004 17:49, Luigi Rizzo wrote: > Here is a snapshot of the new arp code that i have been working on > lately, based a on Andre's ideas. (I say 'ARP' for brevity, what i > mean is the layer3-to-layer2 address translation code -- arp, aarp, > nd6 all fit in the category). Sorry for the delay but I've only just had reason to look at the arp code since I've recently been working on an implementation of rfc2734 IP over firewire. In your patch, you assume that the size of the link-level address is always six bytes. This assumption is not valid - from the looks of the existing arp code, people went to great lengths to avoid making this assumption throughout the networking code. For IP over firewire, the link-level address is sixteen bytes. Other link types have various sizes. You must use ifp->if_addrlen in the generic code to cope with this correctly. From owner-freebsd-current@FreeBSD.ORG Sun May 16 15:07:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5738016A4D0 for ; Sun, 16 May 2004 15:07:03 -0700 (PDT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA0E43D2F for ; Sun, 16 May 2004 15:07:01 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i4GM6m4u010285; Mon, 17 May 2004 08:06:48 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i4GM6iLS016992; Mon, 17 May 2004 08:06:46 +1000 Date: Mon, 17 May 2004 08:06:46 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Marcel Moolenaar In-Reply-To: <20040516153420.GA13929@dhcp01.pn.xcllnt.net> Message-ID: <20040517071308.J2922@gamplex.bde.org> References: <40A26162.9030607@cronyx.ru> <20040512.200542.09569104.imp@bsdimp.com><40A4E2CB.2000007@cronyx.ru> <20040515041301.O22881@gamplex.bde.org> <40A537C8.1010407@cronyx.ru> <40A73401.5010703@cronyx.ru> <20040516153420.GA13929@dhcp01.pn.xcllnt.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Roman Kurakin Subject: Re: Sio & Puc memory mapped X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 22:07:03 -0000 On Sun, 16 May 2004, Marcel Moolenaar wrote: > On Sun, May 16, 2004 at 10:01:18PM +1000, Bruce Evans wrote: > > > > *snip*. The only fundamentally broken thing in the uart driver's > > defaults is that they have echos enabled, so an echo war results if 2 > > ports driven by the uart driver are connected and one of them happens > > to send a character before an ioctl can be done to set a useable state. > > The uart(4) driver uses TTYDEF_xFLAG from > Are the TTY defaults in that header wrong or are those merely a > good general set of defaults that one may need to tweak in ones > particular case (e.g. depending on the device or depending on > the open mode)? They are essentially a good set of defaults for interactive shells, or almost equivalently, for getty(8) and init(8). Note that init(8) knows noththing about termios. It just opens _PATH_CONSOLE and does i/o to it. Thus console drivers must do the same termios initialization that getty would do by default, so that the single user shell doesn't have a surprising termios state. Similarly, shells don't touch most of the termios state. They mostly just do i/o to open file descriptors supplied by their parent. Changes to the whole state are usually done using stty(8). E.g., "stty sane" sets to almost the defaults given in . Not so similarly, syslog(3) and syslogd(8) know nothing about termios. They just open _PATH_CONSOLE and write to it. Thus they depend on some of the driver's defaults (only the ones that affect output) like init(8). The driver's defaults need to be programmable at runtime so that the state for syslog* can be changed. They are essentially a good set of defaults for interactive shells, They are a bad set of defaults for terminal programs and most test programs. Only the issue with echo is critical. Terminal and test programs can handle noise from bogus echoes at the cost of extra complexity, but whatever they are connected to might not. Perhaps this was more of an issue on old slow systems with buggy drivers that didn't discard input on open. The echo war could take almost 100% of the CPU so many characters could be echoed before an ioctl could be run to kill the echoes. Bruce From owner-freebsd-current@FreeBSD.ORG Sun May 16 17:49:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C62A216A4CE for ; Sun, 16 May 2004 17:49:02 -0700 (PDT) Received: from fep10.012.net.il (fep10.012.net.il [212.117.129.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id B634B43D45 for ; Sun, 16 May 2004 17:49:01 -0700 (PDT) (envelope-from neoghost@012.net.il) Received: from Kronos ([80.179.94.120]) by fep10.012.net.il with ESMTP id <20040517004849.GWOW9343.fep10@Kronos> for ; Mon, 17 May 2004 03:48:49 +0300 From: "Alon Kramberg" Sender: "Alon Kramberg" To: Date: Mon, 17 May 2004 03:48:56 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-Index: AcQ7OgTt1dT2I8l6SqqnFyz40MiOygAdlOoA In-Reply-To: <20040516113528.4FFB516A4FD@hub.freebsd.org> Message-Id: <20040517004849.GWOW9343.fep10@Kronos> Subject: dear list manager X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 00:49:02 -0000 Dear list manager, My name is alon, my registered mail is neoghost@netvision.net.il the reason that I write to you personally is because I tried to unsubscribe several times with no eval with the automatic system. It seems that my confirmation mail is getting to the wrong address, Please remove me manually, I'm sorry to bother you with such a task, but it has become impossible for me to unregister (if you don't know which group I'm registered to, please remove all groups) Thanks in advance, Alon Kramberg. From owner-freebsd-current@FreeBSD.ORG Sun May 16 21:08:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A5616A4CE for ; Sun, 16 May 2004 21:08:18 -0700 (PDT) Received: from acelere.net (acelere.net [12.104.134.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09F9043D2F for ; Sun, 16 May 2004 21:08:18 -0700 (PDT) (envelope-from jamesb@acelere.net) Received: from acelere.net (colossus.acelere.net [192.168.0.111]) by acelere.net (8.12.3/8.12.3) with ESMTP id i4H48G6F055477 for ; Sun, 16 May 2004 21:08:17 -0700 (PDT) (envelope-from jamesb@acelere.net) From: "James Bowman" To: freebsd-current@freebsd.org Date: Sun, 16 May 2004 21:08:16 -0600 Message-Id: <20040516210816.M45998@acelere.net> X-Mailer: Open WebMail 1.64 20020415 X-OriginatingIP: 192.168.0.105 (jamesb) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: hostap TX fix in 5.x [Fwd: Re: wi hostap speed] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jamesb@acelere.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 04:08:18 -0000 I spent a few hours tinkering (tampering?) with this driver, and have not exactly a fix, but a clear indication of what the problem is. Verified (using the quick hack below): download speed geoes up from 170 kbytes/sec to 470 kbytes/sec, which is what I'd expect on an 11Mbps network. If anyone's interested, here it is: The Intersil manual on page 4-28 says that transmit packets need to have their TxRate field filled in with 10,20,55 or 110, depending on the transmission speed. The 4.X driver sets the field tx_frame.wi_tx_rate in function wihap_check_tx(), called from wi_start(). The 5.X driver calls this field frmhdr.wi_tx_rate, but leaves it zero. If you want to run at 11MBps, add a line frmhdr.wi_tx_rate = 110; in wi_start(), just before the call to wi_write_bap(). (Obviously, this is just a cheesy hack. The real code would have to find the actual tx rate. I just want to point out where the problem lies). From owner-freebsd-current@FreeBSD.ORG Sun May 16 23:26:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A341F16A4CE for ; Sun, 16 May 2004 23:26:49 -0700 (PDT) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 448E543D2F for ; Sun, 16 May 2004 23:26:48 -0700 (PDT) (envelope-from konfer@mikulas.com) Received: (qmail 26897 invoked by uid 89); 17 May 2004 08:26:46 +0200 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 17 May 2004 08:26:46 +0200 Received: from QMQPqq client ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) with QMQPqq id 25998-10; Mon, 17 May 2004 08:26:46 +0200 (CEST) Received: from unknown (HELO mikulas.com) (jiri@mikulas.com@195.122.218.78) by s1.vhost.cz with AES256-SHA encrypted SMTP; 17 May 2004 08:26:46 +0200 Message-ID: <40A85B24.1000300@mikulas.com> Date: Mon, 17 May 2004 08:26:44 +0200 From: Jiri Mikulas User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7b) Gecko/20040425 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: jamesb@acelere.net References: <20040516210816.M45998@acelere.net> In-Reply-To: <20040516210816.M45998@acelere.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at vhost.cz cc: scottp@tznet.com cc: current@freebsd.org Subject: Re: hostap TX fix in 5.x [Fwd: Re: wi hostap speed] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 06:26:49 -0000 Thanks! for your time ;) Jiri James Bowman wrote: >I spent a few hours tinkering (tampering?) with this driver, and have not >exactly a fix, but a clear indication of what the problem is. > >Verified (using the quick hack below): download speed geoes up from 170 >kbytes/sec to 470 kbytes/sec, which is what I'd expect on an 11Mbps network. > >If anyone's interested, here it is: > >The Intersil manual on page 4-28 says that transmit packets need to have their >TxRate field filled in with 10,20,55 or 110, depending on the transmission speed. > >The 4.X driver sets the field tx_frame.wi_tx_rate in function >wihap_check_tx(), called from wi_start(). > >The 5.X driver calls this field frmhdr.wi_tx_rate, but leaves it zero. >If you want to run at 11MBps, add a line > frmhdr.wi_tx_rate = 110; >in wi_start(), just before the call to wi_write_bap(). > >(Obviously, this is just a cheesy hack. The real code would have to find the >actual tx rate. I just want to point out where the problem lies). >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Sun May 16 23:50:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19A1C16A4CE for ; Sun, 16 May 2004 23:50:06 -0700 (PDT) Received: from mail.syd.swiftdsl.com.au (mail.syd.swiftdsl.com.au [202.154.83.58]) by mx1.FreeBSD.org (Postfix) with SMTP id DAEF743D58 for ; Sun, 16 May 2004 23:50:04 -0700 (PDT) (envelope-from dennis@djdata.dk) Received: (qmail 6856 invoked from network); 17 May 2004 06:50:02 -0000 Received: from unknown (HELO ?192.168.0.50?) (218.214.2.240) by mail.syd.swiftdsl.com.au with SMTP; 17 May 2004 06:50:02 -0000 From: Dennis Kristensen To: Cyrille Lefevre In-Reply-To: <20040511093634.GA41727@gits.dyndns.org> References: <0cc701c43704$fe189fc0$7890a8c0@dyndns.org> <200405110321.i4B3LFGI073037@bunrab.catwhisker.org> <20040511093634.GA41727@gits.dyndns.org> Content-Type: text/plain Message-Id: <1084776599.808.47.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 17 May 2004 16:50:00 +1000 Content-Transfer-Encoding: 7bit cc: freebsd current Subject: Re: bind timeouts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 06:50:06 -0000 On Tue, 2004-05-11 at 19:36, Cyrille Lefevre wrote: > On Mon, May 10, 2004 at 08:21:15PM -0700, David Wolfskill wrote: > > >From: "Cyrille Lefevre" > > CC -current > > > >for some times, I have some troubles to send e-mails, they > > >are returned w/ a host unknown error message (the relay)... > > >I spent a whole day to track down the problem w/o success. > > >... > > >however, it seems to be located around bind, but I don't know > > >if it's the client side or the server side which is broken, > > >maybe the TCP stack ! > > > > >I'm running -current last updated around 18 April 2004. > > > > I have been tracking both -STABLE and -CURRENT daily for quite a while; > > I don't recall seeing the symptoms you report. > > someone (Dennis Kristensen) reports me to have similar problems but > forget to CC -current :( After observing this for some days now (with no progress towards a solution), i think this might be a problem with the kernel rather than BIND. I have a 5.2.1-p5 system that shows the same symptons. It is lightly loaded and the above mentioned symptons start appearing after 1-3 days of uptime. A restart of BIND does not change anything, but af reboot of the system gives me another few days of correct operation. I hope the above can give someone more hints to what might be going on. I also hope to get some pointers to resource counters i can check to try an identify if something is leaking. The mail system is standard qmail, qmail-scanner with clamav and spamassassin and vpopmail - all from ports. Thanks for any hints or information in advance, Dennis Kristensen From owner-freebsd-current@FreeBSD.ORG Mon May 17 02:37:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E5FE16A4CE for ; Mon, 17 May 2004 02:37:21 -0700 (PDT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C05243D4C for ; Mon, 17 May 2004 02:37:20 -0700 (PDT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i4H9bG7Z004791 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 May 2004 11:37:16 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i4H9bFOt004790 for current@freebsd.org; Mon, 17 May 2004 11:37:15 +0200 (CEST) Date: Mon, 17 May 2004 11:37:15 +0200 From: Divacky Roman To: current@freebsd.org Message-ID: <20040517093715.GA4765@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: fdc issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 09:37:21 -0000 When I try to build fdc as a module it doesnt work the problem is in the sys/modules/Makefile which still tries to use ../../isa/ sources would be nice to have it fixed roman From owner-freebsd-current@FreeBSD.ORG Mon May 17 03:37:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9930A16A4CE; Mon, 17 May 2004 03:37:07 -0700 (PDT) Received: from fillmore.dyndns.org (port-212-202-49-130.reverse.qsc.de [212.202.49.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73EFC43D5C; Mon, 17 May 2004 03:37:06 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.34; FreeBSD) id 1BPfUU-0000xP-Hj; Mon, 17 May 2004 12:37:05 +0200 Message-ID: <40A895CE.9050505@fillmore-labs.com> Date: Mon, 17 May 2004 12:37:02 +0200 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: FreeBSD current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: Ruslan Ermilov Subject: RFC: new primary -depth n/-level n for find(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 10:37:07 -0000 find(1) should have a primary that is true iff the current file is n levels deep in the tree. This patch implements `-depth n' and an alias `-level n' which support the usual +/- modifiers, with `-depth +-1' essentially being a noop. The reason for implementing both was a discussion with ruslan, where he preferred `-depth [[+|-]level]', while I did not like the dual syntax that depth would have, because of its definition in IEEE 1003.1. Basically this allow one to do find /usr/ports -maxdepth 2 -name Tools -prune -o -level 2 -type d -print or find /usr/ports -maxdepth 2 -name Tools -prune -o -depth 2 -type d -print which currently can only be done with something like find /usr/ports -mindepth 2 -maxdepth 2 -regex '.*/Tools/[^/]*' -prune -o -type d -print which lists all port directories without Tools (this example lists some additional files, like packages, distfiles and CVS). I'm happy with the dual syntax, and probably I should change the manpage to state that `-depth' is equivalent to `-d' and `-depth n' equivalent to `-level n' if we go with this solution, but I'm also comfortable with having only one of `-level n' or `-depth n', I just wanted to have the functionality available. Any opinions? While I'm here, fix -maxdepth when depth-first traversal is done, try: find -d /usr -maxdepth 2 Which also doesn't give you warnings if any files on level three you don't really care for are unreadable. The patches for -CURRENT and -STABLE are at: http://people.freebsd.org/~eik/patches/find-depth.5.patch MD5 (find-depth.5.patch) = 5e52ac3c090726c609a9b582f6fbc993 http://people.freebsd.org/~eik/patches/find-depth.4.patch MD5 (find-depth.4.patch) = 6b67d3ac20c8fb5857d2d54f0365b518 -Oliver From owner-freebsd-current@FreeBSD.ORG Mon May 17 04:31:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7799116A4CE; Mon, 17 May 2004 04:31:44 -0700 (PDT) Received: from smtp.newipnet.com (5.Red-80-32-157.pooles.rima-tde.net [80.32.157.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97DBC43D54; Mon, 17 May 2004 04:31:40 -0700 (PDT) (envelope-from freebsd@newipnet.com) Received: by smtp.newipnet.com (ESMTP Server, from userid 511) id 9F2062051C; Mon, 17 May 2004 13:31:37 +0200 (CEST) Received: from madre (madre.newipnet.com [192.168.128.4]) by smtp.newipnet.com (ESMTP Server) with ESMTP id 8F36B20608; Mon, 17 May 2004 13:31:25 +0200 (CEST) Message-ID: <200405171330450414.08078360@192.168.128.16> In-Reply-To: <20040506151240.J19057@gamplex.bde.org> References: <200405021259230046.12648609@192.168.128.16> <200405022224250625.14440A3D@192.168.128.16> <20040505233435.B15444@gamplex.bde.org> <200405051746300245.2039F9A4@192.168.128.16> <20040506151240.J19057@gamplex.bde.org> X-Mailer: Courier 3.50.00.09.1097 (http://www.rosecitysoftware.com) (P) Date: Mon, 17 May 2004 13:30:45 +0200 From: "Carlos Velasco" To: "Bruce Evans" Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on atlas.newipnet.com X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=5.0 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.63 cc: freebsd-current@freebsd.org cc: scott@uk.freebsd.org cc: "M. Warner Losh" cc: freebsd-mobile@freebsd.org Subject: Re[5]: Modem + Network in Xircom cards, and maybe others X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 11:31:44 -0000 On 06/05/2004 at 16:44 Bruce Evans wrote: >On Wed, 5 May 2004, Carlos Velasco wrote: > >> On 06/05/2004 at 0:26 Bruce Evans wrote: >> >> >However, you may need only this part of it. This part permits software >> >interrupts to be delayed by 38 ticks instead of the expected maximim >> >of 2 ticks. I keep forgetting to fix this. Scaling by hz is not quite Yes, this patch in sio.c seems to work perfectly. So I think sio swi is being delayed somewhere by Giant or any other thing. >> >right, because hz may be set to values that are too small to work all >> >the time or even most of the time. There is a clamp to 128 (min), but >> >this is a bit small. E.g., with hz = 1000 and speed = 115200, the >> >original code in the above gives cp4ticks = 44 and ibufsize = 128. If what about if we fix the value or making it adjustable via sysctl? >The broken interrupt priorities are easy to see in "ps laxw | sort -n +4" >output. Note that the highest priorities are numerically lowest: > 0 27 0 0 -48 0 0 12 - WL ?? 0:00.06 (swi8: >tty:cy+ clock) > > [I think this is supposed to be the low priority softclock ithread > (the "slow" cy and sio SWIs attach to it and misname themselves as > tty:cy and tty:sio instead of clk:cy and clk:sio). It actually has > _highest_ priority among SWIs, so the problem is sort of the opposite > of what I thought, but mostly worse. The "slow" cy and sio SWIs > actually have the same bogus high priority, so they don't compete > with other SWIs. However, they compete with softclock, and all > other SWIs have lower priority than softclock so they don't even > compete with it. This is the reverse of what is supposed to > happen. I think softclock starts with the correct low priority, but > its priority gets clobbered when the cy and sio SWIs attach to it. > > 0 37 0 0 -48 0 0 12 - WL ?? 0:00.00 (swi0: >tty:cy+) > > [I think this is the "fast" cy and sio SWI. Verbose names which get > truncated complicate debugging.] I have here: 0 22 0 0 -80 0 0 12 - WL ?? 0:00.01 (irq11: cbb0 cbb1+) ... 0 28 0 0 -48 0 0 12 - WL ?? 0:01.74 (swi8: tty:sio clock) 0 39 0 0 -48 0 0 12 - WL ?? 0:00.00 (swi0: tty:sio) So, I assume you are right. >> I believe this patch to sio.c is only a temporary solution that should be >> removed when GIANT dissapears in most drivers, am I right? > >No, it (the cp4ticks one) is a more general patch, though it is temporary >because it is not in its final form. Best-case interrupt latency cannot >be guaranteed for SWIs, and even a saftey margin of a factor of 4 is not >enough even without the Giant and priority bugs, since it doesn't scale >right when "hz" is configured to large values, and configuring "hz" to >too-large values is now encouraged by DEVICE_POLLING. Could we commit it or something similar? I think sio is normal mode is broken for high speeds cause this like my problem with modem pccard. Regards, Carlos Velasco From owner-freebsd-current@FreeBSD.ORG Mon May 17 04:37:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88FEA16A4CE; Mon, 17 May 2004 04:37:25 -0700 (PDT) Received: from smtp.newipnet.com (5.Red-80-32-157.pooles.rima-tde.net [80.32.157.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7124643D2D; Mon, 17 May 2004 04:37:22 -0700 (PDT) (envelope-from freebsd@newipnet.com) Received: by smtp.newipnet.com (ESMTP Server, from userid 511) id B1CDD2065D; Mon, 17 May 2004 13:37:20 +0200 (CEST) Received: from madre (madre.newipnet.com [192.168.128.4]) by smtp.newipnet.com (ESMTP Server) with ESMTP id F23642051A; Mon, 17 May 2004 13:37:12 +0200 (CEST) Message-ID: <200405171336320804.080CD05E@192.168.128.16> In-Reply-To: <20040505.155926.128442915.imp@bsdimp.com> References: <200405051311330554.1F584985@192.168.128.16> <20040505233435.B15444@gamplex.bde.org> <200405051746300245.2039F9A4@192.168.128.16> <20040505.155926.128442915.imp@bsdimp.com> X-Mailer: Courier 3.50.00.09.1097 (http://www.rosecitysoftware.com) (P) Date: Mon, 17 May 2004 13:36:32 +0200 From: "Carlos Velasco" To: "M. Warner Losh" Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====_108479379229275=_" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on atlas.newipnet.com X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=5.0 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.63 cc: freebsd-current@freebsd.org cc: scott@uk.freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re[2]: Modem + Network in Xircom cards, and maybe others X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 11:37:25 -0000 --=====_108479379229275=_ Content-Type: text/plain; charset="us-ascii" On 05/05/2004 at 15:59 M. Warner Losh wrote: >In message: <200405051746300245.2039F9A4@192.168.128.16> > "Carlos Velasco" writes: >: I'm patching it to activate both functions (usually modem/serial and >: network). >: Network is in xe driver, however I'm passing modem to sio. >: It works, however sio reports interrupt-level buffer overflows when I'm >: above 2400bps, losing characters, and here is where I'm lost. > >I don't think you are getting interrupts like you should. Warner, I think my patch is ok, problem is related to sio in normal mode (i think). Aplying a last patch into sio.c makes my xircom modem work perfectly. Have you tested other 16 bits cards? I'm attaching my last complete patch. Regards, Carlos Velasco --=====_108479379229275=_ Content-Type: application/octet-stream; name="xircom_2.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xircom_2.patch" ZGlmZiAtcnUgc3lzL2Rldi9wY2NhcmQvcGNjYXJkLmMgc3lzbmV3L2Rldi9w Y2NhcmQvcGNjYXJkLmMKLS0tIHN5cy9kZXYvcGNjYXJkL3BjY2FyZC5jCVdl ZCBNYXIgMTcgMTc6NTA6MzggMjAwNAorKysgc3lzbmV3L2Rldi9wY2NhcmQv cGNjYXJkLmMJU2F0IE1heSAgMSAwOTo0Nzo1NyAyMDA0CkBAIC05NTUsOCAr OTU1LDggQEAKIAlzdHJ1Y3QgcGNjYXJkX3NvZnRjICpzYyA9IFBDQ0FSRF9T T0ZUQyhidXMpOwogCiAJZGV2aWNlX3ByaW50ZihidXMsICI8dW5rbm93biBj YXJkPiIpOwotCXByaW50ZigiIChtYW51ZmFjdHVyZXI9MHglMDR4LCBwcm9k dWN0PTB4JTA0eCkgYXQgZnVuY3Rpb24gJWRcbiIsCi0JICBzYy0+Y2FyZC5t YW51ZmFjdHVyZXIsIHNjLT5jYXJkLnByb2R1Y3QsIGZ1bmMtPm51bWJlcik7 CisJcHJpbnRmKCIgKG1hbnVmYWN0dXJlcj0weCUwNHgsIHByb2R1Y3Q9MHgl MDR4LCBwcm9kZXh0PTB4JTAyeCkgYXQgZnVuY3Rpb24gJWRcbiIsCisJICBz Yy0+Y2FyZC5tYW51ZmFjdHVyZXIsIHNjLT5jYXJkLnByb2R1Y3QsIHNjLT5j YXJkLnByb2RleHQsIGZ1bmMtPm51bWJlcik7CiAJZGV2aWNlX3ByaW50Zihi dXMsICIgICBDSVMgaW5mbzogJXMsICVzLCAlc1xuIiwgc2MtPmNhcmQuY2lz MV9pbmZvWzBdLAogCSAgc2MtPmNhcmQuY2lzMV9pbmZvWzFdLCBzYy0+Y2Fy ZC5jaXMxX2luZm9bMl0pOwogCXJldHVybjsKQEAgLTEwNzUsNiArMTA3NSw3 IEBACiAJaW50IHBhc3N0aHJvdWdoID0gKGRldmljZV9nZXRfcGFyZW50KGNo aWxkKSAhPSBkZXYpOwogCWludCBpc2RlZmF1bHQgPSAoc3RhcnQgPT0gMCAm JiBlbmQgPT0gfjBVTCAmJiBjb3VudCA9PSAxKTsKIAlzdHJ1Y3QgcmVzb3Vy Y2UgKnIgPSBOVUxMOworICAgICAgIHVfaW50IGFsaWduOwogCiAJLyogWFhY IEknbSBubyBsb25nZXIgc3VyZSB0aGlzIGlzIHJpZ2h0ICovCiAJaWYgKHBh c3N0aHJvdWdoKSB7CkBAIC0xMDkwLDggKzEwOTEsMTUgQEAKIAlpZiAocmxl ID09IE5VTEwgfHwgcmxlLT5yZXMgPT0gTlVMTCkgewogCQkvKiBEbyB3ZSB3 YW50IHRoaXMgZGV2aWNlIHRvIG93biBpdD8gKi8KIAkJLyogWFhYIEkgdGhp bmsgc28sIGJ1dCB0aGF0IG1pZ2h0IGJlIGxhbWUgWFhYICovCisKKyAgICAg ICAgICAgICAgIC8qIGZvcmNlIDY0ayBwYWdlIGFsaWduICovCisgICAgICAg ICAgICAgICBpZiAodHlwZSA9PSBTWVNfUkVTX01FTU9SWSkKKyAgICAgICAg ICAgICAgICAgICBhbGlnbiA9IChmbGFncyAmIH5SRl9BTElHTk1FTlRfTUFT SykgfAorICAgICAgICAgICAgICAgICAgICAgICBybWFuX21ha2VfYWxpZ25t ZW50X2ZsYWdzKDY0KjEwMjQpOworICAgICAgICAgICAgICAgZWxzZQorICAg ICAgICAgICAgICAgICAgIGFsaWduID0gZmxhZ3M7CiAJCXIgPSBidXNfYWxs b2NfcmVzb3VyY2UoZGV2LCB0eXBlLCByaWQsIHN0YXJ0LCBlbmQsCi0JCSAg Y291bnQsIGZsYWdzIC8qIFhYWCBhbGlnbWVudD8gKi8pOworICAgICAgICAg ICAgICAgICBjb3VudCwgYWxpZ24pOwogCQlpZiAociA9PSBOVUxMKQogCQkg ICAgZ290byBiYWQ7CiAJCXJlc291cmNlX2xpc3RfYWRkKCZkaW5mby0+cmVz b3VyY2VzLCB0eXBlLCAqcmlkLApkaWZmIC1ydSBzeXMvZGV2L3BjY2FyZC9w Y2NhcmRfY2lzLmMgc3lzbmV3L2Rldi9wY2NhcmQvcGNjYXJkX2Npcy5jCi0t LSBzeXMvZGV2L3BjY2FyZC9wY2NhcmRfY2lzLmMJTW9uIEFwciAxMiAyMDo1 NjozNCAyMDA0CisrKyBzeXNuZXcvZGV2L3BjY2FyZC9wY2NhcmRfY2lzLmMJ U2F0IE1heSAgMSAwOTo0Nzo1NyAyMDA0CkBAIC05Niw2ICs5Niw4IEBACiAK IAlzdGF0ZS5wZiA9IE5VTEw7CiAKKwlzdGF0ZS5jYXJkLT5tZmMgPSAwOwor CiAJdHNsZWVwKCZzdGF0ZSwgMCwgInBjY2FyZCIsIGh6KTsKIAlpZiAocGNj YXJkX3NjYW5fY2lzKHNjLT5kZXYsIHBjY2FyZF9wYXJzZV9jaXNfdHVwbGUs CiAJICAgICZzdGF0ZSkgPT0gLTEpCkBAIC02NjMsNiArNjY1LDcgQEAKIAkJ ICogdXAuCiAJCSAqLwogCQlzdGF0ZS0+Z290bWZjID0gMTsKKwkJc3RhdGUt PmNhcmQtPm1mYyA9IDE7CiAJCWJyZWFrOwogI2lmZGVmIFBDQ0FSRENJU0RF QlVHCiAJY2FzZSBDSVNUUExfREVWSUNFOgpAQCAtODAzLDYgKzgwNiw0MiBA QAogCiAJCQlTVEFJTFFfSU5TRVJUX1RBSUwoJnN0YXRlLT5jYXJkLT5wZl9o ZWFkLCBzdGF0ZS0+cGYsCiAJCQkgICAgcGZfbGlzdCk7CisJCX0gZWxzZSBp ZiAoc3RhdGUtPnBmLT5mdW5jdGlvbiAhPSBQQ0NBUkRfRlVOQ1RJT05fVU5T UEVDKSB7CisJCQkvKiBXZSBoYXZlIGEgbm9uLU1GQyBjb21wbGlhbnQgY2Fy ZCwgaXQgcHV0cyBtb3JlCisJCQkgKiB0aGFuIDEgRlVOQ0lEIGluIHRoZSBD SVMgd2l0aG91dCBMT05HTElOSy4KKwkJCSAqIGEpIFdlIHB1dCB0aGUgZnVu Y3Rpb25zIGluIHRoZSBsaXN0IGFsYSBNRkMuCisJCQkgKiBiKSBDb3B5IGxh c3QgQ0ZHIGVudHJ5IGZvciBwcmV2aW91cyBmdW5jdGlvbiwKKwkJCSAqICAg IG5vdCBzdXJlIGlmIHRoaXMgaXMgcmlnaHQsIGJ1dCB1c3VhbGx5IHdvcmtz LgorCQkJICovCisJCQlzdHJ1Y3QgcGNjYXJkX2NvbmZpZ19lbnRyeSAqY2Zl LCAqcWNmZTsKKwkJCXVpbnQzMl90CWNjcl9iYXNlID0gc3RhdGUtPnBmLT5j Y3JfYmFzZTsKKwkJCXVpbnQzMl90CWNjcl9tYXNrID0gc3RhdGUtPnBmLT5j Y3JfbWFzazsKKworCQkJY2ZlID0gTlVMTDsKKwkJCVNUQUlMUV9GT1JFQUNI KHFjZmUsICZzdGF0ZS0+cGYtPmNmZV9oZWFkLCBjZmVfbGlzdCkgeworCQkJ CWlmIChxY2ZlLT5udW1iZXIgPT0gc3RhdGUtPnBmLT5sYXN0X2NvbmZpZ19p bmRleCkgeworCQkJCWNmZSA9IChzdHJ1Y3QgcGNjYXJkX2NvbmZpZ19lbnRy eSAqKQorCQkJCSAgICBtYWxsb2Moc2l6ZW9mKCpjZmUpLCBNX0RFVkJVRiwg TV9OT1dBSVQpOworCQkJCSpjZmUgPSAqcWNmZTsKKwkJCQlicmVhazsKKwkJ CQl9CisJCQl9CisKKwkJCXN0YXRlLT5wZiA9IG1hbGxvYyhzaXplb2YoKnN0 YXRlLT5wZiksIE1fREVWQlVGLAorCQkJICAgIE1fTk9XQUlUIHwgTV9aRVJP KTsKKwkJCXN0YXRlLT5wZi0+bnVtYmVyID0gc3RhdGUtPmNvdW50Kys7CisJ CQlzdGF0ZS0+cGYtPmxhc3RfY29uZmlnX2luZGV4ID0gY2ZlLT5udW1iZXI7 CisJCQlzdGF0ZS0+cGYtPmNjcl9iYXNlID0gY2NyX2Jhc2U7CisJCQlzdGF0 ZS0+cGYtPmNjcl9tYXNrID0gY2NyX21hc2s7CisKKwkJCVNUQUlMUV9JTklU KCZzdGF0ZS0+cGYtPmNmZV9oZWFkKTsKKwkJCWlmIChjZmUpIAorCQkJCVNU QUlMUV9JTlNFUlRfVEFJTCgmc3RhdGUtPnBmLT5jZmVfaGVhZCwKKwkJCQkg ICAgY2ZlLCBjZmVfbGlzdCk7CisKKwkJCVNUQUlMUV9JTlNFUlRfVEFJTCgm c3RhdGUtPmNhcmQtPnBmX2hlYWQsIHN0YXRlLT5wZiwKKwkJCSAgICBwZl9s aXN0KTsKKwkJCiAJCX0KIAkJc3RhdGUtPnBmLT5mdW5jdGlvbiA9IHBjY2Fy ZF90dXBsZV9yZWFkXzEodHVwbGUsIDApOwogCmRpZmYgLXJ1IHN5cy9kZXYv cGNjYXJkL3BjY2FyZHZhci5oIHN5c25ldy9kZXYvcGNjYXJkL3BjY2FyZHZh ci5oCi0tLSBzeXMvZGV2L3BjY2FyZC9wY2NhcmR2YXIuaAlTdW4gTm92ICAy IDIwOjE4OjE5IDIwMDMKKysrIHN5c25ldy9kZXYvcGNjYXJkL3BjY2FyZHZh ci5oCVNhdCBNYXkgIDEgMDk6NDc6NTcgMjAwNApAQCAtMTc5LDYgKzE3OSw3 IEBACiAJaW50MzJfdAkJcHJvZHVjdDsKICNkZWZpbmUJUENNQ0lBX1BST0RV Q1RfSU5WQUxJRAkJLTEKIAlpbnQxNl90CQlwcm9kZXh0OworCWludAkJbWZj OwogCXVpbnQxNl90CWVycm9yOwogI2RlZmluZQlQQ01DSUFfQ0lTX0lOVkFM SUQJCXsgTlVMTCwgTlVMTCwgTlVMTCwgTlVMTCB9CiAJU1RBSUxRX0hFQUQo LCBwY2NhcmRfZnVuY3Rpb24pIHBmX2hlYWQ7CkBAIC0yODQsOCArMjg1LDkg QEAKICNkZWZpbmUJUENDQVJEX1NQQUNFX0lPCQkyCiAKICNkZWZpbmUJcGNj YXJkX21mYyhzYykJCQkJCQkJXAotCQkoU1RBSUxRX0ZJUlNUKCYoc2MpLT5j YXJkLnBmX2hlYWQpICYmCQkJXAotCQkgU1RBSUxRX05FWFQoU1RBSUxRX0ZJ UlNUKCYoc2MpLT5jYXJkLnBmX2hlYWQpLHBmX2xpc3QpKQorCQkoc2MtPmNh cmQubWZjKQorLyoJCShTVEFJTFFfRklSU1QoJihzYyktPmNhcmQucGZfaGVh ZCkgJiYJCQlcCisJCSBTVEFJTFFfTkVYVChTVEFJTFFfRklSU1QoJihzYykt PmNhcmQucGZfaGVhZCkscGZfbGlzdCkpICovCiAKICNkZWZpbmUJcGNjYXJk X2lvX2FsbG9jKHBmLCBzdGFydCwgc2l6ZSwgYWxpZ24sIHBjaW9wKQkJCVwK IAkocGNjYXJkX2NoaXBfaW9fYWxsb2MoKHBmKS0+c2MtPnBjdCwgcGYtPnNj LT5wY2gsIChzdGFydCksCVwKZGlmZiAtcnUgc3lzL2Rldi9zaW8vc2lvLmMg c3lzbmV3L2Rldi9zaW8vc2lvLmMKLS0tIHN5cy9kZXYvc2lvL3Npby5jCU1v biBNYXkgIDMgMjI6MzU6MjggMjAwNAorKysgc3lzbmV3L2Rldi9zaW8vc2lv LmMJV2VkIE1heSAgNSAxMzowNDoxNCAyMDA0CkBAIC0yMzc0LDcgKzIzNzQs NyBAQAogCSAqIChhYm91dCAzIHRpY2tzIGlmIGlucHV0IGZsb3cgY29udHJv bCBpcyBub3QgdXNlZCBvciBub3QgaG9ub3VyZWQsCiAJICogYnV0IGEgYml0 IGxlc3MgZm9yIENTNS1DUzcgbW9kZXMpLgogCSAqLwotCWNwNHRpY2tzID0g c3BlZWQgLyAxMCAvIGh6ICogNDsKKwljcDR0aWNrcyA9IHNwZWVkIC8gMTAg LyBoeiAqIDQwOwogCWZvciAoaWJ1ZnNpemUgPSAxMjg7IGlidWZzaXplIDwg Y3A0dGlja3M7KQogCQlpYnVmc2l6ZSA8PD0gMTsKIAlpZiAoaWJ1ZnNpemUg PT0gY29tLT5pYnVmc2l6ZSkgewpkaWZmIC1ydSBzeXMvZGV2L3hlL2lmX3hl X3BjY2FyZC5jIHN5c25ldy9kZXYveGUvaWZfeGVfcGNjYXJkLmMKLS0tIHN5 cy9kZXYveGUvaWZfeGVfcGNjYXJkLmMJU3VuIEFwciAxMSAxNjozNDoyOSAy MDA0CisrKyBzeXNuZXcvZGV2L3hlL2lmX3hlX3BjY2FyZC5jCVNhdCBNYXkg IDEgMDk6NDg6MjQgMjAwNApAQCAtNDAyLDYgKzQwMiw3IEBACiAJY29uc3Qg c3RydWN0IHhlX3BjY2FyZF9wcm9kdWN0KiB4cHA7CiAJdV9pbnQxNl90IHBy b2RleHQ7CiAKKwogCURFVlBSSU5URigyLCAoZGV2LCAicGNjYXJkX3Byb2R1 Y3RfbWF0Y2hcbiIpKTsKIAogCXhwcCA9IChjb25zdCBzdHJ1Y3QgeGVfcGNj YXJkX3Byb2R1Y3QqKWVudDsKQEAgLTQwOSw2ICs0MTAsOCBAQAogCiAJaWYg KHhwcC0+cHJvZGV4dCAhPSBwcm9kZXh0KQogCQl2cGZtYXRjaCA9IDA7CisJ ZWxzZQorCQl2cGZtYXRjaCsrOwogCiAJcmV0dXJuICh2cGZtYXRjaCk7CiB9 CkBAIC00MTYsOCArNDE5LDE5IEBACiBzdGF0aWMgaW50CiB4ZV9wY2NhcmRf bWF0Y2goZGV2aWNlX3QgZGV2KQogeworCWludAkJZXJyb3IgPSAwOworCXVf aW50MzJfdAlmY24gPSBQQ0NBUkRfRlVOQ1RJT05fVU5TUEVDOwogCWNvbnN0 IHN0cnVjdCBwY2NhcmRfcHJvZHVjdCAqcHA7CiAKKwllcnJvciA9IHBjY2Fy ZF9nZXRfZnVuY3Rpb24oZGV2LCAmZmNuKTsKKwlpZiAoZXJyb3IgIT0gMCkK KwkJcmV0dXJuIChlcnJvcik7CisJLyoKKwkgKiBJZiBub3QgYSBuZXR3b3Jr IGNhcmQsIHdlIGFyZSBub3QgdGhlIHJpZ2h0IGRyaXZlci4KKwkgKi8KKwlp ZiAoZmNuICE9IFBDQ0FSRF9GVU5DVElPTl9ORVRXT1JLKQorCQlyZXR1cm4g KEVOWElPKTsKKwogCURFVlBSSU5URigyLCAoZGV2LCAicGNjYXJkX21hdGNo XG4iKSk7CiAKIAlwcCA9IChjb25zdCBzdHJ1Y3QgcGNjYXJkX3Byb2R1Y3Qq KXhlX3BjY2FyZF9wcm9kdWN0czsKQEAgLTQyNSw3ICs0MzksNiBAQAogCWlm ICgocHAgPSBwY2NhcmRfcHJvZHVjdF9sb29rdXAoZGV2LCBwcCwKIAkgICAg IHNpemVvZih4ZV9wY2NhcmRfcHJvZHVjdHNbMF0pLCB4ZV9wY2NhcmRfcHJv ZHVjdF9tYXRjaCkpICE9IE5VTEwpCiAJCXJldHVybiAoMCk7Ci0KIAlyZXR1 cm4gKEVJTyk7CiB9CiAK --=====_108479379229275=_-- From owner-freebsd-current@FreeBSD.ORG Sun May 16 11:32:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B19916A4CE for ; Sun, 16 May 2004 11:32:55 -0700 (PDT) Received: from emboss.bossbox.com (cpc1-tall1-5-0-cust89.dbln.cable.ntl.com [81.98.88.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4C7643D45 for ; Sun, 16 May 2004 11:32:52 -0700 (PDT) (envelope-from Brian@bossbox.com) Received: from bogbox (bogbox.bossbox.com [192.168.0.2]) by emboss.bossbox.com (8.12.10/8.12.10) with ESMTP id i4GITtj9059053 for ; Sun, 16 May 2004 19:29:56 +0100 (IST) (envelope-from Brian@bossbox.com) Message-Id: <200405161829.i4GITtj9059053@emboss.bossbox.com> From: "Brian " To: Date: Wed, 26 May 2004 19:32:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-Index: AcRDT9sVjs0WZ02IQXWCWLMo8rUcRQ== X-Mailman-Approved-At: Mon, 17 May 2004 04:46:33 -0700 Subject: IBM Thinkpad T4 Wireless issue (Evil Project) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 18:32:55 -0000 I have just cvsup'd to 5.2-CURRENT And built the ndis driver # cd /sys/modules/ndis # make; make load # cd /sys/modules/if_ndis # ndiscvt -i w70n51.inf -s w70n51.sys -o ndis_driver_data.h # make; make load Issuing ifconfig ndis0 inet 192.168.0.11 ssid APID netmask 0xffffff00 After this I get ndis0: link up and checking the AP logs I see it's connected. But checking ifconfig ndis0 has no ip address and when I try and give it one manually I get Ifconfig: ioctl (SIOCAIFADDR): File exists I don't run a DHCP server locally so I need to assign it an ip address Can anyone provide meet with some information on something I might be over looking? If you could cc me in replies as I am not subscribed to the list. Thanks em0: flags=8843 mtu 1500 options=3 inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::20d:60ff:fe11:f832%em0 prefixlen 64 scopeid 0x1 ether 00:0d:60:11:f8:32 media: Ethernet autoselect status: no carrier plip0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 ndis0: flags=8843 mtu 1500 inet6 fe80::20c:f1ff:fe07:a717%ndis0 prefixlen 64 scopeid 0x4 ether 00:0c:f1:07:a7:17 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid BOSSBOX 1:BOSSBOX channel 11 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 Copyright (c) 1992-2004 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.2-CURRENT #0: Sun May 16 17:46:04 IST 2004 root@centrino.bossbox,:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc09ec000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc09ec26c. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1600MHz (599.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9f9bf real memory = 536215552 (511 MB) avail memory = 514990080 (491 MB) random: Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [GIANT-LOCKED] acpi_ec0: port 0x66,0x62 on acpi0 pcibios: BIOS version 2.10 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 11 pcib0: slot 29 INTC is routed to irq 11 pcib0: slot 29 INTD is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 agp0: Reserved 0x10000000 bytes for rid 0x10 type 3 at 0xd0000000 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1800 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1820 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1840 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pcib2: slot 0 INTA is routed to irq 11 pcib2: slot 0 INTB is routed to irq 11 pcib2: slot 1 INTA is routed to irq 11 pcib2: slot 2 INTA is routed to irq 11 cbb0: mem 0xb0000000-0xb0000fff irq 11 at device 0.0 on pci2 cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xb0000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0xb1000000-0xb1000fff irq 11 at device 0.1 on pci2 cbb1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xb1000000 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 em0: port 0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0220000-0xc023ffff irq 11 at device 1.0 on pci2 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xc0220000 em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0x8000 em0: [GIANT-LOCKED] em0: Ethernet address: 00:0d:60:11:f8:32 em0: Speed:N/A Duplex:N/A pci2: at device 2.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1860 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: at 0x1f0 irq 14 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: at 0x170 irq 15 on atapci0 pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) pci0: at device 31.6 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x3bc-0x3c3 irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: