This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: 2.6.39 crashes BUG: unable to handle kernel NULL pointer

To: John Stultz <john.stultz@xxxxxxxxxx>
Subject: [Xen-devel] Re: 2.6.39 crashes BUG: unable to handle kernel NULL pointer dereference at 000000000000042 .. cmos_checkintr+0x4d/0x55 under Xen as PV guest.
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 22 Mar 2011 10:38:41 -0400
Cc: tglx@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Mar 2011 07:39:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1300736400.2731.66.camel@work-vm>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110318203830.GA9262@xxxxxxxxxxxx> <1300485566.2731.46.camel@work-vm> <20110319025134.GA3298@xxxxxxxxxxxx> <1300736400.2731.66.camel@work-vm>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
> > 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.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>