From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 24 00:05:47 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 39D7BE9F for ; Sun, 24 Mar 2013 00:05:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by mx1.freebsd.org (Postfix) with ESMTP id D1FCB1C8 for ; Sun, 24 Mar 2013 00:05:46 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm14so9030262wib.9 for ; Sat, 23 Mar 2013 17:05:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/OK67+DIJWXwbLM3WRtACjLqgEzzDzyBFsXHSaAgZnw=; b=X/C6WmWOFS4UdtsKNYpX4ekxqQtKHOp/X3u37VK0VaGf/0sVNT746lMFdOEz1vEo43 4exvArljovuqCDURMW2phgiFdebz1VE596bKHi4gSWRW27yGe5/niCIJR1madtgwVef2 yJPm3e9Ix4zfwXjIQXBDgzPm6kXQmPOg6i+BLx9xBrYdnfB9JPXNgGhqJgoPkB9QpG8D P9mEAvN+ET2GmgCb5dtc0bHWLAC4A13NCwuC+e/cSThOzHjixcB0L2+yU5mXB9Mmu34w an9Tp1bSBbXZ1PXo6CfEq+RCO7AuAHlS1xI7fl3Rf/3QCcy3OHRMvvH0APD1Ip4tVS9B QIqQ== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr10480878wjb.24.1364083545925; Sat, 23 Mar 2013 17:05:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sat, 23 Mar 2013 17:05:45 -0700 (PDT) In-Reply-To: <514E3D6D.4060800@gmail.com> References: <514E3D6D.4060800@gmail.com> Date: Sat, 23 Mar 2013 17:05:45 -0700 X-Google-Sender-Auth: -dAKET6toXqUr4uEfEkjKiSZF3k Message-ID: Subject: Re: Periodic panics with ath From: Adrian Chadd To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Mar 2013 00:05:47 -0000 Ok, do you get crashdumps? Can you attach the core.X.txt files from /var/crash ? Thanks, Adrian On 23 March 2013 16:40, Joshua Isom wrote: > I'm getting periodic panics with the latest ath driver. I've had six panics > today where the debugger was not entered and it just rebooted. Each one > lists ath_edma_tx_processq as the cause. I can provide all six core.txt > files, but here's some of the dmesg listed in one core.txt file. The dmesg > part looks like it has better info than the early backtrace. > >> Kernel page fault with the following non-sleepable locks held: >> exclusive sleep mutex ath0 TX lock (ath0 TX lock) r = 0 >> (0xffffff800090d790) locked @ >> /root/ATH/head/sys/modules/ath/../../dev/ath/if_ath_tx_edma.c:529 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> 0xffffff8020bdd520 >> kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffff8020bdd5d0 >> witness_warn() at witness_warn+0x4a8/frame 0xffffff8020bdd690 >> trap_pfault() at trap_pfault+0x5a/frame 0xffffff8020bdd740 >> trap() at trap+0x659/frame 0xffffff8020bdd950 >> calltrap() at calltrap+0x8/frame 0xffffff8020bdd950 >> --- trap 0xc, rip = 0xffffffff81334da4, rsp = 0xffffff8020bdda10, rbp = >> 0xffffff8020bddb30 --- >> ath_edma_tx_processq() at ath_edma_tx_processq+0x1a4/frame >> 0xffffff8020bddb30 >> taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame >> 0xffffff8020bddb80 >> taskqueue_thread_loop() at taskqueue_thread_loop+0x7b/frame >> 0xffffff8020bddbb0 >> fork_exit() at fork_exit+0x84/frame 0xffffff8020bddbf0 >> fork_trampoline() at fork_trampoline+0xe/frame 0xffffff8020bddbf0 >> --- trap 0, rip = 0, rsp = 0xffffff8020bddcb0, rbp = 0 --- >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x0 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff81334da4 >> stack pointer = 0x28:0xffffff8020bdda10 >> frame pointer = 0x28:0xffffff8020bddb30 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 0 (ath0 taskq) >> Kernel page faultath0: ath_edma_recv_proc_queue: handled npkts 0 >> with the following non-sleepable locks held: >> exclusive sleep mutex ath0 TX lock (ath0 TX lock) r = 0 >> (0xffffff800090d790) locked @ >> /root/ATH/head/sys/modules/ath/../../dev/ath/if_ath_tx_edma.c:529 >> KDB: stack backtrace: >> ath0: ath_edma_recv_proc_queue: handled npkts 0 >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> 0xffffff8020bdd520 >> kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffff8020bdd5d0 >> witness_warn() at witness_warn+0x4a8/frame 0xffffff8020bdd690 >> trap_pfault() at trap_pfault+0x5a/frame 0xffffff8020bdd740 >> trap() at trap+0x659/frame 0xffffff8020bdd950 >> calltrap() at calltrap+0x8/frame 0xffffff8020bdd950 >> --- trap 0xc, rip = 0xffffffff81334da4, rsp = 0xffffff8020bdda10, rbp = >> 0xffffff8020bddb30 --- >> ath_edma_tx_processq() at ath_edma_tx_processq+0x1a4/frame >> 0xffffff8020bddb30 >> taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame >> 0xffffff8020bddb80 >> taskqueue_thread_loop() at taskqueue_thread_loop+0x7b/frame >> 0xffffff8020bddbb0 >> fork_exit() at fork_exit+0x84/frame 0xffffff8020bddbf0 >> fork_trampoline() at fork_trampoline+0xe/frame 0xffffff8020bddbf0 >> --- trap 0, rip = 0, rsp = 0xffffff8020bddcb0, rbp = 0 --- >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x0 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff81334da4 >> stack pointer = 0x28:0xffffff8020bdda10 >> frame pointer = 0x28:0xffffff8020bddb30 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 0 (ath0 taskq) >> Uptime: 32m28s >> Dumping 270 out of 1771 >> MB:..6%..12%..24%..36%..42%..54%..66%..71%..83%..95% > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"