From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 31 May 2002 09:35:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 31 May 2002 09:34:35 -0400 Received: from ns1.alcove-solutions.com ([212.155.209.139]:47499 "EHLO smtp-out.fr.alcove.com") by vger.kernel.org with ESMTP id ; Fri, 31 May 2002 09:34:30 -0400 Date: Fri, 31 May 2002 15:34:29 +0200 From: Stelian Pop To: Linux Kernel Mailing List Subject: USB host drivers test results (2.5.19) and problem. Message-ID: <20020531133429.GF8310@come.alcove-fr> Reply-To: Stelian Pop Mail-Followup-To: Stelian Pop , Linux Kernel Mailing List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, Now that a 2.5 kernel boots again on my laptop (thanks to the ACPI IRQ routing problems being resolved :-) ), I tested the different USB host drivers available (I used to use usb-uhci before). lspci: 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) Results (only simple tests with a USB mouse performed): ehci-hcd.o does load, no output messages, does NOT work ohci-hcd.o does load, no output messages, does NOT work uhci-hcd.o does load, does work correctly usb-uhci-hcd.o does load, does work correctly. 1. Shouldn't the ehci/ohci drivers give some error on loading, since I obviously don't have the hardware ? 2 When doing a rmmod on one of the two last drivers, the kernel oopses with a (hand copied trace): bad EIP: c784fbda <[usbcore]rh_report_status+63/143> c0118f34 <__run_task_queue+61/6a> c784f677 <[usbcore]usb_reset_device+1d4/2df> c011be58 c0118e48 c0118d79 c0118bb7 c01099a0 c0108656 c01abd54 c0106b54 c0106bd0 c01abc6b c0106bd0 c0106c5a c0105000 <_stext+0/0> Another one: bad EIP: <[yenta_socket]yenta_allocate_resources+d/41> Adhoc c011be58 Adhoc c0118e48 Adhoc c0118d79 Adhoc c0118bb7 Adhoc c01099a0 Adhoc c0108656 Adhoc c01abd54 I'm not sure what this trace has to do with USB at all, but I haven't been able to reproduce the oops otherwise... Stelian. -- Stelian Pop Alcove - http://www.alcove.com