i can boot this kernel with noexec=off. this parameter was not required with tuxonice-sources-2.6.34-r4, which was the previous kernel on this machine, which is making wonder whether everything is right. i'm also not filing this with b.k.o initially, since it could be something with gentoo-patches. attachments to follow. Reproducible: Always
Created attachment 271423 [details] dmesg
Created attachment 271425 [details] kernel configuration
Created attachment 271427 [details] emerge --info
$ qlist -IUv v86d sys-apps/v86d 0.1.10
It's a x86_32 PAE-enabled kernel, thus noexec is enabled by default. If you had the same config with tuxonice-sources, I don't think this would differ. You can try booting 2.6.34 with genpatches maybe, just to be sure. 99% this is not a genpatches issue. Can you reproduce this with any other kernel version between 2.6.34 and 2.6.38? It can be related to changes in uvesafb between 2.6.34 and 2.6.38 maybe? Although, a diff didn't show any significant changes, except to a kernel parameter type handling, I think. 2.6.39-rcs have some changes regarding uvesafb, if you want to try.
it is currently too complicated to do thorough testing with intermediary kernels. noexec disabled seems to have no ill effects so i'm happy with that for the time being. thanks for the tip on 2.6.39, we'll see what it brings, i'll post an update when its time for upgrade.
