Bug 32716

Summary:	system hangs when running vid (usb webcam tool)
Product:	Base System	Reporter:	corecode <corecode>
Component:	kern	Assignee:	joe <joe>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	housel
Priority:	Normal
Version:	4.4-STABLE
Hardware:	Any
OS:	Any

Description corecode@corecode.ath.cx 2001-12-12 00:30:01 UTC

after running vid the system stops responding. after hard reset and fsck one can read the following line in /var/log/messages

Dec 11 16:37:52 elevation /kernel: ohci_device_isoc_start: not implemented

i am aware that isochronous transfers are not yet supported (though there must be some use of this port - i must assume that it works, at least sometimes). but this shouldn't be the reason for the system to stop responding! (btw: netbsd supports isoc for more than one year now)
if i can help with more information tell me how to do so.

Fix: 

if i had one i wouldn't ask
How-To-Repeat: make and install vid. run vid.

Comment 1 corecode@corecode.ath.cx 2001-12-12 14:27:18 UTC

i investigated a bit further and noticed the following fact:

the system doesn't freeze when starting vid. it freezes when vid is
stopped.
% vid
^C

-> freeze
same for kill and kill -9

interessting about this stuff is that when checked in the console (no
xterm) one still can:
- use numlock, it toggles the led
- use scroll lock, it also toggles the led and the cursor, though
scrolling is no more possible
- pressing keys results in movement of the cursor (visible after pressing
scroll lock twice)

console switching is no more possible (results in cursor movement)

stopping the process doesn't freeze the system (via ^Z)

tell me how i can investigate further

cheerz
  corecode

-- 
|http://corecode.ath.cx/                                            /"\
|                                                                   \ /
|                                         ASCII Ribbon Campaign      \
|                                      Against HTML Mail and News   / \

Comment 2 Kris Kennaway freebsd_committer

2003-07-18 01:29:00 UTC

Responsible Changed
From-To: freebsd-bugs->joe

Assign to USB maintainer

Comment 3 iedowse freebsd_committer

2004-11-04 02:13:40 UTC

State Changed
From-To: open->feedback


Does this problem still occur wit more recent FreeBSD releases?

Comment 4 iedowse freebsd_committer

2004-11-05 01:31:36 UTC

State Changed
From-To: feedback->closed


Submitter no longer uses this combination of soft- and hardware.