From owner-freebsd-current Thu Aug 2 7:20:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from gate.qubesoft.com (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id EB1DF37B405 for ; Thu, 2 Aug 2001 07:20:20 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from bluebottle.qubesoft.com (bluebottle [192.168.1.2]) by gate.qubesoft.com (8.11.3/8.11.3) with ESMTP id f72EKHl88633; Thu, 2 Aug 2001 15:20:17 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from builder03 (dhcp139.qubesoft.com [192.168.1.139]) by bluebottle.qubesoft.com (8.11.4/8.11.4) with SMTP id f72EKCI56777; Thu, 2 Aug 2001 15:20:13 +0100 (BST) (envelope-from n_hibma@qubesoft.com) From: "Nick Hibma" To: "FUJIMOTO Kou" , Subject: RE: ohci_process_done hangs when uhub detached Date: Thu, 2 Aug 2001 15:20:12 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal In-Reply-To: <3B677C89.D72AA4C8@j.dendai.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The problem with the keyboard is in the layer below the USB keyboard driver I think. It might not handle a keyboard that is detached very well. The second problem shouldn't happen. I'll investigate this at some stage. Nick > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of FUJIMOTO Kou > Sent: 01 August 2001 04:51 > To: freebsd-current@FreeBSD.ORG > Subject: ohci_process_done hangs when uhub detached > > > Hi, > > Last weekend I replaced my socket7 MVP3 board (w/ K6-2+) > to ASUS CUSI-FX socket370 SiS630E board (w/ VIA C3 733MHz), > then I found kernel panics when USB HUBs are detached. > > My USB setup is as follows: > > FreeBSD PC----------+ > | > CPU_switcher----HUB1----HUB2-----Mouse > | | > Windows PC----------+ +----USB-PS/2---Keyboard > > Mouse and USB-PS/2 translator are detached safely. > > When switching FreeBSD to Windows, kernel hangs with flood of > "db>" prompts. This is also the case when I pull out USB cable > between switcher and HUB1. > > When pulling cable between HUB1-HUB2 out, the following error > messages are indicated and I can check trace result: > ==================================================================== > uhub3: detached > ohci_device_ctrl_close: pipe=0xc122e580 > ohci_process_done: err cc=5 (DEVICE_NOT_RESPONDING), xfer=0xc103b500 > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xdeadc0e6 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc01daa5d > stack pointer = 0x10:0xc79a5f20 > frame pointer = 0x10:0xc79a5f34 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def31 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL=0 > current process = 18 (irq 9: ohci0++) > kernel: type 12 trap, code=0 > Stopped at ohci_process_done+0x21d: movl %eax,0x8(%edx) > db> trace > ohci_process_done(c080e000,580620,c1024340,c1016a80,4)at > ohci_process_done+0x21d > ohci_intr1(c080e000,c79a5f7c,c0214157,c080e000,c0213e98) at > ohci_intr1+0x139 > ohci_intr(c080e000) at ohci_intr+0x15 > ithread_loop(c1016a80,c79af5fa8) at ithread_loop+0x2bf > fork_exit(c0213e98,c1016a80,c79a5fa8) at fork_exit+0xb4 > fork_trampoline() at fork_trampoline+0x8 > db> > ====================================================================== > > With MVP3 chipset (UHCI) the setup above have worked peacefully, so > I guess it's due to OHCI code and/or SiS 630E chipset. > > -- > FUJIMOTO Kou, Dept. of Information Sciences, Tokyo Denki Univ. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message