From owner-freebsd-bugs Fri Jul 19 14:50: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09F2537B400 for ; Fri, 19 Jul 2002 14:50:03 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3441543E3B for ; Fri, 19 Jul 2002 14:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g6JLo2JU049316 for ; Fri, 19 Jul 2002 14:50:02 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g6JLo2vX049315; Fri, 19 Jul 2002 14:50:02 -0700 (PDT) Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B09E37B400 for ; Fri, 19 Jul 2002 14:46:28 -0700 (PDT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 433EC43E42 for ; Fri, 19 Jul 2002 14:46:27 -0700 (PDT) (envelope-from weiss@zdvnetz.zdv.Uni-Mainz.DE) Received: from zdvnetz.zdv.Uni-Mainz.DE (zdvnetz.zdv.Uni-Mainz.DE [134.93.8.20]) by mailgate1.zdv.Uni-Mainz.DE (8.12.3/8.12.2) with ESMTP id g6JLkQNV023276 for ; Fri, 19 Jul 2002 23:46:26 +0200 (MEST) Received: from zdvnetz.zdv.Uni-Mainz.DE (localhost [127.0.0.1]) by zdvnetz.zdv.Uni-Mainz.DE (8.12.3/8.11.6) with ESMTP id g6JLkPtC055846 for ; Fri, 19 Jul 2002 23:46:25 +0200 (CEST) (envelope-from weiss@zdvnetz.zdv.Uni-Mainz.DE) Received: (from weiss@localhost) by zdvnetz.zdv.Uni-Mainz.DE (8.12.3/8.12.3/Submit) id g6JLkPI5055845; Fri, 19 Jul 2002 23:46:25 +0200 (CEST) Message-Id: <200207192146.g6JLkPI5055845@zdvnetz.zdv.Uni-Mainz.DE> Date: Fri, 19 Jul 2002 23:46:25 +0200 (CEST) From: Juergen Weiss Reply-To: Juergen Weiss To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: kern/40792: signals lead to data loss on device ugen Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 40792 >Category: kern >Synopsis: signals lead to data loss on device ugen >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 19 14:50:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Juergen Weiss >Release: FreeBSD 4.6-RELEASE i386 >Organization: Universitaet Mainz >Environment: System: FreeBSD zdvnetz.zdv.Uni-Mainz.DE 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Fri Jun 21 17:02:57 CEST 2002 root@zdvnetz.zdv.Uni-Mainz.DE:/usr/src/sys/compile/MPEG i386 >Description: I used a usb smartcard reader. I accessed the device using ugen0.5 and ugen0.6 read/write calls. The protocol is request/response, that is write a command/data, read results. Originally the software was compiled with -ptread. Using the software lead to intermittent lockups. Using ktrace showed, that signals (SIGPROF) from the thread library led to lost data and lockup, that is after a command write, there where no data to be read. An inspection of the usb source code seems to indicate, that signals during read calls lead to loss of data in buffers. >How-To-Repeat: see above. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message