I suspect that it might be LOOP_GET_STATUS64 [EMAIL PROTECTED]:~$ grep -i 4c05 /usr/include/*/*.h /usr/include/linux/loop.h:#define LOOP_GET_STATUS64 0x4C05
Note that the message only appears 50 times after kernel boot. After that it will be throttled by the code in fs/compat.c. This may make confusing behaviour if you are trying to confirm what is happening. Another way to confirm which ioctl call it is is to run strace on the mount command and try to match up the system calls with the code. I don't seem to get the unknown cmd message on my box (may be throttling, different mount options or different kernel version where the ioctl cmd was implemented) Hope this helps Richard > -----Original Message----- > From: Jurzitza, Dieter [mailto:[EMAIL PROTECTED] > Sent: 28 November 2005 08:46 > To: [email protected] > Subject: Question on boot-message > > > Dear listmembers, > is there some way for me to find out which ioctl is missing > here and whether I do have a chance to fix this? > > <4>sys32_ioctl(mount:146): Unknown cmd fd(3) cmd(00004c05) > arg(effff898) > > This appears about 20 times during boot on my U60. The > numbers at mount:XXX vary from XXX=139 to XXX =161, the cmd's > are fd(3) and fd(4). The actual cmd() is always the same, the > arg() is either arg(effff898) or arg(efffed70) > > Many thanks for helping, > take care > > > > Dieter Jurzitza > > > -- > ________________________________________________ > > HARMAN BECKER AUTOMOTIVE SYSTEMS > > Dr.-Ing. Dieter Jurzitza > Manager Hardware Systems > System Development > > Industriegebiet Ittersbach > Becker-Göring Str. 16 > D-76307 Karlsbad / Germany > > Phone: +49 (0)7248 71-1577 > Fax: +49 (0)7248 71-1216 > eMail: [EMAIL PROTECTED] > Internet: http://www.becker.de > > > >
