From owner-freebsd-current@FreeBSD.ORG Fri Nov 7 08:27:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79F08106567D for ; Fri, 7 Nov 2008 08:27:42 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id 5EBCF8FC12 for ; Fri, 7 Nov 2008 08:27:41 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by QMTA01.emeryville.ca.mail.comcast.net with comcast id c8Fv1a0010EPchoA18ThGD; Fri, 07 Nov 2008 08:27:41 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA01.emeryville.ca.mail.comcast.net with comcast id c8Tg1a0082P6wsM8M8The8; Fri, 07 Nov 2008 08:27:41 +0000 X-Authority-Analysis: v=1.0 c=1 a=ho34a-Vniy8A:10 a=tkbIkwAIgeYA:10 a=8BZ8ZQq2AAAA:8 a=QycZ5dHgAAAA:8 a=KgWBncX_slgt88vUWjcA:9 a=leDLDP24OzjARzdcsBQA:7 a=pKLch3M_AtP1aTx3F6Ax0ID1uZsA:4 a=EoioJ0NPDVgA:10 a=6-x43y6uxGMA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 323415C34; Fri, 7 Nov 2008 00:27:40 -0800 (PST) Date: Fri, 7 Nov 2008 00:27:40 -0800 From: Jeremy Chadwick To: freebsd-current@freebsd.org Message-ID: <20081107082740.GA1334@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Kernel panic when copying data to umass device (USB4BSD) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 07 Nov 2008 08:27:42 -0000 Not sure if this is caused by problems with USB4BSD or not, as I can reproduce it on RELENG_7 (but there, the kernel does not panic; it just "wedges" in a loop/thread somewhere; SSH sessions remain up, but commands running stop; hitting Ctrl-T shows them in all sorts of different states, but the states never change; hitting Ctrl-Alt-Esc does in fact drop me to db>). Anyway, WRT CURRENT, here's the scenario: - Insert Sandisk U3 Cruzer (8GB) USB flash drive ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 7663MB (15695871 512 byte sectors: 255H 63S/T 977C) /storage is a ZFS pool /dev/da0s1a is a UFS1 filesystem (e.g. newfs -O1 /dev/da0s1a) # mdconfig -a -t vnode -u 0 -f /storage/7.1-BETA2-amd64-disc1.iso # mdconfig -a -t vnode -u 1 -f /storage/7.1-BETA2-i386-disc1.iso # mount /dev/md0 /iso0 # mount /dev/md1 /iso1 # mount /dev/da0s1a /mnt # cp -vpR /iso0/* /mnt The system will eventually kernel panic in the middle of this copy. I'm unable to obtain a crash dump; doing "panic" at the db> prompt causes the same trace to happen over and over, so I've taken a photo of the console. Kernel has KBD_TRACE set, hence the auto-backtrace: http://www.malkavian.com/~jdc/usb2_da0_crash.jpg -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |