From owner-freebsd-stable@FreeBSD.ORG Thu Feb 28 04:29:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06E20106566C; Thu, 28 Feb 2008 04:29:23 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from misav06.sasknet.sk.ca (misav06.sasknet.sk.ca [142.165.20.170]) by mx1.freebsd.org (Postfix) with ESMTP id 91E658FC26; Thu, 28 Feb 2008 04:29:22 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from bgmpomr1.sasknet.sk.ca ([142.165.72.22]) by misav06 with InterScan Messaging Security Suite; Wed, 27 Feb 2008 22:29:21 -0600 Received: from server.hurd.local (adsl-76-202-204-46.dsl.lsan03.sbcglobal.net [76.202.204.46]) by bgmpomr1.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0JWX008RJLSW9P00@bgmpomr1.sasknet.sk.ca>; Wed, 27 Feb 2008 22:29:21 -0600 (CST) Date: Wed, 27 Feb 2008 20:29:20 -0800 From: Stephen Hurd In-reply-to: <47C5C622.5000209@samsco.org> To: Scott Long Message-id: <47C638A0.4080107@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <47C52948.2070500@sasktel.net> <20080227121129.GA76419@eos.sc1.parodius.com> <47C5ACD0.8000009@sasktel.net> <47C5C622.5000209@samsco.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.9) Gecko/20071123 SeaMonkey/1.1.6 Cc: Jeremy Chadwick , freebsd-stable@freebsd.org Subject: Re: ad0 READ_DMA TIMEOUT errors on install of 7.0-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 04:29:23 -0000 Scott Long wrote: > I'd like to attack these driver problems. What I need is to spend a > couple of days with an affected system that can reliably reproduce the > problem, instrumenting and testing the driver. I have a number of > theories about what might be going wrong, but nothing that I'm > definitely sure about. If you are willing to set up your system with > remote power and remote serial, and if we knew a reliable way to > reproduce the problem, I could probably have the problem identified and > fixed pretty quickly. So, it turns out that I can't have multiple PPPoE sessions at the same time. :-( I should be able to hack together something though if the rest of the stuff I mentioned is fine.