From: Florian Kirstein <xenlist@custom.ray.net>
To: xen-devel@lists.xensource.com
Subject: Re: bug # 477
Date: Wed, 29 Mar 2006 07:24:01 +0200 [thread overview]
Message-ID: <20060329072401.A26981@web.ray.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0603172155560.27119@localhost>; from xen@jasonandjessi.com on Fri, Mar 17, 2006 at 10:00:58PM -0600
Hallo,
> data. I have confirmed this behaviour in the March 14th pull as well as
> the March 17 pull from xen-unstable-hg. I have also found that if
> xenconsoled does not crash, it goes to 100% CPU in dom0. Any thoughts?
Sorry, none, but I can reproduce this in the current unstable version
(2006/04/28) easily and also had it in older versions. Can't reporduce it
in Xen 2, there the console works smoothly. Test-System was a P4
without hyperthreading.
Easiest way seems to be to open a console to a domU, start "cat" and paste
some larger block of text (I used the content of a full 90x80 xterm) and it
brings xenconsoled in Dom0 to 100% CPU reliably, either for quite some
time (30 seconds or so) or even until I kill it. In both cases the DomU
get's the "soft lockup detected" (see below). Tried various console-buffer
sizes in the xend config but it doesn't seem to make a difference.
OK, you could say "then don't do this", but I'd like to give some users
console-acces for their VMs and it wouldn't be nice if they could
bring my Dom0 into such troubles by simply pasting a block of text
into the console...
MfG, Florian Kirstein
P.S: the error I get every time:
Mar 29 06:55:52 vmtest kernel: BUG: soft lockup detected on CPU#0!
Mar 29 06:55:52 vmtest kernel:
Mar 29 06:55:52 vmtest kernel: Pid: 0, comm: swapper
Mar 29 06:55:52 vmtest kernel: EIP: 0061:[<c01010c7>] CPU: 0
Mar 29 06:55:52 vmtest kernel: EIP is at 0xc01010c7
Mar 29 06:55:52 vmtest kernel: EFLAGS: 00000246 Not tainted (2.6.16-xenU #1)
Mar 29 06:55:52 vmtest kernel: EAX: 00000000 EBX: 00000001 ECX: 00000000 EDX: 000027d5
Mar 29 06:55:52 vmtest kernel: ESI: c035a000 EDI: 00000001 EBP: c035bfa8 DS: 007b ES: 007b
Mar 29 06:55:52 vmtest kernel: CR0: 8005003b CR2: 0804e85c CR3: 0035d000 CR4: 00000640
Mar 29 06:55:52 vmtest kernel: [<c01053c1>] show_trace+0x21/0x30
Mar 29 06:55:52 vmtest kernel: [<c0102f80>] show_regs+0x1a0/0x1c8
Mar 29 06:55:52 vmtest kernel: [<c013de51>] softlockup_tick+0x81/0x90
Mar 29 06:55:52 vmtest kernel: [<c01280cf>] do_timer+0x3f/0xd0
Mar 29 06:55:52 vmtest kernel: [<c0108f5c>] timer_interrupt+0x1cc/0x610
Mar 29 06:55:52 vmtest kernel: [<c013e163>] handle_IRQ_event+0x73/0xc0
Mar 29 06:55:52 vmtest kernel: [<c013e239>] __do_IRQ+0x89/0x100
Mar 29 06:55:52 vmtest kernel: [<c0106b20>] do_IRQ+0x20/0x30
Mar 29 06:55:52 vmtest kernel: [<c025414e>] evtchn_do_upcall+0x8e/0x110
Mar 29 06:55:52 vmtest kernel: [<c01050fc>] hypervisor_callback+0x2c/0x34
Mar 29 06:55:52 vmtest kernel: [<c0102c05>] cpu_idle+0x85/0xf0
Mar 29 06:55:52 vmtest kernel: [<c0102035>] rest_init+0x35/0x40
Mar 29 06:55:52 vmtest kernel: [<c035c9a5>] start_kernel+0x1c5/0x210
Mar 29 06:55:52 vmtest kernel: [<c010006f>] 0xc010006f
next prev parent reply other threads:[~2006-03-29 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 4:00 bug # 477 Jason
2006-03-29 5:24 ` Florian Kirstein [this message]
2006-03-29 9:56 ` Ewan Mellor
2006-03-29 22:39 ` Florian Kirstein
2006-03-30 8:57 ` Keir Fraser
2006-03-30 10:41 ` Keir Fraser
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=20060329072401.A26981@web.ray.net \
--to=xenlist@custom.ray.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.