xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Claus Rosenberger <Claus.Rosenberger@rocnet.de>
To: xen-devel@lists.xensource.com
Subject: Re: Freeze with 2.6.32.19 and xen-4.0.1rc5
Date: Mon, 23 Aug 2010 10:01:06 +0200	[thread overview]
Message-ID: <4C722AC2.6080701@rocnet.de> (raw)
In-Reply-To: <4C704E75.2050200@rocnet.de>

Am 22.08.2010 00:08, schrieb Claus Rosenberger:
>  Am 21.08.2010 16:02, schrieb Pasi Kärkkäinen:
>> On Sat, Aug 21, 2010 at 03:47:57PM +0200, Claus Rosenberger wrote:
>>>  Hi,
>>>
>>> i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19
>>> with xen-4.0.1rc5. Due some reason the system freezes from time to time.
>>> I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn't write
>>> anything to serial console so there are no errors or something like that.
>>>
>>> Perhaps there is something to see from the logs ...
>>>



I did some tests and get a configuration working

title		Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32.19
root		(hd0,0)
kernel		/boot/xen-4.0-amd64.gz dom0_mem=524288 console=com1 com1=115200,8n1,0xf1c0,0  sync_console
loglvl=all guest_loglvl=all acpi=ht noapic noirqbalance
module		/boot/vmlinuz-2.6.32.19 root=/dev/md0 ro console=tty0 console=hvc0 nomodeset
module		/boot/initrd.img-2.6.32.19


With "acpi=ht noapic noirqbalance" it seems to be stable.

Without that options i get freezes soon after rebooting but there are no logs an the serial output.
Kernel 2.6.31.14 didn't work as well  and the other working kernel without that acpi options is
2.6.31.9 but thats not a pvops kernel.

  reply	other threads:[~2010-08-23  8:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 13:47 Freeze with 2.6.32.19 and xen-4.0.1rc5 Claus Rosenberger
2010-08-21 14:02 ` Pasi Kärkkäinen
2010-08-21 22:08   ` Claus Rosenberger
2010-08-23  8:01     ` Claus Rosenberger [this message]
2010-08-23 11:09       ` Pasi Kärkkäinen
2010-08-23 12:29         ` Pasi Kärkkäinen
2010-08-24  7:50           ` Claus Rosenberger
2010-08-24  8:16             ` Freeze with 2.6.32.19 and xen-4.0.1rc5, acpi problems Pasi Kärkkäinen
2010-08-24  8:49               ` Jeremy Fitzhardinge
2010-08-24 23:22                 ` Claus Rosenberger
2010-08-25  8:02                   ` Claus Rosenberger
2010-08-25  8:53                     ` Pasi Kärkkäinen
2010-08-27  7:03                       ` Claus Rosenberger
2010-12-05  6:13                         ` Mark Brown
2010-12-06 13:04                           ` Keir Fraser
2010-12-06 17:10                             ` Mark Brown
2010-12-06 17:19                               ` Mark Brown
2010-12-10  2:24                                 ` Freeze with 2.6.32-5 and xen-4.0.2-rc1-pre Lockup Mark Brown
2010-12-13 16:55                                   ` Konrad Rzeszutek Wilk
2010-12-07 11:29                               ` Re: Freeze with 2.6.32.19 and xen-4.0.1rc5, acpi problems Sander Eikelenboom
2010-12-07 11:37                                 ` Ian Campbell
2010-12-07 16:35                                   ` Mark Brown
2010-08-21 23:04 ` Freeze with 2.6.32.19 and xen-4.0.1rc5 Bruce Edge
2010-12-14  0:59 ` Mark Brown
2010-12-14 11:04   ` Pasi Kärkkäinen

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=4C722AC2.6080701@rocnet.de \
    --to=claus.rosenberger@rocnet.de \
    --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).