On Sat, May 28, 2011 at 06:41:19PM +0530, KESHAV P.R. wrote: > On Sat, May 28, 2011 at 15:08, Greg KH <[email protected]> wrote: > > On Sat, May 28, 2011 at 12:44:40PM +0530, KESHAV P.R. wrote: > >> On Sat, May 28, 2011 at 01:58, Greg KH <[email protected]> wrote: > >> > On Fri, May 27, 2011 at 11:23:47PM +0530, KESHAV P.R. wrote: > >> >> Hi, > >> >> Sorry to be bothering you. I am a user of x86_64 Archlinux and I > >> >> have a x86_64 UEFI system (Asus P8P67 Sandy Bridge motherboard). I > >> >> request you to include the following pacthes in the next stable > >> >> release of 2.6.38.X and 2.6.39.X kernels. > >> >> > >> >> x86, efi: Remove virtual-mode SetVirtualAddressMap call - > >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2b5e8ef35bc89eee944c0627edacbb1fea5a1b84 > >> >> x86, efi: Consolidate EFI nx control - > >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9cd2b07c197e3ff594fc04f5fb3d86efbeab6ad8 > >> >> x86, efi: Merge contiguous memory regions of the same type and > >> >> attribute - > >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=202f9d0a41809e3424af5f61489b48b622824aed > >> >> x86, efi: Pass a minimal map to SetVirtualAddressMap() - > >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7cb00b72876ea2451eb79d468da0e8fb9134aa8a > >> >> x86, efi: Ensure that the entirity of a region is mapped - > >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=935a638241b0658b9749edd060f972575f9d4a78 > >> >> x86, efi: Retain boot service code until after switching to virtual > >> >> mode - > >> >> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commit;h=916f676f8dc016103f983c7ec54c18ecdbb6e349 > >> >> > >> >> I was directed to you by a Archlinux developer ( > >> >> https://bugs.archlinux.org/task/24463 ) . Thanks in advance. > >> > > >> > That's a lot of different patches, can you get the ack from the > >> > developer of them that they should go to the stable kernel tree? If so, > >> > I'll be glad to queue them up. > >> > > >> > Also, all stable kernel stuff should be sent to the [email protected] > >> > address so I don't loose them, and so that the other stable developers > >> > see the requests. > >> > > >> > thanks, > >> > > >> > greg k-h > >> > > >> > >> The last commit (efi: Retain Boot Service Code) has been CCed to > >> [email protected] . I don't know whether the previous five patches are > >> required for the last one. As far as I know it is needed. > > > > Ok, could you test with just that one patch applied and see if that > > resolves your problem? > > > > I will try, but this is the first time I am going to compile a kernel > so I can't guarantee I might even compile it successfully and provide > you with debug info. As such I am mainly a desktop user with no proper > tools to obtain debug info as of now. > > >> I am sorry, I am not familiar with how kernel development works and > >> specifically how intermediate -stable kernels release is done. > > > > Not a problem, you can read about the process in the file in the kernel > > source tree called Documentation/stable_kernel_rules.txt > > > > thanks, > > > > greg k-h > > > > These might be interesting > http://mjg59.dreamwidth.org/2929.html?thread=52337#cmt52337 and > http://mjg59.dreamwidth.org/3244.html . They are written by the author > of the patches, explaining the problem.
Yeah, I'm very aware of the problem :( I'll just apply the one that the author marked for the stable trees. If the next .39 stable release doesn't work for you, please work with Matthew as to determining if other patches are needed to be applied and let me know. thanks, greg k-h _______________________________________________ stable mailing list [email protected] http://linux.kernel.org/mailman/listinfo/stable
