mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@gmail.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, penberg@cs.helsinki.fi, mingo@elte.hu
Subject: Re: kmemcheck in linux-next causes NULL pointer dereference at  task_rq_lock
Date: Mon, 10 Aug 2009 20:56:18 +0200	[thread overview]
Message-ID: <19f34abd0908101156x2bc92b22ud1748abb153800fb@mail.gmail.com> (raw)
In-Reply-To: <1249925740.2501.9.camel@dhcp231-106.rdu.redhat.com>

2009/8/10 Eric Paris <eparis@redhat.com>:
> I'm using 2.6.31-rc5-next-20090810 on a vmware server.  Originally I saw
> messages about setting to one cpu, so I booted with maxcpu=1.  I get
> this same panic with and without maxpu.  Booting with kmemcheck=0 boots
> just fine.
>
> I have not tested kmemcheck in linus' tree but will start looking for a
> working version now.  Any suggestions or things I should try?

Hi, thanks for the report, and for trying it out.

Does it crash with "kmemcheck=0 maxcpus=1" (it should be maxcpus, not
maxcpu). This should be a simple way of determining whether it was
kmemcheck or the existing maxcpus code, which we use, that broke.

If you can send config (off-list, probably), I will try to reproduce
and investigate more tomorrow.

Thanks,


Vegard

  reply	other threads:[~2009-08-10 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 17:35 Eric Paris
2009-08-10 18:56 ` Vegard Nossum [this message]
2009-08-10 19:51   ` Eric Paris
2009-08-21 17:20     ` Vegard Nossum
2009-08-21 18:04       ` Eric Paris

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=19f34abd0908101156x2bc92b22ud1748abb153800fb@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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®