Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754606AbZKMReM (ORCPT ); Fri, 13 Nov 2009 12:34:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754513AbZKMReF (ORCPT ); Fri, 13 Nov 2009 12:34:05 -0500 Received: from e23smtp07.au.ibm.com ([202.81.31.140]:46390 "EHLO e23smtp07.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753697AbZKMReD (ORCPT ); Fri, 13 Nov 2009 12:34:03 -0500 Date: Fri, 13 Nov 2009 23:03:25 +0530 From: Dhaval Giani To: Rishikesh Cc: iranna.ankad@in.ibm.com, markwiz@us.ibm.com, Peter Zijlstra , containers@lists.linux-foundation.org, bugzilla-daemon@bugzilla.kernel.org, Srivatsa Vaddagiri , linux-kernel@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, Bharata B Rao , lxie@us.ibm.com, Andrew Morton , sharyath@linux.vnet.ibm.com, santwana.samantray@in.ibm.com, Ingo Molnar Subject: Re: [Bugme-new] [Bug 14150] New: BUG: soft lockup - CPU#3 stuck for 61s!, while running cpu controller latency testcase on two containers parallaly Message-ID: <20091113173324.GI9065@linux.vnet.ibm.com> Reply-To: Dhaval Giani References: <20090911142813.dc823bf1.akpm@linux-foundation.org> <20090915125836.GA4087@linux.vnet.ibm.com> <4AB20086.8070105@linux.vnet.ibm.com> <4AB32EA7.20904@linux.vnet.ibm.com> <4AB34445.4060700@linux.vnet.ibm.com> <4AB8A24E.8060209@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AB8A24E.8060209@linux.vnet.ibm.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2737 Lines: 68 On Tue, Sep 22, 2009 at 03:39:18PM +0530, Rishikesh wrote: > Hi Dhaval, > > Today i tried 2 more scenario requested by you on -tip kernel: > > 1> mount cpu on cgroup & other susbsystems ( ns, cpuset,freezer... > except cpu) on cgroup1 e.g:. > /root/lxc on /cgroup type cgroup > (rw,ns,cpuset,freezer,devices,memory,cpuacct,net_cls) > none on /cgroup1 type cgroup (rw,cpu) > > Result: I am able to create container ( no crash after "lxc-execute > ..." command execution). > 2> mount cpu,ns on cgroup > [root@x335a ~]# mount > none on /cgroup type cgroup (rw,ns,cpu) > [root@x335a ~]# lxc-execute -n foo2 -f /etc/lxc/lxc-macvlan.conf /bin/bash > > Result : The system crash with following trace once i execute > lxc-execute command: > > x335a.in.ibm.com login: BUG: NMI Watchdog detected LOCKUP on CPU1, ip > c0425854, registers: > Modules linked in: nfs lockd nfs_acl auth_rpcgss bridge stp llc bnep sco > l2cap bluetooth autofs4 sunrpc ipv6 p4_clockmod dm_multipath uinput > ata_generic pata_acpi floppy i2c_piix4 i2c_core pata_serverworks tg3 > pcspkr serio_raw mptspi mptscsih mptbase scsi_transport_spi [last > unloaded: scsi_wait_scan] > > Pid: 0, comm: swapper Not tainted (2.6.31-tip #2) eserver xSeries 335 > -[867641X]- > EIP: 0060:[] EFLAGS: 00000246 CPU: 1 > EIP is at native_safe_halt+0xa/0xc > EAX: f70a8000 EBX: c096f0d4 ECX: b9d8d702 EDX: 00000001 > ESI: 00000001 EDI: 00000000 EBP: f70a9f74 ESP: f70a9f74 > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 > Process swapper (pid: 0, ti=f70a8000 task=f7086780 task.ti=f70a8000) > Stack: > f70a9f94 c040e63b f70a9f94 c0460b8d 00000001 c096f0d4 00000001 00000000 > <0> f70a9fa4 c0407637 00000001 00000000 f70a9fb0 c075a578 0602080b 00000000 > <0> 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > Call Trace: > [] ? default_idle+0x4a/0x7c > [] ? tick_nohz_restart_sched_tick+0x115/0x123 > [] ? cpu_idle+0x58/0x79 > [] ? start_secondary+0x19c/0x1a1 > Code: 89 e5 0f 1f 44 00 00 50 9d 5d c3 55 89 e5 0f 1f 44 00 00 fa 5d c3 > 55 89 e5 0f 1f 44 00 00 fb 5d c3 55 89 e5 0f 1f 44 00 00 fb f4 <5d> c3 > 55 89 e5 0f 1f 44 00 00 f4 5d c3 55 89 e5 0f 1f 44 00 00 > > > Evening i am going to try 3rd scenario: > - Enable CONFIG_PROVE_LOCKING and then execute above scenario once > again. > > Hope above result will help you to debug further. > Just tested on latest -tip and this issue is no longer reproducible. -- regards, Dhaval -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/