[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: Recurring OOPS in latest -unstable kernel


  • To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Sun, 3 Jul 2005 13:28:45 -0700
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
  • Delivery-date: Sun, 03 Jul 2005 20:27:35 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OdOHahhyTo0mkJW1QXnMdROwPNTdR1RHRk1RD29HCwTQZuouHtPVPiTAgn9Me3+/S5mzFcPAf+AIwGzL5YiMS7bex1O5AK2UY2O+N8iseohp6BrAaBOOU981+m+1LFFDknXYq8YId5peTLUh23GLy1vxehaptAOxZOfOTqfSHoY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Just to clarify  - this is straight out of the -unstable tree from
yesterday with no CONFIG_REGPARM. Nonetheless, a few things are
different:
CONFIG_MK8=y
CONFIG_SMP=y
# CONFIG_PREEMPT is not set

              -Kip
> 
> The same code (in netback) works in 2.6.9rc2/2.6.11.x, so something
> screws up the ringbuffers -- should we start reviewing the path down
> from hypervisor_callback?
> 
> Something strange seems to happen there with ringbuffer assignment to
> interfaces and I guess we need to review the upcall path.
> Somewhere, we may clobber an argument, possibly involving CONFIG_REGPARM
> ...
> I don't know the code well enough see it without adding a lot of
> instrumentation to the code.
> 
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.