Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752082Ab3CWTpW (ORCPT ); Sat, 23 Mar 2013 15:45:22 -0400 Received: from mail-ve0-f181.google.com ([209.85.128.181]:40118 "EHLO mail-ve0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752044Ab3CWTpT (ORCPT ); Sat, 23 Mar 2013 15:45:19 -0400 MIME-Version: 1.0 In-Reply-To: References: <1363809337-29718-1-git-send-email-riel@surriel.com> Date: Sat, 23 Mar 2013 12:45:18 -0700 X-Google-Sender-Auth: TOwu-bLgWZyGK6j-Zp1_HZqIaX4 Message-ID: Subject: Re: ipc,sem: sysv semaphore scalability From: Linus Torvalds To: Emmanuel Benisty Cc: Rik van Riel , 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: 1096 Lines: 23 On Fri, Mar 22, 2013 at 8:19 PM, Emmanuel Benisty wrote: > > I could reproduce it but could you please let me know what would be > the right tools I should use to catch the original oops? > This is what I got but I doubt it will be helpful: > http://i.imgur.com/Mewi1hC.jpg In this case, I think the best thing to do would be to comment out all of drm_warn_on_modeset_not_all_locked(), because those warnings make the original problem (that probably caused the lock problem in the first place that it is warning about) scroll away. That said, you should also take the oneliner fix that Rik posted to patch 7 (subject line: "[PATCH 7/7 part3] fix for sem_lock") and apply that, just to make sure that you aren't possibly hitting a bug with the shared-memory locking introduced by that (unusual) case. Linus -- 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/