usb_serial_generic_read_bulk_callback dying when it calls tty_flip_buffer_push

When drivers/usb/serial/generic.c calls tty_flip_buffer_push, in
usb_serial_generic_read_bulk_callback, the system goes down hard. 100%
frozen. I'm guessing I'm getting a kernel panic, but I can't even see
that. 

We're writing a driver for a 4 port usb-serial device we have made for a
customer. We have issue with the recv of characters from the device. We
have a bus snooper connected and see the data getting to the PC. When we
comment out the tty_flip_buffer_push call and put a print statement in
its place, we see the data coming up to the callback. 

This behavior happens with data I make up or what actually came from the
usb endpoint.

When I call this function (and tty_buffer_request_room and
tty_insert_flip_string) in an ioctl command I've rigged up, all three
functions work as expected, pushing the tty data to the awaiting program
reading from the /dev/ttyUSB file.

Any pointers on what may be going on here? 

We've verified that the tty is the same one from open. We do a small
action in our port_open function on a separate endpoint on our device,
then call the open function that's in generic.c.

We are on Kernel Version 2.6.20.11.

            --Michael

-- 
Michael Langford
www.TierOneDesign.com
Phone: 404-386-0495
Fax: 770-234-6899



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel