From owner-freebsd-usb@FreeBSD.ORG Mon Mar 16 19:56:30 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 424B7106568B for ; Mon, 16 Mar 2009 19:56:30 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 00C778FC0C for ; Mon, 16 Mar 2009 19:56:29 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KGM00HYU7E44K90@osl1smout1.broadpark.no> for freebsd-usb@freebsd.org; Mon, 16 Mar 2009 20:56:28 +0100 (CET) Received: from kg-work2.kg4.no ([80.203.109.110]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0KGM00GRD7E23C10@osl1sminn1.broadpark.no> for freebsd-usb@freebsd.org; Mon, 16 Mar 2009 20:56:28 +0100 (CET) Date: Mon, 16 Mar 2009 20:56:26 +0100 From: Torfinn Ingolfsen To: freebsd-usb@freebsd.org Message-id: <20090316205626.b0ed5027.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Xorg 7.4 and umass devices - a bad combination? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 19:56:31 -0000 Hi, Have anyone seen bad performance when using umass devices (external hard drives) in combination with Xorg 7.4? The reason I ask is that I have this machine[1] which is both a test workstation, and cheap-ass fileserver. I am using external usb drives for storage (it was the cheapest option when I set this up). root@kg-quiet# dmesg | grep da[01234] da4 at sbp0 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-4 device da4: 50.000MB/s transfers da4: 286188MB (586114704 512 byte sectors: 255H 63S/T 36483C) da3 at umass-sim3 bus 3 target 0 lun 0 da3: Fixed Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) da2 at umass-sim2 bus 2 target 0 lun 0 da2: Fixed Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) da1 at umass-sim1 bus 1 target 0 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) Yes, there is a firewire drive in there too. The machine currently runs FreeBSD 6.4-stable / amd64, and have run through most releases sine 6.1-prerelease. I use Samba for file serving. root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #27: Sun Mar 15 19:42:19 CET 2009 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 The machine have always been in X when it is up (I use XFce) and this hasn't created any problems that I have noticed. However, after I upgraded Xorg to 7.4, I get lots of these messages in /var/log/messages if I try to do a simple 'ls' on any filesystem on a usb drive: Mar 16 17:09:02 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:09:31 kg-quiet kernel: umass1: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:10:00 kg-quiet kernel: umass3: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:10:43 kg-quiet kernel: umass0: BBB reset failed, TIMEOUT Mar 16 17:11:12 kg-quiet kernel: umass2: BBB reset failed, TIMEOUT Mar 16 17:11:41 kg-quiet kernel: umass1: BBB reset failed, TIMEOUT Mar 16 17:11:48 kg-quiet kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Mar 16 17:12:10 kg-quiet kernel: umass3: BBB reset failed, TIMEOUT Followed by these: Mar 16 17:12:53 kg-quiet kernel: g_vfs_done():da0s1d[WRITE(offset=196864589824, length=16384)]error = 5 Mar 16 17:12:53 kg-quiet kernel: g_vfs_done():da0s1d[WRITE(offset=114688, length=16384)]error = 5 Mar 16 17:13:15 kg-quiet kernel: umass3: BBB bulk-in clear stall failed, TIMEOUT Mar 16 17:13:22 kg-quiet kernel: umass2: BBB bulk-out clear stall failed, TIMEOUT Mar 16 17:13:22 kg-quiet kernel: g_vfs_done():da2s1d[WRITE(offset=357707874304, length=16384)]error = 5 Mar 16 17:13:22 kg-quiet kernel: g_vfs_done():da2s1d[WRITE(offset=114688, length=16384)]error = 5 and the 'ls' takes several minutes to complete. Notice that the messages mention all umass drives (umass0 - umass3), even if I only do an ls on one of them. Also notice that the firewire drive is absent fom any messages. Note: hal is NOT running on this machine. What is my workaround? Reboot the machine (needing a forced reset, as the machine hangs on shutdown after the umass errors), let fsck do its thing and then don't start Xorg. But this is no solution. The funny thing is that It worked find before I upgraded Xorg from 7.3.2 to 7.4... Any hints on how I can debug this? More info: FreeBSD work log[2], dmesg output normal[3] and verbose[4]. References: 1) http://tingox.googlepages.com/rs480m2 2) http://tingox.googlepages.com/rs480m2_freebsd 3) http://tingox.googlepages.com/quiet-dmesg-6.4-stable-20090315.txt 4) http://tingox.googlepages.com/quiet-dmesg-6.4-stable-20090315_verb.txt -- Regards, Torfinn Ingolfsen, Norway