From owner-freebsd-mobile Mon Sep 23 09:21:01 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27393 for mobile-outgoing; Mon, 23 Sep 1996 09:21:01 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA27332; Mon, 23 Sep 1996 09:20:54 -0700 (PDT) Received: from rocky.mt.sri.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v5DkY-0008ueC; Mon, 23 Sep 96 09:20 PDT Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA02696; Mon, 23 Sep 1996 10:09:20 -0600 (MDT) Date: Mon, 23 Sep 1996 10:09:20 -0600 (MDT) Message-Id: <199609231609.KAA02696@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: current@freebsd.org, mobile@freebsd.org Subject: Re: 3C589b + ep driver In-Reply-To: <199609231511.BAA00512@walkabout.asstdc.com.au> References: <199609231511.BAA00512@walkabout.asstdc.com.au> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Added -mobile ] > I'm still fighting with my laptop (100MHz TP560) and the ep driver. > Intermittently, the "link OK" light on my hub goes out and ifconfig reports > the driver hung in the OACTIVE state. FWIW, I'm now starting to see these as well with the if_zp driver under -current, and I *NEVER* saw them before in the almost 2 years I ran 2.1 and 2.1.5. However, looking at the code it appears that the other than someone running it through indent which screwed up a lot of the formatting, there aren't that many changes to affect the low-level functionality of the driver. So far I'm seeing the addtion of IPX support, staticizing functions and data and removing dead code, the removal of TRAILERS, BPF changes, and other misc. formatting stuff. But, nothing jumps out at me which should affect the driver itself, so I'm suspecting something in the other code, which also makes no sense. > Since it seems that others are now having similar experiences with similarly > structured drivers (e.g. if_vx), I wonder if someone could shed some light > on what is going on (and how to fix it :-)) ? This is what also implies that it's not something necessarily specific to the drivers, but something that changes which might require all of the drivers to be modified. Nate From owner-freebsd-mobile Mon Sep 23 09:42:11 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05617 for mobile-outgoing; Mon, 23 Sep 1996 09:42:11 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA05543; Mon, 23 Sep 1996 09:42:00 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id CAA04350 Tue, 24 Sep 1996 02:41:20 +1000 (EST) From: michael butler Message-Id: <199609231641.CAA04350@asstdc.scgt.oz.au> Subject: Re: 3C589b + ep driver To: nate@mt.sri.com (Nate Williams) Date: Tue, 24 Sep 1996 02:41:19 +1000 (EST) Cc: current@freebsd.org, mobile@freebsd.org In-Reply-To: <199609231609.KAA02696@rocky.mt.sri.com> from "Nate Williams" at Sep 23, 96 10:09:20 am X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams writes: > FWIW, I'm now starting to see these as well with the if_zp driver under > -current, and I *NEVER* saw them before in the almost 2 years I ran 2.1 > and 2.1.5. I tried the zp driver from yesterday's -current and couldn't get it to work for me (which is odd because I installed using it in July :-() > This is what also implies that it's not something necessarily specific > to the drivers, but something that changes which might require all of > the drivers to be modified. I'm tempted to think (but without proof since I don't have sufficient hardware documentation - any, in fact) that the present drivers are timing sensitive (increasing CPU load causes more frequent failures) and that some other changes in the kernel have provoked a latent weakness. Honestly, I can't see anything wrong with it the way it is so "poking" bits of code to see what has any impact at all is the only way I can approach it. Tonight, I looked at Guido's "newif_vx" stuff on freefall which, amongst other things, breaks out the TX_STATUS stuff into a separate function and has a similar interrupt service restructure to the one I tried. I might try the "BROKEN_AVAIL" strategy to see if that affects the problem, michael From owner-freebsd-mobile Mon Sep 23 09:57:57 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA11376 for mobile-outgoing; Mon, 23 Sep 1996 09:57:57 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA11298; Mon, 23 Sep 1996 09:57:44 -0700 (PDT) Received: from rocky.mt.sri.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v5EK8-0008tYC; Mon, 23 Sep 96 09:57 PDT Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA02885; Mon, 23 Sep 1996 10:46:22 -0600 (MDT) Date: Mon, 23 Sep 1996 10:46:22 -0600 (MDT) Message-Id: <199609231646.KAA02885@rocky.mt.sri.com> From: Nate Williams To: michael butler Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org, mobile@freebsd.org Subject: Re: 3C589b + ep driver In-Reply-To: <199609231641.CAA04350@asstdc.scgt.oz.au> References: <199609231609.KAA02696@rocky.mt.sri.com> <199609231641.CAA04350@asstdc.scgt.oz.au> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > FWIW, I'm now starting to see these as well with the if_zp driver under > > -current, and I *NEVER* saw them before in the almost 2 years I ran 2.1 > > and 2.1.5. > > I tried the zp driver from yesterday's -current and couldn't get it to work > for me (which is odd because I installed using it in July :-() > > > This is what also implies that it's not something necessarily specific > > to the drivers, but something that changes which might require all of > > the drivers to be modified. > > I'm tempted to think (but without proof since I don't have sufficient > hardware documentation - any, in fact) that the present drivers are timing > sensitive (increasing CPU load causes more frequent failures) and that some > other changes in the kernel have provoked a latent weakness. That's possible, but the CPU load wasn't an issue with me. The network load was an issue, but in the 2.1 days I was running the box as an NFS client where I mounted /usr/src & /usr/obj, and re-built the world on my laptop. If that's not a lot of network load on an ethernet card, I don't know what is. :) Recently it's been locking up under remote CVS heavy loads (though not as heavy as before) which can be fixed by a simple 'ifconfig zp0 down; ifconfig zp0 up'. It hasn't went down since then under similar loads, but I was updating the sources from a *very* old version of -current to the latest bits which caused alot more traffic to be sent out. The only thing I can think of that would cause the lockups are missed interrupts, so Bruce would probably be the expert in this. Nate From owner-freebsd-mobile Tue Sep 24 05:55:12 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA29965 for mobile-outgoing; Tue, 24 Sep 1996 05:55:12 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA29826; Tue, 24 Sep 1996 05:54:54 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id WAA05772 Tue, 24 Sep 1996 22:53:42 +1000 (EST) From: michael butler Message-Id: <199609241253.WAA05772@asstdc.scgt.oz.au> Subject: Re: 3C589b + ep driver To: nate@mt.sri.com Date: Tue, 24 Sep 1996 22:53:42 +1000 (EST) Cc: current@freebsd.org, mobile@freebsd.org In-Reply-To: <199609231641.CAA04350@asstdc.scgt.oz.au> from "michael butler" at Sep 24, 96 02:41:19 am X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: > Tonight, I looked at Guido's "newif_vx" stuff on freefall which, amongst > other things, breaks out the TX_STATUS stuff into a separate function and > has a similar interrupt service restructure to the one I tried. I might try > the "BROKEN_AVAIL" strategy to see if that affects the problem, Adding checks for sufficient space in the card's TX FIFO on the assumption that the "space available" status doesn't generate an appropriate interrupt has no impact whatsoever on the problem :-( michael From owner-freebsd-mobile Thu Sep 26 08:19:27 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05877 for mobile-outgoing; Thu, 26 Sep 1996 08:19:27 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA05849 for ; Thu, 26 Sep 1996 08:19:23 -0700 (PDT) Received: from rocky.mt.sri.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v6IDg-00091tC; Thu, 26 Sep 96 08:19 PDT Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA16053; Thu, 26 Sep 1996 09:08:30 -0600 (MDT) Date: Thu, 26 Sep 1996 09:08:30 -0600 (MDT) Message-Id: <199609261508.JAA16053@rocky.mt.sri.com> From: Nate Williams To: mobile@freebsd.org Subject: PCI Power Mgmt. docs Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Forwarded: > * FYI, there is no "power management paper" on the PCI-SIG web page in the > additional documents section. You can find it on the ACPI site: http://www.teleport.com/~acpi/pci_pm7a.pdf From owner-freebsd-mobile Thu Sep 26 10:52:37 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA07796 for mobile-outgoing; Thu, 26 Sep 1996 10:52:37 -0700 (PDT) Received: from mimbres.cs.unm.edu (mimbres.cs.unm.edu [198.59.151.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA07762 for ; Thu, 26 Sep 1996 10:52:34 -0700 (PDT) Received: from fiveup.cs.unm.edu by mimbres.cs.unm.edu (5.65/033093) with SMTP id ; Thu, 26 Sep 96 11:52:33 -0600 Date: Thu, 26 Sep 1996 11:52:32 -0600 (MDT) From: Brian Walenz To: freebsd-mobile@freebsd.org Subject: XF86 config for LCD or external monitor? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone figured out how to configure XF86 so that it is possible to use either the LCD notebook screen or an external monitor? I am able to switch from LCD to external (and back again) on the fly, but how do I change XF86's parameters??? Thanks, brian -- Brian Walenz walenz@cs.unm.edu A hacker does for love what others would not do for money.