WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Rebased patch set xen-patches-2.6.32-1.tar.bz2

Hello,

Patching is needed for building 2.6.32.11, but it should revert commit 14be1f7454ea96ee614467a49cf018a1a383b189 (http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=14be1f7454ea96ee614467a49cf018a1a383b189). Fajar's patch comments two lines and it should only comment the first one. From what I could understand, doing this will open a problem when working with UV systems (I don't know what they are...), but should be ok otherwise. If anyone has a better patch (or could share some light to what UV systems are) please come forward! ;)



On Tue, 2010-05-11 at 14:52 +0100, Luís Silva wrote:
Hello again,

I haven't applied Fajar's patch, but I'm trying again this time with kernel 2.6.32.11. It is still building, but the problem seems to have gone away. I found a commit in 2.6.32 changelog that seems to be the source of my problems (http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=a7b480e7f30b3813353ec009f10f2ac7a6669f3b)...

Any suggestions on how to patch this problem away?

Thanks,
Luís Silva

On Sat, 2010-05-08 at 21:31 -0400, listmail wrote:
Sorry, I just now noticed that you were talking about 2.6.32.12

listmail wrote:
> I never seen the build failure without Fajar's patch, but did you also 
> apply his patch?  I had no issues building the kernel.  I still can't 
> use it because of the previously mentioned keyboard problem I'm 
> having, but that's another story.
>
> Luís Silva wrote:
>> Hello,
>>
>> I've been trying pvops kernel, but also took a look at these rebased 
>> patches... I've applied them to 2.6.32.12 and they apply cleanly, but 
>> I get this error on compilation... Has anyone suceeded in using this 
>> kernel?
>>
>> CC      arch/x86/kernel/cpu/intel_cacheinfo.o
>> arch/x86/kernel/cpu/intel_cacheinfo.c: In function 
>> ‘store_cache_disable’:
>> arch/x86/kernel/cpu/intel_cacheinfo.c:406: error: implicit 
>> declaration of function ‘wbinvd_on_cpu’
>> make[3]: *** [arch/x86/kernel/cpu/intel_cacheinfo.o] Error 1
>> make[2]: *** [arch/x86/kernel/cpu] Error 2
>> make[1]: *** [arch/x86/kernel] Error 2
>> make: *** [arch/x86] Error 2
>>
>> On Thu, 2010-05-06 at 11:44 -0400, listmail wrote:
>>> Fajar A. Nugraha wrote:
>>> > On Thu, May 6, 2010 at 10:17 AM, listmail <listmail@xxxxxxxxxxxx 
>>> <mailto:listmail@xxxxxxxxxxxx>> wrote:
>>> >   >> If you already have a patch please forward it.
>>> >>     >
>>> > It simply disables a call for check_tsc_unstable() on intel.c, which
>>> > enables 2.6.32.11 with xen patches to build cleanly. I'm testing this
>>> > kernel right now on top of RHEL5 + Gitco's Xen 4.0. Seems to work 
>>> fine
>>> > so far, with small caveats:
>>> > - kernel config needs to be adjusted to use 
>>> CONFIG_SYSFS_DEPRECATED=y,
>>> > CONFIG_SYSFS_DEPRECATED_V2=y. Necessary since RHEL5 uses older udev
>>> > version (095).
>>> > - boot seems to take longer, due to /lib/udev/rename_device using 
>>> 100%
>>> > CPU load. Not really sure why
>>> >
>>> > The good news:
>>> > - blktap2 works
>>> > - due to enhanced fuse support in newer kernels, zfs-fuse can be used
>>> > with blktap2.
>>> >
>>> >   >>  I am thinking about
>>> >>  retrying 2.6.32 on the latest possible patchset to see if I have 
>>> the same
>>> >> keyboard repeat issue.
>>> >>     >
>>> > what keyboard repeat issue? I'm accessing the server using ILO serial
>>> > and graphic console, no such issue so far.
>>> >
>>> >   Well I have a USB Logitech 250 keyboard.  For some reason when 
>>> using xen patched 2.6.32.9 I can be typing on tty console and it 
>>> will randomly repeat one of the characters that I type 3-4 times. 
>>> (ie.  xm lisssst / sudddo -s etc.)  I tried using kbdrate settings 
>>> but did not have any luck.  I don't think many people will have the 
>>> issue though.
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
>>> http://lists.xensource.com/xen-users
>>>
>>>     
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users