From owner-freebsd-current@FreeBSD.ORG Mon Jan 12 00:45: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 B6F7016A4CE for ; Mon, 12 Jan 2004 00:45:18 -0800 (PST) Received: from burrito.bitsurf.net (dcn235-229.dcn.davis.ca.us [168.150.235.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id A196543D3F for ; Mon, 12 Jan 2004 00:45:16 -0800 (PST) (envelope-from mharo@bitsurf.net) Received: from burrito.bitsurf.net (localhost.bitsurf.net [127.0.0.1]) by burrito.bitsurf.net (8.12.9p1/8.12.9) with ESMTP id i0C8jF2Q000766 for ; Mon, 12 Jan 2004 00:45:15 -0800 (PST) (envelope-from mharo@bitsurf.net) Received: (from mharo@localhost) by burrito.bitsurf.net (8.12.9p1/8.12.9/Submit) id i0C8jFoK000765 for current@freebsd.org; Mon, 12 Jan 2004 00:45:15 -0800 (PST) (envelope-from mharo@bitsurf.net) X-Authentication-Warning: burrito.bitsurf.net: mharo set sender to mharo@bitsurf.net using -f Date: Mon, 12 Jan 2004 00:45:15 -0800 From: Michael Haro To: current@freebsd.org Message-ID: <20040112084514.GA708@bitsurf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.1-RELEASE-p10 X-SMTP-From: localhost.bitsurf.net [127.0.0.1] (burrito.bitsurf.net) X-Scanned-By: MIMEDefang 2.39 X-Mailman-Approved-At: Mon, 12 Jan 2004 05:18:03 -0800 Subject: freebsd 5.1 ohci driver causing a panic 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, 12 Jan 2004 08:45:18 -0000 I can reproduce a kernel panic in 5.1 by unplugging the usb cable from my UPS. Unfortunately I'm not getting crash dumps. I'm not sure if I'm doing something wrong. I have dumpdev set in /etc/rc.conf, but I also notice that the panic screen says ad0 DRQ timeout so I'm not sure if that is the reason I don't get a dump. Anyway, I saw in CVS logs that the ohci driver has been updated a lot since 5.1 and I was wondering if anyone knows if any of the changes fix this type of panic. I couldn't tell from the logs, but I'm currently cvsup'ing to 5.2 so I get the more recent ohci driver. Let me know if there is anything else I should do. Michael