Re: fs: Strange Device Reply
- From: Ben Gras <beng@xxxxxxxxx>
- Date: 4 May 2006 23:42:38 GMT
All,
fs: strange device reply from 14, type = 4, proc = 1 (2)
If i try the ioctl command again, I get very similar message:
fs: strange device reply from 14, type = 68, proc = 0 (2)
and then i wont get either error for quite some time. I narrowed down
where this message comes from (device.c), but Im having trouble
understanding the message.
What a coincedence, there was a fellow on #minix today with the
same error whom I told about fs/device.c too!
The only thing i noticed is that "type" refers to the message type, and
apparently 4 = DEV_WRITE and 68 = TASK_REPLY. I have no idea what 14,
1 and 0 are. Possible the FS? but there is no process 14 running. Can
anyone help me understand this message, or any has idea on why this is
happening.
Well, the message indicates a strange device reply from 14, of which
the type is 4 (and 68), for proc 1 (and 0), instead of the proc for
which the request was sent. This confuses FS. These aren't necessarily
really processes, just values filled in by the driver.
The process in slot 14 (not pid 14), which is presumably your driver,
sent FS a message with return code 4 and 68. (See the F1-listing for
which process is 14.)
Looking at the code in device.c it seems FS expects the process number
this reply is about in the message, which doesn't match. Any chance
that's not filled in properly (sometimes)?
=Ben
.
- Follow-Ups:
- Re: fs: Strange Device Reply
- From: skparker@xxxxxxxxx
- Re: fs: Strange Device Reply
- References:
- fs: Strange Device Reply
- From: skparker@xxxxxxxxx
- fs: Strange Device Reply
- Prev by Date: fs: Strange Device Reply
- Next by Date: unknown selector error
- Previous by thread: fs: Strange Device Reply
- Next by thread: Re: fs: Strange Device Reply
- Index(es):
Relevant Pages
|
