From owner-freebsd-current@FreeBSD.ORG Tue May 17 14:55:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50D3A16A4CE for ; Tue, 17 May 2005 14:55:47 +0000 (GMT) Received: from bilbo.mebtel.net (bilbo.mebtel.net [64.40.67.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFC3C43D99 for ; Tue, 17 May 2005 14:55:46 +0000 (GMT) (envelope-from dlt@mebtel.net) Received: from localhost (localhost [127.0.0.1]) by bilbo.mebtel.net (Postfix) with ESMTP id B74D22A826 for ; Tue, 17 May 2005 10:55:41 -0400 (EDT) Received: from bilbo.mebtel.net ([127.0.0.1]) by localhost (bilbo [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13036-01 for ; Tue, 17 May 2005 10:55:41 -0400 (EDT) Received: from lorne.arm.org (66-79-79-189.dsl.mebtel.net [66.79.79.189]) by bilbo.mebtel.net (Postfix) with ESMTP id C8C9A2A784 for ; Tue, 17 May 2005 10:55:40 -0400 (EDT) Received: from lorne.arm.org (localhost [127.0.0.1]) by lorne.arm.org (8.13.3/8.13.1) with ESMTP id j4HEterM001351 for ; Tue, 17 May 2005 10:55:40 -0400 (EDT) (envelope-from dlt@lorne.arm.org) Received: (from dlt@localhost) by lorne.arm.org (8.13.3/8.13.1/Submit) id j4HEteKe001348; Tue, 17 May 2005 10:55:40 -0400 (EDT) (envelope-from dlt) Date: Tue, 17 May 2005 10:55:40 -0400 (EDT) Message-Id: <200505171455.j4HEteKe001348@lorne.arm.org> From: Derek Tattersall To: current@FreeBSD.org X-Virus-Scanned: by amavisd-new at mebtel.net Subject: Panic accessing msdosfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2005 14:55:47 -0000 FreeBSD lorne.arm.org 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Mon May 16 11:32:35 EDT 2005 toor@lorne:/usr/obj/usr/src/sys/GENERIC i386 There have been several messages regarding similar panics accessing an msdosfs on a USB flash stick, but it seems that they have been regarding ehci. This is a USB 1.1 stick and uses uhci. I copied the back trace by hand. panic: non-decreasing id, id 0 last id 0 cpuid 0 KDB: enter panic [ thread pid 93 tid 100061 ] stopped at kdb_enter + 0x2b: nop db> trace Tracing pid 93 tid100061 td 0xc240a480 kdb_enter(c0840215) at kdb_enter + 0x2b panic(c0839489,0,0,d6753674,ed43aa60) at panic + 0x127 mbnambuf_write(ed43aa58,0,74657358,305f7075,0) at mbnambuf_write + 0x2b win2unixfn(d6753660,98,c25ddc00,c09184f0,c0938a20) at win2unixfn + 0x11a msdosfs_readdir(ed43ac90)at msdosfs_readdir + 0x51e VOP_READDIR_APV(c089ce00,ed43ac90) at VOP_READDIR_APV + 0x7e getdirentries(c240a480,ed43ad04,4,0,246) at getdirentries + 0x13f syscall(3b,3b,3b,8053000,2) at syscall + 0x227 Xint0x80_syscall() at Xint0x80_syscall + 0x17 --- syscall (196,FreeBSD ELF322, getdirentries), eip=0x2810595f,esp=0xbfbfe6bc,ebp=0xbfbfe6e8 --- The stick works fine on a 5.4 Release system. Any clues? -- Derek Tattersall dlt@mebtel.net