From owner-freebsd-wireless@FreeBSD.ORG  Mon Nov 21 13:44:25 2011
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1233)
	id F2B741065670; Mon, 21 Nov 2011 13:44:25 +0000 (UTC)
Date: Mon, 21 Nov 2011 13:44:25 +0000
From: Alexander Best <arundel@freebsd.org>
To: Adrian Chadd <adrian.chadd@gmail.com>
Message-ID: <20111121134425.GA6047@freebsd.org>
References: <20111121131730.GA3599@freebsd.org>
	<CAJ-VmonoqcA5ZLEO=xNm9TT6btOecX5gH2ac=4M8WV+P_YTxNA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJ-VmonoqcA5ZLEO=xNm9TT6btOecX5gH2ac=4M8WV+P_YTxNA@mail.gmail.com>
Cc: freebsd-wireless@freebsd.org
Subject: Re: issues with the recent ath commits (r227740, r227651, ...)
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussions of 802.11 stack,
	tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2011 13:44:26 -0000

On Mon Nov 21 11, Adrian Chadd wrote:
> Hi,
> 
> Thanks. Please do this. Can you please provide me with some details
> about the panic-on-boot?
> 
> Is the version of the ath driver code from stable/9 ok?

i'm running HEAD, so i can't test that code. reverting to r227739 didn't fix
the issue, however i'm now running r227650 and so far i haven't experienced the
panic, nor the lock up. it seems r227651 introduced the critical code that
caused the issues.

unfortunately i can only take a picture of the panic-on-boot, since the system
locks up after the panic and no debugging is possible. also no crash dump is
being performed.

i'll send you the panic-picture in a private email (since the mailinglists will
scrub the attachment anyway).

cheers.
alex

> 
> 
> Adrian