From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?TWFyY2luIE1pcm9zxYJhdw==?= Subject: Re: Re: [b.g.o.358549] blkfront: Move blkif_interrupt into a tasklet. Date: Tue, 31 May 2011 13:28:44 +0200 Message-ID: <4DE4D0EC.9060508@mejor.pl> References: <4DC15DC8.2010302@mejor.pl> <4DD7C4B9.6070308@mejor.pl> <20110524131353.GA10513@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20110524131353.GA10513@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org W dniu 24.05.2011 15:13, Konrad Rzeszutek Wilk pisze: > On Sat, May 21, 2011 at 03:57:13PM +0200, Marcin Mirosław wrote: >> Hi! >> I've noticed kernel threads "flush-254:9" does 100%CPU utilization. >> Device 254-9 is logical volume created via LVM. >> I don't know if this problem is related to earlier problem, but it >> happens on the same kernel as mentioned issue. > > What kernel? What is your dom0 kernel and your domU kernel? What > is the LVM volume? Is it snapshot? Is it on top of a SATA device? > SSD? Unfortunately i can't say much about dom0. Admin is very busy and didn't answer me. I only know domU is placed at one logical volume (lvm). About domU: - i didn't noticed any problem with kernels <2.6.37 - with kernels >=2.6.37 i noticed two problems, one of them is mentioned earlier (WARNING: at block/blk-core.c:239 blk_start_queue+0x20/0x32() ), second one is "100% of CPU utilization" - i'm not using lvm snapshot (or other features) - domU works as PV - zgrep -i xen /proc/config.gz CONFIG_XEN=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=8 CONFIG_XEN_SAVE_RESTORE=y CONFIG_XEN_BLKDEV_FRONTEND=y CONFIG_XEN_NETDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_BALLOON=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_PLATFORM_PCI=m ( kernel: 2.6.36-hardened-r9 ) - grep -i xen /usr/src/linux-2.6.38-hardened-r5/.config | grep -v "^#" CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_XEN_BLKDEV_FRONTEND=y CONFIG_XEN_NETDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_BALLOON=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_PLATFORM_PCI=m CONFIG_SWIOTLB_XEN=y (problematic kernel) > Do give more details please. I'm sorry for inconvenience. > And what is 'bgo'? I presume a bugzilla, but you hadn't provided > a link. This is gentoo bugzilla: http://bugs.gentoo.org/358549 Regards, Marcin