From owner-freebsd-usb@FreeBSD.ORG  Wed Jul  2 02:39:26 2014
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5ECBC263
 for <freebsd-usb@FreeBSD.org>; Wed,  2 Jul 2014 02:39:26 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2C3812A48
 for <freebsd-usb@FreeBSD.org>; Wed,  2 Jul 2014 02:39:26 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s622dQ8T022507
 for <freebsd-usb@FreeBSD.org>; Wed, 2 Jul 2014 03:39:26 +0100 (BST)
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-usb@FreeBSD.org
Subject: [Bug 191432] FreeBSD 10.0-STABLE #0 r267746: panic when using ue0
 network
Date: Wed, 02 Jul 2014 02:39:26 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: usb
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kevlo@FreeBSD.org
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-191432-17-eYxnXTTWY4@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191432-17@https.bugs.freebsd.org/bugzilla/>
References: <bug-191432-17@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jul 2014 02:39:26 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191432

Kevin Lo <kevlo@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Patch Ready                 |In Discussion
                 CC|                            |kevlo@FreeBSD.org

--- Comment #20 from Kevin Lo <kevlo@FreeBSD.org> ---
(In reply to Vikash Badal from comment #0)
> Created attachment 144187 [details]
> core.txt
> 
> hardware:
> Dell M3800
> 
> nic:
> ugen2.4: <AX88179 ASIX Elec. Corp.> at usbus2, cfg=0 md=HOST spd=HIGH
> (480Mbps) pwr=ON (248mA)
> 
> 
> Unread portion of the kernel message buffer:
> panic: vm_fault: fault on nofault entry, addr: fffffe02346f0000
> cpuid = 0
> KDB: stack backtrace:
> #0 0xffffffff8092a2d0 at kdb_backtrace+0x60
> #1 0xffffffff808ef825 at panic+0x155
> #2 0xffffffff80b5f8e9 at vm_fault_hold+0x1a89
> #3 0xffffffff80b5de17 at vm_fault+0x77
> #4 0xffffffff80ce455c at trap_pfault+0x19c
> #5 0xffffffff80ce3d80 at trap+0x4a0
> #6 0xffffffff80cca7f2 at calltrap+0x8
> #7 0xffffffff81c1687e at axge_bulk_read_callback+0x19e
> #8 0xffffffff8079684c at usbd_callback_wrapper+0x71c
> #9 0xffffffff80797ac3 at usb_command_wrapper+0x113
> #10 0xffffffff80796a71 at usb_callback_proc+0xc1
> #11 0xffffffff80791b8f at usb_process+0x11f
> #12 0xffffffff808c03da at fork_exit+0x9a
> #13 0xffffffff80ccad2e at fork_trampoline+0xe
> Uptime: 10m38s

I can't reproduce the issue here.  Could you tell me how to reproduce it?
Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.