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

Re: [Xen-devel] Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@xxxxxxxxxx: [PATCH 01/35] x86: fix sci on ioapic 1]



Konrad Rzeszutek Wilk wrote:
> FYI.
>
> ----- Forwarded message from Yinghai Lu <yinghai@xxxxxxxxxx> -----
>
> Date: Tue, 09 Feb 2010 11:32:12 -0800
> From: Yinghai Lu <yinghai@xxxxxxxxxx>
> To: Ingo Molnar <mingo@xxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>,
>       "H. Peter Anvin" <hpa@xxxxxxxxx>,
>       Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>,
>       Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> Cc: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>,
>       Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>,
>       linux-kernel@xxxxxxxxxxxxxxx, linux-pci@xxxxxxxxxxxxxxx,
>       Yinghai Lu <yinghai@xxxxxxxxxx>, stable@xxxxxxxxxx
> Subject: [PATCH 01/35] x86: fix sci on ioapic 1
>
> Thomas Renninger <trenn@xxxxxxx> reported on IBM x3330
>
> booting a latest kernel on this machine results in:
>
> PCI: PCI BIOS revision 2.10 entry at 0xfd61c, last bus=1
> PCI: Using configuration type 1 for base access bio: create slab <bio-0> at 0
> ACPI: SCI (IRQ30) allocation failed
> ACPI Exception: AE_NOT_ACQUIRED, Unable to install System Control Interrupt 
> handler (20090903/evevent-161)
> ACPI: Unable to start the ACPI Interpreter
>
> Later all kind of devices fail...
>
> and bisect it down to this commit:
> commit b9c61b70075c87a8612624736faf4a2de5b1ed30
>
>     x86/pci: update pirq_enable_irq() to setup io apic routing
>
> it turns out we need to set irq routing for the sci on ioapic1 early.
>   

Yes, this did the trick. Introduced the code changes manually in the
kernel tree, and now, networking is available (see also output of
/proc/interrupts).

xen ~ # cat /proc/interrupts
           CPU0       CPU1
  1:          8          0  xen-pirq-ioapic-edge  i8042
  4:          1          0  xen-pirq-ioapic-edge
  6:          3          0  xen-pirq-ioapic-edge  floppy
  8:          2          0  xen-pirq-ioapic-edge  rtc0
 12:        110          0  xen-pirq-ioapic-edge  i8042
 14:      14559          0  xen-pirq-ioapic-edge  ide0
 15:         56          0  xen-pirq-ioapic-edge  ide1
 19:      17492          0  xen-pirq-ioapic-level  uhci_hcd:usb1, peth0
 20:          0          0   IO-APIC-fasteoi   acpi
408:          0          0   xen-dyn-event     evtchn:xenstored
409:         45          0   xen-dyn-event     evtchn:xenstored
410:          0          0   xen-dyn-virq      hvc_console
411:         74          0   xen-dyn-event     xenbus
412:          0        346   xen-dyn-ipi       callfuncsingle1
413:          0          0   xen-dyn-virq      debug1
414:          0          0   xen-dyn-ipi       callfunc1
415:          0      12160   xen-dyn-ipi       resched1
416:          0       2517   xen-dyn-ipi       spinlock1
417:          0     112999   xen-dyn-virq      timer1
418:        437          0   xen-dyn-ipi       callfuncsingle0
419:          0          0   xen-dyn-virq      debug0
420:          0          0   xen-dyn-ipi       callfunc0
421:       4950          0   xen-dyn-ipi       resched0
422:       1983          0   xen-dyn-ipi       spinlock0
423:     112722          0   xen-dyn-virq      timer0
NMI:          0          0   Non-maskable interrupts
LOC:          0          0   Local timer interrupts
SPU:          0          0   Spurious interrupts
CNT:          0          0   Performance counter interrupts
PND:          0          0   Performance pending work
RES:       4950      12160   Rescheduling interrupts
CAL:        437        346   Function call interrupts
TLB:          0          0   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:          1          1   Machine check polls
ERR:          0
MIS:          0


Question: Is it known when this piece of code will be introduced in the
"pv_ops Kernel tree"?

_______________________________________________
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®.