Subject: kern/36476: HP ScanJet 4100C USB scanner crashes NetBSD
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Andreas Gustafsson <gson@gson.org>
List: netbsd-bugs
Date: 06/12/2007 15:30:01
>Number: 36476
>Category: kern
>Synopsis: HP ScanJet 4100C USB scanner crashes NetBSD
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jun 12 15:30:00 +0000 2007
>Originator: Andreas Gustafsson
>Release: NetBSD 4.99.20 (-current as of June 6, 2007)
>Organization:
>Environment:
System: NetBSD gubuntu2.araneus.fi 4.99.20 NetBSD 4.99.20 (GUITAR), etc.
Architecture: i386
Machine: i386
>Description:
I'm trying to use a Hewlett Packard 4100C USB flatbed scanner with
a NetBSD-current system. When I try to connect it, I sometimes
get the error message:
uhub0: device problem, disabling port 2
and sometimes the following:
uscanner0: Hewlett Packard 100C, rev 1.00/1.00, addr 2
uscanner0: setting config no failed
(yes, it really says 100C, not 4100C). In the latter case, if I
subsequently try to access the scanner in any way, even just opening
the uscanner0 device with "true </dev/uscanner0", I get a panic:
usbd_open_pipe: iface=0x0 address=0x0 flags=0x1
uvm_fault(0xcb02d620, 0, 1) -> 0xe
kernel: supervisor trap page fault, code=0
Stopped in pid 3485.1 (sh) at netbsd:usbd_open_pipe_ival+0x83: movl 0x4 (%eax),%eax
Here is the USB controller information from dmesg:
uhci0 at pci0 dev 31 function 4: Intel 82801BA USB Controller (rev. 0x01)
uhci0: interrupting at ioapic0 pin 23 (irq 10)
usb0 at uhci0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Dmesg output from a kernel built with with USB_DEBUG=10 and
UHUB_DEBUG=10, showing the scanner being attached at boot time up to
and including the the "uscanner0: setting config no failed" message,
is at <http://www.gson.org/netbsd/bugs/hp4100c/usbdebug.out>.
>How-To-Repeat:
See above. I can provide serial console access to the machine for
anyone with a serious interest in looking into this.
>Fix:
Please.