Andrew Morton <akpm <at> linux-foundation.org> writes: > > Revert "[PATCH] Fix CONFIG_COMPAT_VDSO" > > This reverts commit a1f3bb9ae4497a2ed3eac773fd7798ac33a0371f. > > > > Several systems couldnt boot using CONFIG_HIGHMEM64G=y as > > reported in bug #8040. Reverting the above patch solved the problem.
> I think reverting it is probably the right thing to do, unless we can fix > it for real quite promptly. Chuck Ebbert at redhat.com asked: > Can you please double check this by trying with/without again -- sometimes bisects go bad. As requested I started to redo the test but now without git using kernel.org tars. The results now are, still using the same .config: linux-2.6.20.tar.gz : bad linux-2.6.20.1.tar.gz: bad (boot log equal) linux-2.6.20.2.tar.gz: good linux-2.6.20.3.tar.gz: good (triple checked) Chuck is right, the bisect gone bad. I asked Nilshar to try these kernels too with: COMPAT_VDSO=y CONFIG_HIGHMEM64G=y He did and says 2.6.20.3 works fine. So only 2.6.20 and 2.6.20.1 had this 'hang' at boot behavior on my Supermicro 7044 while Nilshar's machine started working with 2.6.20.3 Reverting avoided imo. I hope more people cheer up who reported bug #8040 and confirm it's fine with the latest stable. - 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/