Re: [Xen-devel] xen 4.0.1 w/2.6.32.47 hangs at boot

[Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>]

On Wed, Dec 14, 2011 at 07:31:38PM +0100, Quartexx wrote:
> 2011/12/2 Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>:
> > On Fri, Dec 02, 2011 at 08:22:46PM +0100, Quartexx wrote:
> >> ### lspci
> >
> > <sigh> You seem to be missing the most important - that is the serial
> > console output with 'sync_console' enabled.
> 
> [   15.202110] 3ware 9000 Storage Controller device driver for Linux
> v2.26.02.012.
> [   15.226331] xen_allocate_pirq: returning irq 16 for gsi 16
> [   15.244631] Already setup the GSI :16
> [   15.256909] 3w-9xxx 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 
> 16
> [   15.535246] 3w-9xxx: scsi0: AEN: INFO (0x04:0x0053): Battery
> capacity test is overdue:.
> [   15.662242] scsi0 : 3ware 9000 Storage Controller
> [   15.677727] 3w-9xxx: scsi0: Found a 3ware 9000 Storage Controller
> at 0xb3a00000, IRQ: 16.
> [   16.010243] 3w-9xxx: scsi0: Firmware FH9X 4.10.00.021, BIOS BE9X
> 4.08.00.003, Ports: 128.
> [   16.037272] scsi 0:0:0:0: Direct-Access     AMCC     9690SA-4I
> DISK  4.10 PQ: 0 ANSI: 5
> [   16.073169] sd 0:0:0:0: [sda] 2929666048 512-byte logical blocks:
> (1.49 TB/1.36 TiB)

.. snip..
> [   16.077572] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [   16.077953] Intel(R) PRO/1000 Network Driver - version 7.3.21-k5-NAPI
> [   16.077955] Copyright (c) 1999-2006 Intel Corporation.
> [   16.078011] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
> [   16.078012] e1000e: Copyright (c) 1999-2008 Intel Corporation.
> [   16.078055] xen_allocate_pirq: returning irq 16 for gsi 16
> [   16.078058] Already setup the GSI :16
> [   16.078061] e1000e 0000:00:19.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [   16.248299] sd 0:0:0:0: [sda] Write Protect is off
> [   16.264315] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, supports DPO and FUA
> [   16.293627]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >
> [   16.362257] sd 0:0:0:0: [sda] Attached SCSI disk

I would hazzard a guess that it is something with the 3ware driver.
Can you configure Alt-SysRq so that you can see the stack trace of
dom0 and where it hanged? And also do Ctrl-Ax3 and press 'q' to see
where dom0 is stuck? It should print out a bunch of 0xff.. and I can
help you debug what that is in the dom0 kernel so we can figure out
what is happening.

Or you can also try the latest kernel - 3.0.x and see if the problem
appears there as well - which is much easier for us to fix and has
some other important fixes that won't be back-ported to 2.6.32.


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