All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: John Stultz <john.stultz@linaro.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
	xen-devel@lists.xensource.com
Subject: Re: 2.6.39 crashes BUG: unable to handle kernel NULL pointer dereference at 000000000000042 .. cmos_checkintr+0x4d/0x55 under Xen as PV guest.
Date: Tue, 22 Mar 2011 10:38:41 -0400	[thread overview]
Message-ID: <20110322143841.GA26952@dumpdata.com> (raw)
In-Reply-To: <1300736400.2731.66.camel@work-vm>

> > No. 2.6.38 vaniall works great.
> 
> Ok. Hrm. 
> 
> > > Any insight there?
> > 
> > I hoped you might have :-)
> 
> Could you help me understand where in the probe logic xen bombs out of
> the cmos code?

Sure. The issue is that rtc_update_irq calls schedule_work with rtc->irqwork
which has not been initialized. The reason for that is that rtc_device_register
has never been called.. uh wait, that does not make sense, it is called in
cmos_do_probe. Hmm, let get find out exactly on which variable queue_work_on
bombs out on.


  reply	other threads:[~2011-03-22 14:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 20:38 2.6.39 crashes BUG: unable to handle kernel NULL pointer dereference at 000000000000042 .. cmos_checkintr+0x4d/0x55 under Xen as PV guest Konrad Rzeszutek Wilk
2011-03-18 21:59 ` John Stultz
2011-03-19  2:51   ` Konrad Rzeszutek Wilk
2011-03-19  2:51     ` Konrad Rzeszutek Wilk
2011-03-21 19:40     ` John Stultz
2011-03-22 14:38       ` Konrad Rzeszutek Wilk [this message]
2011-03-24 12:27         ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-03-24 19:05           ` John Stultz
2011-03-24 20:39             ` John Stultz
2011-03-25 12:21               ` Konrad Rzeszutek Wilk
2011-03-19  9:28   ` Richard Cochran

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=20110322143841.GA26952@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.