Hallo,
we discussed the following problem in march
my compiled 2.6.20-1.2925 kernel does not boot. It hangs after unmounting the old proc and sys filesystems. However, I can still use Ctrl+Alt+Del to reboot.
Maybe, the problem is related to Selinux.
My compiled kernels 2.6.19-1.2895 and 2.6.19-1.2911 worked fine, and I did not change the kernel configuration.
The Fedora-kernels 2.6.19-1.2895, 2.6.19-1.2911 and 2.6.20-1.2925 also work.
The same problem occured in 2.6.20-1.2933. However, in a needle-in-the-haystick search, I solved the problem by DISabeling the option
Compat VDSO support (COMPAT_VDSO)
Best regards, Daniel
On Thu, Apr 12, 2007 at 05:49:05PM +0200, Daniel Kirsten wrote:
Hallo,
we discussed the following problem in march
my compiled 2.6.20-1.2925 kernel does not boot. It hangs after unmounting the old proc and sys filesystems. However, I can still use Ctrl+Alt+Del to reboot.
Maybe, the problem is related to Selinux.
My compiled kernels 2.6.19-1.2895 and 2.6.19-1.2911 worked fine, and I did not change the kernel configuration.
The Fedora-kernels 2.6.19-1.2895, 2.6.19-1.2911 and 2.6.20-1.2925 also work.
The same problem occured in 2.6.20-1.2933. However, in a needle-in-the-haystick search, I solved the problem by DISabeling the option
Compat VDSO support (COMPAT_VDSO)
That should only be necessary if you're running an ancient glibc. (FC1 era). You can also boot with vdso=off in such situations.
Dave
On Thursday April 12 2007, you wrote:
On Thu, Apr 12, 2007 at 05:49:05PM +0200, Daniel Kirsten wrote:
Hallo,
we discussed the following problem in march
my compiled 2.6.20-1.2925 kernel does not boot. It hangs after unmounting the old proc and sys filesystems. However, I can still use Ctrl+Alt+Del to reboot.
Maybe, the problem is related to Selinux.
My compiled kernels 2.6.19-1.2895 and 2.6.19-1.2911 worked fine, and I did not change the kernel configuration.
The Fedora-kernels 2.6.19-1.2895, 2.6.19-1.2911 and 2.6.20-1.2925 also work.
The same problem occured in 2.6.20-1.2933. However, in a needle-in-the-haystick search, I solved the problem by DISabeling the option
Compat VDSO support (COMPAT_VDSO)
That should only be necessary if you're running an ancient glibc. (FC1 era).
I use glibc-2.5-10.fc6
Daniel
On Thu, Apr 12, 2007 at 08:20:14PM +0200, Daniel Kirsten wrote:
On Thursday April 12 2007, you wrote:
On Thu, Apr 12, 2007 at 05:49:05PM +0200, Daniel Kirsten wrote:
Hallo,
we discussed the following problem in march
my compiled 2.6.20-1.2925 kernel does not boot. It hangs after unmounting the old proc and sys filesystems. However, I can still use Ctrl+Alt+Del to reboot.
Maybe, the problem is related to Selinux.
My compiled kernels 2.6.19-1.2895 and 2.6.19-1.2911 worked fine, and I did not change the kernel configuration.
The Fedora-kernels 2.6.19-1.2895, 2.6.19-1.2911 and 2.6.20-1.2925 also work.
The same problem occured in 2.6.20-1.2933. However, in a needle-in-the-haystick search, I solved the problem by DISabeling the option
Compat VDSO support (COMPAT_VDSO)
That should only be necessary if you're running an ancient glibc. (FC1 era).
I use glibc-2.5-10.fc6
That's.. puzzling. Roland, any ideas?
does booting with vdso=0 as I suggested also work ?
Dave
I may have missed some of the context, so forgive me if I'm confused. It sounds like the report was of CONFIG_COMPAT_VDSO=y causing problems, the problem being fixed by using CONFIG_COMPAT_VDSO=n. Is that right, or inverted?
CONFIG_COMPAT_VDSO=y has never been set in Fedora configs AFAIK. It is not desireable. It's been cleaned up and fixed upstream, some by me and some not by me, fairly recently (probably after 2.6.19, don't really remember). It may well never have been reconciled with the exec-shield patch, and I wouldn't lay odds on whether the current upstream code jibes or not, though I don't know of any interaction problems there off hand.
With the very latest code (certainly after 2.6.20), now perhaps in -mm and not yet all the way in upstream, it will become possible to compile in support for the compatibility mode without undesireable effects when it's not enabled at runtime (by "vdso=2" or a sysctl equivalent). When those changes go in, it will make sense to compile in the compatibility support but not enable it at boot, and this will also likely be the default upstream configuration.
As to the state of some existing or older Fedora kernel, I don't really know off hand (and won't be in a position to try any debugging of my own until I get home next week). print-fatal-signals might shed some light.
Thanks, Roland
On Thursday April 12 2007, you wrote:
I may have missed some of the context, so forgive me if I'm confused. It sounds like the report was of CONFIG_COMPAT_VDSO=y causing problems, the problem being fixed by using CONFIG_COMPAT_VDSO=n. Is that right, or inverted?
It is right.
CONFIG_COMPAT_VDSO=y causes the kernel to hang after unmounting the old proc and sys filesystems. I can boot the same kernel if I use the kernel option vdso=0.
I can boot with CONFIG_COMPAT_VDSO=n
The problem appeared in 2.6.20-1.2925 and 2.6.20-1.2933. I do not know how the option CONFIG_COMPAT_VDSO was turned on. It is turned on in every kernel-config since 2868 (the oldest one I found)
Daniel
Daniel Kirsten wrote:
The problem appeared in 2.6.20-1.2925 and 2.6.20-1.2933. I do not know how the option CONFIG_COMPAT_VDSO was turned on. It is turned on in every kernel-config since 2868 (the oldest one I found)
You mean in your own private config, right? It's not enabled in the standard Fedora kernel config.
On Friday April 13 2007, Chuck Ebbert wrote:
Daniel Kirsten wrote:
The problem appeared in 2.6.20-1.2925 and 2.6.20-1.2933. I do not know how the option CONFIG_COMPAT_VDSO was turned on. It is turned on in every kernel-config since 2868 (the oldest one I found)
You mean in your own private config, right? It's not enabled in the standard Fedora kernel config.
yes. in my private config
kernel@lists.fedoraproject.org
-
Chuck Ebbert -
Daniel Kirsten -
Dave Jones -
Roland McGrath