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

Re: [Xen-devel] Failure to load the most recent 2.6.31.5 under Xen Unstable on ASUS P5Q3 Serial Console outputs with different length


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Sun, 1 Nov 2009 22:22:13 -0800 (PST)
  • Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 01 Nov 2009 22:22:49 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=kUDPO4SKb7a/MjHa6arwCNCquQW/re3WMD0mX8xsE5Qv1hwUK0NE3PgZqeEcyr+4l2TQxQzU5474n2jEvtpMpfZEBUGSbFOQGRLtOmy2QO+IRBBy10WobfBIb9nMwlOqVHhGL2o/9D4a73uZVwX7IyfC9aIR9fR3AD8v3b55sh8=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I was unable to find entries like this :-

(XEN) io_apic.c:2251:

(XEN) ioapic_guest_write: apic=0, pin=0, irq=0

(XEN) ioapic_guest_write: new_entry=00010900

(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!

(XEN) io_apic.c:2251:

(XEN) ioapic_guest_write: apic=0, pin=2, irq=0

(XEN) ioapic_guest_write: new_entry=00010900

(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!

(XEN) irq.c:1426: dom0: pirq 0 or irq 3 already mapped

(XEN) io_apic.c:2251:

(XEN) ioapic_guest_write: apic=0, pin=4, irq=4

(XEN) ioapic_guest_write: new_entry=00010900

(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!

in /var/log/dmesg after successful boot 2.6.31.5 under Xen Unstable on ASUS P5Q-E
vs ASUS P5Q3

Boris.

--- On Sat, 10/31/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Failure to load the most recent 2.6.31.5 under Xen Unstable on ASUS P5Q3 Serial Console outputs with different length
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, October 31, 2009, 6:50 AM

The tail of longest one obtained
. . . . .

xen_balloon: Initialising balloon driver.
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing

IO APIC resources couldn't be allocated.

NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
pnp: PnP ACPI init
ACPI: bus type pnp registered
xen_allocate_pirq: returning irq 8 for gsi 8
xen_set_ioapic_routing: irq 8 gsi 8 vector 8 ioapic 0 pin 8 triggering 0 polarity 0
xen_allocate_pirq: returning irq 13 for gsi 13
xen_set_ioapic_routing: irq 13 gsi 13 vector 13 ioapic 0 pin 13 triggering 0 polarity 0
xen_allocate_pirq: returning irq 6 for gsi 6
xen_set_ioapic_routing: irq 6 gsi 6 vector 6 ioapic 0 pin 6 triggering 0 polarity 0
xen_allocate_pirq: returning irq 4 for gsi 4
xen_set_ioapic_routing: irq 4 gsi 4 vector 4 ioapic 0 pin 4 triggering 0 polarity 0
(XEN) io_apic.c:2251:
(XEN) ioapic_guest_write: apic=0, pin=4, irq=4
(XEN) ioapic_guest_write: new_entry=00000904
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
xen_allocate_pirq: returning irq 1 for gsi 1
xen_set_ioapic_routing: irq 1 gsi 1 vector 1 ioapic 0 pin 1 triggering 0 polarity 0
xen_allocate_pirq: returning irq 12 for gsi 12
xen_set_ioapic_routing: irq 12 gsi 12 vector 12 ioapic 0 pin 12 triggering 0 polarity 0
pnp: PnP ACPI: found 18 devices

STOP

--- On Sat, 10/31/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Failure to load the most recent 2.6.31.5 under Xen Unstable on ASUS P5Q3 Serial Console
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, October 31, 2009, 6:34 AM

Serial console hangs output hangs near the point :-

SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing

IO APIC resources couldn't be allocated.

NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
pnp: PnP ACPI init
ACPI: bus type pnp registered
xen_allocate_pirq: returning irq 8 for gsi 8

I have attached the ones seem the longest

Boris


--- On Fri, 10/30/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: [Xen-devel] Failure to load the most recent 2.6.31.5 under Xen Unstable on ASUS P5Q3 (8 GB RAM)
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Friday, October 30, 2009, 6:50 PM

Hardware config:-

CPU C2D 8400
ASUS P5Q3
4x2 GB Kingston KVR1333 (DDR3)
SATA Seagate Barracuda 250 GB
RTL 8111C PC-E Ethernet

Console hangs and drops into stack trace exactly at the same point as on GA-EP45-UDLR3, having same Ethernet Controller.

Same kernel loads fine under Xen 3.4.1 on the box
CPU Q9550
ASUS P5Q-E
8 GB DDR2 Kingston
Marvell Yukon PC-E 8056
SATA Seagate Barracuda 500 GB.

I will provide serial console output shortly.

Boris




-----Inline Attachment Follows-----

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


-----Inline Attachment Follows-----

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


-----Inline Attachment Follows-----

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

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