Removing USB stick before usb stack shutdown causes loss of

QNX Newsgroups (Archives) qnx.qnx4
1

Hi,
We are using the usb stack (io-usb, Fsys.umass, Fatfsys, Fsys, Fsys.ide)
from 4.25. I have noticed that if I remove the usb stick before I have
killed off io-usb, Fsys-umass, and Fatfsys the entire filesystem on QNX
dies. Is this normal? (I know that the USB stack does not support plug and
pray). Of course there is nothing stopping the user from removing the USB
stick so it is nothing one can really guard against… Any one else have any
ideas?

/Darel

2

Darel Cullen <nospam-darelj@gmail.com> wrote:

Hi,
We are using the usb stack (io-usb, Fsys.umass, Fatfsys, Fsys, Fsys.ide)
from 4.25. I have noticed that if I remove the usb stick before I have
killed off io-usb, Fsys-umass, and Fatfsys the entire filesystem on QNX
dies. Is this normal? (I know that the USB stack does not support plug and
pray). Of course there is nothing stopping the user from removing the USB
stick so it is nothing one can really guard against… Any one else have any
ideas?

I am unable to reproduce the problem. Do you have a SIGSEGV address? Do you
see the problem if you use a separate Fsys with the umass driver? ie
Fsys -Numass
Fsys.umass fsys -Fumass

Can you post the output from:
show_pci -vvv
usb -vvv
sin ver
sin mem

3

Sorry for the delay, been away for a month.

I think this is my fault, I was using FatFsys to do the mount automatically.
If one starts Fatfsys and separately mounts after the key insertion it works
okay, even if the usb key is removed.

/Darel

“Kevin Chiles” <kchiles@qnx.com> wrote in message
news:ea2ect$m6e$1@inn.qnx.com…

Darel Cullen <> nospam-darelj@gmail.com> > wrote:
Hi,
We are using the usb stack (io-usb, Fsys.umass, Fatfsys, Fsys, Fsys.ide)
from 4.25. I have noticed that if I remove the usb stick before I have
killed off io-usb, Fsys-umass, and Fatfsys the entire filesystem on QNX
dies. Is this normal? (I know that the USB stack does not support plug
and
pray). Of course there is nothing stopping the user from removing the USB
stick so it is nothing one can really guard against… Any one else have
any
ideas?

I am unable to reproduce the problem. Do you have a SIGSEGV address? Do
you
see the problem if you use a separate Fsys with the umass driver? ie
Fsys -Numass
Fsys.umass fsys -Fumass

Can you post the output from:
show_pci -vvv
usb -vvv
sin ver
sin mem