From owner-freebsd-usb@FreeBSD.ORG Sun Nov 22 03:46:25 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 96DC5106566C; Sun, 22 Nov 2009 03:46:25 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70.appriver.com [69.20.119.203]) by mx1.freebsd.org (Postfix) with ESMTP id 00B358FC0A; Sun, 22 Nov 2009 03:46:24 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-5/SG:5 11/21/2009 10:46:18 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.733847 p=-0.903069 Source Normal X-Signature-Violations: 0-0-0-28178-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107744208; Sat, 21 Nov 2009 22:46:29 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 21 Nov 2009 19:40:27 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB problem -- how to recover a damaged USB stick Thread-Index: AcpoP3z6JZv+wKUaR6W88hemmQS/OQC4iGNc References: <200911181213.34112.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: questions@freebsd.org, freebsd-stable@freebsd.org Subject: 8.0-RC USB problem -- how to recover a damaged USB stick 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: Sun, 22 Nov 2009 03:46:25 -0000 It seems this is more serious problem in 8.0, and I hope it could be = resolved before a formal release. I can help to diagnose this if people = need more information (this is destructive). I have picked a USB stick (DataTraveler 2GB), that has two partitions s0 = for DOS and s1 for FreeBSD. Both USB hard drive and the USB stick have worked under FreeBSD 6.2, = 6.3, 6.4 and 7.2 for a few years without any problem. Plugged USB stick in 8.0-RC and mounted it on /mnt; then untar a file, tarred one day ago from FreeBSD 6.3 machine onto stick,to = a IDE drive then tar it back to the USB stick. During tar writting from IDE to USB stick, did "ls /mnt", and "tar" = paused and "ls" hangs. A couple of minutes later, ls comes back, but tar still pauses. Hit ^C on tar process around 14:30, it took another minutes to stop the = process. Tried tar again, and system disallowed to write on the USB stick. "ls" shows all file = still there (probably cached inods). Went out for a few hours, and came back found /var/log/message are = flooded with following message: -rw-r--r-- 1 root wheel 167181 Nov 21 19:02 messages -rw-r--r-- 1 root wheel 7390 Nov 21 18:00 messages.0.bz2 -rw-r--r-- 1 root wheel 7509 Nov 21 17:00 messages.1.bz2 -rw-r--r-- 1 root wheel 9365 Nov 21 16:00 messages.2.bz2 -rw-r--r-- 1 root wheel 20598 Nov 21 15:00 messages.3.bz2 Nov 21 18:00:00 wolf newsyslog[2635]: logfile turned over due to = size>384K Nov 21 18:00:27 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D625688576, length=3D1 31072)]error =3D 5 Nov 21 18:00:27 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D625819648, length=3D1 31072)]error =3D 5 ..... Nov 21 18:19:03 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D524451840, length=3D1 6384)]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D5586944, = length=3D204 8)]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D65536, = length=3D2048) ]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D114688, = length=3D1638 4)]error =3D 5 Nov 21 18:20:05 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D349700096, length=3D1 and has to reboot the system, and reboot was not able to umount = everything (boot up message): Nov 21 18:24:03 wolf kernel: da0: = Removable Dir ect Access SCSI-2 device Nov 21 18:24:03 wolf kernel: da0: 40.000MB/s transfers Nov 21 18:24:03 wolf kernel: da0: 1947MB (3987456 512 byte sectors: 255H = 63S/T 2 48C) Nov 21 18:24:03 wolf kernel: WARNING: / was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /data was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /home was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /tmp was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /usr was not properly dismounted ... # mount /dev/da0s2 /mnt mount: /dev/da0s2 : Operation not permitted The USB stick cannot be mount under any FreeBSD OS now, and everything = on the drive has lost. Does anyone know if it is possible to revocer such damaged USB stick? -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Wed 11/18/2009 3:13 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; freebsd-stable@freebsd.org; questions@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB = drive =20 Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE = errors and=20 the drive simply dies then it might be the case. Else it is a system = issue. There are quirks for mass storage which you can add to=20 sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: > Did newfs on those partition and made things worsen -- restore = completely > fails: (I had experienced another similar problem on an IDE, which = works > well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD = 6.4. > > Is something new in 8.0 making disk partition schema changed? > > g_vfs_done():da0s3d[READ(offset=3D98304, length=3D16384)]error =3D 6 > g_vfs_done():da0s3d[WRITE(offset=3D192806912, length=3D16384)]error = =3D 6 > fopen: Device not configured > cannot create save file ./restoresymtable for symbol table > abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status = =3D=3D > 0xa, scs i status =3D=3D 0x0 > (da0:umass-sim0:0:0:0): removing device entry > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks =3D 0x0000 > umass0:0:0:-1: Attached to scbus0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > Device da0s3d went missing before all of the data could be written to = it; > expect data loss. > > 99 23:19 sysinstall > 100 23:20 newfs /dev/da0s3d > 101 23:20 newfs /dev/da0s3e > 102 23:21 mount /dev/da0s3d /mnt > 103 23:21 cd /mnt > 104 23:21 dump -0f - /home | restore -rf - > 105 23:27 history 15 > > > > -----Original Message----- > From: Guojun Jin > Sent: Tue 11/17/2009 11:05 PM > To: freebsd-stable@freebsd.org > Cc: questions@freebsd.org; freebsd-usb@freebsd.org > Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB = drive > > When mounting two partitions from a USB dirve, it can cause the drive > access lock up for a long time. Details: > > Terminal 1 -- > term1# mount /dev/da0s3d /mnt > term1# cd /mnt ; rm -fr * > > when rm starts, go to terminal 2 and do: > > term2# mount /dev/da0s3e /dist ### this will hanging for a long time = and > USB hard drive activity light is off. After more than 1-2 minutes, = mount > returns, and the drive activity light is blinking, thus removing is = going > on. > > term2# ls /dist ### this will cause dUSB dirve hanging again -- no > avtivity. Similarly, ls will finish in a couple of miniutes or longer, = the > rm command continues; but for a while, the drive activity will stop = again. > > Reboot machine, repeat the above steps, and result will be the same. = Reboot > machine again, and just mount one partition, then doing "rm -rf *" = without > involve the second partition, rm will finish quickly. > > Has anyone obseved this behave on 8.0-RC? > > -Jin From owner-freebsd-usb@FreeBSD.ORG Sun Nov 22 04:45:34 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 28742106566B; Sun, 22 Nov 2009 04:45:34 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70b.appriver.com [74.205.4.150]) by mx1.freebsd.org (Postfix) with ESMTP id 8CE738FC14; Sun, 22 Nov 2009 04:45:33 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-30/SG:5 11/21/2009 11:45:18 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.734345 p=-0.903537 Source Normal X-Signature-Violations: 0-0-0-32767-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107744544; Sat, 21 Nov 2009 23:45:38 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 21 Nov 2009 20:38:13 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcpoP3z6JZv+wKUaR6W88hemmQS/OQC4iGNcAAKBqPo= References: <200911181213.34112.hselasky@c2i.net> From: "Guojun Jin" To: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Sun, 22 Nov 2009 04:45:34 -0000 Tried on the USB hard drive: Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e. Was happy because successfully did dump/restore on s3d, and thought it = just partition format issue; but system crashed during dump/restore on s3e, and partition lost the = file system type. wolf# mount /dev/da0s3e /mnt WARNING: /mnt was not properly dismounted /mnt: mount pending error: blocks 35968 files 0 wolf# fsck da0s3e fsck: Could not determine filesystem type wolf# bsdlabel da0s3 # /dev/da0s3: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 175735035 0 unused 0 0 # "raw" part, = don't edi t d: 18874368 0 4.2BSD 0 0 0 e: 156860667 18874368 4.2BSD 0 0 0 Therefore, tried directly use fsck_ufs on both USB hard drive and USB = stick to get file system clean up. All data got back now. The machine has run with FreeBSD 6.1 all the way to 7.2 without such = problem. How can we determine what could go wrong in 8.0? FS or USB. By the way, IDE to IDE dump/restore seems not having such problem at = this point, although one of IDE drive experienced partition recognizing problem, which went = away after deleting slices and recreating slices. -----Original Message----- From: Guojun Jin Sent: Sat 11/21/2009 7:40 PM To: Hans Petter Selasky; freebsd-usb@freebsd.org Cc: freebsd-stable@freebsd.org; questions@freebsd.org Subject: 8.0-RC USB problem -- how to recover a damaged USB stick =20 It seems this is more serious problem in 8.0, and I hope it could be = resolved before a formal release. I can help to diagnose this if people = need more information (this is destructive). I have picked a USB stick (DataTraveler 2GB), that has two partitions s0 = for DOS and s1 for FreeBSD. Both USB hard drive and the USB stick have worked under FreeBSD 6.2, = 6.3, 6.4 and 7.2 for a few years without any problem. Plugged USB stick in 8.0-RC and mounted it on /mnt; then untar a file, tarred one day ago from FreeBSD 6.3 machine onto stick,to = a IDE drive then tar it back to the USB stick. During tar writting from IDE to USB stick, did "ls /mnt", and "tar" = paused and "ls" hangs. A couple of minutes later, ls comes back, but tar still pauses. Hit ^C on tar process around 14:30, it took another minutes to stop the = process. Tried tar again, and system disallowed to write on the USB stick. "ls" shows all file = still there (probably cached inods). Went out for a few hours, and came back found /var/log/message are = flooded with following message: -rw-r--r-- 1 root wheel 167181 Nov 21 19:02 messages -rw-r--r-- 1 root wheel 7390 Nov 21 18:00 messages.0.bz2 -rw-r--r-- 1 root wheel 7509 Nov 21 17:00 messages.1.bz2 -rw-r--r-- 1 root wheel 9365 Nov 21 16:00 messages.2.bz2 -rw-r--r-- 1 root wheel 20598 Nov 21 15:00 messages.3.bz2 Nov 21 18:00:00 wolf newsyslog[2635]: logfile turned over due to = size>384K Nov 21 18:00:27 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D625688576, length=3D1 31072)]error =3D 5 Nov 21 18:00:27 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D625819648, length=3D1 31072)]error =3D 5 ..... Nov 21 18:19:03 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D524451840, length=3D1 6384)]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D5586944, = length=3D204 8)]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D65536, = length=3D2048) ]error =3D 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=3D114688, = length=3D1638 4)]error =3D 5 Nov 21 18:20:05 wolf kernel: = g_vfs_done():da0s2[WRITE(offset=3D349700096, length=3D1 and has to reboot the system, and reboot was not able to umount = everything (boot up message): Nov 21 18:24:03 wolf kernel: da0: = Removable Dir ect Access SCSI-2 device Nov 21 18:24:03 wolf kernel: da0: 40.000MB/s transfers Nov 21 18:24:03 wolf kernel: da0: 1947MB (3987456 512 byte sectors: 255H = 63S/T 2 48C) Nov 21 18:24:03 wolf kernel: WARNING: / was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /data was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /home was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /tmp was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /usr was not properly dismounted ... # mount /dev/da0s2 /mnt mount: /dev/da0s2 : Operation not permitted The USB stick cannot be mount under any FreeBSD OS now, and everything = on the drive has lost. Does anyone know if it is possible to revocer such damaged USB stick? -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Wed 11/18/2009 3:13 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; freebsd-stable@freebsd.org; questions@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB = drive =20 Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE = errors and=20 the drive simply dies then it might be the case. Else it is a system = issue. There are quirks for mass storage which you can add to=20 sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: > Did newfs on those partition and made things worsen -- restore = completely > fails: (I had experienced another similar problem on an IDE, which = works > well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD = 6.4. > > Is something new in 8.0 making disk partition schema changed? > > g_vfs_done():da0s3d[READ(offset=3D98304, length=3D16384)]error =3D 6 > g_vfs_done():da0s3d[WRITE(offset=3D192806912, length=3D16384)]error = =3D 6 > fopen: Device not configured > cannot create save file ./restoresymtable for symbol table > abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status = =3D=3D > 0xa, scs i status =3D=3D 0x0 > (da0:umass-sim0:0:0:0): removing device entry > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks =3D 0x0000 > umass0:0:0:-1: Attached to scbus0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > Device da0s3d went missing before all of the data could be written to = it; > expect data loss. > > 99 23:19 sysinstall > 100 23:20 newfs /dev/da0s3d > 101 23:20 newfs /dev/da0s3e > 102 23:21 mount /dev/da0s3d /mnt > 103 23:21 cd /mnt > 104 23:21 dump -0f - /home | restore -rf - > 105 23:27 history 15 > > > > -----Original Message----- > From: Guojun Jin > Sent: Tue 11/17/2009 11:05 PM > To: freebsd-stable@freebsd.org > Cc: questions@freebsd.org; freebsd-usb@freebsd.org > Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB = drive > > When mounting two partitions from a USB dirve, it can cause the drive > access lock up for a long time. Details: > > Terminal 1 -- > term1# mount /dev/da0s3d /mnt > term1# cd /mnt ; rm -fr * > > when rm starts, go to terminal 2 and do: > > term2# mount /dev/da0s3e /dist ### this will hanging for a long time = and > USB hard drive activity light is off. After more than 1-2 minutes, = mount > returns, and the drive activity light is blinking, thus removing is = going > on. > > term2# ls /dist ### this will cause dUSB dirve hanging again -- no > avtivity. Similarly, ls will finish in a couple of miniutes or longer, = the > rm command continues; but for a while, the drive activity will stop = again. > > Reboot machine, repeat the above steps, and result will be the same. = Reboot > machine again, and just mount one partition, then doing "rm -rf *" = without > involve the second partition, rm will finish quickly. > > Has anyone obseved this behave on 8.0-RC? > > -Jin From owner-freebsd-usb@FreeBSD.ORG Sun Nov 22 09:31:44 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 AA7BF106566C; Sun, 22 Nov 2009 09:31:44 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id D03968FC0A; Sun, 22 Nov 2009 09:31:43 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=iMyEeliNSOsA:10 a=RERtC8nhXGhYvIZhK0yWrQ==:17 a=VHrStUV67yV2xKv06s0A:9 a=jNZRmPzEl3JUsrUVeXkbrUMrroUA:4 Received: from [90.149.203.35] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1330222682; Sun, 22 Nov 2009 10:31:41 +0100 From: Hans Petter Selasky To: "Guojun Jin" Date: Sun, 22 Nov 2009 10:33:15 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911181213.34112.hselasky@c2i.net> In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911221033.17251.hselasky@c2i.net> Cc: questions@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB problem -- how to recover a damaged USB stick 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: Sun, 22 Nov 2009 09:31:44 -0000 On Sunday 22 November 2009 04:40:27 Guojun Jin wrote: > Does anyone know if it is possible to revocer such damaged USB stick? Hi, There are several recovery tools in /usr/ports for this kind of task. For example photorec . --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Nov 22 09:45:47 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 809381065670; Sun, 22 Nov 2009 09:45:47 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 78A148FC0C; Sun, 22 Nov 2009 09:45:46 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=RERtC8nhXGhYvIZhK0yWrQ==:17 a=YQtf8eRKws4ADrAROVgA:9 a=_rwKxgonmejjDw73-l6V-51-0GQA:4 Received: from [90.149.203.35] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1322095374; Sun, 22 Nov 2009 10:45:44 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 22 Nov 2009 10:47:18 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911221047.20362.hselasky@c2i.net> Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, Guojun Jin Subject: Re: 8.0-RC USB/FS problem 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: Sun, 22 Nov 2009 09:45:47 -0000 On Sunday 22 November 2009 05:38:13 Guojun Jin wrote: > Tried on the USB hard drive: > > Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e. > Was happy because successfully did dump/restore on s3d, and thought it just > partition format issue; but system crashed during dump/restore on s3e, and > partition lost the file system type. > > wolf# mount /dev/da0s3e /mnt > WARNING: /mnt was not properly dismounted > /mnt: mount pending error: blocks 35968 files 0 > wolf# fsck da0s3e > fsck: Could not determine filesystem type > wolf# bsdlabel da0s3 > # /dev/da0s3: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 175735035 0 unused 0 0 # "raw" part, > don't edi t > d: 18874368 0 4.2BSD 0 0 0 > e: 156860667 18874368 4.2BSD 0 0 0 > > Therefore, tried directly use fsck_ufs on both USB hard drive and USB stick > to get file system clean up. All data got back now. > > The machine has run with FreeBSD 6.1 all the way to 7.2 without such > problem. How can we determine what could go wrong in 8.0? FS or USB. Hi, Error 5 means IO error, so probably the transport layer, USB or lower, is to blame. Some things to check: 1) Make sure the connection for your memory stick is Ok. 2) Make sure there is enough power for your memory stick. Regarding memory sticks: Other operating systems do a port bus reset when the device has a problem. On FreeBSD we just try a software reset via the control endpoint. I guess that it is a device problem you are seeing. The USB stack in FreeBSD is faster than the old one, and maybe the faster queueing of mass storage requests trigger some hidden bugs in your device. When the problem happens try: sysctl hw.usb.umass.debug=-1 --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Nov 22 20:09:05 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 74FE5106566B for ; Sun, 22 Nov 2009 20:09:05 +0000 (UTC) (envelope-from sasha.devel@gmail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id F29338FC08 for ; Sun, 22 Nov 2009 20:09:04 +0000 (UTC) Received: by fxm10 with SMTP id 10so2332992fxm.14 for ; Sun, 22 Nov 2009 12:09:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=pKr2ZTWHtX0ZJkjhlM0oV3tna6GWb5mAYuXjIobwkIQ=; b=YpS2udgX53prvzf1Qs5+sSoPW6Es1Sn8f7UAHZWw4wpp0azCpl1AS6i8am/1TQWyOE /NsyrTXViGkdW4XDtvViGL6SNYM58ZyTmJaRKl10LT/pvJZLnBRAYzk49698AHpz044z AvyA6iAksydkJbc5WPbCtV+N3fXu3r2pXH3zI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=fXb5AItqG8l72qducg0HKLRfUJTeWDjiyEWqqAX+YKnjbgfNx+XQGtWk1afeumYPAW DzO1omY4e/6Vs+dKxry6bpOiCneFdwebPIRGsaDrJf+2jdRzc8WoVBbubegKxDO9klho jyB8DS4B00boMhjKbLlLZe7NMch8HysX9OgaE= Received: by 10.103.21.24 with SMTP id y24mr1815318mui.110.1258920539444; Sun, 22 Nov 2009 12:08:59 -0800 (PST) Received: from ?192.168.1.1? ([94.253.80.54]) by mx.google.com with ESMTPS id w5sm13746547mue.22.2009.11.22.12.08.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 22 Nov 2009 12:08:58 -0800 (PST) Message-ID: <4B099A50.9000006@gmail.com> Date: Sun, 22 Nov 2009 23:08:48 +0300 From: Alexander Samarin User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: usb ethernet driver question 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: Sun, 22 Nov 2009 20:09:05 -0000 Hello, all! I'm trying to write a kernel module driver for WiMAX modem. I have Samsung SWC-U100 USB modem. Driver is based on if_cue module (it's source file is smallest in the tree). I've get module successfully attaching to device and registering new network interface, but some questions appeared: 1. madwimax project have a description of protocol of the modem, but it says simply "This data should be sent over OUT endpoint in bulk mode." In other drivers I found only calls to functionu ether_do_request() e.g: struct usb_device_request req; req.bmRequestType = UT_READ_VENDOR_DEVICE; req.bRequest = CUE_CMD_GET_MACADDR; USETW(req.wValue, 0); USETW(req.wIndex, 0); USETW(req.wLength, ETHER_ADDR_LEN); uether_do_request(&sc->sc_ue, &req, buf, 1000); Here I can't understand: Buffer can be sent or received via buf argument of ether_do_request(), but what value should be used for req.bRequest, req.wValue and req.wIndex fields? In dev/usb/net/if_* files drivers read and write to registers or memory of chip; libusb just writes to file descriptor. Can anyone take me a link where I can read more about programming usb drivers for kernel? 2. Is it possible to detach CAM subsystem from virtual DVD-ROM on other interface? This DVD-ROM contains WinXP drivers and access program, which will never be used (I think) on UNIX systems. PS: I know that if_cue is an ethernet driver, but WiMAX is a wireless so basing driver on if_cue code is not a good idea, but wireless drivers are big and my modem can connect only to one provider (Yota) so I decided to use if_cue as base code. PS2: sorry for my English. -- Best regards, Alexander Samarin mailto:sasha at enikasoft.ru https://www.fsora.ru (waits for FreeBSD 8.0-RELEASE) From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 04:12:00 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 099F91065670; Mon, 23 Nov 2009 04:12:00 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70.appriver.com [69.20.119.203]) by mx1.freebsd.org (Postfix) with ESMTP id 82B7A8FC08; Mon, 23 Nov 2009 04:11:59 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-30/SG:5 11/22/2009 11:12:00 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.675531 p=-0.900427 Source Normal X-Signature-Violations: 0-0-0-19685-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107759545; Sun, 22 Nov 2009 23:12:02 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 22 Nov 2009 19:59:10 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcprWqhOc0di4XCLQnutgxkzKDrTkwAg+g77 References: <200911221047.20362.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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, 23 Nov 2009 04:12:00 -0000 >From more intensive diagnose, it looks like more related USB layer. repeated a few time on following process and ithe crash happened at = different USB access phase at each time. dd if=3D/dev/zero of=3D/dev/da0 count=3D1000 bs=3D4k sysinstall partition=20 slice 1 (da0s1) 18GB ID=3D12 slice 2 (da0s2) 10-15GB Id=3D165 slice 3 (da0s3) rest ID=3D165 W ---> OK label da0s3d 9GB /mnt da0s3e rest /dist W ---> da0s3e ---- device is not configured. w# ll /dev/da0* # after sysinstall did partition + W at 1st time crw-r----- 1 root operator 0, 97 Nov 22 11:23 /dev/da0 crw-r----- 1 root operator 0, 98 Nov 22 11:23 /dev/da0s1 crw-r----- 1 root operator 0, 99 Nov 22 11:23 /dev/da0s2 crw-r----- 1 root operator 0, 100 Nov 22 11:23 /dev/da0s3 # ll /dev/da0* # after sysinstall start at 2nd time crw-r----- 1 root operator 0, 97 Nov 22 11:27 /dev/da0 System crashed The crash log is available at = http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2 (All logs are based on hw.usb.umass.debug=3D-1) After system reboot, and repeated above processes, the da0s3e was = mounted on /dist, but da0s3d cannot. It tunred out that newfs fail inside labeling process in sysinstall. = Manually did newfs on da0s3d, and it cannot be mounted on /mnt, but access to it caused crash. The crash log is available at = http:/www.daemonfun.com/archives/pub/USB/newfs Tried entire process again, this time, both partitons are formatted = (newfs) inside labaling process (sysinstall) but crahsed system during dump/restore on da0s3e (/dist). The crash log is available at = http:/www.daemonfun.com/archives/pub/USB/usb-log.crash2.bz2, which is = huge one. It contains two parts, one dump/restore IDE to da0s3d (passed), and the = rest is dump/restore to da0s3e (crashed). I am going to reinstall the system with the new ISO from Nov 21 = 8.0-RELEASE to see if anything will improve. -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Sun 11/22/2009 1:47 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; bugs@freebsd.org; freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Sunday 22 November 2009 05:38:13 Guojun Jin wrote: > Tried on the USB hard drive: > > Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e. > Was happy because successfully did dump/restore on s3d, and thought it = just > partition format issue; but system crashed during dump/restore on s3e, = and > partition lost the file system type. > > wolf# mount /dev/da0s3e /mnt > WARNING: /mnt was not properly dismounted > /mnt: mount pending error: blocks 35968 files 0 > wolf# fsck da0s3e > fsck: Could not determine filesystem type > wolf# bsdlabel da0s3 > # /dev/da0s3: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 175735035 0 unused 0 0 # "raw" part, > don't edi t > d: 18874368 0 4.2BSD 0 0 0 > e: 156860667 18874368 4.2BSD 0 0 0 > > Therefore, tried directly use fsck_ufs on both USB hard drive and USB = stick > to get file system clean up. All data got back now. > > The machine has run with FreeBSD 6.1 all the way to 7.2 without such > problem. How can we determine what could go wrong in 8.0? FS or USB. Hi, Error 5 means IO error, so probably the transport layer, USB or lower, = is to=20 blame. Some things to check: 1) Make sure the connection for your memory stick is Ok. 2) Make sure there is enough power for your memory stick. Regarding memory sticks: Other operating systems do a port bus reset when the device has a = problem. On=20 FreeBSD we just try a software reset via the control endpoint. I guess = that it=20 is a device problem you are seeing. The USB stack in FreeBSD is faster = than=20 the old one, and maybe the faster queueing of mass storage requests = trigger=20 some hidden bugs in your device. When the problem happens try: sysctl hw.usb.umass.debug=3D-1 --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 11:07:06 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 85E8C1065698 for ; Mon, 23 Nov 2009 11:07:06 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7208D8FC24 for ; Mon, 23 Nov 2009 11:07:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANB76QL070282 for ; Mon, 23 Nov 2009 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANB75PS070280 for freebsd-usb@FreeBSD.org; Mon, 23 Nov 2009 11:07:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Nov 2009 11:07:05 GMT Message-Id: <200911231107.nANB75PS070280@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org 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, 23 Nov 2009 11:07:06 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f usb/140714 usb [hang] system freeze when disconect my flash usb o kern/140614 usb [uplcom] [patch] adding support for Radio Shack Gigwar o usb/140590 usb [bluetooth] [usb] ng_ubt(4) ng_l2cap_process_cmd_rej w o usb/140477 usb [umass] [patch] allow boot-time attachment of daX devi o usb/140325 usb Missing/incorrect initialisation and memory leak in li o usb/140259 usb libusb-1.0 portability/compatibility nits o usb/140242 usb dev/usb/controller/ehci_ix4xx.c shortcomings o usb/140236 usb [msdosfs] Labels wiped on external Journaled USB HDD o o usb/140160 usb USB ports are no longer "active" after ACPI suspend/re o usb/139990 usb [panic] Kernel frequently panics after printing o usb/139598 usb [umass] CAM reports "xptioctl: put "device pass" in yo o usb/139243 usb [uhci] unplug prolific USB serial -> uhci_abort_xfer: o usb/139142 usb [regression] ehci drivers (NVIDIA nForce4 USB 2.0 cont o usb/138915 usb [patch][usb8][usb67] add support for SheevaPlug serial o usb/138904 usb [rum] unpluging USB wifi card panics system f usb/138882 usb [ohci] [panic] Can't install FreeBSD 7.2 due to ohci p o usb/138879 usb [uftdi] [patch] Patch to add support for CTI USB-Mini o usb/138798 usb 8.0-BETA4 can't boot from USB flash drive [regression] o usb/138675 usb [usb8] [panic] page fault, perhaps in USB o usb/138659 usb [usb8][uftdi] driver broken in RELENG_8/CURRENT o usb/138389 usb [usb8] [patch] NULL pointer dereference in usb_endpoin o usb/138175 usb [usb67] [boot] System cannot boot, when USB reader wit o usb/138172 usb Additional dev id for u3g (Option mini PCIe) o usb/138138 usb Novatel U760 for u3g (Verizon and Bell Canada) o usb/138124 usb [usb8] Axed uaudio functionality in the usbng (alterna o usb/138119 usb MultiBay CDROM (propably on USB bus) is not recognized o usb/137872 usb slow booting on usb flash drive f usb/137848 usb Page fault when using an USB bluetooth adapter o usb/137806 usb [ukbd] USB keyboard doesn't work until it's unplugged o usb/137763 usb [usb67][ukbd] Logitech wireless keyboard media keys no o usb/137616 usb [usb67][usb8][usbdevs] [patch]: usbdevs update: Please o usb/137377 usb [usb8] Support for Huawei E180 o usb/137341 usb [usb8][rum] driver if_rum doesn't work at all and thro p usb/137226 usb [usb67][patch] quirk for Philips extern USB disk o usb/137190 usb [usb8][patch] inhibit spurious button releases for som o usb/137189 usb [usb8][patch] create and use sysctl nodes for HID repo p usb/137188 usb [usb8][patch] correctly handle USB report descriptors o usb/137129 usb SteelSeries Ikari USB laser mouse not attaching p usb/136761 usb [usbdevs][usb67][patch] Teach usbdevs / u3g(4) about H o usb/135938 usb [aue] aue driver only passes traffic in promisc mode f usb/135857 usb RTL8187 Wireless Adapter o usb/135575 usb [usbdevs] [patch] Add HTC Wizard phone vid/pid informa o usb/135542 usb [keyboard] boot loader does not work with a usb keyboa p usb/135372 usb [usb67][umass] Quirk report for Teclast TL-C300 usb me o usb/135348 usb [umass] USB Drive Hangs with ZFS (JMicron USB2/eSata) o usb/135206 usb machine reboots when inserted USB device o usb/135200 usb SAMSUNG i740 usb mass: Synchronize cache failed, statu o usb/135182 usb UMASS quirk - Olympus FE20 camera o usb/134950 usb Lowering DTR for USB-modem via ubsa is not possible o usb/134633 usb Add support for WILLCOM03(SHARP smart phone) o usb/134631 usb [usbdevs] [patch] WiSPY DBx support requires usb tweak o usb/134299 usb Kernel Panic plugging in MF626 USB UMTS Stick u3g o usb/134193 usb System freeze on usb MP3 player insertion o usb/134117 usb [Patch] Add support for 'Option GlobeTrotter HSDPA Mod o usb/134085 usb [umass] Adding usb quirk for Sony USB flash drive o usb/133989 usb [newusb] [ukbd] USB keyboard dead at mountroot> prompt o usb/133712 usb [ural] [patch] RE: Fixed an issue with ural(4) that wa o usb/133390 usb umass crashes system in 7.1 when Olympus D-540 attache o usb/133296 usb [rum] driver not working properly in hostap mode p usb/132799 usb [usb][patch]GENESYS USB2IDE requires NO_SYNCHRONIZE_CA o usb/132785 usb [usb] [patch] Gemtech remote powersocket is classed as o usb/132594 usb USB subsystem causes page fault and crashes o usb/132312 usb Xorg 7.4 halts USB controller o usb/132080 usb [patch] [usb] [rum] Kernel panic after NOMEM caused by o usb/132066 usb [ukbd] Keyboard failure USB keyboard DELL 760 o usb/132036 usb [panic] page fault when connecting Olympus C740 camera o usb/131912 usb [uslcom] [patch] New devices using Silicon Labs chips o usb/131900 usb [usbdevs] [patch] Additional product identification co o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c o usb/131123 usb [patch] re-add UQ_ASSUME_CM_OVER_DATA USB quirk o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130230 usb Samsung Electronics YP-U3 does not attach in 7.1-RELEA o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [newusb] DVD drive detects as 'da' device o usb/129945 usb [usbdevs] [patch] add u3g support for Longcheer WM66 U o usb/129766 usb [usb] plugging in usb modem HUAWEI E226 panics system o usb/129758 usb [uftdi] [patch] add Pyramid LCD usb support o usb/129673 usb [uhci] uhci (uhub) confused on replugging USB 1.1 scan o usb/129522 usb [ubsa] [patch] add support for ZTE AC8700 modem o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader o usb/129251 usb [usbdevs] [patch] Liebert UPS being assigned uhid and o usb/129173 usb [uplcom] [patch] Add support for Corega CG-USBRS232R a s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb] [patch] uaudio is not full duplex o usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive o usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/128324 usb [uplcom] [patch] remove baud rate restriction for PL23 o usb/127980 usb [umass] [patch] Fix Samsung YP U2 MP3 player on 7.x an o usb/127926 usb [boot] USB Timeout during bootup p usb/127549 usb [umass] [usb67] [patch] Meizu MiniPlayer M6 (SL) requi s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127423 usb [boot] BTX halted on Gigabyte GA-MA69VM-S2 / AMD Sempr o usb/127342 usb [boot] [panic] enabling usb keyboard and mouse support o usb/127248 usb [ucom] panic while uplcom devices attaach and detach o usb/127222 usb [ohci] Regression in 7.0 usb storage generic driver o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c o usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125736 usb [ukbd] [hang] system hangs after AT keyboard detect if o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d o usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125238 usb [ums] Habu Mouse turns off in X o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o usb/124604 usb [ums] Microsoft combo wireless mouse doesn't work o kern/124130 usb [usb] gmirror fails to start usb devices that were pre o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/123509 usb [umass] continuous reset Samsung SGH-G600 phone o usb/123352 usb [usbdevs] [patch] Add Option GTMAX3.6/7.2 and Quallcom o usb/123351 usb [usbdevs] [patch] Add Reiner SCT cyberJack, Omnikey [2 o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122956 usb [ubsa] [patch] add support for Novatel Wireless XU870 o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa o usb/122819 usb [usb] [patch] Patch to provide dynamic additions to th o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122621 usb [new driver] [patch] New driver for Sierra Wireless 3G o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/122025 usb [uscanner] [patch] uscanner does not attach to Epson R o usb/121755 usb [ohci] [patch] Fix panic after ohci/uhub cardbus devic o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121426 usb [patch] [uscanner] add HP ScanJet 3570C o usb/121275 usb [boot] [panic] FreeBSD fails to boot with usb legacy s o usb/121232 usb [usb] [panic] USB CardBus card removal causes reboot s p usb/121184 usb [uipaq] [patch] add ids from linux ipaq driver (plus a o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS o usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120572 usb [umass] [patch] quirk to support ASUS P535 as umass (a o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/119981 usb [axe] [patch] add support for LOGITEC LAN-GTJ/U2 gigab o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119513 usb [irq] inserting dlink dwl-g630 wireless card results i o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119481 usb [hang] FreeBSD not responding after connecting USB-Mas o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118485 usb [usbdevs] [patch] Logitech Headset Workaround o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [uaudio] [patch] Not possible to record with Plantroni o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a o usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116699 usb [usbhid] USB HID devices do not initialize at system b o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [usb67] [usb8] [umass] [patch] Problem with connection o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff o usb/113060 usb [usb67] [ulpt] [patch] Samsung printer not working in o usb/110856 usb [usb67] [ugen] [patch] interrupt in msgs are truncated s usb/108344 usb [usb67] [atausb] [panic] kernel with atausb panics whe o usb/107827 usb [usb67] [ohci] [panic] ohci_add_done addr not found o usb/107388 usb [usb67] [usb8] [new driver] [patch] add utoppy device o usb/107243 usb [usb67] [cam] [quirk] [patch] Apacer USB Flash Drive q o usb/106041 usb [usb67] [usb8] [request] FreeBSD does not recognise Mu o usb/105361 usb [usb67] [panic] Kernel panic during unmounting mass st s usb/103917 usb [usb67] [uhub] USB driver reports "Addr 0 should never o usb/103418 usb [usb67] [usb8] [patch] [request] usbhidctl(8) add abil o usb/103046 usb [usb67] [ulpt] [patch] ulpt event driven I/O with sele o usb/101775 usb [usb67] [usb8] [libusbhid] [patch] possible error in r o usb/101761 usb [usb67] [patch] [request] usb.h: increase maximal size o usb/100746 usb [usb67] [ukbd] system does not boot due to USB keyboar o usb/99538 usb [keyboard] while using USB keyboard default params of o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o kern/99200 usb [bluetooth] SMP-Kernel crashes reliably when Bluetooth o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb s usb/95348 usb [keyboard] USB keyboard unplug causes noise on screen o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg o usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91629 usb [usb] usbd_abort_pipe() may result in infinite loop o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device f usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa s usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83563 usb [umass] [panic] Page Fault while detaching Mpman Usb d o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82660 usb [ehci] [panic] EHCI: I/O stuck in state 'physrd'/panic s usb/82569 usb [umass] [panic] USB mass storage plug/unplug causes sy o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/80854 usb [patch] [request] suggestion for new iface-no-probe me o usb/80829 usb [modules] [panic] possible panic when loading USB-modu s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails o usb/80040 usb [sound] [hang] Use of sound mixer causes system freeze o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/79722 usb [ehci] wrong alignments in ehci.h a usb/79656 usb [ehci] RHSC interrupts lost o usb/79524 usb [ulpt] printing to Minolta PagePro 1[23]xxW via USB fa o usb/79287 usb [uhci] [hang] UHCI hang after interrupt transfer o usb/79269 usb [ohci] USB ohci da0 plug/unplug causes crashes and loc o usb/78984 usb [umass] [patch] Creative MUVO umass failure o usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/77184 usb [umass] [panic] kernel panic on USB device disconnect, o usb/76732 usb [ums] Mouse problems with USB KVM Switch o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75797 usb [sound] [regression] 5.3-STABLE(2005 1/4) detect USB h o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) o usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/73307 usb [panic] Kernel panics on USB disconnect s usb/72733 usb [ucom] [request] Kyocera 7135 Palm OS connection probl o usb/71455 usb [umass] Slow USB umass performance of 5.3 o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/70523 usb [umct] [patch] umct sending/receiving wrong characters o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s o usb/59698 usb [keyboard] [patch] Rework of ukbd HID to AT code trans s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o i386/46371 usb USB controller cannot be initialized on IBM Netfinity o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 316 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 15:50:02 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5A82106566B for ; Mon, 23 Nov 2009 15:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 797D68FC19 for ; Mon, 23 Nov 2009 15:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANFo2Mn068045 for ; Mon, 23 Nov 2009 15:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANFo2mY068044; Mon, 23 Nov 2009 15:50:02 GMT (envelope-from gnats) Resent-Date: Mon, 23 Nov 2009 15:50:02 GMT Resent-Message-Id: <200911231550.nANFo2mY068044@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-usb@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Corey Smith Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1183106566C for ; Mon, 23 Nov 2009 15:45:54 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0EF8FC15 for ; Mon, 23 Nov 2009 15:45:54 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nANFjsY3091299 for ; Mon, 23 Nov 2009 15:45:54 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nANFjs2W091289; Mon, 23 Nov 2009 15:45:54 GMT (envelope-from nobody) Message-Id: <200911231545.nANFjs2W091289@www.freebsd.org> Date: Mon, 23 Nov 2009 15:45:54 GMT From: Corey Smith To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow 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, 23 Nov 2009 15:50:02 -0000 >Number: 140810 >Category: usb >Synopsis: 8.X+ uftdi copy and paste problem / tty overflow >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 23 15:50:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Corey Smith >Release: 8.0-RC3 >Organization: BondDesk Group >Environment: FreeBSD 8.0-RC3 FreeBSD 8.0-RC3 #2: Fri Nov 20 18:28:57 EST 2009 root@:/usr/src/sys/amd64/compile/GENERIC amd64 >Description: We are using a VSCOM USB-16COM-RM which is a UFTDI based 16 port serial terminal. It is detected as 8 FT2232C dual port serial connections: product FTDI SERIAL_2232C 0x6010 FT2232C Dual port Serial ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x0403 idProduct = 0x6010 bcdDevice = 0x0500 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 If you 'tip ucom1' and paste a long sequence of text into the terminal then the terminal will start to constantly spew what appears to be random memory contents to the host connected on ucom1. This same configuration is known good in 7.1-RELEASE. The problem definitely occurs on 8.0-BETA3 and 8.0-RC3. The serial ports work fine if you never copy and paste but as soon as you start to copy and paste more than 60 odd characters at a time you see this random garbage on the tty. AFAIK the garbage will continuously send to the attached host until you reboot the box. I don't know if this problem is reproducible using other uftdi based devices as I don't have any other hardware to test with. >How-To-Repeat: Paste long sequences of text into a tip session connected through a uftdi device under 8.0-RC3. Notice constant garbage being transmitted to the host until you reboot the console server. >Fix: No fix but a workaround is to not copy and paste into terminals connected through uftdi devices. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 16:23:49 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 A5A5C106566B; Mon, 23 Nov 2009 16:23:49 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swip.net [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id CFDDF8FC0C; Mon, 23 Nov 2009 16:23:48 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MwvWZ3YEoloA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=IzxjMftRdCktUPC0Np8A:9 a=-am4eWILiePMzuJSKrQA:7 a=qPdlMeudGqLF5TLjBP3kCEJ5ws4A:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1151476395; Mon, 23 Nov 2009 17:23:46 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 23 Nov 2009 17:25:19 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911231545.nANFjs2W091289@www.freebsd.org> In-Reply-To: <200911231545.nANFjs2W091289@www.freebsd.org> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911231725.20787.hselasky@c2i.net> Cc: Corey Smith , freebsd-gnats-submit@freebsd.org Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow 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, 23 Nov 2009 16:23:49 -0000 On Monday 23 November 2009 16:45:54 Corey Smith wrote: > >Number: 140810 > >Category: usb > >Synopsis: 8.X+ uftdi copy and paste problem / tty overflow > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon Nov 23 15:50:01 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Corey Smith > >Release: 8.0-RC3 > >Organization: > > BondDesk Group > > >Environment: > > FreeBSD 8.0-RC3 FreeBSD 8.0-RC3 #2: Fri Nov 20 18:28:57 EST 2009 > root@:/usr/src/sys/amd64/compile/GENERIC amd64 > > >Description: > > We are using a VSCOM USB-16COM-RM which is a UFTDI based 16 port serial > terminal. > > It is detected as 8 FT2232C dual port serial connections: > > product FTDI SERIAL_2232C 0x6010 FT2232C Dual port Serial > > ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0008 > idVendor = 0x0403 > idProduct = 0x6010 > bcdDevice = 0x0500 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > If you 'tip ucom1' and paste a long sequence of text into the terminal then > the terminal will start to constantly spew what appears to be random memory > contents to the host connected on ucom1. This same configuration is known > good in 7.1-RELEASE. > > The problem definitely occurs on 8.0-BETA3 and 8.0-RC3. The serial ports > work fine if you never copy and paste but as soon as you start to copy and > paste more than 60 odd characters at a time you see this random garbage on > the tty. AFAIK the garbage will continuously send to the attached host > until you reboot the box. > > I don't know if this problem is reproducible using other uftdi based > devices as I don't have any other hardware to test with. > > >How-To-Repeat: > > Paste long sequences of text into a tip session connected through a uftdi > device under 8.0-RC3. Notice constant garbage being transmitted to the > host until you reboot the console server. > > >Fix: > > No fix but a workaround is to not copy and paste into terminals connected > through uftdi devices. > Hi, I can you enable ucom debugging while doing the test? sysctl hw.usb.ucom.debug=15 --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 16:30:11 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 801881065670 for ; Mon, 23 Nov 2009 16:30:11 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id DBD1D8FC08 for ; Mon, 23 Nov 2009 16:30:10 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=wi4sf3SumDsKocyKlhMA:9 a=ybdNRJvGGF3-J4Xq5J4A:7 a=KNBZ6aWmjzg5utrE_p3opsJ6g1YA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1334494582; Mon, 23 Nov 2009 17:30:08 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 23 Nov 2009 17:31:44 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <4B099A50.9000006@gmail.com> In-Reply-To: <4B099A50.9000006@gmail.com> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911231731.45953.hselasky@c2i.net> Cc: Subject: Re: usb ethernet driver question 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, 23 Nov 2009 16:30:11 -0000 On Sunday 22 November 2009 21:08:48 Alexander Samarin wrote: > Hello, all! > > I'm trying to write a kernel module driver for WiMAX modem. > I have Samsung SWC-U100 USB modem. > > Driver is based on if_cue module (it's source file is smallest in the > tree). I've get module successfully attaching to device and registering new > network interface, but some questions appeared: > > 1. madwimax project have a description of protocol of the modem, but it > says simply "This data should be sent over OUT endpoint in bulk mode." In > other drivers I found only calls to functionu ether_do_request() e.g: > > struct usb_device_request req; > > req.bmRequestType = UT_READ_VENDOR_DEVICE; > req.bRequest = CUE_CMD_GET_MACADDR; > USETW(req.wValue, 0); > USETW(req.wIndex, 0); > USETW(req.wLength, ETHER_ADDR_LEN); > > uether_do_request(&sc->sc_ue, &req, buf, 1000); > > Here I can't understand: > Buffer can be sent or received via buf argument of ether_do_request(), > but what value should be used for req.bRequest, req.wValue and req.wIndex > fields? Hi, The example you have given is for a CONTROL endpoint. CONTROL endpoint messages typically consist of 3 stages: BULK endpoints only transfer If the configuration data is sent accross a BULK endpoint, you need to allocate a separate BULK endpoint for that and consequently cannot use ether_do_request(). > > In dev/usb/net/if_* files drivers read and write to registers or memory > of chip; libusb just writes to file descriptor. > > Can anyone take me a link where I can read more about programming usb > drivers for kernel? man 4 usb > > 2. Is it possible to detach CAM subsystem from virtual DVD-ROM on other > interface? This DVD-ROM contains WinXP drivers and access program, > which will never be used (I think) on UNIX systems. Yes: 1) parent the CAM interface to your driver. Then umass won't attach to it 2) look in sys/dev/usb/usb_msctest.c > > PS: I know that if_cue is an ethernet driver, but WiMAX is a wireless so > basing driver on if_cue code is not a good idea, but wireless drivers are > big and my modem can connect only to one provider (Yota) so I decided to > use if_cue as base code. > > PS2: sorry for my English. Your English is good! --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 16:30:13 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28694106566C for ; Mon, 23 Nov 2009 16:30:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F22A88FC18 for ; Mon, 23 Nov 2009 16:30:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANGUCi1091385 for ; Mon, 23 Nov 2009 16:30:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANGUC9l091372; Mon, 23 Nov 2009 16:30:12 GMT (envelope-from gnats) Date: Mon, 23 Nov 2009 16:30:12 GMT Message-Id: <200911231630.nANGUC9l091372@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 16:30:13 -0000 The following reply was made to PR usb/140810; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Corey Smith , freebsd-gnats-submit@freebsd.org Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow Date: Mon, 23 Nov 2009 17:25:19 +0100 On Monday 23 November 2009 16:45:54 Corey Smith wrote: > >Number: 140810 > >Category: usb > >Synopsis: 8.X+ uftdi copy and paste problem / tty overflow > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon Nov 23 15:50:01 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Corey Smith > >Release: 8.0-RC3 > >Organization: > > BondDesk Group > > >Environment: > > FreeBSD 8.0-RC3 FreeBSD 8.0-RC3 #2: Fri Nov 20 18:28:57 EST 2009 > root@:/usr/src/sys/amd64/compile/GENERIC amd64 > > >Description: > > We are using a VSCOM USB-16COM-RM which is a UFTDI based 16 port serial > terminal. > > It is detected as 8 FT2232C dual port serial connections: > > product FTDI SERIAL_2232C 0x6010 FT2232C Dual port Serial > > ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0008 > idVendor = 0x0403 > idProduct = 0x6010 > bcdDevice = 0x0500 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > bNumConfigurations = 0x0001 > > If you 'tip ucom1' and paste a long sequence of text into the terminal then > the terminal will start to constantly spew what appears to be random memory > contents to the host connected on ucom1. This same configuration is known > good in 7.1-RELEASE. > > The problem definitely occurs on 8.0-BETA3 and 8.0-RC3. The serial ports > work fine if you never copy and paste but as soon as you start to copy and > paste more than 60 odd characters at a time you see this random garbage on > the tty. AFAIK the garbage will continuously send to the attached host > until you reboot the box. > > I don't know if this problem is reproducible using other uftdi based > devices as I don't have any other hardware to test with. > > >How-To-Repeat: > > Paste long sequences of text into a tip session connected through a uftdi > device under 8.0-RC3. Notice constant garbage being transmitted to the > host until you reboot the console server. > > >Fix: > > No fix but a workaround is to not copy and paste into terminals connected > through uftdi devices. > Hi, I can you enable ucom debugging while doing the test? sysctl hw.usb.ucom.debug=15 --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 18:04:24 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 05C861065672 for ; Mon, 23 Nov 2009 18:04:24 +0000 (UTC) (envelope-from oxyd.oxyd@gmail.com) Received: from mail-bw0-f220.google.com (mail-bw0-f220.google.com [209.85.218.220]) by mx1.freebsd.org (Postfix) with ESMTP id 917978FC08 for ; Mon, 23 Nov 2009 18:04:23 +0000 (UTC) Received: by bwz20 with SMTP id 20so4221820bwz.14 for ; Mon, 23 Nov 2009 10:04:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=XEYCWLKoaXFGBptNysuyQrHnnbRa9tVeCyiQkUvIMPM=; b=ZdUeM3ASlU4+4sU7sjDMImhI/FWQT/XbSkrsNgf0cxfIkI/N5JYCEpvEgPSJppg3zS WL1Y5OsoVtwu4Vyi9vqCb0MMaO4iHLLIszKe3QwmmxV0C0rOc7fhuvRKvCUfobYPtl5E FnS5GZqVISYC2tyZ3iTS82WaC8Rk+pnqun6/s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CDLQzEwOXTeSMbaWLhQ3XtAgA7mUgEgQgnklaYvC5eZuBUp7VB4FW8UMsxCH7gHOqM yIxeHuDB6T6+ua3r9APCWUL0E/Xr2IVK+UF7SDR4qx3g/25EbZar70pGTBjLHw17of8k Cd9PxixYjHOJtSpx6V/EOjumz+TIbkm1hHHTs= MIME-Version: 1.0 Received: by 10.103.37.27 with SMTP id p27mr2380947muj.46.1258999462503; Mon, 23 Nov 2009 10:04:22 -0800 (PST) Date: Mon, 23 Nov 2009 19:04:22 +0100 Message-ID: From: =?UTF-8?Q?Ond=C5=99ej_Majerech?= To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: USB mouse not working on 8.0-RELEASE 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, 23 Nov 2009 18:04:24 -0000 Hello, I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009 root@starlight:/usr/obj/usr/src/sys/STARLIGHT i386) via csup'ing to RELENG_8_0 and the usual suite of buildworld, buildkernel, installkernel, mergemaster -p, installworld, mergemaster. My USB mouse doesn't work now. While booting, I can see error messages from the USB part of the kernel; the same messages also reappear when I disconnect and reconnect the thing. They read the following: (Grabbed from /var/log/messages after having dis- and re-connected the mouse.) Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2 failed (USB_ERR_TIMEOUT, ignored) Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT! Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT! Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT! Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0 (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435: could not allocate new device! The mouse was working without any problems whatsoever on 8.0-RC3 and all older FBSD versions that I used. Other USB devices work as they should, without producing anything unusual in dmesg. So, what's up? Any clues? ~ Ondra From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 19:16:18 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 95129106566B; Mon, 23 Nov 2009 19:16:18 +0000 (UTC) (envelope-from csmith@bonddesk.com) Received: from msmisps01.bonddesk.com (msmisps01.bonddesk.com [12.47.70.99]) by mx1.freebsd.org (Postfix) with ESMTP id 471E28FC08; Mon, 23 Nov 2009 19:16:18 +0000 (UTC) Received: from MIEXCH.bdg.local ([10.132.16.199]) by mimail2.bdg.local with Microsoft SMTPSVC(6.0.3790.3959); Mon, 23 Nov 2009 14:01:12 -0500 Received: from [10.133.16.38] (10.133.16.38) by miexch.bonddesk.com (10.132.16.199) with Microsoft SMTP Server id 8.1.393.1; Mon, 23 Nov 2009 14:01:11 -0500 From: Corey Smith To: Hans Petter Selasky In-Reply-To: <200911231725.20787.hselasky@c2i.net> References: <200911231545.nANFjs2W091289@www.freebsd.org> <200911231725.20787.hselasky@c2i.net> Content-Type: text/plain; charset="UTF-8" Date: Mon, 23 Nov 2009 13:59:56 -0500 Message-ID: <1259002796.16068.110.camel@csmith-desktop.bdg.local> MIME-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Nov 2009 19:01:12.0272 (UTC) FILETIME=[52F94D00:01CA6C6F] Cc: "freebsd-gnats-submit@freebsd.org" , "freebsd-usb@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow 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, 23 Nov 2009 19:16:18 -0000 On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote: > sysctl hw.usb.ucom.debug=15 Thanks for the quick reply. I decided to do a fresh install of 8.0-RELEASE amd64 before I re-ran the test. Here are the details: # uname -a FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # sysctl hw.usb.ucom.debug=15 # tip ucom1 connected # paste 160 "a"s followed by a newline (may take several attempts when debugging is enabled) aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 2 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 4 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 8 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 4 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 13 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 26 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 14 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 37 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 34 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 2 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 4 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 8 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 4 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 3 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 3 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 14 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 9 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 14 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 11 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 5 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 12 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 5 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 17 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 12 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 2 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 7 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 5 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 4 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 23 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 16 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 14 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 68 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 4 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 last message repeated 135 times Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 last message repeated 9 times Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 last message repeated 3 times Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:39 lab1 last message repeated 1307 times Nov 23 14:57:39 lab1 kernel: Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:42 lab1 last message repeated 212 times Nov 23 14:57:43 lab1 kernel: Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:45 lab1 last message repeated 187 times Nov 23 14:57:46 lab1 kernel: Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:58 lab1 last message repeated 801 times Nov 23 14:57:58 lab1 kernel: Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:58:29 lab1 last message repeated 1891 times Nov 23 14:58:29 lab1 last message repeated 50 times Nov 23 14:58:29 lab1 kernel: Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:58:55 lab1 last message repeated 1640 times Nov 23 14:58:56 lab1 kernel: Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:59:27 lab1 last message repeated 1940 times Nov 23 14:59:43 lab1 last message repeated 1051 times Nov 23 14:59:43 lab1 kernel: Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:59:57 lab1 last message repeated 825 times Nov 23 14:59:57 lab1 kernel: Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K Nov 23 15:00:00 lab1 last message repeated 208 times I believe the problem occurs whenever you see a message like this: Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 >From a look at the code it looks like the largest uftdi frame is 64 characters (UFTDI_[IO]BUFSIZE in uftdi.c). Perhaps it is an off by one bug? -Corey Smith From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 19:20:07 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5032106566B for ; Mon, 23 Nov 2009 19:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 797008FC1A for ; Mon, 23 Nov 2009 19:20:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANJK7MA038547 for ; Mon, 23 Nov 2009 19:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANJK7rA038529; Mon, 23 Nov 2009 19:20:07 GMT (envelope-from gnats) Date: Mon, 23 Nov 2009 19:20:07 GMT Message-Id: <200911231920.nANJK7rA038529@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Corey Smith Cc: Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Corey Smith List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 19:20:07 -0000 The following reply was made to PR usb/140810; it has been noted by GNATS. From: Corey Smith To: Hans Petter Selasky Cc: "freebsd-usb@freebsd.org" , "freebsd-gnats-submit@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow Date: Mon, 23 Nov 2009 13:59:56 -0500 On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote: > sysctl hw.usb.ucom.debug=15 Thanks for the quick reply. I decided to do a fresh install of 8.0-RELEASE amd64 before I re-ran the test. Here are the details: # uname -a FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # sysctl hw.usb.ucom.debug=15 # tip ucom1 connected # paste 160 "a"s followed by a newline (may take several attempts when debugging is enabled) aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 2 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 4 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 8 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 4 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 13 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 26 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 14 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 37 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37 Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:14 lab1 last message repeated 34 times Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33 Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 2 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 4 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 8 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 4 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 3 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 3 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 14 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 9 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 14 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 11 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 5 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 12 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 5 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41 Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 17 times Nov 23 14:57:15 lab1 kernel: Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:15 lab1 last message repeated 12 times Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29 Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 2 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 7 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 5 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 4 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 23 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 16 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 14 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 68 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:16 lab1 last message repeated 4 times Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 last message repeated 135 times Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 last message repeated 9 times Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 last message repeated 3 times Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:18 lab1 kernel: Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:39 lab1 last message repeated 1307 times Nov 23 14:57:39 lab1 kernel: Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:42 lab1 last message repeated 212 times Nov 23 14:57:43 lab1 kernel: Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:45 lab1 last message repeated 187 times Nov 23 14:57:46 lab1 kernel: Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:57:58 lab1 last message repeated 801 times Nov 23 14:57:58 lab1 kernel: Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:58:29 lab1 last message repeated 1891 times Nov 23 14:58:29 lab1 last message repeated 50 times Nov 23 14:58:29 lab1 kernel: Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:58:55 lab1 last message repeated 1640 times Nov 23 14:58:56 lab1 kernel: Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:59:27 lab1 last message repeated 1940 times Nov 23 14:59:43 lab1 last message repeated 1051 times Nov 23 14:59:43 lab1 kernel: Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 14:59:57 lab1 last message repeated 825 times Nov 23 14:59:57 lab1 kernel: Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K Nov 23 15:00:00 lab1 last message repeated 208 times I believe the problem occurs whenever you see a message like this: Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 >From a look at the code it looks like the largest uftdi frame is 64 characters (UFTDI_[IO]BUFSIZE in uftdi.c). Perhaps it is an off by one bug? -Corey Smith From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 20:59:46 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 C2376106566C; Mon, 23 Nov 2009 20:59:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id A7EB78FC1A; Mon, 23 Nov 2009 20:59:45 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MwvWZ3YEoloA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=P3HaITYvK0r1JtnhZhIA:9 a=mSna2sX48TDHwHJ8OtsA:7 a=SLjr6PWxxXwPglxtzvFpqlqjm_AA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1239323204; Mon, 23 Nov 2009 21:59:40 +0100 From: Hans Petter Selasky To: Corey Smith Date: Mon, 23 Nov 2009 22:01:12 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911231545.nANFjs2W091289@www.freebsd.org> <200911231725.20787.hselasky@c2i.net> <1259002796.16068.110.camel@csmith-desktop.bdg.local> In-Reply-To: <1259002796.16068.110.camel@csmith-desktop.bdg.local> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911232201.15414.hselasky@c2i.net> Cc: "freebsd-gnats-submit@freebsd.org" , "freebsd-usb@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow 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, 23 Nov 2009 20:59:46 -0000 On Monday 23 November 2009 19:59:56 Corey Smith wrote: > On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote: > > sysctl hw.usb.ucom.debug=15 > > Thanks for the quick reply. I decided to do a fresh install of > 8.0-RELEASE amd64 before I re-ran the test. Here are the details: > > # uname -a > FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC > 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # > sysctl hw.usb.ucom.debug=15 > # tip ucom1 > connected > # paste 160 "a"s followed by a newline (may take several attempts when > debugging is enabled) > aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa >aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa >aaaaaaaa > > Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 2 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 4 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 8 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 4 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 13 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 26 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 14 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 37 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 34 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 2 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 4 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 8 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 4 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 3 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 3 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 14 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 9 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 14 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 11 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 5 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 12 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 5 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 17 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 12 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 2 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 7 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 5 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 4 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 23 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 16 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 14 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 68 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 4 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 last message repeated 135 times > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 last message repeated 9 times > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 last message repeated 3 times > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:39 lab1 last message repeated 1307 times > Nov 23 14:57:39 lab1 kernel: > Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:42 lab1 last message repeated 212 times > Nov 23 14:57:43 lab1 kernel: > Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:45 lab1 last message repeated 187 times > Nov 23 14:57:46 lab1 kernel: > Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:58 lab1 last message repeated 801 times > Nov 23 14:57:58 lab1 kernel: > Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:58:29 lab1 last message repeated 1891 times > Nov 23 14:58:29 lab1 last message repeated 50 times > Nov 23 14:58:29 lab1 kernel: > Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:58:55 lab1 last message repeated 1640 times > Nov 23 14:58:56 lab1 kernel: > Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:59:27 lab1 last message repeated 1940 times > Nov 23 14:59:43 lab1 last message repeated 1051 times > Nov 23 14:59:43 lab1 kernel: > Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:59:57 lab1 last message repeated 825 times > Nov 23 14:59:57 lab1 kernel: > Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K > Nov 23 15:00:00 lab1 last message repeated 208 times > > I believe the problem occurs whenever you see a message like this: > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 > > >From a look at the code it looks like the largest uftdi frame is 64 > > characters (UFTDI_[IO]BUFSIZE in uftdi.c). Perhaps it is an off by one > > bug? > > -Corey Smith Hi, Your issue looks like a hardware issue. Does the following patch help? ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 - src/sys/dev/usb/serial/uftdi.c ==== @@ -165,7 +165,7 @@ .endpoint = UE_ADDR_ANY, .direction = UE_DIR_OUT, .bufsize = UFTDI_OBUFSIZE, - .flags = {.pipe_bof = 1,.force_short_xfer = 1,}, + .flags = {.pipe_bof = 1,}, .callback = &uftdi_write_callback, }, From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 21:00:21 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E71581065672 for ; Mon, 23 Nov 2009 21:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CA5D18FC12 for ; Mon, 23 Nov 2009 21:00:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANL0Lui023125 for ; Mon, 23 Nov 2009 21:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANL0L8t023101; Mon, 23 Nov 2009 21:00:21 GMT (envelope-from gnats) Date: Mon, 23 Nov 2009 21:00:21 GMT Message-Id: <200911232100.nANL0L8t023101@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 21:00:22 -0000 The following reply was made to PR usb/140810; it has been noted by GNATS. From: Hans Petter Selasky To: Corey Smith Cc: "freebsd-usb@freebsd.org" , "freebsd-gnats-submit@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow Date: Mon, 23 Nov 2009 22:01:12 +0100 On Monday 23 November 2009 19:59:56 Corey Smith wrote: > On Mon, 2009-11-23 at 11:25 -0500, Hans Petter Selasky wrote: > > sysctl hw.usb.ucom.debug=15 > > Thanks for the quick reply. I decided to do a fresh install of > 8.0-RELEASE amd64 before I re-ran the test. Here are the details: > > # uname -a > FreeBSD lab1 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC > 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # > sysctl hw.usb.ucom.debug=15 > # tip ucom1 > connected > # paste 160 "a"s followed by a newline (may take several attempts when > debugging is enabled) > aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa >aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa >aaaaaaaa > > Nov 23 14:54:13 lab1 su: csmith to root on /dev/pts/0 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 2 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=3 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 4 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 8 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=9 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 4 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 13 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=13 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 26 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=27 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 14 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=15 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 37 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=37 > Nov 23 14:57:14 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:14 lab1 last message repeated 34 times > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=33 > Nov 23 14:57:14 lab1 kernel: ucom_get_data:1064: cnt=0 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 2 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=3 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 4 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 8 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=9 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 4 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 3 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 3 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=14 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 14 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 9 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=26 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 14 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=15 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 11 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 5 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 12 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 5 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=41 > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 17 times > Nov 23 14:57:15 lab1 kernel: > Nov 23 14:57:15 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:15 lab1 last message repeated 12 times > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=29 > Nov 23 14:57:15 lab1 kernel: ucom_get_data:1064: cnt=0 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 2 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=3 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=2 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 7 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=8 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 5 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 4 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=5 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 23 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=23 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 16 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=17 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 14 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=15 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 68 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 > Nov 23 14:57:16 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:16 lab1 last message repeated 4 times > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=6 > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=0 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: ucom_get_data:1064: cnt=1 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 last message repeated 135 times > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 last message repeated 9 times > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 last message repeated 3 times > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:18 lab1 kernel: > Nov 23 14:57:18 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:39 lab1 last message repeated 1307 times > Nov 23 14:57:39 lab1 kernel: > Nov 23 14:57:39 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:42 lab1 last message repeated 212 times > Nov 23 14:57:43 lab1 kernel: > Nov 23 14:57:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:45 lab1 last message repeated 187 times > Nov 23 14:57:46 lab1 kernel: > Nov 23 14:57:46 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:57:58 lab1 last message repeated 801 times > Nov 23 14:57:58 lab1 kernel: > Nov 23 14:57:58 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:58:29 lab1 last message repeated 1891 times > Nov 23 14:58:29 lab1 last message repeated 50 times > Nov 23 14:58:29 lab1 kernel: > Nov 23 14:58:29 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:58:55 lab1 last message repeated 1640 times > Nov 23 14:58:56 lab1 kernel: > Nov 23 14:58:56 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:59:27 lab1 last message repeated 1940 times > Nov 23 14:59:43 lab1 last message repeated 1051 times > Nov 23 14:59:43 lab1 kernel: > Nov 23 14:59:43 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 14:59:57 lab1 last message repeated 825 times > Nov 23 14:59:57 lab1 kernel: > Nov 23 14:59:57 lab1 kernel: ucom_outwakeup:1009: sc = 0xffffff0003052858 > Nov 23 15:00:00 lab1 newsyslog[926]: logfile turned over due to size>100K > Nov 23 15:00:00 lab1 last message repeated 208 times > > I believe the problem occurs whenever you see a message like this: > Nov 23 14:57:16 lab1 kernel: ucom_get_data:1064: cnt=64 > > >From a look at the code it looks like the largest uftdi frame is 64 > > characters (UFTDI_[IO]BUFSIZE in uftdi.c). Perhaps it is an off by one > > bug? > > -Corey Smith Hi, Your issue looks like a hardware issue. Does the following patch help? ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 - src/sys/dev/usb/serial/uftdi.c ==== @@ -165,7 +165,7 @@ .endpoint = UE_ADDR_ANY, .direction = UE_DIR_OUT, .bufsize = UFTDI_OBUFSIZE, - .flags = {.pipe_bof = 1,.force_short_xfer = 1,}, + .flags = {.pipe_bof = 1,}, .callback = &uftdi_write_callback, }, From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 21:36:46 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 D81E21065672 for ; Mon, 23 Nov 2009 21:36:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 3A80C8FC08 for ; Mon, 23 Nov 2009 21:36:45 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pE_spTFHMUsA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=1AuMVPy_i8CPJVH2ngkA:9 a=1G3XFPASYMnsZx0DDKYA:7 a=KwxrJMzhpXiRCqXDUgTSnZIz1lQA:4 a=dQ29aqnPkupDFo4c:21 a=9TsVT3Bf9FU8KMOW:21 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1322449251; Mon, 23 Nov 2009 22:36:43 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 23 Nov 2009 22:38:17 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpO< =?utf-8?q?Q0yAl=7E=3F=60=27F=3FjDVb=5DE6TQ7=27=23h-VlLs=7Dk/=0A=09?=(yxg(p!IL.`#ng"%`BMrham7%UK,}VH\wUOm=^>wEEQ+KWt[{J#x6ow~JO:,zwp.(t; @ =?utf-8?q?Aq=0A=09=3A4=3A=26nFCgDb8=5B3oIeTb=5E=27?=",; u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200911232238.19592.hselasky@c2i.net> Cc: Subject: Re: USB mouse not working on 8.0-RELEASE 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, 23 Nov 2009 21:36:46 -0000 On Monday 23 November 2009 19:04:22 Ond=C5=99ej Majerech wrote: > Hello, > > I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight > 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009 > root@starlight:/usr/obj/usr/src/sys/STARLIGHT i386) via csup'ing to > RELENG_8_0 and the usual suite of buildworld, buildkernel, > installkernel, mergemaster -p, installworld, mergemaster. > > My USB mouse doesn't work now. While booting, I can see error > messages from the USB part of the kernel; the same messages also > reappear when I disconnect and reconnect the thing. They read the > following: (Grabbed from /var/log/messages after having dis- and > re-connected the mouse.) > > Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2 > failed (USB_ERR_TIMEOUT, ignored) > Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting > device descriptor at addr 2 failed, USB_ERR_TIMEOUT! > Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=3D2, > set address failed! (USB_ERR_TIMEOUT, ignored) > Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting > device descriptor at addr 2 failed, USB_ERR_TIMEOUT! > Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=3D2, > set address failed! (USB_ERR_TIMEOUT, ignored) > Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting > device descriptor at addr 2 failed, USB_ERR_TIMEOUT! > Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0 > (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435: > could not allocate new device! > > The mouse was working without any problems whatsoever on 8.0-RC3 and > all older FBSD versions that I used. > > Other USB devices work as they should, without producing anything > unusual in dmesg. > > So, what's up? Any clues? Hi, This looks like a regression issue. There has been some changes with regard= to=20 USB legacy support handling. Try disabling USB legacy support in the BIOS o= r=20 try to see if the problem is present in a 9-current kernel. Thanks for reporting your issue! =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 22:05:47 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 60FCB106568F; Mon, 23 Nov 2009 22:05:47 +0000 (UTC) (envelope-from csmith@bonddesk.com) Received: from msmisps01.bonddesk.com (msmisps01.bonddesk.com [12.47.70.99]) by mx1.freebsd.org (Postfix) with ESMTP id 0C5098FC17; Mon, 23 Nov 2009 22:05:46 +0000 (UTC) Received: from MIEXCH.bdg.local ([10.132.16.199]) by mimail2.bdg.local with Microsoft SMTPSVC(6.0.3790.3959); Mon, 23 Nov 2009 17:05:43 -0500 Received: from [10.133.16.38] (10.133.16.38) by miexch.bonddesk.com (10.132.16.199) with Microsoft SMTP Server id 8.1.393.1; Mon, 23 Nov 2009 17:05:42 -0500 From: Corey Smith To: Hans Petter Selasky In-Reply-To: <200911232201.15414.hselasky@c2i.net> References: <200911231545.nANFjs2W091289@www.freebsd.org> <200911231725.20787.hselasky@c2i.net> <1259002796.16068.110.camel@csmith-desktop.bdg.local> <200911232201.15414.hselasky@c2i.net> Content-Type: text/plain; charset="UTF-8" Date: Mon, 23 Nov 2009 17:04:27 -0500 Message-ID: <1259013867.16068.116.camel@csmith-desktop.bdg.local> MIME-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Nov 2009 22:05:43.0480 (UTC) FILETIME=[19ED9380:01CA6C89] Cc: "freebsd-gnats-submit@freebsd.org" , "freebsd-usb@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow 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, 23 Nov 2009 22:05:47 -0000 On Mon, 2009-11-23 at 16:01 -0500, Hans Petter Selasky wrote: > Your issue looks like a hardware issue. Does the following patch help? > > ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 - > src/sys/dev/usb/serial/uftdi.c ==== > @@ -165,7 +165,7 @@ > .endpoint = UE_ADDR_ANY, > .direction = UE_DIR_OUT, > .bufsize = UFTDI_OBUFSIZE, > - .flags = {.pipe_bof = 1,.force_short_xfer = 1,}, > + .flags = {.pipe_bof = 1,}, > .callback = &uftdi_write_callback, > }, > Your patch worked. FWIW: This patch also works: # diff -u sys/dev/usb/serial/uftdi.c.orig sys/dev/usb/serial/uftdi.c --- sys/dev/usb/serial/uftdi.c.orig 2009-11-23 16:48:01.000000000 -0500 +++ sys/dev/usb/serial/uftdi.c 2009-11-23 17:54:23.000000000 -0500 @@ -93,7 +93,7 @@ #define UFTDI_IBUFSIZE 64 /* bytes, maximum number of bytes per * frame */ -#define UFTDI_OBUFSIZE 64 /* bytes, cannot be increased due to +#define UFTDI_OBUFSIZE 63 /* bytes, cannot be increased due to * do size encoding */ enum { Is there a way to fix this so USB-16COM-RM will work properly in a -RELEASE again? -Corey Smith From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 22:10:09 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A322D106568B for ; Mon, 23 Nov 2009 22:10:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 91A158FC19 for ; Mon, 23 Nov 2009 22:10:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANMA9t4063865 for ; Mon, 23 Nov 2009 22:10:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANMA8cc063848; Mon, 23 Nov 2009 22:10:08 GMT (envelope-from gnats) Date: Mon, 23 Nov 2009 22:10:08 GMT Message-Id: <200911232210.nANMA8cc063848@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Corey Smith Cc: Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Corey Smith List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 22:10:09 -0000 The following reply was made to PR usb/140810; it has been noted by GNATS. From: Corey Smith To: Hans Petter Selasky Cc: "freebsd-usb@freebsd.org" , "freebsd-gnats-submit@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow Date: Mon, 23 Nov 2009 17:04:27 -0500 On Mon, 2009-11-23 at 16:01 -0500, Hans Petter Selasky wrote: > Your issue looks like a hardware issue. Does the following patch help? > > ==== //depot/projects/usb/src/sys/dev/usb/serial/uftdi.c#16 - > src/sys/dev/usb/serial/uftdi.c ==== > @@ -165,7 +165,7 @@ > .endpoint = UE_ADDR_ANY, > .direction = UE_DIR_OUT, > .bufsize = UFTDI_OBUFSIZE, > - .flags = {.pipe_bof = 1,.force_short_xfer = 1,}, > + .flags = {.pipe_bof = 1,}, > .callback = &uftdi_write_callback, > }, > Your patch worked. FWIW: This patch also works: # diff -u sys/dev/usb/serial/uftdi.c.orig sys/dev/usb/serial/uftdi.c --- sys/dev/usb/serial/uftdi.c.orig 2009-11-23 16:48:01.000000000 -0500 +++ sys/dev/usb/serial/uftdi.c 2009-11-23 17:54:23.000000000 -0500 @@ -93,7 +93,7 @@ #define UFTDI_IBUFSIZE 64 /* bytes, maximum number of bytes per * frame */ -#define UFTDI_OBUFSIZE 64 /* bytes, cannot be increased due to +#define UFTDI_OBUFSIZE 63 /* bytes, cannot be increased due to * do size encoding */ enum { Is there a way to fix this so USB-16COM-RM will work properly in a -RELEASE again? -Corey Smith From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 22:18:08 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 C43051065679 for ; Mon, 23 Nov 2009 22:18:08 +0000 (UTC) (envelope-from oxyd.oxyd@gmail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 5A4928FC16 for ; Mon, 23 Nov 2009 22:18:08 +0000 (UTC) Received: by fxm10 with SMTP id 10so3389697fxm.14 for ; Mon, 23 Nov 2009 14:18:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fUoaBwkute98W+MqK32gzaG948a3u9rWjZ0pf6IGc9w=; b=eZzY8RLpJyWkQEj1fDVz4CuQX+42Q4WTggYervfKuNYz4S7wP/bvLBhvmLRg5/2tia AjJK0FhhjG4OatZfab+NbPSNLtVQIPPbfFHY/GH4MERFTljTOgxUpnCLqXRFbRETbm9x myV0uoAF3Xoc+pV0dUu7Qyiqn+dVKuxaRJ2Cc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=laVl94ze56/olcabBNaW96wzN/nCb0Ajckx6bnh7bFLtoaGVg3Cv9H7SHhVIPqN4Bm jW5idsW6uWPD3uiwu70Fq9UwEwt85QyM8MifCNmqjwx7SbFiykGsT8BAn1i+NgTF6eRx K33RV8PJE+E85gOhZIYtxKa03si8is2Pa8fX8= MIME-Version: 1.0 Received: by 10.103.81.2 with SMTP id i2mr2421079mul.81.1259014687379; Mon, 23 Nov 2009 14:18:07 -0800 (PST) In-Reply-To: <200911232238.19592.hselasky@c2i.net> References: <200911232238.19592.hselasky@c2i.net> Date: Mon, 23 Nov 2009 23:18:07 +0100 Message-ID: From: =?UTF-8?Q?Ond=C5=99ej_Majerech?= To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB mouse not working on 8.0-RELEASE 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, 23 Nov 2009 22:18:08 -0000 2009/11/23 Hans Petter Selasky : > On Monday 23 November 2009 19:04:22 Ond=C5=99ej Majerech wrote: >> Hello, >> >> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight >> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009 >> root@starlight:/usr/obj/usr/src/sys/STARLIGHT =C2=A0i386) via csup'ing t= o >> RELENG_8_0 and the usual suite of buildworld, buildkernel, >> installkernel, mergemaster -p, installworld, mergemaster. >> >> My USB mouse doesn't work now. =C2=A0While booting, I can see error >> messages from the USB part of the kernel; the same messages also >> reappear when I disconnect and reconnect the thing. =C2=A0They read the >> following: (Grabbed from /var/log/messages after having dis- and >> re-connected the mouse.) >> >> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2 >> failed (USB_ERR_TIMEOUT, ignored) >> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting >> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! >> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=3D2, >> set address failed! (USB_ERR_TIMEOUT, ignored) >> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting >> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! >> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=3D2, >> set address failed! (USB_ERR_TIMEOUT, ignored) >> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting >> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! >> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0 >> (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435: >> could not allocate new device! >> >> The mouse was working without any problems whatsoever on 8.0-RC3 and >> all older FBSD versions that I used. >> >> Other USB devices work as they should, without producing anything >> unusual in dmesg. >> >> So, what's up? =C2=A0Any clues? > > Hi, > > This looks like a regression issue. There has been some changes with rega= rd to > USB legacy support handling. Try disabling USB legacy support in the BIOS= or > try to see if the problem is present in a 9-current kernel. > > Thanks for reporting your issue! > > --HPS > > The only option in my BIOS regarding legacy USB is "Legacy USB storage detect" -- I set this one to Disabled and booted with the mouse disabled -- when I connected it to the running system, it got detected properly, but it simply wouldn't work in X. When I rebooted with the mouse plugged in, the same thing as before happened -- error messages during boot, and un- and re-plugging produced the same errors. I'll try 9-CURRENT sometime tomorrow and report back how that turned out. ~ Ondra From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 22:22:03 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 B02AC1065693; Mon, 23 Nov 2009 22:22:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.tele2.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id DC50B8FC16; Mon, 23 Nov 2009 22:22:02 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MwvWZ3YEoloA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=6I5d2MoRAAAA:8 a=J30LZI322NJJtqDZba8A:9 a=GyLPzoCu-8dgUu5cPk4A:7 a=mSKDy3ffd1vxV5LYOHCE7X06LTIA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1149145934; Mon, 23 Nov 2009 23:22:00 +0100 From: Hans Petter Selasky To: Corey Smith , Andrew Thompson Date: Mon, 23 Nov 2009 23:23:36 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911231545.nANFjs2W091289@www.freebsd.org> <200911232201.15414.hselasky@c2i.net> <1259013867.16068.116.camel@csmith-desktop.bdg.local> In-Reply-To: <1259013867.16068.116.camel@csmith-desktop.bdg.local> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911232323.37784.hselasky@c2i.net> Cc: "freebsd-gnats-submit@freebsd.org" , "freebsd-usb@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow 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, 23 Nov 2009 22:22:03 -0000 On Monday 23 November 2009 23:04:27 Corey Smith wrote: > Corey Smith Hi, I've committed your patch to USB P4. Should end up in 8+9-current soon. http://p4web.freebsd.org/chv.cgi?CH=170963 --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Nov 23 22:30:08 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 694891065692 for ; Mon, 23 Nov 2009 22:30:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3E98B8FC12 for ; Mon, 23 Nov 2009 22:30:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANMU7gY092640 for ; Mon, 23 Nov 2009 22:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANMU7sD092637; Mon, 23 Nov 2009 22:30:07 GMT (envelope-from gnats) Date: Mon, 23 Nov 2009 22:30:07 GMT Message-Id: <200911232230.nANMU7sD092637@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 22:30:08 -0000 The following reply was made to PR usb/140810; it has been noted by GNATS. From: Hans Petter Selasky To: Corey Smith , Andrew Thompson Cc: "freebsd-usb@freebsd.org" , "freebsd-gnats-submit@freebsd.org" Subject: Re: usb/140810: 8.X+ uftdi copy and paste problem / tty overflow Date: Mon, 23 Nov 2009 23:23:36 +0100 On Monday 23 November 2009 23:04:27 Corey Smith wrote: > Corey Smith Hi, I've committed your patch to USB P4. Should end up in 8+9-current soon. http://p4web.freebsd.org/chv.cgi?CH=170963 --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 00:08:15 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 BA6401065676 for ; Tue, 24 Nov 2009 00:08:15 +0000 (UTC) (envelope-from 166162@gmail.com) Received: from mail-vw0-f173.google.com (mail-vw0-f173.google.com [209.85.212.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1B6C68FC17 for ; Tue, 24 Nov 2009 00:08:13 +0000 (UTC) Received: by vws3 with SMTP id 3so1675228vws.3 for ; Mon, 23 Nov 2009 16:08:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=i+2fjp6UPQDSAW/uoPzAuVcJ/h4qCOC1exLeQeeCxWQ=; b=DT8x02+sdMt2iBSl00C+PbjvDVo8W09OQby+ayMdMJ8yFG1e981jGnZ4RkRZooLmFk GWFVs55Cn6Oh++Q7+5VC8TFcXbjXJlCmDkYAg8a82d5VWfLOUd7FjeADD4VZqMwYhL4Y oPs0hLQuJyhBRE0/ruGB99tICG41ph3zCNaYM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hvQ6mfzzI8YoS+XgwRhZkMPh1hgothJHnzj96A3nP++F098udWeBGGUWmVDagGhW5M KhW35+2LjToeiMtTtMejYPlPZ3Oq0G2nPcCeT8au3tEdteIJaasUgEL9YZSmY00Y5VcJ 3ZVk1BBganT2d222a5rSvAZ6YiONq4in2bOGU= MIME-Version: 1.0 Received: by 10.220.122.96 with SMTP id k32mr6592070vcr.96.1259021293022; Mon, 23 Nov 2009 16:08:13 -0800 (PST) In-Reply-To: <200911212300.20154.hselasky@c2i.net> References: <200911201224.08313.hselasky@c2i.net> <200911212300.20154.hselasky@c2i.net> Date: Tue, 24 Nov 2009 03:08:12 +0300 Message-ID: From: Travelling Particle <166162@gmail.com> To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: [keyboard] ukbd stops working after filesystems mount at boot time 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: Tue, 24 Nov 2009 00:08:15 -0000 > > > There was a recent EHCI interrupt patch. I'm not sure if it is committed to > > > 9-current yet. > > Do you mean there was a patch that might have caused this problem, or the > > patch fixing this problem? Also, I'm on 8-RC3, not 9-CURRENT > > > > I mean fixing. Well, indeed there're changes, but they're not good for me. I've tried to boot 8.0-RELEASE and keyboard appears to be dead when I need to type the geli password at root mount. Sometimes it's possible to send the passphrase by hitting Enter, but not every hit does so, and the passphrase entered appears to be wrong. I suppose certain keypresses are just dropped. Can't say much about empty lines interleaving the output of the late stage, as that would be happening later, after root fs is mounted. Is there anything I can do to debug the problem or help? I'm back to using RC3 now, since I can at least enter the passphrase and boot the system. From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 08:16:17 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 71449106566C; Tue, 24 Nov 2009 08:16:17 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70.appriver.com [69.20.119.203]) by mx1.freebsd.org (Postfix) with ESMTP id EAA258FC08; Tue, 24 Nov 2009 08:16:16 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-85/SG:5 11/24/2009 3:15:37 AM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.736882 p=-0.901176 Source Normal X-Signature-Violations: 0-0-0-26217-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107870192; Tue, 24 Nov 2009 03:16:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 24 Nov 2009 00:12:45 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcprWqhOc0di4XCLQnutgxkzKDrTkwAg+g77AD9+WyA= References: <200911221047.20362.hselasky@c2i.net> From: "Guojun Jin" To: "Guojun Jin" , "Hans Petter Selasky" , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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: Tue, 24 Nov 2009 08:16:17 -0000 Freshly installed 8.0-RELEASE on two differnt machines, and USB stick = work well so far, but the USB hard drive still has crash on this SMP (4-core AMD phenom 9600) during the = dump/restore. I will try it on the single CPU machine tomorrow. Re-tested dump/restore with FreeBSD 6.3/6.4 on this SMP machine and they = are working well. Also the another strange thing ocurred during the mount a partition on = /tmp, which ended with two /tmp, and the last one mounted is on the top (the first should be hidden): : df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 756750 165484 530726 24% / devfs 1 1 0 100% /dev /dev/ad0s2e 43194318 27833648 11905126 70% /data /dev/ad0s2d 9135182 5870390 2533978 70% /home /dev/ad0s1e 507630 34882 432138 7% /tmp /dev/ad0s1f 13246730 1424522 10762470 12% /usr /dev/ad0s1d 5077038 12700 4658176 0% /var /dev/da0s2 661176 487660 120622 80% /mnt /dev/da1s3d 9135182 4 8404364 0% /dist /dev/da1s3e 74938948 4 68943830 0% /tmp : df /tmp Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da1s3e 74938948 4 68943830 0% /tmp -----Original Message----- From: Guojun Jin Sent: Sun 11/22/2009 7:59 PM To: Hans Petter Selasky; freebsd-usb@freebsd.org Cc: bugs@freebsd.org; freebsd-stable@freebsd.org Subject: RE: 8.0-RC USB/FS problem =20 >From more intensive diagnose, it looks like more related USB layer. repeated a few time on following process and ithe crash happened at = different USB access phase at each time. dd if=3D/dev/zero of=3D/dev/da0 count=3D1000 bs=3D4k sysinstall partition=20 slice 1 (da0s1) 18GB ID=3D12 slice 2 (da0s2) 10-15GB Id=3D165 slice 3 (da0s3) rest ID=3D165 W ---> OK label da0s3d 9GB /mnt da0s3e rest /dist W ---> da0s3e ---- device is not configured. w# ll /dev/da0* # after sysinstall did partition + W at 1st time crw-r----- 1 root operator 0, 97 Nov 22 11:23 /dev/da0 crw-r----- 1 root operator 0, 98 Nov 22 11:23 /dev/da0s1 crw-r----- 1 root operator 0, 99 Nov 22 11:23 /dev/da0s2 crw-r----- 1 root operator 0, 100 Nov 22 11:23 /dev/da0s3 # ll /dev/da0* # after sysinstall start at 2nd time crw-r----- 1 root operator 0, 97 Nov 22 11:27 /dev/da0 System crashed The crash log is available at = http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2 (All logs are based on hw.usb.umass.debug=3D-1) After system reboot, and repeated above processes, the da0s3e was = mounted on /dist, but da0s3d cannot. It tunred out that newfs fail inside labeling process in sysinstall. = Manually did newfs on da0s3d, and it cannot be mounted on /mnt, but access to it caused crash. The crash log is available at = http:/www.daemonfun.com/archives/pub/USB/newfs Tried entire process again, this time, both partitons are formatted = (newfs) inside labaling process (sysinstall) but crahsed system during dump/restore on da0s3e (/dist). The crash log is available at = http:/www.daemonfun.com/archives/pub/USB/usb-log.crash2.bz2, which is = huge one. It contains two parts, one dump/restore IDE to da0s3d (passed), and the = rest is dump/restore to da0s3e (crashed). I am going to reinstall the system with the new ISO from Nov 21 = 8.0-RELEASE to see if anything will improve. -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Sun 11/22/2009 1:47 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; bugs@freebsd.org; freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Sunday 22 November 2009 05:38:13 Guojun Jin wrote: > Tried on the USB hard drive: > > Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e. > Was happy because successfully did dump/restore on s3d, and thought it = just > partition format issue; but system crashed during dump/restore on s3e, = and > partition lost the file system type. > > wolf# mount /dev/da0s3e /mnt > WARNING: /mnt was not properly dismounted > /mnt: mount pending error: blocks 35968 files 0 > wolf# fsck da0s3e > fsck: Could not determine filesystem type > wolf# bsdlabel da0s3 > # /dev/da0s3: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 175735035 0 unused 0 0 # "raw" part, > don't edi t > d: 18874368 0 4.2BSD 0 0 0 > e: 156860667 18874368 4.2BSD 0 0 0 > > Therefore, tried directly use fsck_ufs on both USB hard drive and USB = stick > to get file system clean up. All data got back now. > > The machine has run with FreeBSD 6.1 all the way to 7.2 without such > problem. How can we determine what could go wrong in 8.0? FS or USB. Hi, Error 5 means IO error, so probably the transport layer, USB or lower, = is to=20 blame. Some things to check: 1) Make sure the connection for your memory stick is Ok. 2) Make sure there is enough power for your memory stick. Regarding memory sticks: Other operating systems do a port bus reset when the device has a = problem. On=20 FreeBSD we just try a software reset via the control endpoint. I guess = that it=20 is a device problem you are seeing. The USB stack in FreeBSD is faster = than=20 the old one, and maybe the faster queueing of mass storage requests = trigger=20 some hidden bugs in your device. When the problem happens try: sysctl hw.usb.umass.debug=3D-1 --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 08:31:44 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 36205106566B; Tue, 24 Nov 2009 08:31:44 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 63BE38FC0A; Tue, 24 Nov 2009 08:31:42 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=rPscrj6gAAAA:8 a=VSprzn2SJXCWY732YVwA:9 a=efImWuUJO7OosnRcqHoqtDoppKMA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1334636849; Tue, 24 Nov 2009 09:31:41 +0100 From: Hans Petter Selasky To: "Guojun Jin" Date: Tue, 24 Nov 2009 09:33:18 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911240933.19329.hselasky@c2i.net> Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Tue, 24 Nov 2009 08:31:44 -0000 On Tuesday 24 November 2009 09:12:45 Guojun Jin wrote: > http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2 I'm not able to fetch this file. Could you extract the panic backtrace? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 17:09:03 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 4A1C2106566B; Tue, 24 Nov 2009 17:09:03 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (gwlb1.appriver.com [69.20.60.122]) by mx1.freebsd.org (Postfix) with ESMTP id CD4AD8FC0C; Tue, 24 Nov 2009 17:09:01 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-415/SG:5 11/24/2009 12:08:03 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.745707 p=-0.900648 Source Normal X-Signature-Violations: 0-0-0-4797-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107930775; Tue, 24 Nov 2009 12:09:02 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 24 Nov 2009 08:58:47 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: Acps4DRh91jZwvKvTYah2bfhsI4ySQARy8PJ References: <200911240933.19329.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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: Tue, 24 Nov 2009 17:09:03 -0000 Sorry for the typo -- it is public not pub in the middle. The others = should be all public. http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2 -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Tue 11/24/2009 12:33 AM To: Guojun Jin Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; = freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Tuesday 24 November 2009 09:12:45 Guojun Jin wrote: > http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2 I'm not able to fetch this file. Could you extract the panic backtrace? --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 17:11:54 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 35F06106568D; Tue, 24 Nov 2009 17:11:54 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 5A2FC8FC13; Tue, 24 Nov 2009 17:11:52 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=rPscrj6gAAAA:8 a=8kQB0OdkAAAA:8 a=6I5d2MoRAAAA:8 a=mK_DLrGy7CXV3tfyuFgA:9 a=wx7D4YLKRSFbyesQ_58A:7 a=Vtk2n1sZcEM6qDpyLC9ZRYUwTHAA:4 a=9aOQ2cSd83gA:10 a=SV7veod9ZcQA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1331367170; Tue, 24 Nov 2009 18:11:51 +0100 From: Hans Petter Selasky To: "Guojun Jin" Date: Tue, 24 Nov 2009 18:13:21 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911240933.19329.hselasky@c2i.net> In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911241813.23616.hselasky@c2i.net> Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Tue, 24 Nov 2009 17:11:54 -0000 On Tuesday 24 November 2009 17:58:47 Guojun Jin wrote: > Sorry for the typo -- it is public not pub in the middle. The others should > be all public. > > http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2 > %fetch http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2 fetch: http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2: No address record --HPS > -----Original Message----- > From: Hans Petter Selasky [mailto:hselasky@c2i.net] > Sent: Tue 11/24/2009 12:33 AM > To: Guojun Jin > Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; freebsd-stable@freebsd.org > Subject: Re: 8.0-RC USB/FS problem > > On Tuesday 24 November 2009 09:12:45 Guojun Jin wrote: > > http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2 > > I'm not able to fetch this file. Could you extract the panic backtrace? > > --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 17:53:26 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 AFBE01065670 for ; Tue, 24 Nov 2009 17:53:26 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-ew0-f221.google.com (mail-ew0-f221.google.com [209.85.219.221]) by mx1.freebsd.org (Postfix) with ESMTP id 41B858FC19 for ; Tue, 24 Nov 2009 17:53:25 +0000 (UTC) Received: by ewy21 with SMTP id 21so784184ewy.13 for ; Tue, 24 Nov 2009 09:53:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2RIAIVCSrim2faGgyzeYE/GE4I9jdNgzzBYgODpkrcM=; b=XwWAdQMcZpE13EqAZRZdJKB4o8QBF6hI8h6q8xw7D2MWUr/Ux4UtT7pv7aXgLM62w5 lkWQKQ7JfjEpMRjYJM5q7yUtL8kjdrvS5lEv3auJ5OYbi1yA21HcEHQWutishnhcEDnr c9OoAN4+BDsKD6wOPDmSxYUGHZJ19YO7J4LEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kw0563SMzTQhxu1rvF8lXLxTv1p1ima0hhVpzoddcFI8FaPnib3TDAsGlubdz5M6IV DcD5vzp3skdjdGuds9PkQFe4+p9FG2b9PXaRNQuEh7B0IBj61dDV927msbi2gE/8yZkt ZpWdJCTV77WUVduH3TmdXitoELEsy5jePYzFc= MIME-Version: 1.0 Received: by 10.213.0.195 with SMTP id 3mr5430288ebc.87.1259083408354; Tue, 24 Nov 2009 09:23:28 -0800 (PST) In-Reply-To: <200911241813.23616.hselasky@c2i.net> References: <200911240933.19329.hselasky@c2i.net> <200911241813.23616.hselasky@c2i.net> Date: Tue, 24 Nov 2009 17:23:28 +0000 Message-ID: <2e027be00911240923q7b8e192dk1ad67346d2f7e4d4@mail.gmail.com> From: Tom Evans To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Guojun Jin , freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Tue, 24 Nov 2009 17:53:26 -0000 On Tue, Nov 24, 2009 at 5:13 PM, Hans Petter Selasky wrote: > On Tuesday 24 November 2009 17:58:47 Guojun Jin wrote: > > Sorry for the typo -- it is public not pub in the middle. The others > should > > be all public. > > > > http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2 > > > > %fetch http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2 > fetch: http:/www.daemonfun.com/archives/public/USB/crash1-reset.bz2: No > address record > > You need two '/' for a URL :) Try: http://www.daemonfun.com/archives/public/USB/crash1-reset.bz2 Cheers Tom From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 20:59:55 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 C5179106568B for ; Tue, 24 Nov 2009 20:59:55 +0000 (UTC) (envelope-from oxyd.oxyd@gmail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 537C98FC0C for ; Tue, 24 Nov 2009 20:59:54 +0000 (UTC) Received: by fxm10 with SMTP id 10so4385704fxm.14 for ; Tue, 24 Nov 2009 12:59:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OLzG1f6DkU7DFIgl2xNWYt4hGmFIAbdymdHUh23G1ww=; b=w3djpu8LUONx/EmGYEf5oDVNkrESK4c7Y4OZEp3NxToWcTBW90r5NdVvWRfzQ2UrNk Ic7QwS1yMJN/x/HCy7zxFnIwIUgNUc6Fzw3HqHl4lQ4bjn9j5Mb9wW4bknxqFH0ghAfr sB5O3e1yBbuRRpWMzxM0RtPFystcvDDWCZIkw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=lPb0fwEStRGDBZ+jjJIr/vWt+UI4Gmq74m/veOBqlxY7Fphg88Esx0xvexuT1dPjRQ JFHmT8CdMclvizk5cuy2yLwwHGLbbRCZLEcymePMFNQpZUE0bF8Z2/ZlOeuQPCJpw6O6 WaMd4mROgTZ4zqOpHnqs6Dhew3e+0kNTahkK0= MIME-Version: 1.0 Received: by 10.103.126.33 with SMTP id d33mr2979137mun.109.1259096393327; Tue, 24 Nov 2009 12:59:53 -0800 (PST) In-Reply-To: References: <200911232238.19592.hselasky@c2i.net> Date: Tue, 24 Nov 2009 21:59:53 +0100 Message-ID: From: =?UTF-8?Q?Ond=C5=99ej_Majerech?= To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB mouse not working on 8.0-RELEASE 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: Tue, 24 Nov 2009 20:59:55 -0000 2009/11/23 Ond=C5=99ej Majerech : > 2009/11/23 Hans Petter Selasky : >> On Monday 23 November 2009 19:04:22 Ond=C5=99ej Majerech wrote: >>> Hello, >>> >>> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight >>> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009 >>> root@starlight:/usr/obj/usr/src/sys/STARLIGHT =C2=A0i386) via csup'ing = to >>> RELENG_8_0 and the usual suite of buildworld, buildkernel, >>> installkernel, mergemaster -p, installworld, mergemaster. >>> >>> My USB mouse doesn't work now. =C2=A0While booting, I can see error >>> messages from the USB part of the kernel; the same messages also >>> reappear when I disconnect and reconnect the thing. =C2=A0They read the >>> following: (Grabbed from /var/log/messages after having dis- and >>> re-connected the mouse.) >>> >>> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2 >>> failed (USB_ERR_TIMEOUT, ignored) >>> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! >>> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=3D2, >>> set address failed! (USB_ERR_TIMEOUT, ignored) >>> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! >>> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=3D2, >>> set address failed! (USB_ERR_TIMEOUT, ignored) >>> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! >>> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0 >>> (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435= : >>> could not allocate new device! >>> >>> The mouse was working without any problems whatsoever on 8.0-RC3 and >>> all older FBSD versions that I used. >>> >>> Other USB devices work as they should, without producing anything >>> unusual in dmesg. >>> >>> So, what's up? =C2=A0Any clues? >> >> Hi, >> >> This looks like a regression issue. There has been some changes with reg= ard to >> USB legacy support handling. Try disabling USB legacy support in the BIO= S or >> try to see if the problem is present in a 9-current kernel. >> >> Thanks for reporting your issue! >> >> --HPS >> >> > > The only option in my BIOS regarding legacy USB is "Legacy USB storage > detect" -- I set this one to Disabled and booted with the mouse > disabled -- when I connected it to the running system, it got detected > properly, but it simply wouldn't work in X. > > When I rebooted with the mouse plugged in, the same thing as before > happened -- error messages during boot, and un- and re-plugging > produced the same errors. > > I'll try 9-CURRENT sometime tomorrow and report back how that turned out. > > ~ Ondra > Alright, I tried with 9-CURRENT and indeed, it works without problems. So, shall I file a bug? I'd prefer to continue using -RELEASE, but I'd also like to have my mouse working. x) ~ Ondra From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 21:28:31 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 A6BF51065670 for ; Tue, 24 Nov 2009 21:28:31 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 096CC8FC08 for ; Tue, 24 Nov 2009 21:28:30 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=pE_spTFHMUsA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=pGLkceISAAAA:8 a=8kQB0OdkAAAA:8 a=u5Gm35QoULjH1AL1wpkA:9 a=5Kr-DMJ-aYILCXX03NYA:7 a=0C77qpYaIthkQrJs8eDSHv48GFAA:4 a=MSl-tDqOz04A:10 a=9aOQ2cSd83gA:10 a=pdKdl0rufNbVrsrN:21 a=HINPcdgV2LIwr8rX:21 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1334834930; Tue, 24 Nov 2009 22:28:29 +0100 From: Hans Petter Selasky To: =?utf-8?q?Ond=C5=99ej_Majerech?= Date: Tue, 24 Nov 2009 22:30:04 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpO< =?utf-8?q?Q0yAl=7E=3F=60=27F=3FjDVb=5DE6TQ7=27=23h-VlLs=7Dk/=0A=09?=(yxg(p!IL.`#ng"%`BMrham7%UK,}VH\wUOm=^>wEEQ+KWt[{J#x6ow~JO:,zwp.(t; @ =?utf-8?q?Aq=0A=09=3A4=3A=26nFCgDb8=5B3oIeTb=5E=27?=",; u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200911242230.05637.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: USB mouse not working on 8.0-RELEASE 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: Tue, 24 Nov 2009 21:28:31 -0000 On Tuesday 24 November 2009 21:59:53 Ond=C5=99ej Majerech wrote: > 2009/11/23 Ond=C5=99ej Majerech : > > 2009/11/23 Hans Petter Selasky : > >> On Monday 23 November 2009 19:04:22 Ond=C5=99ej Majerech wrote: > >>> Hello, > >>> > >>> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight > >>> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009 > >>> root@starlight:/usr/obj/usr/src/sys/STARLIGHT i386) via csup'ing to > >>> RELENG_8_0 and the usual suite of buildworld, buildkernel, > >>> installkernel, mergemaster -p, installworld, mergemaster. > >>> > >>> My USB mouse doesn't work now. While booting, I can see error > >>> messages from the USB part of the kernel; the same messages also > >>> reappear when I disconnect and reconnect the thing. They read the > >>> following: (Grabbed from /var/log/messages after having dis- and > >>> re-connected the mouse.) > >>> > >>> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2 > >>> failed (USB_ERR_TIMEOUT, ignored) > >>> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting > >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! > >>> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=3D= 2, > >>> set address failed! (USB_ERR_TIMEOUT, ignored) > >>> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting > >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! > >>> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=3D= 2, > >>> set address failed! (USB_ERR_TIMEOUT, ignored) > >>> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting > >>> device descriptor at addr 2 failed, USB_ERR_TIMEOUT! > >>> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0 > >>> (disconnected) Nov 23 18:54:25 starlight kernel: > >>> uhub_reattach_port:435: could not allocate new device! > >>> > >>> The mouse was working without any problems whatsoever on 8.0-RC3 and > >>> all older FBSD versions that I used. > >>> > >>> Other USB devices work as they should, without producing anything > >>> unusual in dmesg. > >>> > >>> So, what's up? Any clues? > >> > >> Hi, > >> > >> This looks like a regression issue. There has been some changes with > >> regard to USB legacy support handling. Try disabling USB legacy support > >> in the BIOS or try to see if the problem is present in a 9-current > >> kernel. > >> > >> Thanks for reporting your issue! > >> > >> --HPS > > > > The only option in my BIOS regarding legacy USB is "Legacy USB storage > > detect" -- I set this one to Disabled and booted with the mouse > > disabled -- when I connected it to the running system, it got detected > > properly, but it simply wouldn't work in X. > > > > When I rebooted with the mouse plugged in, the same thing as before > > happened -- error messages during boot, and un- and re-plugging > > produced the same errors. > > > > I'll try 9-CURRENT sometime tomorrow and report back how that turned ou= t. > > > > ~ Ondra > > Alright, I tried with 9-CURRENT and indeed, it works without problems. > > So, shall I file a bug? I'd prefer to continue using -RELEASE, but > I'd also like to have my mouse working. x) Yes, file a bug report. =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Tue Nov 24 23:09:40 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 EFD90106568D; Tue, 24 Nov 2009 23:09:40 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70.appriver.com [69.20.119.203]) by mx1.freebsd.org (Postfix) with ESMTP id 7ADE98FC19; Tue, 24 Nov 2009 23:09:40 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-26/SG:2 11/24/2009 6:09:27 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.758919 p=-0.912603 Source White X-Signature-Violations: 0-0-0-14325-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 107975677; Tue, 24 Nov 2009 18:09:41 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 24 Nov 2009 15:08:59 -0800 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcprWqhOc0di4XCLQnutgxkzKDrTkwAg+g77AD9+WyAAHqRYgA== References: <200911221047.20362.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" , Cc: bugs@freebsd.org, freebsd-stable@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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: Tue, 24 Nov 2009 23:09:41 -0000 Interesting now by some incident :-) The single CPU machine (Intel P4) with 8.0 works fine on the USB drives and the USB stick. So, installed 8.0 on another AMD Turion64 HP Pavilion dv5210us Laptop, it comes the same problem -- accessing the USB hard drive causes system panic and reboot: Took the previously dump/restored USB drive and mount it on this Laptop, tried to remove the data before dump/restore, it crashed the system after=20 hit ^C and unplugged USB hard drive when the LED on USB hard drive becomes solid red and spiting out numbers of lines Operation not permitted=20 (the user is root, so this means accessing hard drive is not possible): rm: bin/... : Operation not permitted ...... A second try causes the system locks up After ^C. So, try to re-partitioning the USB hard drive on AMD laptop and dump/restore, partitioning passed, but dump/restore crashed. Since hw.usb.umass.debug=3D-1 does not tell a USB problem beside the RESET, What other debug shall we turn on to analyze this problem. -----Original Message----- From: Guojun Jin=20 Sent: Tuesday, November 24, 2009 12:13 AM To: Guojun Jin; Hans Petter Selasky; freebsd-usb@freebsd.org Cc: bugs@freebsd.org; freebsd-stable@freebsd.org Subject: RE: 8.0-RC USB/FS problem Freshly installed 8.0-RELEASE on two differnt machines, and USB stick work well so far, but the USB hard drive still has crash on this SMP (4-core AMD phenom 9600) during the dump/restore. I will try it on the single CPU machine tomorrow. Re-tested dump/restore with FreeBSD 6.3/6.4 on this SMP machine and they are working well. Also the another strange thing ocurred during the mount a partition on /tmp, which ended with two /tmp, and the last one mounted is on the top (the first should be hidden): : df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 756750 165484 530726 24% / devfs 1 1 0 100% /dev /dev/ad0s2e 43194318 27833648 11905126 70% /data /dev/ad0s2d 9135182 5870390 2533978 70% /home /dev/ad0s1e 507630 34882 432138 7% /tmp /dev/ad0s1f 13246730 1424522 10762470 12% /usr /dev/ad0s1d 5077038 12700 4658176 0% /var /dev/da0s2 661176 487660 120622 80% /mnt /dev/da1s3d 9135182 4 8404364 0% /dist /dev/da1s3e 74938948 4 68943830 0% /tmp : df /tmp Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da1s3e 74938948 4 68943830 0% /tmp -----Original Message----- From: Guojun Jin Sent: Sun 11/22/2009 7:59 PM To: Hans Petter Selasky; freebsd-usb@freebsd.org Cc: bugs@freebsd.org; freebsd-stable@freebsd.org Subject: RE: 8.0-RC USB/FS problem =20 >From more intensive diagnose, it looks like more related USB layer. repeated a few time on following process and ithe crash happened at different USB access phase at each time. dd if=3D/dev/zero of=3D/dev/da0 count=3D1000 bs=3D4k sysinstall partition=20 slice 1 (da0s1) 18GB ID=3D12 slice 2 (da0s2) 10-15GB Id=3D165 slice 3 (da0s3) rest ID=3D165 W ---> OK label da0s3d 9GB /mnt da0s3e rest /dist W ---> da0s3e ---- device is not configured. w# ll /dev/da0* # after sysinstall did partition + W at 1st time crw-r----- 1 root operator 0, 97 Nov 22 11:23 /dev/da0 crw-r----- 1 root operator 0, 98 Nov 22 11:23 /dev/da0s1 crw-r----- 1 root operator 0, 99 Nov 22 11:23 /dev/da0s2 crw-r----- 1 root operator 0, 100 Nov 22 11:23 /dev/da0s3 # ll /dev/da0* # after sysinstall start at 2nd time crw-r----- 1 root operator 0, 97 Nov 22 11:27 /dev/da0 System crashed The crash log is available at http:/www.daemonfun.com/archives/pub/USB/crash1-reset.bz2 (All logs are based on hw.usb.umass.debug=3D-1) After system reboot, and repeated above processes, the da0s3e was mounted on /dist, but da0s3d cannot. It tunred out that newfs fail inside labeling process in sysinstall. Manually did newfs on da0s3d, and it cannot be mounted on /mnt, but access to it caused crash. The crash log is available at http:/www.daemonfun.com/archives/pub/USB/newfs Tried entire process again, this time, both partitons are formatted (newfs) inside labaling process (sysinstall) but crahsed system during dump/restore on da0s3e (/dist). The crash log is available at http:/www.daemonfun.com/archives/pub/USB/usb-log.crash2.bz2, which is huge one. It contains two parts, one dump/restore IDE to da0s3d (passed), and the rest is dump/restore to da0s3e (crashed). I am going to reinstall the system with the new ISO from Nov 21 8.0-RELEASE to see if anything will improve. -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Sun 11/22/2009 1:47 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; bugs@freebsd.org; freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Sunday 22 November 2009 05:38:13 Guojun Jin wrote: > Tried on the USB hard drive: > > Deleted slice 3 and recreated slice 3 with two partitions s3d and s3e. > Was happy because successfully did dump/restore on s3d, and thought it just > partition format issue; but system crashed during dump/restore on s3e, and > partition lost the file system type. > > wolf# mount /dev/da0s3e /mnt > WARNING: /mnt was not properly dismounted > /mnt: mount pending error: blocks 35968 files 0 > wolf# fsck da0s3e > fsck: Could not determine filesystem type > wolf# bsdlabel da0s3 > # /dev/da0s3: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 175735035 0 unused 0 0 # "raw" part, > don't edi t > d: 18874368 0 4.2BSD 0 0 0 > e: 156860667 18874368 4.2BSD 0 0 0 > > Therefore, tried directly use fsck_ufs on both USB hard drive and USB stick > to get file system clean up. All data got back now. > > The machine has run with FreeBSD 6.1 all the way to 7.2 without such > problem. How can we determine what could go wrong in 8.0? FS or USB. Hi, Error 5 means IO error, so probably the transport layer, USB or lower, is to=20 blame. Some things to check: 1) Make sure the connection for your memory stick is Ok. 2) Make sure there is enough power for your memory stick. Regarding memory sticks: Other operating systems do a port bus reset when the device has a problem. On=20 FreeBSD we just try a software reset via the control endpoint. I guess that it=20 is a device problem you are seeing. The USB stack in FreeBSD is faster than=20 the old one, and maybe the faster queueing of mass storage requests trigger=20 some hidden bugs in your device. When the problem happens try: sysctl hw.usb.umass.debug=3D-1 --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 01:56:11 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 45901106568B for ; Wed, 25 Nov 2009 01:56:11 +0000 (UTC) (envelope-from tlb@anybots.com) Received: from anybots.com (mail.anybots.com [64.142.12.96]) by mx1.freebsd.org (Postfix) with SMTP id 113CA8FC1D for ; Wed, 25 Nov 2009 01:56:10 +0000 (UTC) Received: (qmail 81097 invoked from network); 25 Nov 2009 01:29:28 -0000 Received: from unknown (HELO mobile004.mycingular.net) (tlb@32.177.142.165) by mail.anybots.com with SMTP; 25 Nov 2009 01:29:28 -0000 Message-Id: From: Trevor Blackwell To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 24 Nov 2009 17:29:25 -0800 X-Mailer: Apple Mail (2.936) Subject: Identifying serial ports 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: Wed, 25 Nov 2009 01:56:11 -0000 I have two USB devices that work as serial ports: ugen2.2.0: umodem0: ugen2.3.0: uplcom0: and they appear as serial devices /dev/cuaU0 and /dev/cuaU1. But I can't find a general-purpose way to figure out which is which. It depends on which gets enumerated first. In FreeBSD 7, the USB device minor # seemed to correspond to the cuaU device number, but here they are both zero. Any ideas? -- Trevor Blackwell tlb@anybots.com 650 776 7870 From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 08:35:34 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 39F1D10656C3; Wed, 25 Nov 2009 08:35:34 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 602628FC1C; Wed, 25 Nov 2009 08:35:32 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=LyfRj6cwWzvHMnOFOJMA:9 a=T-Vo3nG-Aqvxpwz43i1AfT4DWmwA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1350553548; Wed, 25 Nov 2009 09:35:31 +0100 From: Hans Petter Selasky To: "Guojun Jin" Date: Wed, 25 Nov 2009 09:37:06 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911250937.08267.hselasky@c2i.net> Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Wed, 25 Nov 2009 08:35:34 -0000 On Wednesday 25 November 2009 00:08:59 Guojun Jin wrote: > What other debug shall we turn on to analyze this problem. Are you able to extract the panic message? Try enabling dump on the swap partition. --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 12:14:02 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 B6ADD106566C for ; Wed, 25 Nov 2009 12:14:02 +0000 (UTC) (envelope-from 166162@gmail.com) Received: from mail-vw0-f173.google.com (mail-vw0-f173.google.com [209.85.212.173]) by mx1.freebsd.org (Postfix) with ESMTP id 6712C8FC1F for ; Wed, 25 Nov 2009 12:14:02 +0000 (UTC) Received: by vws3 with SMTP id 3so2151013vws.3 for ; Wed, 25 Nov 2009 04:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=WCM4tlWMI7DqK25ElXe/zka+YXZIHFEtgmPBOJy0Obs=; b=NSBLb0WjO9TNsGerZrjNbFgvV3DfoYutOMuqSZYALG1Yz9Xn4CFZ+g+unW0Yzzyq3o 7Qn/sgvMybmHOq0XnJsceFsJ35eRfObAdNf0inCVW5LgLL/PdT9fNevx7JyDVjXZGZGu cb21oyLELyxtyFVSOFh/XUlYVMZzjYGy3SQSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=x+W1/z7yPSD63roqjwISQe5N0T8r52L7lAdCco5udhr4vyNgYAppsEPIxLOMdv9J86 K7S4N0R1ZbRejndI8SRSRPp8BkOJ/9gB5156/FhH9hKgInaBIqwPhD3x/7u+4HUS5otQ NNQugYjvRJ6OPWQlBD/7pu2HdVAKSQOZDckDo= MIME-Version: 1.0 Received: by 10.220.123.230 with SMTP id q38mr9036319vcr.73.1259151241330; Wed, 25 Nov 2009 04:14:01 -0800 (PST) In-Reply-To: References: <200911201224.08313.hselasky@c2i.net> <200911212300.20154.hselasky@c2i.net> Date: Wed, 25 Nov 2009 15:14:01 +0300 Message-ID: From: Travelling Particle <166162@gmail.com> To: Hiroharu Tamaru , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: Re: [keyboard] ukbd stops working after filesystems mount at boot time 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: Wed, 25 Nov 2009 12:14:02 -0000 > Does this let you work around your problem too? > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+0+/usr/local/www/db/text/2008/freebsd-mobile/20080309.freebsd-mobile Haven't tried the patch, but I see what you mean. I had tested with atkbd and kbdmux both disabled and having geli passphrase visible. It appears that in 8.0-PRERELEASE (cvsuped Nov 23 2009, I think) the original problem I had reported is gone: if I can get thru the passphrase, the late stage continues fine and keyboard works at login prompt without any problem. However, the keyboard works unreliably(*) just before the late boot stage, at the moment when the geli passphrase is expected. 8.0-RC3 behaved the opposite way: no problem at the passphrase, but unusable console right after that. (*) By working unreliably I mean that key presses are randomly skipped. Sometimes you see keys pressed right after the first press, sometimes it takes 3-4 times to repeat the press before the symbol gets entered. I have googled up that skipping key presses at the passphrase prompt was reported since a long time ago. I see that it was somewhat fixed in 8.0-RC3 with undesired side-effects. This leaves me wonder if the keyboard can be fixed without breaking the console. I am willing to help: if anyone needs debugging output or anything, just tell me what I should do. USB keyboard is the only input device this computer has (no PS/2 or serial port), so I' somewhat desperate. > Chances are that unreliable key inputs at boot stage is not that > usb specific, but I couldn't dig any deeper then... I think it's usb-specific. What else would be responsible for dropping input from the usb device? Thanks. From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 16:13:07 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 2385A1065672 for ; Wed, 25 Nov 2009 16:13:07 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mailv1.ecc.u-tokyo.ac.jp (mailv1.ecc.u-tokyo.ac.jp [133.11.225.59]) by mx1.freebsd.org (Postfix) with ESMTP id C2FF48FC1E for ; Wed, 25 Nov 2009 16:13:06 +0000 (UTC) Received: from mhs001.ecc.u-tokyo.ac.jp (mhs001.ecc.u-tokyo.ac.jp [133.11.70.161]) by mailv1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id C57326C0043 for ; Thu, 26 Nov 2009 01:13:05 +0900 (JST) Received: from amulet.amuletic.net (124.155.55.252 [124.155.55.252]) by mhs001.ecc.u-tokyo.ac.jp (SpamBlock.pstn.b 3.4.102) with ESMTP id for ; Thu, 26 Nov 2009 01:12:59 +0900 Date: Thu, 26 Nov 2009 01:13:00 +0900 Message-ID: From: Hiroharu Tamaru To: Travelling Particle <166162@gmail.com> In-Reply-To: References: <200911201224.08313.hselasky@c2i.net> <200911212300.20154.hselasky@c2i.net> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 124.155.55.252 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: freebsd-usb@freebsd.org Subject: Re: [keyboard] ukbd stops working after filesystems mount at boot time 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: Wed, 25 Nov 2009 16:13:07 -0000 Hi At Wed, 25 Nov 2009 15:14:01 +0300, Travelling Particle wrote: > > Does this let you work around your problem too? > > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+0+/usr/local/www/db/text/2008/freebsd-mobile/20080309.freebsd-mobile > > Haven't tried the patch, but I see what you mean. I had tested with > atkbd and kbdmux both disabled and having geli passphrase visible. > It appears that in 8.0-PRERELEASE (cvsuped Nov 23 2009, I think) the > original problem I had reported is gone: if I can get thru the > passphrase, the late stage continues fine and keyboard works at login > prompt without any problem. However, the keyboard works unreliably(*) > just before the late boot stage, at the moment when the geli > passphrase is expected. 8.0-RC3 behaved the opposite way: no problem > at the passphrase, but unusable console right after that. > > (*) By working unreliably I mean that key presses are randomly > skipped. Sometimes you see keys pressed right after the first press, > sometimes it takes 3-4 times to repeat the press before the symbol > gets entered. > > I have googled up that skipping key presses at the passphrase prompt > was reported since a long time ago. I see that it was somewhat fixed > in 8.0-RC3 with undesired side-effects. This leaves me wonder if the > keyboard can be fixed without breaking the console. I am willing to > help: if anyone needs debugging output or anything, just tell me what > I should do. USB keyboard is the only input device this computer has > (no PS/2 or serial port), so I' somewhat desperate. > > > Chances are that unreliable key inputs at boot stage is not that > > usb specific, but I couldn't dig any deeper then... > > I think it's usb-specific. What else would be responsible for dropping > input from the usb device? BIOS or something alike, or some non-interrupt driven method, or some interrupt mechanism itself? Back then, I wondered if the kernel used BIOS or any of the above, that probably is different from how the device is driven after the boot stage is finalized, but I never reached the actual code to know it myself. I'd appreciate if someone can confirm it either way. Anyway, in my case, I was using atkbd, and not ukbd, and it was just that I thought if it were really the BIOS, the same work around may help. Anyway, reading your description above, more than one thing is probably involved, so just take what I wrote as my wild guess at best. I wish I knew the kernel better not to guess a lot like this, of course... So, the ball is back on the side of the experts here ;-p > Thanks. From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 17:25:38 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 778FC1065676 for ; Wed, 25 Nov 2009 17:25:38 +0000 (UTC) (envelope-from br@rambler-co.ru) Received: from mailrelay1.rambler.ru (mailrelay1.rambler.ru [81.19.66.239]) by mx1.freebsd.org (Postfix) with ESMTP id EF7858FC29 for ; Wed, 25 Nov 2009 17:25:37 +0000 (UTC) Received: from kas30pipe.localhost (localhost [127.0.0.1]) by mailrelay1.rambler.ru (Postfix) with ESMTP id 0ACBF130CC7 for ; Wed, 25 Nov 2009 20:08:33 +0300 (MSK) Received: from br.park.rambler.ru (index27.rambler.ru [81.19.79.222]) by mailrelay1.rambler.ru (Postfix) with SMTP id 7EECC130CC3 for ; Wed, 25 Nov 2009 20:08:32 +0300 (MSK) Received: by br.park.rambler.ru (nbSMTP-1.00) for uid 5007 br@rambler-co.ru; Wed, 25 Nov 2009 20:08:32 +0300 (MSK) Date: Wed, 25 Nov 2009 20:08:32 +0300 From: Bukin Ruslan To: freebsd-usb@freebsd.org Message-ID: <20091125170832.GA78035@rambler-co.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.33/RELEASE, bases: 02092009 #2738642, status: clean X-SpamTest-Envelope-From: br@rambler-co.ru X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 9536 [Sen 02 2009] X-SpamTest-Info: {HEADERS: header Content-Type found without required header Content-Transfer-Encoding} X-SpamTest-Method: none X-SpamTest-Rate: 10 X-SpamTest-SPF: pass X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0284], KAS30/Release Subject: uhci_interrupt: host controller halted 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: Wed, 25 Nov 2009 17:25:38 -0000 hello, i have about 1000 UHCI_STS_HCH intrr per second: Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000 Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000 Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000 Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted Nov 25 19:55:27 br kernel: uhci_dumpregs:741: usbus2 regs: cmd=0080, sts=0020, intr=000f, frnum=01c9, flbase=01a23724, sof=0040, portsc1=0080, portsc2=0080 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073005000) at 0x01a24002: h_next=0x01a25002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073006000) at 0x01a25002: h_next=0x01a26002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073007000) at 0x01a26002: h_next=0x01a27002 e_next=0x00000001 Nov 25 19:55:27 br kernel: uhci_dump_qh:814: QH(0xffffff8073008000) at 0x01a27002: h_next=0x00000001 e_next=0x01a28000 Nov 25 19:55:27 br kernel: uhci_interrupt:1506: uhci_interrupt: host controller halted is this normal? kern.version: FreeBSD 9.0-CURRENT #6: Wed Nov 25 06:48:28 UTC 2009 From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 17:42:35 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 357111065670; Wed, 25 Nov 2009 17:42:35 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (gwlb1.appriver.com [69.20.60.122]) by mx1.freebsd.org (Postfix) with ESMTP id B1B5F8FC1A; Wed, 25 Nov 2009 17:42:34 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-175/SG:5 11/25/2009 12:41:38 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.777555 p=-0.911205 Source White X-Signature-Violations: 0-0-0-4980-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 108025808; Wed, 25 Nov 2009 12:42:34 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 25 Nov 2009 09:35:44 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcptrLXhvnlwlhtHT/OlRRc5JWrzIgASQHSw References: <200911250937.08267.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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: Wed, 25 Nov 2009 17:42:35 -0000 I will do, I also borrowed two other machiens -- one AMD two core laptop, and one = P4 desktop -- for further testing. I will enable kernel coredump for all of them and will make cores = available by end of today. -Jin -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Wed 11/25/2009 12:37 AM To: Guojun Jin Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; = freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Wednesday 25 November 2009 00:08:59 Guojun Jin wrote: > What other debug shall we turn on to analyze this problem. Are you able to extract the panic message? Try enabling dump on the swap = partition. --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 17:54:26 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 83F8D1065670 for ; Wed, 25 Nov 2009 17:54:26 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 198C78FC1E for ; Wed, 25 Nov 2009 17:54:25 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=CQ_WfKyuRkkA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=x6wFsfSnts62v29TJGAA:9 a=iBKaFtokayzGf3kPmdntI2lFE4IA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1350826912; Wed, 25 Nov 2009 18:54:24 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Wed, 25 Nov 2009 18:55:57 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <20091125170832.GA78035@rambler-co.ru> In-Reply-To: <20091125170832.GA78035@rambler-co.ru> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911251855.59108.hselasky@c2i.net> Cc: Bukin Ruslan Subject: Re: uhci_interrupt: host controller halted 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: Wed, 25 Nov 2009 17:54:26 -0000 On Wednesday 25 November 2009 18:08:32 Bukin Ruslan wrote: > hello, > > i have about 1000 UHCI_STS_HCH intrr per second: > > > is this normal? No, it is not normal. Maybe this happens because the interrupt line is shared. What does vmstat -i say? --HPS From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 18:21:45 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 7384B106568B for ; Wed, 25 Nov 2009 18:21:45 +0000 (UTC) (envelope-from br@rambler-co.ru) Received: from mailrelay1.rambler.ru (mailrelay1.rambler.ru [81.19.66.239]) by mx1.freebsd.org (Postfix) with ESMTP id 26B718FC18 for ; Wed, 25 Nov 2009 18:21:44 +0000 (UTC) Received: from kas30pipe.localhost (localhost [127.0.0.1]) by mailrelay1.rambler.ru (Postfix) with ESMTP id 9BC80130C64; Wed, 25 Nov 2009 21:21:43 +0300 (MSK) Received: from br.park.rambler.ru (index27.rambler.ru [81.19.79.222]) by mailrelay1.rambler.ru (Postfix) with SMTP id 37539130C60; Wed, 25 Nov 2009 21:21:43 +0300 (MSK) Received: by br.park.rambler.ru (nbSMTP-1.00) for uid 5007 br@rambler-co.ru; Wed, 25 Nov 2009 21:21:43 +0300 (MSK) Date: Wed, 25 Nov 2009 21:21:43 +0300 From: Bukin Ruslan To: Hans Petter Selasky Message-ID: <20091125182143.GA78322@rambler-co.ru> References: <20091125170832.GA78035@rambler-co.ru> <200911251855.59108.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <200911251855.59108.hselasky@c2i.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.33/RELEASE, bases: 02092009 #2738642, status: clean X-SpamTest-Envelope-From: br@rambler-co.ru X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 9536 [Sen 02 2009] X-SpamTest-Info: {HEADERS: header Content-Type found without required header Content-Transfer-Encoding} X-SpamTest-Method: none X-SpamTest-Rate: 10 X-SpamTest-SPF: pass X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0284], KAS30/Release Cc: freebsd-usb@freebsd.org Subject: Re: uhci_interrupt: host controller halted 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: Wed, 25 Nov 2009 18:21:45 -0000 On Wed, Nov 25, 2009 at 06:55:57PM +0100, Hans Petter Selasky wrote: > On Wednesday 25 November 2009 18:08:32 Bukin Ruslan wrote: > > hello, > > > > i have about 1000 UHCI_STS_HCH intrr per second: > > > > > > > is this normal? > > No, it is not normal. Maybe this happens because the interrupt line is shared. > What does vmstat -i say? > > --HPS #vmstat -i interrupt total rate irq1: atkbd0 3527 6 irq9: acpi0 741 1 irq16: uhci2+ 82402 150 irq20: uhci0 13 0 irq21: uhci1 3303 6 irq22: ehci0 3 0 cpu0: timer 1090324 1996 irq256: em0 3514 6 irq257: hdac0 72093 132 cpu1: timer 1090197 1996 irq258: vgapci0 4535 8 Total 2350652 4305 From owner-freebsd-usb@FreeBSD.ORG Wed Nov 25 18:23:36 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 9D78B1065670 for ; Wed, 25 Nov 2009 18:23:36 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swip.net [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 1F6398FC15 for ; Wed, 25 Nov 2009 18:23:35 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=CQ_WfKyuRkkA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=DGce-UJtNFp-ezVENhUA:9 a=vZviXL6QuwYIUL2gHhQ0IISkQj8A:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 597979597; Wed, 25 Nov 2009 19:23:34 +0100 From: Hans Petter Selasky To: Bukin Ruslan Date: Wed, 25 Nov 2009 19:25:09 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <20091125170832.GA78035@rambler-co.ru> <200911251855.59108.hselasky@c2i.net> <20091125182143.GA78322@rambler-co.ru> In-Reply-To: <20091125182143.GA78322@rambler-co.ru> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911251925.11024.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: uhci_interrupt: host controller halted 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: Wed, 25 Nov 2009 18:23:36 -0000 On Wednesday 25 November 2009 19:21:43 Bukin Ruslan wrote: > On Wed, Nov 25, 2009 at 06:55:57PM +0100, Hans Petter Selasky wrote: > > On Wednesday 25 November 2009 18:08:32 Bukin Ruslan wrote: > > > hello, > > > > > > i have about 1000 UHCI_STS_HCH intrr per second: > > > > > > > > > > > > is this normal? > > > > No, it is not normal. Maybe this happens because the interrupt line is > > shared. What does vmstat -i say? > > > > --HPS > > #vmstat -i > interrupt total rate > irq1: atkbd0 3527 6 > irq9: acpi0 741 1 > irq16: uhci2+ 82402 150 > irq20: uhci0 13 0 > irq21: uhci1 3303 6 > irq22: ehci0 3 0 > cpu0: timer 1090324 1996 > irq256: em0 3514 6 > irq257: hdac0 72093 132 > cpu1: timer 1090197 1996 > irq258: vgapci0 4535 8 > Total 2350652 4305 Hi, There should be some code so that the UHCI only prints this message once. Thought it looks like the IRQ is shared so the message is printed multiple times. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 03:00:12 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E775106568B for ; Thu, 26 Nov 2009 03:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0D01C8FC1A for ; Thu, 26 Nov 2009 03:00:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAQ30B7H098881 for ; Thu, 26 Nov 2009 03:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAQ30BIG098880; Thu, 26 Nov 2009 03:00:11 GMT (envelope-from gnats) Resent-Date: Thu, 26 Nov 2009 03:00:11 GMT Resent-Message-Id: <200911260300.nAQ30BIG098880@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-usb@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, sub mesa Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E3E91065670 for ; Thu, 26 Nov 2009 02:59:55 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 7D2038FC12 for ; Thu, 26 Nov 2009 02:59:55 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nAQ2xtVw000959 for ; Thu, 26 Nov 2009 02:59:55 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nAQ2xtXf000958; Thu, 26 Nov 2009 02:59:55 GMT (envelope-from nobody) Message-Id: <200911260259.nAQ2xtXf000958@www.freebsd.org> Date: Thu, 26 Nov 2009 02:59:55 GMT From: sub mesa To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic 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: Thu, 26 Nov 2009 03:00:12 -0000 >Number: 140883 >Category: usb >Synopsis: axe(4) USB gigabit ethernet hangs after short period of traffic >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 26 03:00:11 UTC 2009 >Closed-Date: >Last-Modified: >Originator: sub mesa >Release: FreeBSD 8.0-RELEASE i386 >Organization: >Environment: FreeBSD gut 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 14:30:17 CET 2009 xor@xor:/usr/obj/usr/src/sys/XOR i386 >Description: I own a USB gigabit ethernet adapter with ASIX Electronics AX88178 chip supported by the axe(4) driver in FreeBSD 8.0. It works, but it 'freezes' or 'hangs' after some traffic, like downloading at ~50Mbps for 5-10 minutes will cause the device to freeze. This has been happening since a long time on 8.0, ever since i bought the device and was running one of the early beta's. Upgrading to the final release of 8.0 did not resolve the issue. Googling on the problem i found this mailinglist thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-April/005738.html However, there doesn't seem to be a single conclusion. Even though my product ("Belkin F5D5055") seems to be supported according to the axe(4) manpage, it doesn't get detected as such, rather with a vendor id. Quoting dmesg output: axe0: on usbus4 axe0: PHYADDR 0xe0:0x01 miibus1: on axe0 ue0: on axe0 May i suggest removing the Belkin F5D5055 from the supported devices list in the axe(4) manpage, until a fix has been committed? I specifically bought the device believing it would work since it was explicitly listed in the manpage. As of 8.0, it doesn't even get detected by name. It is of course possible my device is of a different revision. I would be happy to try any patches. Also see: http://forums.freebsd.org/showthread.php?t=8661 >How-To-Repeat: Connect axe(4) gigabit ethernet device Send/receive packets using the ueX ethernet device Device will stop receiving/transmitting packets after a short while >Fix: Workaround: re-plug device or use usbreset command. No fix known. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 07:35:05 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 C2E14106568F; Thu, 26 Nov 2009 07:35:05 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70b.appriver.com [74.205.4.150]) by mx1.freebsd.org (Postfix) with ESMTP id 461D38FC28; Thu, 26 Nov 2009 07:35:04 +0000 (UTC) Received: by server70.appriver.com (CommuniGate Pro PIPE 5.3c2) with PIPE id 108069255; Thu, 26 Nov 2009 02:35:03 -0500 Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 108069252; Thu, 26 Nov 2009 02:34:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CA6E6A.61D5C50E" Date: Wed, 25 Nov 2009 23:30:52 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcptrLXhvnlwlhtHT/OlRRc5JWrzIgAu9bGS References: <200911250937.08267.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Note: VCH-CT/SI:0-824/SG:1 11/26/2009 2:34:26 AM X-Virus-Scan: V-X0M0 X-Note: ICH-CT/SI:0-458/SG:1 11/26/2009 2:34:26 AM X-Note: TCH-CT/SI:0-128/SG:8 11/26/2009 2:34:26 AM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.792533 p=-0.913163 Source White X-Signature-Violations: 0-0-0-17447-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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: Thu, 26 Nov 2009 07:35:05 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA6E6A.61D5C50E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Most crash had the same back trace. This is also true when USB access = hangs, then unplug the drive. More interesting is the third AMD laptop (dual core) had similar = problem, but it is less crashing but hanging. The core information is available at the same place (bt file is also = attached): http://www.daemonfun.com/archives/public/USB -rw-r--r-- 1 jin wheel 4668 Nov 25 23:17 bt -rw------- 1 4294967294 wheel 80074 Nov 25 22:59 core.txt.0 -rw-r--r-- 1 4294967294 wheel 72108588 Nov 25 23:09 coredump-0.tbz core.txt.0 is from savecore, and bt is I did back trace so it has = slightly more information than core.txt. The tbz file contains the kernel.symbol and all files from savecore. I will continute to dig this and I will set more coredump if new crash = happens at different place. Please let me know anything I can help debug futher before Dec 3rd. I = will on travel for a while and I do not want to hold release for another two weeks. So let's resolve the = problem before I am on travel if possible. -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Wed 11/25/2009 12:37 AM To: Guojun Jin Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; = freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Wednesday 25 November 2009 00:08:59 Guojun Jin wrote: > What other debug shall we turn on to analyze this problem. Are you able to extract the panic message? Try enabling dump on the swap = partition. --HPS ------_=_NextPart_001_01CA6E6A.61D5C50E Content-Type: application/octet-stream; name="bt" Content-Transfer-Encoding: base64 Content-Description: bt Content-Disposition: attachment; filename="bt" ICBEVU1QOiAxMy4yNiUgZG9uZSwgZmluaXNoZWQgaW4gMDozMiBhdCBXZWQgTm92IDI1IDIyOjI4 OjIzIDIwMDkKICBEVU1QOiBzaG9ydCByZWFkIGVycm9yIGZyb20gL2Rldi9kYTBzMmQ6IFtibG9j ayA1NDU5OTg2MF06IGNvdW50PTEwMjQsIGdvdD0wCiAgRFVNUDogc2hvcnQgcmVhZCBlcnJvciBm cm9tIC9kZXYvZGEwczJkOiBbYmxvY2sgNzg0NjQ3MDRdOiBjb3VudD03MTY4LCBnb3Q9MAogIERV TVA6IDIwLjU1JSBkb25lLCBmaW5pc2hlZCBpbiAwOjM4IGF0IFdlZCBOb3YgMjUgMjI6Mzk6MjIg MjAwOQogIERVTVA6IDI1Ljk1JSBkb25lLCBmaW5pc2hlZCBpbiAwOjQzIGF0IFdlZCBOb3YgMjUg MjI6NDg6NDYgMjAwOQogIERVTVA6IDI2LjAwJSBkb25lLCBmaW5pc2hlZCBpbiAwOjU3IGF0IFdl ZCBOb3YgMjUgMjM6MDg6MDcgMjAwOQogIERVTVA6IHNob3J0IHJlYWQgZXJyb3IgZnJvbSAvZGV2 L2RhMHMyZDogW2Jsb2NrIDI2MzA3NzUzNl06IGNvdW50PTMwNzIsIGdvdD0wCiAgRFVNUDogMjYu MDMlIGRvbmUsIGZpbmlzaGVkIGluIDE6MTEgYXQgV2VkIE5vdiAyNSAyMzoyNzoxOSAyMDA5CiAg RFVNUDogMjYuMDYlIGRvbmUsIGZpbmlzaGVkIGluIDE6MjUgYXQgV2VkIE5vdiAyNSAyMzo0Njoz NCAyMDA5CiAgRFVNUDogMjYuMTAlIGRvbmUsIGZpbmlzaGVkIGluIDE6MzkgYXQgVGh1IE5vdiAy NiAwMDowNTo0NiAyMDA5CgoxNSAvdmFyL2NyYXNoOiB2aSBjb3JlLnR4dC4wIAoxNiAvdmFyL2Ny YXNoOiBrZ2RiIC9ib290L2tlcm5lbC9rZXJuZWwuc3ltYm9scyB2bWNvcmUuMCAKR05VIGdkYiA2 LjEuMSBbRnJlZUJTRF0KQ29weXJpZ2h0IDIwMDQgRnJlZSBTb2Z0d2FyZSBGb3VuZGF0aW9uLCBJ bmMuCkdEQiBpcyBmcmVlIHNvZnR3YXJlLCBjb3ZlcmVkIGJ5IHRoZSBHTlUgR2VuZXJhbCBQdWJs aWMgTGljZW5zZSwgYW5kIHlvdSBhcmUKd2VsY29tZSB0byBjaGFuZ2UgaXQgYW5kL29yIGRpc3Ry aWJ1dGUgY29waWVzIG9mIGl0IHVuZGVyIGNlcnRhaW4gY29uZGl0aW9ucy4KVHlwZSAic2hvdyBj b3B5aW5nIiB0byBzZWUgdGhlIGNvbmRpdGlvbnMuClRoZXJlIGlzIGFic29sdXRlbHkgbm8gd2Fy cmFudHkgZm9yIEdEQi4gIFR5cGUgInNob3cgd2FycmFudHkiIGZvciBkZXRhaWxzLgpUaGlzIEdE QiB3YXMgY29uZmlndXJlZCBhcyAiaTM4Ni1tYXJjZWwtZnJlZWJzZCIuLi4KClVucmVhZCBwb3J0 aW9uIG9mIHRoZSBrZXJuZWwgbWVzc2FnZSBidWZmZXI6CnVnZW4yLjI6IDxETUk+IGF0IHVzYnVz MiAoZGlzY29ubmVjdGVkKQp1bWFzczA6IGF0IHVodWIyLCBwb3J0IDQsIGFkZHIgMiAoZGlzY29u bmVjdGVkKQooZGEwOnVtYXNzLXNpbTA6MDowOjApOiBsb3N0IGRldmljZQooZGEwOnVtYXNzLXNp bTA6MDowOjApOiBJbnZhbGlkYXRpbmcgcGFjawpnX3Zmc19kb25lKCk6ZGEwczNkW1dSSVRFKG9m ZnNldD0yMzIyOTcyNjcyLCBsZW5ndGg9MTMxMDcyKV1lcnJvciA9IDYKL21udDogZ290IGVycm9y IDYgd2hpbGUgYWNjZXNzaW5nIGZpbGVzeXN0ZW0KcGFuaWM6IHNvZnRkZXBfZGVhbGxvY2F0ZV9k ZXBlbmRlbmNpZXM6IHVucmVjb3ZlcmVkIEkvTyBlcnJvcgpjcHVpZCA9IDAKVXB0aW1lOiAxNW01 N3MKKGRhMDp1bWFzcy1zaW0wOjA6MDowKTogU3luY2hyb25pemUgY2FjaGUgZmFpbGVkLCBzdGF0 dXMgPT0gMHhhLCBzY3NpIHN0YXR1cyA9PSAweDAKUGh5c2ljYWwgbWVtb3J5OiAzNzAgTUIKRHVt cGluZyAxMzMgTUI6IDExOCAxMDIgODYgNzAgNTQgMzggMjIgNgoKUmVhZGluZyBzeW1ib2xzIGZy b20gL2Jvb3Qva2VybmVsL2lmX3JsLmtvLi4uUmVhZGluZyBzeW1ib2xzIGZyb20gL2Jvb3Qva2Vy bmVsL2lmX3JsLmtvLnN5bWJvbHMuLi5kb25lLgpkb25lLgpMb2FkZWQgc3ltYm9scyBmb3IgL2Jv b3Qva2VybmVsL2lmX3JsLmtvClJlYWRpbmcgc3ltYm9scyBmcm9tIC9ib290L2tlcm5lbC9zbmRf YXRpaXhwLmtvLi4uUmVhZGluZyBzeW1ib2xzIGZyb20gL2Jvb3Qva2VybmVsL3NuZF9hdGlpeHAu a28uc3ltYm9scy4uLmRvbmUuCmRvbmUuCkxvYWRlZCBzeW1ib2xzIGZvciAvYm9vdC9rZXJuZWwv c25kX2F0aWl4cC5rbwpSZWFkaW5nIHN5bWJvbHMgZnJvbSAvYm9vdC9rZXJuZWwvc291bmQua28u Li5SZWFkaW5nIHN5bWJvbHMgZnJvbSAvYm9vdC9rZXJuZWwvc291bmQua28uc3ltYm9scy4uLmRv bmUuCmRvbmUuCkxvYWRlZCBzeW1ib2xzIGZvciAvYm9vdC9rZXJuZWwvc291bmQua28KUmVhZGlu ZyBzeW1ib2xzIGZyb20gL2Jvb3Qva2VybmVsL3JhZGVvbi5rby4uLlJlYWRpbmcgc3ltYm9scyBm cm9tIC9ib290L2tlcm5lbC9yYWRlb24ua28uc3ltYm9scy4uLmRvbmUuCmRvbmUuCkxvYWRlZCBz eW1ib2xzIGZvciAvYm9vdC9rZXJuZWwvcmFkZW9uLmtvClJlYWRpbmcgc3ltYm9scyBmcm9tIC9i b290L2tlcm5lbC9kcm0ua28uLi5SZWFkaW5nIHN5bWJvbHMgZnJvbSAvYm9vdC9rZXJuZWwvZHJt LmtvLnN5bWJvbHMuLi5kb25lLgpkb25lLgpMb2FkZWQgc3ltYm9scyBmb3IgL2Jvb3Qva2VybmVs L2RybS5rbwojMCAgZG9hZHVtcCAoKSBhdCBwY3B1Lmg6MjQ2CjI0NiAgICAgcGNwdS5oOiBObyBz dWNoIGZpbGUgb3IgZGlyZWN0b3J5LgogICAgICAgIGluIHBjcHUuaAooa2dkYikgdXAKIzEgIDB4 YzA3Njg4NTcgaW4gYm9vdCAoaG93dG89MjYwKSBhdCAuLi8uLi8uLi9rZXJuL2tlcm5fc2h1dGRv d24uYzo0MTYKNDE2ICAgICAgICAgICAgICAgICAgICAgZG9hZHVtcCgpOwooa2dkYikgdXAKIzIg IDB4YzA3NjhiNDkgaW4gcGFuaWMgKGZtdD1WYXJpYWJsZSAiZm10IiBpcyBub3QgYXZhaWxhYmxl LgopIGF0IC4uLy4uLy4uL2tlcm4va2Vybl9zaHV0ZG93bi5jOjU3OQo1NzkgICAgICAgICAgICAg Ym9vdChib290b3B0KTsKKGtnZGIpIHVwCiMzICAweGMwOTkwMDVkIGluIHNvZnRkZXBfZGVhbGxv Y2F0ZV9kZXBlbmRlbmNpZXMgKGJwPVZhcmlhYmxlICJicCIgaXMgbm90IGF2YWlsYWJsZS4KKQog ICAgYXQgLi4vLi4vLi4vdWZzL2Zmcy9mZnNfc29mdGRlcC5jOjYzNjcKNjM2NyAgICAgICAgICAg IHBhbmljKCJzb2Z0ZGVwX2RlYWxsb2NhdGVfZGVwZW5kZW5jaWVzOiB1bnJlY292ZXJlZCBJL08g ZXJyb3IiKTsKKGtnZGIpIGwKNjM2MiAgICB7CjYzNjMKNjM2NCAgICAgICAgICAgIGlmICgoYnAt PmJfaW9mbGFncyAmIEJJT19FUlJPUikgPT0gMCkKNjM2NSAgICAgICAgICAgICAgICAgICAgcGFu aWMoInNvZnRkZXBfZGVhbGxvY2F0ZV9kZXBlbmRlbmNpZXM6IGRhbmdsaW5nIGRlcHMiKTsKNjM2 NiAgICAgICAgICAgIHNvZnRkZXBfZXJyb3IoYnAtPmJfdnAtPnZfbW91bnQtPm1udF9zdGF0LmZf bW50b25uYW1lLCBicC0+Yl9lcnJvcik7CjYzNjcgICAgICAgICAgICBwYW5pYygic29mdGRlcF9k ZWFsbG9jYXRlX2RlcGVuZGVuY2llczogdW5yZWNvdmVyZWQgSS9PIGVycm9yIik7CjYzNjggICAg fQo2MzY5CjYzNzAgICAgLyoKNjM3MSAgICAgKiBGdW5jdGlvbiB0byBoYW5kbGUgYXN5bmNocm9u b3VzIHdyaXRlIGVycm9ycyBpbiB0aGUgZmlsZXN5c3RlbS4KKGtnZGIpIHAveCBicC0+Yl9pb2Zs YWdzClZhcmlhYmxlICJicCIgaXMgbm90IGF2YWlsYWJsZS4KKGtnZGIpIGwgNjM2MAo2MzU1ICAg ICAqIENhbGxlZCB3aGVuZXZlciBhIGJ1ZmZlciB0aGF0IGlzIGJlaW5nIGludmFsaWRhdGVkIG9y IHJlYWxsb2NhdGVkCjYzNTYgICAgICogY29udGFpbnMgZGVwZW5kZW5jaWVzLiBUaGlzIHNob3Vs ZCBvbmx5IGhhcHBlbiBpZiBhbiBJL08gZXJyb3IgaGFzCjYzNTcgICAgICogb2NjdXJyZWQuIFRo ZSByb3V0aW5lIGlzIGNhbGxlZCB3aXRoIHRoZSBidWZmZXIgbG9ja2VkLgo2MzU4ICAgICAqLyAK NjM1OSAgICBzdGF0aWMgdm9pZAo2MzYwICAgIHNvZnRkZXBfZGVhbGxvY2F0ZV9kZXBlbmRlbmNp ZXMoYnApCjYzNjEgICAgICAgICAgICBzdHJ1Y3QgYnVmICpicDsKNjM2MiAgICB7CjYzNjMKNjM2 NCAgICAgICAgICAgIGlmICgoYnAtPmJfaW9mbGFncyAmIEJJT19FUlJPUikgPT0gMCkKKGtnZGIp IHVwCiM0ICAweGMwN2Q4ZDUwIGluIGJyZWxzZSAoYnA9MHhjYTFmOTZjMCkgYXQgYnVmLmg6NDE4 CjQxOCAgICAgYnVmLmg6IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkuCiAgICAgICAgaW4gYnVm LmgKKGtnZGIpIHVwCiM1ICAweGMwN2RiNmM2IGluIGJ1ZmRvbmVfZmluaXNoIChicD0weGNhMWY5 NmMwKQogICAgYXQgLi4vLi4vLi4va2Vybi92ZnNfYmlvLmM6MzQwMQozNDAxICAgICAgICAgICAg ICAgICAgICAgICAgICAgIGJyZWxzZShicCk7CihrZ2RiKSBwIGJwCiQxID0gKHN0cnVjdCBidWYg KikgMHhjYTFmOTZjMAooa2dkYikgcC94IGJwLT5iX2lvZmxhZ3MKJDIgPSAweDEKKGtnZGIpIHVw CiM2ICAweGMwN2RiNzNkIGluIGJ1ZmRvbmUgKGJwPTB4Y2ExZjk2YzApIGF0IC4uLy4uLy4uL2tl cm4vdmZzX2Jpby5jOjMyNjEKMzI2MSAgICAgICAgICAgIGJ1ZmRvbmVfZmluaXNoKGJwKTsKKGtn ZGIpCg== ------_=_NextPart_001_01CA6E6A.61D5C50E-- From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 08:18:57 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 EBFA4106566B; Thu, 26 Nov 2009 08:18:57 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.tele2.se [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 1DA488FC1A; Thu, 26 Nov 2009 08:18:56 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=AZ1ajIJw4K75eKegOlwA:9 a=Xa-G-XI08IdcHqc1iairc3C-kDUA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1169561369; Thu, 26 Nov 2009 09:18:52 +0100 From: Hans Petter Selasky To: "Guojun Jin" Date: Thu, 26 Nov 2009 09:20:31 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911250937.08267.hselasky@c2i.net> In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911260920.32342.hselasky@c2i.net> Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Thu, 26 Nov 2009 08:18:58 -0000 On Thursday 26 November 2009 08:30:52 Guojun Jin wrote: > Most crash had the same back trace. This is also true when USB access > hangs, then unplug the drive. I think from the backtrace that this is not an USB issue. It is a file-system issue. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 08:31:07 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 5753E1065672; Thu, 26 Nov 2009 08:31:07 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swip.net [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 854408FC0C; Thu, 26 Nov 2009 08:31:06 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Aj2zMsuF2oAA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=6I5d2MoRAAAA:8 a=Vo5eOzl4joT-BK3aZdQA:9 a=pzG6Mx_hnqxYVNSxlUYA:7 a=6Q2wmM-8A8W92q95WFx9uptvr9gA:4 a=qwhcAUU6ev8A:10 a=tlJW8gxtbz4A:10 a=GqVEd-P18nsA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 598238700; Thu, 26 Nov 2009 09:31:04 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 26 Nov 2009 09:32:43 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200911260259.nAQ2xtXf000958@www.freebsd.org> In-Reply-To: <200911260259.nAQ2xtXf000958@www.freebsd.org> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911260932.44225.hselasky@c2i.net> Cc: freebsd-gnats-submit@freebsd.org, sub mesa Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic 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: Thu, 26 Nov 2009 08:31:07 -0000 On Thursday 26 November 2009 03:59:55 sub mesa wrote: > >Number: 140883 > >Category: usb > >Synopsis: axe(4) USB gigabit ethernet hangs after short period of > > traffic Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Nov 26 03:00:11 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: sub mesa > >Release: FreeBSD 8.0-RELEASE i386 > >Organization: > >Environment: > > FreeBSD gut 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 14:30:17 CET > 2009 xor@xor:/usr/obj/usr/src/sys/XOR i386 > > >Description: > > I own a USB gigabit ethernet adapter with ASIX Electronics AX88178 chip > supported by the axe(4) driver in FreeBSD 8.0. It works, but it 'freezes' > or 'hangs' after some traffic, like downloading at ~50Mbps for 5-10 minutes > will cause the device to freeze. This has been happening since a long time > on 8.0, ever since i bought the device and was running one of the early > beta's. Upgrading to the final release of 8.0 did not resolve the issue. > > Googling on the problem i found this mailinglist thread: > http://lists.freebsd.org/pipermail/freebsd-current/2009-April/005738.html > > However, there doesn't seem to be a single conclusion. Even though my > product ("Belkin F5D5055") seems to be supported according to the axe(4) > manpage, it doesn't get detected as such, rather with a vendor id. Quoting > dmesg output: > > axe0: on usbus4 > axe0: PHYADDR 0xe0:0x01 > miibus1: on axe0 > ue0: on axe0 > > May i suggest removing the Belkin F5D5055 from the supported devices list > in the axe(4) manpage, until a fix has been committed? I specifically > bought the device believing it would work since it was explicitly listed in > the manpage. As of 8.0, it doesn't even get detected by name. It is of > course possible my device is of a different revision. > > I would be happy to try any patches. > > Also see: > http://forums.freebsd.org/showthread.php?t=8661 > > >How-To-Repeat: > > Connect axe(4) gigabit ethernet device > Send/receive packets using the ueX ethernet device > Device will stop receiving/transmitting packets after a short while > > >Fix: > > Workaround: re-plug device or use usbreset command. No fix known. > > >Release-Note: > >Audit-Trail: > >Unformatted: You can try enabling debugging: sysctl hw.usb.axe.debug=15 --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 08:40:05 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FE771065672 for ; Thu, 26 Nov 2009 08:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 342A58FC1D for ; Thu, 26 Nov 2009 08:40:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAQ8e4tu030170 for ; Thu, 26 Nov 2009 08:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAQ8e4c7030168; Thu, 26 Nov 2009 08:40:04 GMT (envelope-from gnats) Date: Thu, 26 Nov 2009 08:40:04 GMT Message-Id: <200911260840.nAQ8e4c7030168@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2009 08:40:05 -0000 The following reply was made to PR usb/140883; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: sub mesa , freebsd-gnats-submit@freebsd.org Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic Date: Thu, 26 Nov 2009 09:32:43 +0100 On Thursday 26 November 2009 03:59:55 sub mesa wrote: > >Number: 140883 > >Category: usb > >Synopsis: axe(4) USB gigabit ethernet hangs after short period of > > traffic Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Nov 26 03:00:11 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: sub mesa > >Release: FreeBSD 8.0-RELEASE i386 > >Organization: > >Environment: > > FreeBSD gut 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Wed Nov 25 14:30:17 CET > 2009 xor@xor:/usr/obj/usr/src/sys/XOR i386 > > >Description: > > I own a USB gigabit ethernet adapter with ASIX Electronics AX88178 chip > supported by the axe(4) driver in FreeBSD 8.0. It works, but it 'freezes' > or 'hangs' after some traffic, like downloading at ~50Mbps for 5-10 minutes > will cause the device to freeze. This has been happening since a long time > on 8.0, ever since i bought the device and was running one of the early > beta's. Upgrading to the final release of 8.0 did not resolve the issue. > > Googling on the problem i found this mailinglist thread: > http://lists.freebsd.org/pipermail/freebsd-current/2009-April/005738.html > > However, there doesn't seem to be a single conclusion. Even though my > product ("Belkin F5D5055") seems to be supported according to the axe(4) > manpage, it doesn't get detected as such, rather with a vendor id. Quoting > dmesg output: > > axe0: on usbus4 > axe0: PHYADDR 0xe0:0x01 > miibus1: on axe0 > ue0: on axe0 > > May i suggest removing the Belkin F5D5055 from the supported devices list > in the axe(4) manpage, until a fix has been committed? I specifically > bought the device believing it would work since it was explicitly listed in > the manpage. As of 8.0, it doesn't even get detected by name. It is of > course possible my device is of a different revision. > > I would be happy to try any patches. > > Also see: > http://forums.freebsd.org/showthread.php?t=8661 > > >How-To-Repeat: > > Connect axe(4) gigabit ethernet device > Send/receive packets using the ueX ethernet device > Device will stop receiving/transmitting packets after a short while > > >Fix: > > Workaround: re-plug device or use usbreset command. No fix known. > > >Release-Note: > >Audit-Trail: > >Unformatted: You can try enabling debugging: sysctl hw.usb.axe.debug=15 --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 19:33:55 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 921FC1065693; Thu, 26 Nov 2009 19:33:55 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (server70.appriver.com [69.20.119.203]) by mx1.freebsd.org (Postfix) with ESMTP id 215798FC08; Thu, 26 Nov 2009 19:33:54 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-240/SG:5 11/26/2009 2:33:19 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.797229 p=-0.910044 Source White X-Signature-Violations: 0-0-0-4693-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 108087470; Thu, 26 Nov 2009 14:33:52 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 26 Nov 2009 11:25:50 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-RC USB/FS problem Thread-Index: AcpucLHwJ6bfJmWlQYaRaAUxK7k9NgAXZE+h References: <200911250937.08267.hselasky@c2i.net> <200911260920.32342.hselasky@c2i.net> From: "Guojun Jin" To: "Hans Petter Selasky" Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: RE: 8.0-RC USB/FS problem 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: Thu, 26 Nov 2009 19:33:55 -0000 Shall I fill a defect? or someone on this mailing list can take care of = this problem before release. -Jin -----Original Message----- From: Hans Petter Selasky [mailto:hselasky@c2i.net] Sent: Thu 11/26/2009 12:20 AM To: Guojun Jin Cc: freebsd-usb@freebsd.org; bugs@freebsd.org; = freebsd-stable@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Thursday 26 November 2009 08:30:52 Guojun Jin wrote: > Most crash had the same back trace. This is also true when USB access > hangs, then unplug the drive. I think from the backtrace that this is not an USB issue. It is a = file-system=20 issue. --HPS From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 19:56:58 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 4B7DE1065693; Thu, 26 Nov 2009 19:56:58 +0000 (UTC) (envelope-from gjin@ubicom.com) Received: from server70.appriver.com (gwlb1.appriver.com [69.20.60.122]) by mx1.freebsd.org (Postfix) with ESMTP id CC6248FC14; Thu, 26 Nov 2009 19:56:57 +0000 (UTC) X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Policy: GLOBAL - ubicom.com X-Primary: gjin@ubicom.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note: TCH-CT/SI:0-185/SG:5 11/26/2009 2:56:19 PM X-GBUdb-Analysis: 0, 216.112.109.98, Ugly c=0.797274 p=-0.910083 Source White X-Signature-Violations: 0-0-0-5884-c X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 216.112.109.98 X-Note-Reverse-DNS: 216.112.109.98.ptr.us.xo.net X-Note-WHTLIST: gjin@ubicom.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 115 116 117 118 122 123 221 X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [216.112.109.98] (HELO stork.scenix.com) by server70.appriver.com (CommuniGate Pro SMTP 5.3c2) with ESMTP id 108087851; Thu, 26 Nov 2009 14:56:55 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 26 Nov 2009 11:48:18 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 8.0-R USB/FS problem Thread-Index: Acpu0RWtLDXlAiaQSguKNjWVz3+4BAAAFDVW References: <200911250937.08267.hselasky@c2i.net> <200911260920.32342.hselasky@c2i.net> <86DD8C42-A49C-49F1-9EBE-1DFF8B8CAD73@exscape.org> From: "Guojun Jin" To: "Thomas Backman" Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bugs@freebsd.org, freebsd-stable , freebsd-usb@freebsd.org Subject: RE: 8.0-R USB/FS problem 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: Thu, 26 Nov 2009 19:56:58 -0000 Be clear, the recent (last 5 days) tests are based on -RELEASE made on = 21st, not RC any more, so I changed title now. Since this problem occurs on multiple machines (not just single one), = with different USB drives, so I would like this to be fixed before the formal release if possible. -----Original Message----- From: Thomas Backman [mailto:serenity@exscape.org] Sent: Thu 11/26/2009 11:48 AM To: Guojun Jin Cc: Hans Petter Selasky; bugs@freebsd.org; freebsd-stable; = freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem =20 On Nov 26, 2009, at 8:25 PM, Guojun Jin wrote: > Shall I fill a defect? or someone on this mailing list can take care = of this problem before release. >=20 > -Jin 8.0 is halfway out already, you can download -RELEASE ISOs or upgrade = using freebsd-update. The main announcement just hasn't been made yet. Regards, Thomas From owner-freebsd-usb@FreeBSD.ORG Thu Nov 26 20:04:36 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 6BD0F1065670; Thu, 26 Nov 2009 20:04:36 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 21EB38FC08; Thu, 26 Nov 2009 20:04:35 +0000 (UTC) Received: from c83-253-248-99.bredband.comhem.se ([83.253.248.99]:47203 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1NDkL6-0003RG-6L; Thu, 26 Nov 2009 20:49:18 +0100 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 896C41D5E2F; Thu, 26 Nov 2009 20:49:01 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Thomas Backman In-Reply-To: Date: Thu, 26 Nov 2009 20:48:58 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <86DD8C42-A49C-49F1-9EBE-1DFF8B8CAD73@exscape.org> References: <200911250937.08267.hselasky@c2i.net> <200911260920.32342.hselasky@c2i.net> To: Guojun Jin X-Mailer: Apple Mail (2.1077) X-Originating-IP: 83.253.248.99 X-Scan-Result: No virus found in message 1NDkL6-0003RG-6L. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1NDkL6-0003RG-6L 1a7e732dd16442cc988ee70a89109156 Cc: bugs@freebsd.org, freebsd-stable , freebsd-usb@freebsd.org Subject: Re: 8.0-RC USB/FS problem 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: Thu, 26 Nov 2009 20:04:36 -0000 On Nov 26, 2009, at 8:25 PM, Guojun Jin wrote: > Shall I fill a defect? or someone on this mailing list can take care = of this problem before release. >=20 > -Jin 8.0 is halfway out already, you can download -RELEASE ISOs or upgrade = using freebsd-update. The main announcement just hasn't been made yet. Regards, Thomas= From owner-freebsd-usb@FreeBSD.ORG Fri Nov 27 06:00:13 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3ECA106566B for ; Fri, 27 Nov 2009 06:00:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6630D8FC13 for ; Fri, 27 Nov 2009 06:00:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAR60B4X092675 for ; Fri, 27 Nov 2009 06:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAR60Bdb092674; Fri, 27 Nov 2009 06:00:11 GMT (envelope-from gnats) Resent-Date: Fri, 27 Nov 2009 06:00:11 GMT Resent-Message-Id: <200911270600.nAR60Bdb092674@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-usb@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Brett Glass Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 207CE1065672 for ; Fri, 27 Nov 2009 05:50:33 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id E8F2C8FC1E for ; Fri, 27 Nov 2009 05:50:32 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nAR5oWFC091402 for ; Fri, 27 Nov 2009 05:50:32 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nAR5oW63091401; Fri, 27 Nov 2009 05:50:32 GMT (envelope-from nobody) Message-Id: <200911270550.nAR5oW63091401@www.freebsd.org> Date: Fri, 27 Nov 2009 05:50:32 GMT From: Brett Glass To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: usb/140923: Add support for new rev of USB Ethernet chip 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: Fri, 27 Nov 2009 06:00:13 -0000 >Number: 140923 >Category: usb >Synopsis: Add support for new rev of USB Ethernet chip >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Nov 27 06:00:11 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Brett Glass >Release: 8.0-RELEASE >Organization: LARIAT >Environment: >Description: The ASIX AX88772A USB 2.0 Ethernet chip has replaced the ASIC AX88772. Unlike the original, it doesn't tend to corrupt its buffers. I just bought about a dozen inexpensive USB Ethernet adapters that use this chip, and discovered to my dismay that though there was driver support (axe(4)) for the older version, the driver would not recognize the newer one. I managed to get it working by patching two files. Please incorporate the changes into the tree. >How-To-Repeat: Plug in a Sabrent (or similar) USB Ethernet adapter based on the AX88772A. FreeBSD 8.0-RELEASE won't recognize it. >Fix: Patch file attached. I also recommend including options USB_VERBOSE in the GENERIC kernel configuration (it is not there currently). Otherwise, the vendor and device names won't be printed in the boot messages. Patch attached with submission follows: *** /sys/dev/usb/usbdevs.orig Thu Nov 26 17:00:13 2009 --- /sys/dev/usb/usbdevs Thu Nov 26 18:43:33 2009 *************** *** 894,897 **** --- 894,899 ---- product ASIX AX88178 0x1780 AX88178 product ASIX AX88772 0x7720 AX88772 + /* Added by Brett Glass to support ASIX AX88772A, an updated AX88772 */ + product ASIX AX88772A 0x772a AX88772A USB 2.0 10/100 Ethernet /* ASUS products */ *** /sys/dev/usb/net/if_axe.c.orig Thu Nov 26 17:07:25 2009 --- /sys/dev/usb/net/if_axe.c Thu Nov 26 17:13:12 2009 *************** *** 142,145 **** --- 142,147 ---- {USB_VPI(USB_VENDOR_ASIX, USB_PRODUCT_ASIX_AX88178, AXE_FLAG_178)}, {USB_VPI(USB_VENDOR_ASIX, USB_PRODUCT_ASIX_AX88772, AXE_FLAG_772)}, + /* Added by Brett Glass to support ASIX AX88772A, an updated AX88772 */ + {USB_VPI(USB_VENDOR_ASIX, USB_PRODUCT_ASIX_AX88772A, AXE_FLAG_772)}, {USB_VPI(USB_VENDOR_ATEN, USB_PRODUCT_ATEN_UC210T, 0)}, {USB_VPI(USB_VENDOR_BELKIN, USB_PRODUCT_BELKIN_F5D5055, AXE_FLAG_178)}, >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-usb@FreeBSD.ORG Fri Nov 27 06:46:25 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D9F11065672; Fri, 27 Nov 2009 06:46:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E77BB8FC16; Fri, 27 Nov 2009 06:46:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAR6kO7V039619; Fri, 27 Nov 2009 06:46:24 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAR6kO7o039615; Fri, 27 Nov 2009 06:46:24 GMT (envelope-from linimon) Date: Fri, 27 Nov 2009 06:46:24 GMT Message-Id: <200911270646.nAR6kO7o039615@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-usb@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: usb/140920: [install] USB based install fails on 8.0-RELEASE [regression] 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: Fri, 27 Nov 2009 06:46:25 -0000 Old Synopsis: USB based install fails on 8.0-RELEASE New Synopsis: [install] USB based install fails on 8.0-RELEASE [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Fri Nov 27 06:45:40 UTC 2009 Responsible-Changed-Why: not sure if this is solely related to USB or not. http://www.freebsd.org/cgi/query-pr.cgi?pr=140920 From owner-freebsd-usb@FreeBSD.ORG Fri Nov 27 07:20:02 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D5C7106568D for ; Fri, 27 Nov 2009 07:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0DD998FC15 for ; Fri, 27 Nov 2009 07:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nAR7K1LU066473 for ; Fri, 27 Nov 2009 07:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nAR7K1bQ066472; Fri, 27 Nov 2009 07:20:01 GMT (envelope-from gnats) Resent-Date: Fri, 27 Nov 2009 07:20:01 GMT Resent-Message-Id: <200911270720.nAR7K1bQ066472@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-usb@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Eimar Koort Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3D911065740 for ; Fri, 27 Nov 2009 07:11:50 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id C787D8FC08 for ; Fri, 27 Nov 2009 07:11:50 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nAR7Boou060841 for ; Fri, 27 Nov 2009 07:11:50 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nAR7BoVP060840; Fri, 27 Nov 2009 07:11:50 GMT (envelope-from nobody) Message-Id: <200911270711.nAR7BoVP060840@www.freebsd.org> Date: Fri, 27 Nov 2009 07:11:50 GMT From: Eimar Koort To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: usb/140928: ZTE CDMA2000 1X EV-DO (MG478/AC8700) is not working 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: Fri, 27 Nov 2009 07:20:02 -0000 >Number: 140928 >Category: usb >Synopsis: ZTE CDMA2000 1X EV-DO (MG478/AC8700) is not working >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Nov 27 07:20:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Eimar Koort >Release: 8.0-RELEASE >Organization: >Environment: FreeBSD laptop 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Thu Nov 26 20:59:52 EET 2009 root@laptop:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When attaching mentioned device /dev/ttyU*'s aren't appearing. So device is not usable. >How-To-Repeat: >Fix: Add patch. shell# /usr/src/sys/dev/usb/serial shell# patch < /tmp/u3g.c.txt shell# patch < u3g.c.txt Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- u3g.c.bak 2009-11-27 08:59:04.000000000 +0200 |+++ u3g.c 2009-11-27 08:58:34.000000000 +0200 -------------------------- Patching file u3g.c using Plan A... Hunk #1 succeeded at 184. done After rebuilding kernel and reboot finally ttyU's are appearing at last. shell# dmesg /*/ ugen1.2: at usbus1 u3g0: on usbus1 u3g0: Found 3 ports. /*/ shell# ls -la /dev/ttyU* crw------- 1 root wheel 0, 122 27 nov 09:00 /dev/ttyU0.0 crw------- 1 root wheel 0, 123 27 nov 09:11 /dev/ttyU0.0.init crw------- 1 root wheel 0, 124 27 nov 09:11 /dev/ttyU0.0.lock crw------- 1 root wheel 0, 128 27 nov 09:11 /dev/ttyU0.1 crw------- 1 root wheel 0, 129 27 nov 09:11 /dev/ttyU0.1.init crw------- 1 root wheel 0, 130 27 nov 09:11 /dev/ttyU0.1.lock crw------- 1 root wheel 0, 134 27 nov 09:11 /dev/ttyU0.2 crw------- 1 root wheel 0, 135 27 nov 09:11 /dev/ttyU0.2.init crw------- 1 root wheel 0, 136 27 nov 09:11 /dev/ttyU0.2.lock Patch attached with submission follows: --- u3g.c.bak 2009-11-27 08:59:04.000000000 +0200 +++ u3g.c 2009-11-27 08:58:34.000000000 +0200 @@ -184,6 +184,7 @@ /* OEM: Qualcomm, Inc. */ U3G_DEV(QUALCOMMINC, ZTE_STOR, U3GFL_SCSI_EJECT), U3G_DEV(QUALCOMMINC, CDMA_MSM, U3GFL_SCSI_EJECT), + U3G_DEV(QUALCOMMINC, AC8700, 0), /* OEM: Huawei */ U3G_DEV(HUAWEI, MOBILE, U3GFL_HUAWEI_INIT), U3G_DEV(HUAWEI, E180V, U3GFL_HUAWEI_INIT), >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-usb@FreeBSD.ORG Fri Nov 27 23:10:03 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FD121065694 for ; Fri, 27 Nov 2009 23:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DAC6F8FC17 for ; Fri, 27 Nov 2009 23:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nARNA2X2001857 for ; Fri, 27 Nov 2009 23:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nARNA2Eu001856; Fri, 27 Nov 2009 23:10:02 GMT (envelope-from gnats) Resent-Date: Fri, 27 Nov 2009 23:10:02 GMT Resent-Message-Id: <200911272310.nARNA2Eu001856@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-usb@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Romain Tartiere Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3BAF106566B for ; Fri, 27 Nov 2009 23:09:04 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from marvin.blogreen.org (unknown [IPv6:2a01:e35:2f7d:58c0::2]) by mx1.freebsd.org (Postfix) with ESMTP id 50D858FC12 for ; Fri, 27 Nov 2009 23:09:04 +0000 (UTC) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 49C2B15E8D; Sat, 28 Nov 2009 00:09:03 +0100 (CET) Message-Id: <20091127230903.49C2B15E8D@marvin.blogreen.org> Date: Sat, 28 Nov 2009 00:09:03 +0100 (CET) From: Romain Tartiere To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: usb/140951: [usb uftdi] Add support for FT2232D Dual USB UART/FIFO I.C. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Romain Tartiere List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2009 23:10:03 -0000 >Number: 140951 >Category: usb >Synopsis: [usb uftdi] Add support for FT2232D Dual USB UART/FIFO I.C. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Nov 27 23:10:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Romain Tartiere >Release: FreeBSD 8.0-STABLE amd64 >Organization: >Environment: System: FreeBSD marvin.blogreen.org 8.0-STABLE FreeBSD 8.0-STABLE #2 r199851M: Fri Nov 27 03:40:46 CET 2009 root@marvin.blogreen.org:/usr/obj/usr/src/sys/MARVIN amd64 >Description: The OpenRD [1] board features a FT2232D chip for USB communication. It is not recognized by the UFTDI(4) driver. The attached patch adds support for this device (according to the documentation it is pin to pin compatible with the FT2232C chip, so I hope they can speak the same way). Tested on FreeBSD 8.0-STABLE, with an OpenRD board (devices /dev/cuaU[01]* appeared, the one corresponding to the console working as expected). References: 1. http://www.open-rd.org/ >How-To-Repeat: >Fix: --- SERIAL_2232D.patch begins here --- Index: sys/dev/usb/serial/uftdi.c =================================================================== --- sys/dev/usb/serial/uftdi.c (révision 199868) +++ sys/dev/usb/serial/uftdi.c (copie de travail) @@ -221,6 +221,7 @@ {USB_VPI(USB_VENDOR_DRESDENELEKTRONIK, USB_PRODUCT_DRESDENELEKTRONIK_WIRELESSHANDHELDTERMINAL, UFTDI_TYPE_8U232AM)}, {USB_VPI(USB_VENDOR_FTDI, USB_PRODUCT_FTDI_SERIAL_8U100AX, UFTDI_TYPE_SIO)}, {USB_VPI(USB_VENDOR_FTDI, USB_PRODUCT_FTDI_SERIAL_2232C, UFTDI_TYPE_8U232AM)}, + {USB_VPI(USB_VENDOR_FTDI, USB_PRODUCT_FTDI_SERIAL_2232D, UFTDI_TYPE_8U232AM)}, {USB_VPI(USB_VENDOR_FTDI, USB_PRODUCT_FTDI_SERIAL_8U232AM, UFTDI_TYPE_8U232AM)}, {USB_VPI(USB_VENDOR_FTDI, USB_PRODUCT_FTDI_SERIAL_8U232AM4, UFTDI_TYPE_8U232AM)}, {USB_VPI(USB_VENDOR_FTDI, USB_PRODUCT_FTDI_SEMC_DSS20, UFTDI_TYPE_8U232AM)}, Index: sys/dev/usb/usbdevs =================================================================== --- sys/dev/usb/usbdevs (révision 199868) +++ sys/dev/usb/usbdevs (copie de travail) @@ -1317,6 +1317,7 @@ product FTDI SERIAL_8U232AM 0x6001 8U232AM Serial product FTDI SERIAL_8U232AM4 0x6004 8U232AM Serial product FTDI SERIAL_2232C 0x6010 FT2232C Dual port Serial +product FTDI SERIAL_2232D 0x9e90 FT2232D Dual port Serial /* Gude Analog- und Digitalsysteme products also uses FTDI's id: */ product FTDI TACTRIX_OPENPORT_13M 0xcc48 OpenPort 1.3 Mitsubishi product FTDI TACTRIX_OPENPORT_13S 0xcc49 OpenPort 1.3 Subaru --- SERIAL_2232D.patch ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-usb@FreeBSD.ORG Sat Nov 28 21:11:26 2009 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62A181065679 for ; Sat, 28 Nov 2009 21:11:26 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.119.58.2]) by mx1.freebsd.org (Postfix) with ESMTP id 027AA8FC16 for ; Sat, 28 Nov 2009 21:11:25 +0000 (UTC) Received: from anne-o1dpaayth1.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id NAA05930 for ; Sat, 28 Nov 2009 13:40:23 -0700 (MST) Message-Id: <200911282040.NAA05930@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 28 Nov 2009 13:40:18 -0700 To: usb@freebsd.org From: Brett Glass Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: ASIX USB-to-Ethernet drivers 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: Sat, 28 Nov 2009 21:11:26 -0000 Everyone: Just tried to plug an ASIX-based USB-to-Ethernet interface into a system running FreeBSD 8.0-RELEASE, and discovered that it wasn't recognized. It turns out that ASIX has come out with a new version of one of its chips: the AX88772A. It has a smaller package with fewer pins, slightly less buffer memory, and a serial interface so that it can also support power line networking (see http://www.asix.com.tw/products.php?op=ProductList&PLine=71&PSeries=100). The AX88772 is being phased out by most interface manufacturers because the "A" chip is smaller and cheaper and takes up less board space. I am sure that I will not be the only person who is frustrated when plugging in an interface that looks the same as the older ones and finding that it doesn't work! I've discovered that the existing axe(4) driver for FreeBSD seems to work on the AX88772A without any changes if it is told to treat the chip like an AX88772. (It may not be optimal, because the ASIX Linux driver code does differentiate between the two. And the command "systat -vmstat 1" does show a lot of IRQs -- about one per millisecond. Also, the link light on the interface does not work, though this is a minor nit that I can live with. But the interface does at least run.) For the moment, I've patched /sys/dev/usb/usbdevs and /sys/dev/usb/net/axe to treat the AX88772A as if it were an AX88772 (patch submitted as PR 140923) so that I can get my systems working. But it would probably be a good idea to do more thorough testing.... --Brett Glass From owner-freebsd-usb@FreeBSD.ORG Sat Nov 28 22:15:07 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7765B1065692; Sat, 28 Nov 2009 22:15:07 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4F33A8FC17; Sat, 28 Nov 2009 22:15:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nASMF6xi052239; Sat, 28 Nov 2009 22:15:06 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nASMF6xC052235; Sat, 28 Nov 2009 22:15:06 GMT (envelope-from gavin) Date: Sat, 28 Nov 2009 22:15:06 GMT Message-Id: <200911282215.nASMF6xC052235@freefall.freebsd.org> To: csmith@bonddesk.com, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/140810: [uftdi] 8.X copy and paste problem / tty overflow 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: Sat, 28 Nov 2009 22:15:07 -0000 Old Synopsis: 8.X+ uftdi copy and paste problem / tty overflow New Synopsis: [uftdi] 8.X copy and paste problem / tty overflow State-Changed-From-To: open->analyzed State-Changed-By: gavin State-Changed-When: Sat Nov 28 22:13:07 UTC 2009 State-Changed-Why: Looks like this problem is understood, a fix is in Perforce http://www.freebsd.org/cgi/query-pr.cgi?pr=140810 From owner-freebsd-usb@FreeBSD.ORG Sat Nov 28 22:31:13 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04630106566C; Sat, 28 Nov 2009 22:31:12 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D03B48FC1D; Sat, 28 Nov 2009 22:31:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nASMVBIa069782; Sat, 28 Nov 2009 22:31:11 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nASMVBTh069778; Sat, 28 Nov 2009 22:31:11 GMT (envelope-from gavin) Date: Sat, 28 Nov 2009 22:31:11 GMT Message-Id: <200911282231.nASMVBTh069778@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/140849: [umouse] [usb8] USB mouse doesn't work under FreeBSD 8.0-RELEASE 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: Sat, 28 Nov 2009 22:31:13 -0000 Old Synopsis: USB mouse doesn't work under FreeBSD 8.0-RELEASE New Synopsis: [umouse] [usb8] USB mouse doesn't work under FreeBSD 8.0-RELEASE Responsible-Changed-From-To: freebsd-i386->freebsd-usb Responsible-Changed-By: gavin Responsible-Changed-When: Sat Nov 28 22:29:08 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). FWIW, I'm not aware of any changes between 8.0-RC3 and RELEASE that could have caused this, can I just confirm that it was RC3 and not BETA3 where the mouse last worked? http://www.freebsd.org/cgi/query-pr.cgi?pr=140849 From owner-freebsd-usb@FreeBSD.ORG Sat Nov 28 22:45:04 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8469E106566C; Sat, 28 Nov 2009 22:45:04 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4668FC15; Sat, 28 Nov 2009 22:45:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nASMj4Se078692; Sat, 28 Nov 2009 22:45:04 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nASMj3d7078688; Sat, 28 Nov 2009 22:45:03 GMT (envelope-from gavin) Date: Sat, 28 Nov 2009 22:45:03 GMT Message-Id: <200911282245.nASMj3d7078688@freefall.freebsd.org> To: sub.mesa@gmail.com, gavin@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/140883: axe(4) USB gigabit ethernet hangs after short period of traffic 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: Sat, 28 Nov 2009 22:45:04 -0000 Synopsis: axe(4) USB gigabit ethernet hangs after short period of traffic State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Sat Nov 28 22:43:41 UTC 2009 State-Changed-Why: Submitter has been asked for feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=140883 From owner-freebsd-usb@FreeBSD.ORG Sat Nov 28 22:51:27 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB3D21065672; Sat, 28 Nov 2009 22:51:27 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 938798FC1A; Sat, 28 Nov 2009 22:51:27 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nASMpRNr086868; Sat, 28 Nov 2009 22:51:27 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nASMpREf086864; Sat, 28 Nov 2009 22:51:27 GMT (envelope-from gavin) Date: Sat, 28 Nov 2009 22:51:27 GMT Message-Id: <200911282251.nASMpREf086864@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/140893: [urtw] WPA2 not working on rtl8187b 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: Sat, 28 Nov 2009 22:51:27 -0000 Old Synopsis: not working wi-fi using rtl8187bne working wi-fi using rtl8187b New Synopsis: [urtw] WPA2 not working on rtl8187b Responsible-Changed-From-To: freebsd-i386->freebsd-usb Responsible-Changed-By: gavin Responsible-Changed-When: Sat Nov 28 22:49:34 UTC 2009 Responsible-Changed-Why: Pass this over to USB maintainers, although this could be a problem for -net - hopefully someone on the USB list will have an dea where the problem may lie http://www.freebsd.org/cgi/query-pr.cgi?pr=140893 From owner-freebsd-usb@FreeBSD.ORG Sat Nov 28 23:15:03 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37DD81065676; Sat, 28 Nov 2009 23:15:03 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0F0E88FC0A; Sat, 28 Nov 2009 23:15:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nASNF2H4004440; Sat, 28 Nov 2009 23:15:02 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nASNF2RW004436; Sat, 28 Nov 2009 23:15:02 GMT (envelope-from gavin) Date: Sat, 28 Nov 2009 23:15:02 GMT Message-Id: <200911282315.nASNF2RW004436@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-usb@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: usb/140904: [build] Kernel fails to build if some unused USB Ethernet interfaces are omitted; error in /sys/conf/files 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: Sat, 28 Nov 2009 23:15:03 -0000 Synopsis: [build] Kernel fails to build if some unused USB Ethernet interfaces are omitted; error in /sys/conf/files Responsible-Changed-From-To: freebsd-bugs->freebsd-usb Responsible-Changed-By: gavin Responsible-Changed-When: Sat Nov 28 23:13:22 UTC 2009 Responsible-Changed-Why: Over to USB maintainer(s), the submitter has found a fix that works for him by changing sys/conf/files, hopefully somebody can verify and commit it http://www.freebsd.org/cgi/query-pr.cgi?pr=140904