Matthew Dillon wrote: > > :After playing with my mobile phone (mounted it's memory card with mount -t > :msdosfs), a umount triggered the panic (well, I did run sync a second or 2 > :before doing a umount). The memory dump is at leaf:~rumko/crash/19.05.2008/ > :and the backtrace (including the kernel message buffer that kgdb prints) is > :here: > : > :Unread portion of the kernel message buffer: > :panic: VOP_STDCLOSE: BAD WRITECOUNT 0xf2629e68 0 > : > :mp_lock = 00000001; cpuid = 1 > :boot() called on cpu#1 > : > :syncing disks... 3 ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue > :timeout - completing request directly > :ad8: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=12361855 > : > :done > :-- > :Regards, > :Rumko > > Did you mount it normally or use options like -o ro (read-only), or > -u (update) at any point ? > > And, is the panic reproducable? > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]>
If I remember correctly, I did mount it readonly, then did a umount -u, copied a file, ran sync (I'm not sure, but could've been more than one time) and tried umount-ing it. As for being reproducable ... I can try it again, if the need to reproduce it arises. -- Regards, Rumko
