NetBSD Problem Report #19326
Received: (qmail 11429 invoked by uid 605); 8 Dec 2002 12:43:12 -0000
Message-Id: <200212081243.gB8Ch9X08639@lyssa.zhadum.de>
Date: Sun, 8 Dec 2002 13:43:09 +0100 (CET)
From: Matthias Scheler <tron@colwyn.zhadum.de>
Sender: gnats-bugs-owner@netbsd.org
Reply-To: tron@colwyn.zhadum.de
To: gnats-bugs@gnats.netbsd.org
Subject: Olympus C-5050 can crash umass(4)
X-Send-Pr-Version: 3.95
>Number: 19326
>Category: kern
>Synopsis: Olympus C-5050 can crash umass(4)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Dec 08 12:44:01 +0000 2002
>Closed-Date: Wed Jan 01 17:16:53 +0000 2003
>Last-Modified: Sun Jan 12 16:51:01 +0000 2003
>Originator:
>Release: NetBSD 1.6K (2002-12-08 sources)
>Organization:
Matthias Scheler http://scheler.de/~matthias/
>Environment:
System: NetBSD lyssa.zhadum.de 1.6K NetBSD 1.6K (LYSSA) #0: Sun Dec 8 11:45:33 CET 2002 tron@lyssa.zhadum.de:/src/sys/compile/LYSSA i386
Architecture: i386
Machine: i386
>Description:
Connecting an Olympus C-5050 to a NetBSD system works fine most of the time:
umass0 at uhub2 port 1 configuration 1 interface 0
umass0: OLYMPUS C5050Z, rev 1.10/1.00, addr 3
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, 1 lun per target
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus1 target 1 lun 0: <OLYMPUS, C5050Z, 1.00> disk removable
sd0: could not mode sense (4/5); using fictitious geometry
sd0: 32000 KB, 31 cyl, 64 head, 32 sec, 512 bytes/sect x 64000 sectors
sd0: could not mode sense (4/5); using fictitious geometry
sd0: no disk label
However sometimes (about every 10th time) NetBSD gets stuck while
attaching the devices:
umass0 at uhub2 port 1 configuration 1 interface 0
umass0: OLYMPUS C5050Z, rev 1.10/1.00, addr 3
umass0: using SCSI over Bulk-Only
The memory card in the camera can of course not be accessed in this case
because no sd(4) disk was attached. Even worse if you remove the camera
the system crashes. Here's what "gdb" found out from the crash dump:
panic: trap
#0 0x1 in ?? ()
(gdb) where
#0 0x1 in ?? ()
#1 0xc02c910e in cpu_reboot ()
#2 0xc025869f in panic ()
#3 0xc02d0a1e in trap ()
#4 0xc0102c38 in calltrap ()
#5 0xc0330f52 in usbd_abort_pipe ()
#6 0xc03402b4 in umass_detach ()
#7 0xc0253753 in config_detach ()
#8 0xc0333f07 in usb_disconnect_port ()
#9 0xc0334589 in uhub_explore ()
#10 0xc03346ca in uhub_explore ()
#11 0xc0330358 in usb_discover ()
#12 0xc032fc3d in usb_event_thread ()
In case it matters here the attachment messages for the USB hostadapter ...
uhci0 at pci0 dev 31 function 2: Intel 82801BA USB Controller (rev. 0x05)
uhci0: interrupting at irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
... and the hub:
uhub2 at uhub0 port 1
uhub2: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr 2
uhub2: 4 ports with 4 removable, self powered
>How-To-Repeat:
Connect Olympus C-5050 and check the kernel messages afterwards. If
umass(4) gets stuck before attaching a sd(4) disk unconnect the camera
and the system will panic.
>Fix:
Not known.
>Release-Note:
>Audit-Trail:
From: IWAMOTO Toshihiro <iwamoto@sat.t.u-tokyo.ac.jp>
To: tron@colwyn.zhadum.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/19326: Olympus C-5050 can crash umass(4)
Date: Sun, 08 Dec 2002 23:41:12 +0900
At Sun, 8 Dec 2002 13:43:09 +0100 (CET),
Matthias Scheler wrote:
> >Description:
> Connecting an Olympus C-5050 to a NetBSD system works fine most of the time:
> However sometimes (about every 10th time) NetBSD gets stuck while
> attaching the devices:
>
> umass0 at uhub2 port 1 configuration 1 interface 0
> umass0: OLYMPUS C5050Z, rev 1.10/1.00, addr 3
> umass0: using SCSI over Bulk-Only
I have the same problem with Nikon E5000.
umass0 at uhub0 port 2 configuration 1 interface 0
umass0: Nikon NIKON DSC E5000, rev 1.10/1.00, addr 2
umass0: using SCSI over Bulk-Only
uhub0 is the root hub of SiS745 as shown below.
ohci0 at pci0 dev 2 function 2: Silicon Integrated System 5597/5598 USB host controller (rev. 0x07)
ohci0: interrupting at irq 15
ohci0: OHCI version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: Silicon Integra OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
--
IWAMOTO Toshihiro
From: IWAMOTO Toshihiro <iwamoto@sat.t.u-tokyo.ac.jp>
To: tron@colwyn.zhadum.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/19326: Olympus C-5050 can crash umass(4)
Date: Mon, 09 Dec 2002 00:06:54 +0900
Failed to mention in the previous mail...,
My kernel is -current and the source was last updated on Dec 3 except
for /sys/dev/usb, and /sys/dev/usb is up to date as of writing.
From: IWAMOTO Toshihiro <iwamoto@sat.t.u-tokyo.ac.jp>
To: tron@colwyn.zhadum.de
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/19326: Olympus C-5050 can crash umass(4)
Date: Thu, 02 Jan 2003 01:21:43 +0900
I committed some fix to umass.c, but I couldn't test that the panic
problem is actually fixed because I could not reproduce the situation.
Please let me know if you find my commit fixed panic or not.
--
IWAMOTO Toshihiro
State-Changed-From-To: open->closed
State-Changed-By: tron
State-Changed-When: Wed Jan 1 09:16:16 PST 2003
State-Changed-Why:
I cannot reproduce the problem after IWAMOTO Toshihiro's fix anymore.
From: Matthias Scheler <tron@zhadum.de>
To: NetBSD GNATS <gnats-bugs@gnats.netbsd.org>
Cc:
Subject: Re: kern/19326: Olympus C-5050 can crash umass(4)
Date: Sun, 12 Jan 2003 17:50:50 +0100
Just for the record:
The attachment problem occured again today but the system didn't crash
when I unplugged the camera.
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.