Messages in this thread | | | Subject | Re: kmemcheck in linux-next causes NULL pointer dereference at task_rq_lock | From | Eric Paris <> | Date | Mon, 10 Aug 2009 15:51:27 -0400 |
| |
On Mon, 2009-08-10 at 20:56 +0200, Vegard Nossum wrote: > 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.
I boots fine with kmemcheck=0
I did get the command line right. maxcpus=1 kmemcheck=1 was the panic I showed in the last message.
> If you can send config (off-list, probably), I will try to reproduce > and investigate more tomorrow.
Will send it now.
Thanks.
-Eric
| |