From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Kirstein Subject: Re: bug # 477 Date: Wed, 29 Mar 2006 07:24:01 +0200 Message-ID: <20060329072401.A26981@web.ray.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: ; from xen@jasonandjessi.com on Fri, Mar 17, 2006 at 10:00:58PM -0600 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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:[] 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: [] show_trace+0x21/0x30 Mar 29 06:55:52 vmtest kernel: [] show_regs+0x1a0/0x1c8 Mar 29 06:55:52 vmtest kernel: [] softlockup_tick+0x81/0x90 Mar 29 06:55:52 vmtest kernel: [] do_timer+0x3f/0xd0 Mar 29 06:55:52 vmtest kernel: [] timer_interrupt+0x1cc/0x610 Mar 29 06:55:52 vmtest kernel: [] handle_IRQ_event+0x73/0xc0 Mar 29 06:55:52 vmtest kernel: [] __do_IRQ+0x89/0x100 Mar 29 06:55:52 vmtest kernel: [] do_IRQ+0x20/0x30 Mar 29 06:55:52 vmtest kernel: [] evtchn_do_upcall+0x8e/0x110 Mar 29 06:55:52 vmtest kernel: [] hypervisor_callback+0x2c/0x34 Mar 29 06:55:52 vmtest kernel: [] cpu_idle+0x85/0xf0 Mar 29 06:55:52 vmtest kernel: [] rest_init+0x35/0x40 Mar 29 06:55:52 vmtest kernel: [] start_kernel+0x1c5/0x210 Mar 29 06:55:52 vmtest kernel: [] 0xc010006f