Re: [Xen-ia64-devel] [Patch] fix warnings while rebooting

2006-12-07 Thread Alex Williamson
Applied, thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel

Re: [Xen-ia64-devel] [Patch] fix warnings while rebooting

2006-12-07 Thread Alex Williamson
Hi Akio, Unfortunately I've found a problem with this patch since committing it. My system has a 2 port e1000 card that shows up as PCI devices :01:02.0 and :01:02.1. I hide function 1 from dom0 using pciback.hide=(:01:02.1). Without trying to start up any guest domains, on

Re: [Xen-ia64-devel] [Patch] fix warnings while rebooting

2006-12-07 Thread Akio Takebe
Hi, Alex Unfortunately I've found a problem with this patch since committing it. My system has a 2 port e1000 card that shows up as PCI devices :01:02.0 and :01:02.1. I hide function 1 from dom0 using pciback.hide=(:01:02.1). Without trying to start up any guest domains, on

Re: [Xen-ia64-devel] [Patch] fix warnings while rebooting

2006-12-07 Thread Alex Williamson
On Fri, 2006-12-08 at 10:50 +0900, Akio Takebe wrote: Hi, Alex Unfortunately I've found a problem with this patch since committing it. My system has a 2 port e1000 card that shows up as PCI devices :01:02.0 and :01:02.1. I hide function 1 from dom0 using

Re: [Xen-ia64-devel] [Patch] fix warnings while rebooting

2006-12-04 Thread Aron Griffis
Hi Akio, I'm sorry, but I'm confused by your message. Are you saying there are two problems here? One problem in xen/ia64 and one problem in the e1000 driver? You sent a patch, I guess that is for xen-ia64-unstable, right? If that is ready to be applied, could you include a description of the

Re: [Xen-ia64-devel] [Patch] fix warnings while rebooting

2006-12-04 Thread Akio Takebe
Hi, Aron Hi Akio, I'm sorry, but I'm confused by your message. Are you saying there are two problems here? One problem in xen/ia64 and one problem in the e1000 driver? Yes, there are two problem here. 1. double free message is happened 2. CallTrace is happened problem 1 is a issue of