From owner-freebsd-stable@FreeBSD.ORG Wed Nov 26 08:14:56 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 283F316A4CE for ; Wed, 26 Nov 2003 08:14:56 -0800 (PST) Received: from konvergencia.hu (konvergencia.hu [195.228.254.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD7D043FE0 for ; Wed, 26 Nov 2003 08:14:49 -0800 (PST) (envelope-from mkenyeres@konvergencia.hu) Received: from [127.0.0.25] (helo=localhost) by konvergencia.hu with esmtp (Exim 4.10) id 1AP2KE-000Kba-00 for freebsd-stable@FreeBSD.org; Wed, 26 Nov 2003 16:15:34 +0000 Received: from konvergencia.hu ([127.0.0.25]) by localhost (kavegep.konvergencia.hu [127.0.0.25]) (amavisd-new, port 10024) with ESMTP id 78888-02 for ; Wed, 26 Nov 2003 17:15:33 +0100 (CET) Received: from 103.65-182-adsl-pool.axelero.hu ([81.182.65.103] helo=nerd.kvg.hu) by konvergencia.hu with asmtp (TLSv1:RC4-MD5:128) (Exim 4.10) id 1AP2KD-000KbV-00 for freebsd-stable@FreeBSD.org; Wed, 26 Nov 2003 16:15:33 +0000 From: Marton Kenyeres Organization: KVG Konvergencia Kft. To: freebsd-stable@FreeBSD.org Date: Wed, 26 Nov 2003 17:14:34 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311261714.34747.mkenyeres@konvergencia.hu> X-Virus-Scanned: by amavisd-new at konvergencia.hu Subject: da doesn't attach to usb memory card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2003 16:14:56 -0000 Hi all, I'm playing with a usb memory card (aka. pen drive) which identifies itself as: /kernel: umass0: Intelligent Stick Intelligent Stick, rev 1.10/1.00, addr 2 My current system is 4.9-STABLE built from todays sources. The problem is that allthough the umass driver attaches to the device, da does not. # camcontrol devlist at scbus0 target 0 lun 0 (pass0) No sign of da0 in dmesg either :/ If I issue a camcontrol rescan command only thing I get is: /kernel: umass0: BBB reset failed, TIMEOUT /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT repeating endlessly. Strange enough the same device did show up as da0 with a 4.9-RC kernel built on October 20th: /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 /kernel: da0: Removable Direct Access SCSI-2 device /kernel: da0: 650KB/s transfers /kernel: da0: 127MB (260800 512 byte sectors: 64H 32S/T 127C) It even worked if I booted with the device plugged in. I can test any patches/provide more info on request. Any ideas, RTFMs, hints wellcome. Cheers, -- Marton Kenyeres - mkenyeres@konvergencia.hu KVG Konvergencia Kft.