Surprise DEVCTL 7fc6ddc

QNX Newsgroups (Archives) qnx.rtos
1

I received a surprise devctl call in a serial driver that I’m writing,

7fc6ddc. is there a reference to all of these somewhere?

Thanks,

2

I haven’t tried to decode this specific devctl, but there are some surprise
devctl messages that occur when you start a process using on (i.e. on -t
/dev/null) or that style of attaching to other mountpoints. These will
present some QNX system level messages (IO_DEVCTL, IO_DUP…) that are not
expected if you follow the resource manager templates as documented.

“maschoen” <maschoen@pobox-dot-com.no-spam.invalid> wrote in message
news:f30drb$9kg$1@inn.qnx.com…

I received a surprise devctl call in a serial driver that I’m writing,

7fc6ddc. is there a reference to all of these somewhere?

Thanks,

3

Ken,

Thanks, that is not the case here. The only thing strange about
the circumstances I think was that this may have occured because I
was doing a CTRL-BREAK on the client when it happened.

4

maschoen <maschoen@pobox-dot-com.no-spam.invalid> wrote:

I received a surprise devctl call in a serial driver that I’m writing,

7fc6ddc. is there a reference to all of these somewhere?

Do you give the default devctl handler a chance to run? There’s a few
devctl()s that most/all resmgrs are “expected” to handle.

Otherwise, if the standard handler doesn’t recognise it, and you
don’t, then return an ENOSYS error is generally sensible.

I don’t think there’s a list that way. But, a bunch of the ones we
do generate are defined in various dmcd* header files.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

5

Thanks Dave, you are are correct. I put in the default hander first,
and I’ve not seen it since.