From owner-freebsd-stable@FreeBSD.ORG Fri Oct 3 04:13:55 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 128BC16A4B3 for ; Fri, 3 Oct 2003 04:13:55 -0700 (PDT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC09043FDD for ; Fri, 3 Oct 2003 04:13:53 -0700 (PDT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp190-128.lns1.bne1.internode.on.net [150.101.190.128])h93BDqTK040498; Fri, 3 Oct 2003 20:43:52 +0930 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.12.8p1/8.11.6) with ESMTP id h93BDoJW013160; Fri, 3 Oct 2003 21:13:50 +1000 (EST) (envelope-from mckay) Message-Id: <200310031113.h93BDoJW013160@dungeon.home> To: Josef Karthauser References: <200310030944.h939isJW010930@dungeon.home> <20031003101411.GA19458@genius.tao.org.uk> In-Reply-To: <20031003101411.GA19458@genius.tao.org.uk> from Josef Karthauser at "Fri, 03 Oct 2003 11:14:11 +0100" Date: Fri, 03 Oct 2003 21:13:50 +1000 From: Stephen McKay cc: freebsd-stable@freebsd.org cc: Stephen McKay Subject: Re: 4.9-rc + usb + asus a7n8x == bad news 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: Fri, 03 Oct 2003 11:13:55 -0000 On Friday, 3rd October 2003, Josef Karthauser wrote: >The usb stack in 4.9 is the same as that in 4.7 and so I'd expect no >improvements. And I thought I'd waited long enough before buying a USB device. :-) >Please check the -stable mail list for a post by me a >month or so ago with a patch that brings the -current USB stack into >stable. I would expect that to be much better. We missed getting it >into 4.9, but it will be committed to RELENG_4 as soon as the 4.9 tag >have been laid down. I tried this just now. The result is different, but not really any better. On my first attempt to plug in my USB memory stick, I got: umass0: IMGSYS-3 Security X-Disk V1.02, rev 1.10/2.01, addr 2 umass0: at uhub0 port 3 (addr 2) disconnected umass0: detached umass0: IMGSYS-3 Security X-Disk V1.02, rev 1.10/2.01, addr 2 panic: Removing other than first element Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.429 db> This was just a single insertion. It looks like there's some sort of "bounce" involved (ie insert, remove, insert detected even though it's only one insertion). DDB seems to work, and just listing the call stack, I get: Debugger panic usb_transfer_complete ohci_abort_xfer ohci_timeout_task usb_task_thread(0) fork_trampoline() No, I don't currently have a serial console set up. Then, when I try to get a core dump to check this further I get (funny, ha, ha) this message: dump failed, reason: device doesn't support a dump routine I remember the good old days when core dumps worked because everybody needed them. :-) Stephen.