From owner-freebsd-net@FreeBSD.ORG Mon Oct 24 08:39:37 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FDB416A41F for ; Mon, 24 Oct 2005 08:39:37 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 1B2A543D45 for ; Mon, 24 Oct 2005 08:39:36 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 40901 invoked from network); 24 Oct 2005 08:39:35 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 24 Oct 2005 08:39:35 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 24 Oct 2005 03:39:34 -0500 (CDT) From: Mike Silbersack To: Jan Mikael Melen In-Reply-To: <200510091827.03988.jan@melen.org> Message-ID: <20051024033756.V26073@odysseus.silby.com> References: <200509251353.j8PDr5XE005907@lurza.secnetix.de> <200509271107.37830.jan@melen.org> <200510091827.03988.jan@melen.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Kernel panic due atheros driver after finalsync (Was: VIA VT6103 support (VIA EPIA PD)) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2005 08:39:37 -0000 On Sun, 9 Oct 2005, Jan Mikael Melen wrote: > Hi, > > I have the D-Link DWL-G520 which has the atheros 5212 chip. When rebooting the > FreeBSD 6.0-BETA5 after the final sync kernel panics. If the if_ath module has > not been loaded in to the memory all works fine. Does anyone have any good > idea how to get rid of this problem? Unloading the kernel module will cause > the whole system to halt totally, the system does not respond to anything > except power button and reset ;) >From what you pasted, the problem appears to be that ath0 and vr0 share an interrupt, ath0 is triggering a late interrupt, and vr0 can't handle it. I think someone might've fixed the problem in -current, you should check the cvs history for if_vr.c. Mike "Silby" Silbersack