RE: Question on boot-message
Dear Mr. Borwer, thanks for the hint - I'll be back with you as soon as I know more. Take care Dieter Jurzitza -Original Message- From: Eric Brower [mailto:[EMAIL PROTECTED] Sent: Tue 11/29/2005 3:33 AM To: debian-sparc@lists.debian.org Cc: Subject:Re: Question on boot-message On 11/28/05, Jurzitza, Dieter [EMAIL PROTECTED] wrote: Dear listmembers, is there some way for me to find out which ioctl is missing here and whether * *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. ***
RE: Question on boot-message
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: debian-sparc@lists.debian.org 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? 4sys32_ioctl(mount:146): Unknown cmd fd(3) cmd(4c05) arg(e898) 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(e898) 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
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? 4sys32_ioctl(mount:146): Unknown cmd fd(3) cmd(4c05) arg(e898) 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(e898) 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
Re: Question on boot-message
On 11/28/05, Jurzitza, Dieter [EMAIL PROTECTED] wrote: 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? 4sys32_ioctl(mount:146): Unknown cmd fd(3) cmd(4c05) arg(e898) Run the cmd value backwards through the macros defined in asm/ioctl.h and perhaps you'll get an idea. 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(e898) or arg(efffed70) The number after mount: is the pid. The mount command is attempting an unknown ioctl, so start there and try to narrow down what mount may be attempting. You could strace or ltrace the offending mount command during the boot process as well. Come on back if you can't figure it out. -- E
