Skip to contentSkip to conversation

BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64

DISCUSSION Kasper Sandberg 4 participants 10 messages Nov 22, 2006 – Dec 5, 2006

lore
Share & tools
lore
#0 lore raw

Hello..

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(explorer.exe:11806): Unknown cmd fd(8) cmd(82187201){02} arg(00222000) on /home/redeeman/.wine/drive_c/windows/system32 ioctl32(explorer.exe:11806): Unknown cmd fd(8) cmd(82187201){02} arg(00222000) on /home/redeeman/.wine/drive_c/windows ioctl32(explorer.exe:11806): Unknown cmd fd(8) cmd(82187201){02} arg(00222000) on /home/redeeman/.wine/drive_c/windows/fonts ioctl32(explorer.exe:11806): Unknown cmd fd(8) cmd(82187201){02} arg(00222000) on /home/redeeman/.wine/drive_c/windows

however it doesent seem to affect the regedit and explorer.exe, some applications when run within wine does some VERY weird shit, i have even observed a few hardlock which i suspect may be due to this.

im sorry to say that i havent had time to do a git bisect, but i thought i'd report it anyway.

mvh.
Kasper Sandberg

#1 lore raw
Quoted 9 lines · On Wed, 22 Nov 2006 15:29:02 +0100 Kasper Sandberg <[email protected]> wrote:

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Try

echo 0 > /proc/sys/kernel/compat-log

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

#2 lore raw
Quoted 13 lines · Andrew Morton
Quoted 9 lines · On Wed, 22 Nov 2006 15:29:02 +0100 Kasper Sandberg <[email protected]> wrote:

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Quoted 4 lines

Try

echo 0 > /proc/sys/kernel/compat-log

this appears to make the logging stop, however, it still acts somewhat weird, and i am somewhat certain its because of this. this appears to be able to cause hardlocks.

Quoted 2 lines

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

.18

Quoted 2 lines
#3 lore raw

Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64| perhaps duplicate bug report?

In reply to Andrew Morton
Quoted 13 lines · Andrew Morton
Quoted 9 lines · On Wed, 22 Nov 2006 15:29:02 +0100 Kasper Sandberg <[email protected]> wrote:

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Quoted 7 lines

Try

echo 0 > /proc/sys/kernel/compat-log

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

it just struck me, that this may be the same bug Jesper Juhl has discovered (atleast the hardlock part), as i read that thread, it strike me that whenever i have hardlocks from this, its when i in wine runs stuff that uses basically all my ram, and MAY even touch my swap.

just an idea.

Quoted 1 line
#4 lore raw

Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64| perhaps duplicate bug report?

Quoted 18 lines · Kasper Sandberg
Quoted 17 lines · Andrew Morton

On Wed, 22 Nov 2006 15:29:02 +0100

Quoted 9 lines · Kasper Sandberg

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Try

echo 0 > /proc/sys/kernel/compat-log

Quoted 7 lines
Quoted 2 lines

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

it just struck me, that this may be the same bug Jesper Juhl has discovered (atleast the hardlock part), as i read that thread, it strike me that whenever i have hardlocks from this, its when i in wine runs stuff that uses basically all my ram, and MAY even touch my swap.

I see this same ioctl32 warning on a few apps running inside Wine, but I've not had any hard locks. On the contrary, everything works fine.

I guess it would be nice to know which ioctl it is that doesn't have a compat wrapper on x86-64, 82187201 is a bit cryptic.

HTH.

Signature · 5 lines
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
#5 lore raw

Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64| perhaps duplicate bug report?

Quoted 22 lines · Alistair John Strachan
Quoted 21 lines · Kasper Sandberg
Quoted 19 lines · Andrew Morton

On Wed, 22 Nov 2006 15:29:02 +0100

Quoted 9 lines · Kasper Sandberg

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Try

echo 0 > /proc/sys/kernel/compat-log

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

Quoted 7 lines
Quoted 4 lines

