From owner-freebsd-stable Wed Oct 4 13:59:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8548537B66C for ; Wed, 4 Oct 2000 13:59:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e94KxAM17487; Wed, 4 Oct 2000 14:59:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA39955; Wed, 4 Oct 2000 14:59:10 -0600 (MDT) Message-Id: <200010042059.OAA39955@harmony.village.org> To: John Reynolds~ Subject: Re: breakage with two ed network devices Cc: stable@freebsd.org In-reply-to: Your message of "Wed, 04 Oct 2000 13:29:21 PDT." <14811.37665.447008.535024@hip186.ch.intel.com> References: <14811.37665.447008.535024@hip186.ch.intel.com> <14808.45618.368338.347768@hip186.ch.intel.com> <14804.65209.8908.316746@hip186.ch.intel.com> <200009292130.PAA03763@harmony.village.org> <200010021625.KAA11862@harmony.village.org> Date: Wed, 04 Oct 2000 14:59:10 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14811.37665.447008.535024@hip186.ch.intel.com> John Reynolds~ writes: : OK. I've finally had a chance to start figuring out why 4.1.1 kernels don't : see both of my ed devices. Here's what I've done thus far: .. : If that theory is true, then something else has gone south in the kernel from : 4.1 to 4.1.1 which is causing my problem. ... Do you have any other drivers in your kernel that might be looking at iospace 0x2c0-0x2df. Also, did you know that both of these cards have the same memory address. I don't think that matters for the ne2000 since they don't do memory mapped I/O. Areas that would cause this: New drivers changed drivers changed configure code (kern/subr_bus.c) whacked out space aliens messing with your mind Resource allocation plug and play Now, one of the above list is almost certainly not right, but as for the rest... You might try updating the filesystems and vm to 4.1.1 from 4.1. I'd expect 0 effect by doing that. Beyond that, I'm not quite sure what to suggest. This is weird, eh? Let's see. Looking at the logs, I'd say that July 26th to September 25th is the target range. I'd do a binary serach over that time frame for the kernel as a whole. Two months shouldn't take more than 6 or 7 kernels to track the problem down with to a given day and maybe 2 or 3 more to find the change that broke things. I'd also be tempted to try Sept 9th first, since that's the day before the MFC of the ed driver and something tells me that it is a good place to start. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message