Skip to contentSkip to conversation

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

DISCUSSION Chuck Ebbert 4 participants 8 messages Dec 6, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 6 lines · David Howells
Quoted 3 lines

I only have 32-bit userspace. When I run your program against a directory on a JFS filesystem (msdos ioctls not supported) I get this on vanilla 2.6.19:

Can I just check? You're using an x86_64 CPU in 64-bit mode with a 64-bit kernel, but with a completely 32-bit userspace?

It's FC5 i386 so there's no way any 64-bit userspace code is in there. (I have a cross-compiler only for building kernels.) Having a pure 32-bit userspace lets me switch between i386 and x86_64 kernels without having to maintain two separate Linux installs.

Quoted 2 lines

A question for you: Why is userspace assuming that it'll get ENOTTY rather than EINVAL?

I'm not sure it is, but that's what it used to get.

Kasper, what problems (other that the annoying message) are you having?

Signature · 2 lines
Chuck
"Even supernovas have their duller moments."
#1 lore raw
Quoted 16 lines · Chuck Ebbert

In-Reply-To: <[email protected]>

Quoted 6 lines · David Howells
Quoted 3 lines

I only have 32-bit userspace. When I run your program against a directory on a JFS filesystem (msdos ioctls not supported) I get this on vanilla 2.6.19:

Can I just check? You're using an x86_64 CPU in 64-bit mode with a 64-bit kernel, but with a completely 32-bit userspace?

It's FC5 i386 so there's no way any 64-bit userspace code is in there. (I have a cross-compiler only for building kernels.) Having a pure 32-bit userspace lets me switch between i386 and x86_64 kernels without having to maintain two separate Linux installs.

Quoted 6 lines
Quoted 2 lines

A question for you: Why is userspace assuming that it'll get ENOTTY rather than EINVAL?

I'm not sure it is, but that's what it used to get.

Kasper, what problems (other that the annoying message) are you having?

if it had only been the messages i wouldnt have complained. the thing is, when i get these messages, the app provoking them acts very strange, and in some cases, my system simply hardlocks.

and i am very very sure its because of this, i can run with the kernel (atleast with rc5 i had that long) for 10 days, and then chroot in, run the 32bit apps, and within hours of using, hardlock.

wine seems to be worst at provoking hardlock, however i encountered one i am sure was caused by java(the 32bit one inside chroot).

as i said in my post yesterday, my chroot doesent have access to my vfat partitions, so i dont believe thats it.

Quoted 1 line
#2 lore raw
Quoted 3 lines · Kasper Sandberg

and i am very very sure its because of this, i can run with the kernel (atleast with rc5 i had that long) for 10 days, and then chroot in, run the 32bit apps, and within hours of using, hardlock.

What do you mean by "hardlock"? Do you mean the application has to be killed, or do you mean the kernel is stuck and the machine has to be rebooted?

David

#3 lore raw
Quoted 8 lines · David Howells
Quoted 3 lines · Kasper Sandberg

and i am very very sure its because of this, i can run with the kernel (atleast with rc5 i had that long) for 10 days, and then chroot in, run the 32bit apps, and within hours of using, hardlock.

What do you mean by "hardlock"? Do you mean the application has to be killed, or do you mean the kernel is stuck and the machine has to be rebooted?

i mean the kernel itself, two of the times it has happened to me, magic sysrq havent even been able to reboot for me, i had to hit the button on my tower.

when i the very first time encountered this, it was with regedit, the app went nuts, and then it frooze, i had to kill -9 it, and then an hour later i noticed the kernel messages.

Quoted 3 lines

David

#4 lore raw
Quoted 5 lines · Kasper Sandberg
Quoted 2 lines

What do you mean by "hardlock"? Do you mean the application has to be killed, or do you mean the kernel is stuck and the machine has to be rebooted?

i mean the kernel itself, two of the times it has happened to me, magic sysrq havent even been able to reboot for me, i had to hit the button on my tower.

That's got to be some other problem. There's no way this ioctl error message change should cause the kernel to die - applications, yes; but not the kernel.

David

#5 lore raw
Quoted 10 lines · David Howells
Quoted 5 lines · Kasper Sandberg
Quoted 2 lines

What do you mean by "hardlock"? Do you mean the application has to be killed, or do you mean the kernel is stuck and the machine has to be rebooted?

i mean the kernel itself, two of the times it has happened to me, magic sysrq havent even been able to reboot for me, i had to hit the button on my tower.

That's got to be some other problem. There's no way this ioctl error message change should cause the kernel to die - applications, yes; but not the kernel.

Okay, do you have an idea what it can be then? it have to be something in relation to 32bit emulation, cause it happens only when using 32bit apps.

Quoted 3 lines

David

#6 lore raw
In reply to Kasper Sandberg
Quoted 3 lines

and i am very very sure its because of this, i can run with the kernel (atleast with rc5 i had that long) for 10 days, and then chroot in, run the 32bit apps, and within hours of using, hardlock.

Early AMD K8 platforms had a hardware bug that could have caused such hardlocks when running 32bit code under 64bit (independent of anything the kernel does). If you have such a board/CPU try a BIOS update.

-Andi

#7 lore raw
Quoted 7 lines · Andi Kleen
Quoted 3 lines

and i am very very sure its because of this, i can run with the kernel (atleast with rc5 i had that long) for 10 days, and then chroot in, run the 32bit apps, and within hours of using, hardlock.

Early AMD K8 platforms had a hardware bug that could have caused such hardlocks when running 32bit code under 64bit (independent of anything the kernel does). If you have such a board/CPU try a BIOS update.

well, 2.6.18 were 100% stable, none of these issues.

however you have caught my attention, cause i have one of the first amd64's, a 3200+ 1mb cache, socket 754. and an asus board. ill try find a floppy and upgrade the bios if there are updates available.

Quoted 3 lines

-Andi