Messages in this thread | | | Subject | Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64 | From | Kasper Sandberg <> | Date | Sun, 26 Nov 2006 14:47:15 +0100 |
| |
On Wed, 2006-11-22 at 15:25 -0800, Andrew Morton wrote: > On Wed, 22 Nov 2006 15:29:02 +0100 > Kasper Sandberg <lkml@metanurb.dk> 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 > 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. > 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 > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |