From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: Please test xen/stable-2.6.32.x in xen.git
Date: Thu, 01 Apr 2010 23:04:18 +0200 [thread overview]
Message-ID: <4BB50A52.2000302@access.denied> (raw)
In-Reply-To: <4BB4FD36.3070408@goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
Am 01.04.2010 22:08, schrieb Jeremy Fitzhardinge:
> On 04/01/2010 12:55 PM, Stefan Kuhne wrote:
HEllo Jeremy,
>
> What device is it? Is it something with only an out-of-tree driver that
> your domU kernel has, or are you running it in domU for some other reason?
>
no, i've it not activate in Dom0 Kernel.
I make WLAN in DomU.
My Dom0 only manage my DomUs.
>> All hangs. Even "CTRL + ALT + DEL" doesn't work.
>> I can test it later or tomorrow (MEST).
>>
>
> Do you have access to the Xen console? Does it still respond?
>
Do you mean "xm console $DomU"?
Yes i have, i don't know if i've try it.
>>>> Another question, cpufreq isn't running with 2.6.32 from you (Intel
>>>> T5200 CPU). 2.6.31 works fine.
>>>>
>>>>
>>> Hm, yeah, it seems to work sometimes and not others. I'm not sure why.
>>> Is ACPI_PROCESSOR(_XEN) =y or =m in your .config?
>>>
>>>
>> Dev-Eis # grep ACPI_PROCESSOR build-2.6.32.x-xen/.config
>> CONFIG_ACPI_PROCESSOR=m
>> # CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
>> Dev-Eis #
>>
>
> You should also be able to enable ACPI_PROCESSOR_XEN (also requires
> CPU_FREQ).
>
Were can i find it in menuconfig?
>> Then i have to use 2.6.31 from you :(, but only with running WLAN.
>> It should be nice when both is running ;).
>>
>> My AMD Hardware has no support for it ...
>>
>
> What doesn't it have support for?
>
cpufreq, it is a K8 (3800+ EE SFF).
Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-04-01 21:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 17:58 Please test xen/stable-2.6.32.x in xen.git Jeremy Fitzhardinge
2010-03-31 18:14 ` Stefan Kuhne
2010-03-31 19:06 ` Jeremy Fitzhardinge
2010-03-31 20:26 ` Stefan Kuhne
2010-03-31 20:31 ` Jeremy Fitzhardinge
2010-04-01 7:38 ` Stefan Kuhne
2010-04-01 17:55 ` Martinx - ジェームズ
2010-04-01 19:35 ` Jeremy Fitzhardinge
2010-04-01 20:29 ` Martinx - ジェームズ
2010-04-01 20:06 ` Konrad Rzeszutek Wilk
2010-04-01 19:06 ` Jeremy Fitzhardinge
2010-04-01 19:55 ` Stefan Kuhne
2010-04-01 20:08 ` Jeremy Fitzhardinge
2010-04-01 21:04 ` Stefan Kuhne [this message]
2010-04-01 21:49 ` Jeremy Fitzhardinge
2010-04-01 21:54 ` Stefan Kuhne
2010-04-01 22:02 ` Jeremy Fitzhardinge
2010-04-01 22:08 ` Stefan Kuhne
2010-04-02 10:51 ` Pasi Kärkkäinen
2010-04-03 14:10 ` X-Server doesn't start under Xen 4.0-rc9 & 2.6.31.11 pvops on top of F12 Boris Derzhavets
2010-04-06 18:30 ` Jeremy Fitzhardinge
2010-04-06 21:37 ` Boris Derzhavets
2010-04-06 22:01 ` Jeremy Fitzhardinge
2010-04-06 22:40 ` Mark Hurenkamp
2010-04-06 22:41 ` Jeremy Fitzhardinge
2010-04-06 23:08 ` Mark Hurenkamp
2010-04-07 11:30 ` Boris Derzhavets
2010-04-07 16:20 ` Boris Derzhavets
2010-04-06 22:38 ` Mark Hurenkamp
2010-04-06 22:40 ` Jeremy Fitzhardinge
2010-04-02 13:11 ` Bugs in 2.6.31.12-pvops Carsten Schiers
2010-04-02 18:11 ` Jeremy Fitzhardinge
2010-04-08 0:30 ` Please test xen/stable-2.6.32.x in xen.git Konrad Rzeszutek Wilk
[not found] ` <4BBD9DC7.603@access.denied>
2010-04-08 14:59 ` Konrad Rzeszutek Wilk
2010-03-31 18:45 ` Pasi Kärkkäinen
2010-03-31 20:10 ` Olivier B.
2010-03-31 20:32 ` Olivier B.
2010-03-31 20:35 ` Jeremy Fitzhardinge
2010-03-31 20:43 ` Olivier B.
2010-04-05 16:53 ` Guillaume Rousse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB50A52.2000302@access.denied \
--to=stefan.kuhne@gmx.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).