linux-kernel - Re: 2.6.30-rc1 A few issues and a stall

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200904141803.14660.edt@aei.ca>
Date:	Tue, 14 Apr 2009 18:03:14 -0400
From:	Ed Tomlinson <edt@....ca>
To:	Avi Kivity <avi@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: 2.6.30-rc1 A few issues and a stall

On Tuesday 14 April 2009 08:39:42 Avi Kivity wrote:
> Ed Tomlinson wrote:
> > On Tuesday 14 April 2009 06:03:58 Avi Kivity wrote:
> >   
> >> Ed Tomlinson wrote:
> >>     
> >>> Once the above networking stuff is setup I start kvm with the command below
> >>>
> >>> QEMU_AUDIO_DRV=alsa kvm -m 1024 -cdrom /mnt/sdc4/divx/archlinux-2009.02-ftp-i686.iso -boot c -smp 3 -usb -usbdevice tablet -vga std -drive file=arch.img -net nic,macaddr=52:54:00:12:34:23 -net tap,ifname=qtap0,script=no -soundhw all -mem-path /hugepages
> >>>
> >>> which works and the kvm session boots just fine.  
> >>>
> >>> Issue 2.  When I attempt to ping outside the kvm session the pc (not just the kvm session) hangs.
> >>> Its impossible to kill the kvm session and there are numerious info messages from RCU (tree RCU enabled)
> >>> about stalls.  
> >>>   
> >>>       
> >> The rcu messages are likely because a processor has died.
> >>
> >> Do things work if you drop -mem-path?
> >>     
> >
> > It makes no difference.  I did notice that one cpu is peged at 100% though.  I'll be trying
> > CONFIG_PROVE_LOCKING tonight for another problem - might give interesting results.
> >   
> 
> Oh, so this goes away without CONFIG_PROVE_LOCKING?

Nothing goes away.  This happens without CONFIG_PROVE_LOCKING active in the kernel.  Given 
that one CPU is running at 100% I suspect that a spinlock is stuck...

Ed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/