From owner-freebsd-usb@FreeBSD.ORG Tue Dec 23 22:05:04 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5CDAE53 for ; Tue, 23 Dec 2014 22:05:04 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9AA441832 for ; Tue, 23 Dec 2014 22:05:04 +0000 (UTC) Received: from laptop015.home.selasky.org (unknown [89.11.148.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id CB7C91FE022; Tue, 23 Dec 2014 23:05:01 +0100 (CET) Message-ID: <5499E734.1070507@selasky.org> Date: Tue, 23 Dec 2014 23:05:40 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: kott , freebsd-usb@freebsd.org Subject: Re: usb_pc_cpu_flush References: <1419359192795-5975583.post@n5.nabble.com> In-Reply-To: <1419359192795-5975583.post@n5.nabble.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2014 22:05:04 -0000 On 12/23/14 19:26, kott wrote: > Hello - > I am seeing this fault when i plugin a external usb device, and was > wondering if this indicates DMA/Cache coherency problem > ----- > _ehci_append_qh: 0xf3dd2300 to 0xf3dc3c00 > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex ehci0 (usb_def_mtx) r = 0 (0xc73ece74) locked @ > sys/dev/usb/usb_transfer.c > exclusive sleep mutex USB device mutex (USB device mutex) r = 0 (0xc73da850) > locked @ /sys/dev/usb/usb_transfer.c > > Stopped at usb_pc_cpu_flush+0xc: ldr r2, [r0, #0x018] > ---------------------------- > > Thanks > kott Hi, The flush is supposed to call some other functions which write the memory cache to RAM. It should not panic like that. Can you get the complete backtrace. I guess that some memory content might have been lost due to missing or wrong cache sync operations. What is the value of "r0" ? --HPS