it just struck me, that this may be the same bug Jesper Juhl has discovered (atleast the hardlock part), as i read that thread, it strike me that whenever i have hardlocks from this, its when i in wine runs stuff that uses basically all my ram, and MAY even touch my swap.

I see this same ioctl32 warning on a few apps running inside Wine, but I've not had any hard locks. On the contrary, everything works fine.

thats why i have come to suspect it may not be the ioctl thing that causes the hardlocks, as i read that other thread

Quoted 3 lines

I guess it would be nice to know which ioctl it is that doesn't have a compat wrapper on x86-64, 82187201 is a bit cryptic.

yes, it did not say these things on .18 :)

how do i get more verbose information on what exactly it is?

Quoted 3 lines

HTH.

#6 lore raw
In reply to Andrew Morton

i know i said i suspected this was another bug, but i have revised my suspecisions, and i do believe its in relation to x86 chroot on x86_64 install, as it has happened with more stuff now, inside the chroot, and only inside the chroot, while the same apps dont do it outside chroot.

2.6.19 release is affected too

Quoted 26 lines · Andrew Morton
Quoted 9 lines · On Wed, 22 Nov 2006 15:29:02 +0100 Kasper Sandberg <[email protected]> wrote:

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Try

echo 0 > /proc/sys/kernel/compat-log

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#7 lore raw
Quoted 4 lines · Kasper Sandberg

i know i said i suspected this was another bug, but i have revised my suspecisions, and i do believe its in relation to x86 chroot on x86_64 install, as it has happened with more stuff now, inside the chroot, and only inside the chroot, while the same apps dont do it outside chroot.

and by that (so that theres no confusion), i mean that with the x86_64 binaries of the same application dont crash it, but the x86 binaries in the chroot does :)

Quoted 37 lines

2.6.19 release is affected too

Quoted 17 lines · Andrew Morton
Quoted 9 lines · On Wed, 22 Nov 2006 15:29:02 +0100 Kasper Sandberg <[email protected]> wrote:

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Try

echo 0 > /proc/sys/kernel/compat-log

Quoted 9 lines

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#8 lore raw
In reply to Kasper Sandberg
Quoted 6 lines · On Tue, 05 Dec 2006 03:36:09 +0100 Kasper Sandberg <[email protected]> wrote:

i know i said i suspected this was another bug, but i have revised my suspecisions, and i do believe its in relation to x86 chroot on x86_64 install, as it has happened with more stuff now, inside the chroot, and only inside the chroot, while the same apps dont do it outside chroot.

2.6.19 release is affected too

Please don't top-post.

Quoted 14 lines · Andrew Morton
Quoted 13 lines
Quoted 9 lines · On Wed, 22 Nov 2006 15:29:02 +0100 Kasper Sandberg <[email protected]> wrote:

it appears some sort of bug has gotten into .19, in regards to x86 emulation on x86_64.

i have only tested with >=rc5, thw folling, as an example, appears in dmesg:
ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman ioctl32(regedit.exe:11801): Unknown cmd fd(9) cmd(82187201){02} arg(00221000) on /home/redeeman/.wine/drive_c/windows/system32

Quoted 6 lines
Quoted 6 lines

Try

echo 0 > /proc/sys/kernel/compat-log

I don't _think_ we did anything to change the logging in there. Which kernel version were you using previously (the one which didn't do this)?

Possibly some ioctl got removed. I don't know why it would only occur within a chrooted environment.

Possibly one could work out what's going on by reverse-engineering x86_64 ioctl command 0x82187201, but unfortunately I don't have time to do that.

Also unfortunately there appears to be an assumption that unless I personally can immediately and straightforwardly identify a bug-owner, I personally own the bug. The best I can suggest is that you raise a report at bugzilla.kernel.org so this issue gets ignored in a more organised fashion.

Sorry.

#9 lore raw
Quoted 2 lines · Andrew Morton

Possibly one could work out what's going on by reverse-engineering x86_64 ioctl command 0x82187201, but unfortunately I don't have time to do that.

strace can do that.

David