mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joao Correia <joaomiguelcorreia@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Amerigo Wang <xiyou.wangcong@gmail.com>,
	linux-kernel@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: lockdep max numbers (was Re: Crashes during boot on 2.6.30 /  2.6.31-rc, random programs)
Date: Thu, 2 Jul 2009 11:45:39 +0100	[thread overview]
Message-ID: <a5d9929e0907020345o4e57897n597bedb2fd1fcf2a@mail.gmail.com> (raw)
In-Reply-To: <1246530720.4752.12.camel@laptop>

Every boot, different programs, on a fedora 11 box. If i dont touch
any of the limits mentioned, it happens every boot.

Changing the two values mentioned, a third complain appears, althouh
more infrequently. I have had  MAX_LOCKDEP_CHAINS pop up regarding
qemu-kvm, and once again on unrar, during regular box usage.

(quad core phenom 9600, asus m3a-h/hdmi board with 4gb ram).

Thank you very much for your time,
Joao Correia
Centro de Informatica
Universidade da Beira Interior
Portugal

On Thu, Jul 2, 2009 at 11:32 AM, Peter Zijlstra<a.p.zijlstra@chello.nl> wrote:
> On Thu, 2009-07-02 at 17:31 +0800, Amerigo Wang wrote:
>> On Wed, Jul 01, 2009 at 09:30:23PM +0100, Joao Correia wrote:
>> >Hello again
>> >
>> >Looks like this just opened the lid on some other limits. I just hit
>> >another thing, which hadn't shown up before i made the changes, but
>> >looks like its just another limit thats too low. This one is harder to
>> >reproduce tho.
>> >
>> >Jun 30 21:35:03 hightech kernel: BUG: MAX_LOCKDEP_CHAINS too low!
>> >Jun 30 21:35:03 hightech kernel: turning off the locking correctness validator.
>> >Jun 30 21:35:03 hightech kernel: Pid: 9379, comm: qemu-kvm Not tainted
>>
>>
>> Similar problem...
>>
>> Peter? Would like to increase these numbers?
>
>> >2.6.30-wl #3
>
>> >Jun 30 21:35:03 hightech kernel: [<c05d0c66>] debug_dma_map_sg+0xe1/0x147
>
> We recently fixed the dma debug stuff to require less lockdep resources,
> Joerg might know if that made it into .30.
>
>> >>>So i dug a little on the source and changed
>> >>>
>> >>>include/linux/sched.h
>> >>>
>> >>># define MAX_LOCK_DEPTH 48UL
>> >>>
>> >>>to
>> >>>
>> >>># define MAX_LOCK_DEPTH 96UL
>
>> >> Let's Cc: Peter to see if he would like to change this number...
>> >>
>> >> Peter?
>
> I really don't think we want to raise this, I mean, holding more that 48
> locks at the same time is somewhat pushing it, don't you think?
>
> Where do you run into this limit?
>
>

      reply	other threads:[~2009-07-02 10:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27 15:07 Crashes during boot on 2.6.30 / 2.6.31-rc, random programs Joao Correia
2009-06-27 15:11 ` Joao Correia
2009-06-29  2:08 ` Américo Wang
2009-06-29  8:53   ` Joao Correia
2009-06-29  9:15     ` Amerigo Wang
2009-06-29 10:30       ` Joao Correia
2009-06-30  9:16         ` Amerigo Wang
2009-07-01 20:30           ` Joao Correia
2009-07-02  9:31             ` lockdep max numbers (was Re: Crashes during boot on 2.6.30 / 2.6.31-rc, random programs) Amerigo Wang
2009-07-02 10:32               ` Peter Zijlstra
2009-07-02 10:45                 ` Joao Correia [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a5d9929e0907020345o4e57897n597bedb2fd1fcf2a@mail.gmail.com \
    --to=joaomiguelcorreia@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®