> Especially if the sense code is NO SENSE. Logically that should
> indicate the driver needed to find out whether or not there was error,
> and it learned that there wasn't.
For tape drives, sense key == NO SENSE is not equivalent to no error to
report. Often a tape drive returns a sense key of
> As you are writing to a tty device, you need to set up the tty layer
> properly from userspace before calling write(). See a Serial
> Programming HOWTO for information on how to do this. If you don't do
> this, the tty layer is in an unknown state, and odd things
> can happen on
> what kind of
> Can you load the driver with "debug=1" and send the kernel debug log
> output for when you run the program?
I loaded both the usbserial.o and ftdi_sio.o drivers with debug=1 and crashed it again.
The output is below.
>
> And have you tried the uhci.o driver instead of the usb-uhci.o driver?
>
Hello,
My company (Cybernetics) is using the FTDI USB to Serial converter in an embedded
application. I keep getting a kernel panic when I try to access the device. The panic
seems to happen when the driver receives serial data from the device while the driver
is
opened. I have attached debug
