On Sun, 02 Aug 2009 14:35:32 -0300 Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:
Dan McGee wrote:
On a slightly related note, take a look at the dmesg output on sigurd- something is acting up a bit:
$ dmesg | tail ioctl32(grub:28054): Unknown cmd fd(3) cmd(00001261){t:12;sz:0} arg(00000000) on /home/archiso/install-iso/archlinux-2009.08-alpha-ftp-i686.img ioctl32(mke2fs:28828): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(ff810c40) on /home/archiso/install-iso/archlinux-2009.08-alpha-core-i686.img.part1
ioctl32 messages from kernel are triggered when you are running a x86-64 kernel, and when call an ioclt() from 32 bit user-space app with an unsupported command (in other words when no conversion between 32 bit to 64 bit ioctl). But only 50 of this messages are showed by the kernel, next call just return -EINVAL
So, what does this mean? we call commands that don't exist, isn't that pretty bad? How does this affect iso building? Dieter