From owner-freebsd-current@FreeBSD.ORG Thu Apr 21 22:37:52 2005 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 9E44A16A4CE for ; Thu, 21 Apr 2005 22:37:52 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D3B643D3F for ; Thu, 21 Apr 2005 22:37:52 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465 for ; Thu, 21 Apr 2005 15:37:51 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C5F6B5D07 for ; Thu, 21 Apr 2005 15:37:51 -0700 (PDT) To: current@freebsd.org Date: Thu, 21 Apr 2005 15:37:51 -0700 From: "Kevin Oberman" Message-Id: <20050421223751.C5F6B5D07@ptavv.es.net> Subject: I/O breakage in today's 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: Thu, 21 Apr 2005 22:37:52 -0000 After rebuilding the current kernel today (cvsup at 16:20 UTC) on my T30 ThinkPad, I saw to major (though possibly unrelated) problems. 1. My second disk (master on the secondary bus) suddenly probes as having a non-ATA66 cable. It is a laptop drive and has not cable. It probes fine with the old kernel and runs at UDMA5. Attempts to use atacontrol to reset it to UDMA5 received the same message. The drive does work and I had not problems reading or writing. It was just slow. The master on the primary bus (the system disk) probed correctly. 2. My network card (Intel Pro 100 VE) probes fine and looks fine, but never seems to send a packet. I monitored the Ethernet using tcpdump on a directly connected system and receives NO packets. dhclient reported the error "send_packet: Network is down". I don't know if these are two different problems that cropped up at the same time or a common failure. A kernel built from sources dated yesterday at 16:29 UTC works fine. Our cvs mirror updates every hour, so there is some fuzz in the times. Any ideas? (mdodd just fixed one really annoying problem yesterday and today I get an even more annoying problem. The joy of running current. :-( If I don't see any report of what might be wrong, I'll try to do some more in-depth testing tomorrow. No time today. Thanks, -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634