From owner-freebsd-stable@FreeBSD.ORG Sun Oct 19 18:21:03 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 EED91106567A for ; Sun, 19 Oct 2008 18:21:03 +0000 (UTC) (envelope-from gtcmail@mm.st) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id C91F88FC08 for ; Sun, 19 Oct 2008 18:21:03 +0000 (UTC) (envelope-from gtcmail@mm.st) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id B3AF5181BAB for ; Sun, 19 Oct 2008 14:06:01 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 19 Oct 2008 14:06:01 -0400 X-Sasl-enc: Tq9BKDY5AiQiFQFhB8WsPzv0zJoUa4WiwdZYIRUHMoow 1224439561 Received: from fire.alarm (5ac8a44f.bb.sky.com [90.200.164.79]) by mail.messagingengine.com (Postfix) with ESMTPSA id 40B9BE7FE for ; Sun, 19 Oct 2008 14:06:01 -0400 (EDT) Message-ID: <48FB7706.90604@mm.st> Date: Sun, 19 Oct 2008 19:05:58 +0100 From: Guy Coleman User-Agent: Thunderbird 2.0.0.16 (X11/20080730) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: kern/123552: ath panic 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: Sun, 19 Oct 2008 18:21:04 -0000 I've been hitting a panic with any non-trivial network activity on an ath wireless card. I've already submitted the details to a PR (kern/123552) and after a quick search it looks like kern/125914, kern/126475 and kern/125332 are all the same panic. The last time I tried an up-to-date RELENG_7 was October 5th and the panic was still present. I can just about manage to get a backtrace but am a bit lost when it comes down to tracking down the actual problem. Are there any more debugging details it might be helpful to add to the PR? Alternatively, has anybody found any workarounds? Cheers, Guy p.s., please include me in any replies, I'm not subscribed to the list.