mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hubbard" <david.c.hubbard@gmail.com>
To: "Peter Zijlstra" <peterz@infradead.org>,
	"Linux kernel" <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.23-git8: Lock dependency engine debugging failure
Date: Tue, 16 Oct 2007 08:17:58 -0700	[thread overview]
Message-ID: <4dfa50520710160817l2774c983u2531a45ff08d8c80@mail.gmail.com> (raw)
In-Reply-To: <1192543173.27435.96.camel@twins>

Hi Peter,

On 10/16/07, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, 2007-10-15 at 20:28 -0700, David Hubbard wrote:
> > I am not subscribed to LKML, so please CC me in replies. I am
> > reporting a regression when CONFIG_DEBUG_LOCKDEP is enabled in
> > 2.6.23-git8. The error occurs immediately before loading init.
> > Complete dmesg and kernel config are attached.
> >
> > [   28.528074] VFS: Mounted root (ext3 filesystem) readonly.
> > [   28.528090] Freeing unused kernel memory: 212k freed
> > [   28.537431] Write protecting the kernel read-only data: 1036k
> > [   28.622874] WARNING: at kernel/lockdep.c:2658 check_flags()
>
> Could you try if the below patch works for you?
>
> --
> Subject: lockdep: fix fault vs irq tracing
>
> Ensure we fixup the IRQ state before we hit any locking code.
>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
>  arch/x86/mm/fault_32.c |   10 ++++++++++
>  arch/x86/mm/fault_64.c |   10 ++++++++++
>  2 files changed, 20 insertions(+)

That fixed the problem.

Cheers!
David

      reply	other threads:[~2007-10-16 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  3:28 David Hubbard
2007-10-16 13:59 ` Peter Zijlstra
2007-10-16 15:17   ` David Hubbard [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=4dfa50520710160817l2774c983u2531a45ff08d8c80@mail.gmail.com \
    --to=david.c.hubbard@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /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®