Panic accessing msdosfs

[Derek Tattersall]

FreeBSD lorne.arm.org 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Mon May 16
11:32:35 EDT 2005     toor at 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 at mebtel.net