First tests looked good, but tonight after approx. 2 hours after boot the
Since my previous setup ran perfectly stable for 55 days, i didn't have a
serial console attached.
I shot a photo of what was left onscreen (attached), will attach a serial
console later to get it all.
Friday, May 20, 2011, 8:09:05 PM, you wrote:
> On Fri, May 20, 2011 at 07:57:47PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad / Yu Ke,
>> I have tried konrad's master tree:
> Might want to try devel/next-2.6.39. It has the CPU freq and S3 patches in it.
> I am still working through them, but they do seem to work (I can suspend
> and resume a machine).
> The #master has the ones that have been cleaned up and are slowly going
> to make their path through the maintainers. The ACPI/S#/CPU freq aren't there
>> commit 329408d788f62629131ea28c112e973878d52c9e
>> Merge: e370fe2 773f8cf
>> Author: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
>> Date: Thu May 19 14:37:32 2011 -0400
>> Merge branch 'linux-next'
>> With a xen-4.1.0 hypervisor, on my AMD x6 phenom.
>> Curious if Xen Power Management would work...
>> Output of all xenpm get* commands is attached, prefix 32 is with a stable
>> working 126.96.36.199 kernel from jeremy's tree with working xenpm.
>> prefix 39 is with the kernel from the tree mentoined above.
>> There are differences in cpu-idle-states (C0 and C1 state are not reported
>> on .39)
>> and cpu-freq-states/para (which fails entirely on .39)
>> But it doesn't crash .. just fails .. so that's positive ! :-)
>> Of course i'm willing to give any more information or test additional
>> Will let it run for the night on 2.6.39 to see how blkback works !
Description: JPEG image
Xen-devel mailing list