On 12/9/07 00:33, "Shaun R." <mailinglists@xxxxxxxxxxxxxxxx> wrote:
> Here is the serial output from a kernel patched with 3.0.4. The xen.gz is
> 3.1 and the same exact file/version i used to boot 2.6.18 thats having the
> BUG. Also the 3ware driver in this kernel may be a bit older because i
> build this kernel a while ago...
So it's not a core hypervisor issue, since new Xen works with old kernel and
driver, and it doesn't look like an IRQ routing issue because both working
and non-working drivers on Xen work out the same routing. Question is then
whether it's the new driver or the new kernel causing the problem. Can you
try new driver with old kernel or vice versa? If it's not too hard to back-
or forward-port.
 -- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel