public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <henrix@sapo.pt>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@redhat.com>,
	mark.langsdorf@amd.com, linux-kernel@vger.kernel.org,
	Avi Kivity <avi@redhat.com>
Subject: Re: [BUG -tip] unable to handle kernel paging request
Date: Mon, 27 Apr 2009 17:55:11 +0100	[thread overview]
Message-ID: <20090427165511.GA4801@hades.domain.com> (raw)
In-Reply-To: <49F57030.3010802@siemens.com>

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

      reply	other threads:[~2009-04-27 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 16:59 [BUG -tip] unable to handle kernel paging request Luis Henriques
2009-04-13 20:59 ` Paul E. McKenney
2009-04-23 18:24   ` Luis Henriques
2009-04-27  8:43     ` Jan Kiszka
2009-04-27 16:55       ` Luis Henriques [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=20090427165511.GA4801@hades.domain.com \
    --to=henrix@sapo.pt \
    --cc=avi@redhat.com \
    --cc=davej@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.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