[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090427165511.GA4801@hades.domain.com>
Date: Mon, 27 Apr 2009 17:55:11 +0100
From: Luis Henriques <henrix@...o.pt>
To: Jan Kiszka <jan.kiszka@...mens.com>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Dave Jones <davej@...hat.com>, Ingo Molnar <mingo@...hat.com>,
mark.langsdorf@....com, linux-kernel@...r.kernel.org,
Avi Kivity <avi@...hat.com>
Subject: Re: [BUG -tip] unable to handle kernel paging request
On Mon, Apr 27, 2009 at 10:43:28AM +0200, Jan Kiszka wrote:
> > I believe my problem has finally been solved by commit
> > 888d256e9c565cb61505bd218eb37c81fe77a325 in kvm git tree. Basically, the kvm
> > notifier for the cpufreq was not being unregistered when kvm module was
> > unloaded and, thus, when notifier_call_chain invoked the handler for the kvm,
> > there was a NULL pointer there.
> >
> > Does this make sense to everybody?
>
> If your system unloads the kvm modules on shutdown/reboot: yes, would
> make sense.
Yes, I am using kvm modules and these modules are indeed unloaded on shutdown.
So, I believe this is what caused the bug I reported -- Although I initially
though it was related with the powernow-k8 module.
Regards,
--
Luis Henriques
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists