Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758141Ab3CYPUW (ORCPT ); Mon, 25 Mar 2013 11:20:22 -0400 Received: from mail-qe0-f45.google.com ([209.85.128.45]:65505 "EHLO mail-qe0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757830Ab3CYPUV (ORCPT ); Mon, 25 Mar 2013 11:20:21 -0400 MIME-Version: 1.0 In-Reply-To: <51505923.2070504@surriel.com> References: <1363809337-29718-1-git-send-email-riel@surriel.com> <51505881.5060409@surriel.com> <51505923.2070504@surriel.com> Date: Mon, 25 Mar 2013 22:20:19 +0700 Message-ID: Subject: Re: ipc,sem: sysv semaphore scalability From: Emmanuel Benisty To: Rik van Riel Cc: Linus Torvalds , Davidlohr Bueso , Linux Kernel Mailing List , Andrew Morton , hhuang@redhat.com, "Low, Jason" , Michel Lespinasse , Larry Woodman , "Vinod, Chegu" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 915 Lines: 24 On Mon, Mar 25, 2013 at 9:03 PM, Rik van Riel wrote: >>> With the first four patches only, I got some X server freeze (just >>> tried once). >> >> >> Could you try booting with panic=1 so the kernel panics on the first >> oops? > > > Sorry that should be "oops=panic" > > >> Maybe that way (if we are lucky) we will be able to capture the first >> oops, and maybe get an idea of what causes the problem. Sorry Rik, I get all kind of weird behaviors (wireless dies, compiling gets stuck and is impossible to kill, can't kill X) with the 4 patches+oops=panic but no trace. Here after is 7+1 patches with oops=panic boot: http://i.imgur.com/1jep1qx.jpg -- 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/