All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: Re: [Xen-users] xen 3.0 boot problem
@ 2005-10-10 22:10 Ian Pratt
  2005-10-10 22:15 ` Andrew Theurer
  0 siblings, 1 reply; 4+ messages in thread
From: Ian Pratt @ 2005-10-10 22:10 UTC (permalink / raw)
  To: Stephan Böni, The Smoking Man; +Cc: xen-devel, xen-users

 
> Well, i'm using here the qla2340 on several boxes. It works 
> with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0:

Interesting. If the driver really doews work flawlessly in Xen 2, then I think the culprit has to be interrupt routeing.

Under Xen 3, does /proc/interrupts show you're receiving interrupts?

Do other devices with high irq numbers appear to be working OK?

Ian

  
> kernel-xen-2.6.13-15
> kernel-xen-nongpl-2.6.13-15
> xen-3.0_6715-2
>  
> System startup with xen kernel fails on detecting the boot 
> device, which is attached to the qla2300 fibre channel host 
> bus adapter.
> 
> qla2300 0000:05:01.0: Found an ISP2312, irq 185, iobase 
> 0xf8812000 qla2300 0000:05:01.0: Configuring PCI space...
> qla2300 0000:05:01.0: Configure NVRAM parameters...
> qla2300 0000:05:01.0: Verifying loaded RISC code...
> qla2300 0000:05:01.0: Waiting for LIP to complete...
> 
> Until here it's alle fine, but then:
> 
> qla2300 0000:05:01.0: LIP reset occured (f7f7).
> qla2300 0000:05:01.0: LOOP UP detected (2 Gbps).
> qla2300 0000:05:01.0: Topology - (F_Port), Host Loop address 0xffff
> scsi3 : qla2xxx
> qla2300 0000:04:02.0:
> QLogic Fibre Channel HBA Driver: 8.01.00b5-k
>   QLogic QLA2340 - 133MHz PCI-X to 2Gb FC, Single Channel
>   ISP2312: PCI-X (100 MHz) @ 0000:05:01.0 hdma+, host#=3, 
> fw=3.03.15 IPX Loading kernel/fs/reiserfs/reiserfs.ko Waiting 
> for device /dev/sda4 to appear: .....not found --- exiting to 
> /bin/sh $
> 
> With the 2.6.13-15-smp kernel as part of SUSE Linux 10 it 
> goes on without any problem:
> 
> SCSI device sda: 41943040 512-byte hdwr sectors (21475 MB) 
> SCSI device sda: drive cache: write back SCSI device sda: 
> 41943040 512-byte hdwr sectors (21475 MB) SCSI device sda: 
> drive cache: write back
> sda: sda1 sda2 sda3 sda4
> ....etc.
> 
> Stephan
>  
> 
> 	-----Ursprüngliche Nachricht-----
> 	Von: The Smoking Man [mailto:datashark@gmail.com]
> 	Gesendet: Freitag, 7. Oktober 2005 19:13
> 	An: Ian Pratt
> 	Cc: xen-devel@lists.xensource.com; Stephan Böni; 
> xen-users@lists.xensource.com
> 	Betreff: [Xen-devel] Re: [Xen-users] xen 3.0 boot problem
> 	
> 	
> 	Beein used here the qla2344 on several boxes. works  
> trully fine  on  gentoo-xensources (vanilla kernel plus xen 
> patches) and (this is what i'm using in production) with suse 
> kotd sources. 
> 	
> 	Bellow is the relevant bootlog... 
> 	
> 	Best regards,
> 	
> 	[    6.599201] QLogic Fibre Channel HBA Driver
> 	[    6.599446] ACPI: PCI Interrupt 0000:02:04.0[A] -> 
> GSI 29 (level, low) -> IRQ 29
> 	[    6.599749] qla2300 0000:02:04.0: Found an ISP2312, 
> irq 29, iobase 0xe8804000
> 	[    6.600392] qla2300 0000:02:04.0: Configuring PCI space...
> 	[    6.600687] qla2300 0000:02:04.0: Configure NVRAM 
> parameters...
> 	[    6.685681] qla2300 0000:02:04.0: Verifying loaded 
> RISC code...
> 	[    6.809175] qla2300 0000:02:04.0: Waiting for LIP to 
> complete...
> 	[   27.200114] qla2300 0000:02:04.0: Cable is unplugged...
> 	[   27.200289] scsi0 : qla2xxx
> 	[   27.200579] qla2300 0000:02:04.0:
> 	[   27.200580]  QLogic Fibre Channel HBA Driver: 8.00.02b5-k
> 	[   27.200581]   QLogic QLA2344 -
> 	[   27.200582]   ISP2312: PCI-X (133 MHz) @ 
> 0000:02:04.0 hdma+, host#=0, fw=3.03.08 IPX
> 	[   27.201211] ACPI: PCI Interrupt 0000:02:04.1[B] -> 
> GSI 30 (level, low) -> IRQ 30
> 	[   27.201482] qla2300 0000:02:04.1: Found an ISP2312, 
> irq 30, iobase 0xe8806000
> 	[   27.202082] qla2300 0000:02:04.1: Configuring PCI space...
> 	[   27.202369] qla2300 0000:02:04.1: Configure NVRAM 
> parameters...
> 	[   27.287483] qla2300 0000:02:04.1: Verifying loaded 
> RISC code...
> 	[   27.410625] qla2300 0000:02:04.1: Waiting for LIP to 
> complete...
> 	[   47.810115] qla2300 0000:02:04.1: Cable is unplugged...
> 	[   47.810279] scsi1 : qla2xxx
> 	[   47.810504] qla2300 0000:02:04.1:
> 	[   47.810505]  QLogic Fibre Channel HBA Driver: 8.00.02b5-k
> 	[   47.810507]   QLogic QLA2344 -
> 	[   47.810508]   ISP2312: PCI-X (133 MHz) @ 
> 0000:02:04.1 hdma+, host#=1, fw=3.03.08 IPX
> 	[   47.811136] ACPI: PCI Interrupt 0000:02:06.0[A] -> 
> GSI 31 (level, low) -> IRQ 31
> 	[   47.811404] qla2300 0000:02:06.0: Found an ISP2312, 
> irq 31, iobase 0xe881a000
> 	[   47.812006] qla2300 0000:02:06.0: Configuring PCI space...
> 	[   47.812295] qla2300 0000:02:06.0: Configure NVRAM 
> parameters...
> 	[   47.897025] qla2300 0000:02:06.0: Verifying loaded 
> RISC code...
> 	[   48.020170] qla2300 0000:02:06.0: Waiting for LIP to 
> complete...
> 	[   68.410104] qla2300 0000:02:06.0: Cable is unplugged...
> 	[   68.410270] scsi2 : qla2xxx
> 	[   68.410514] qla2300 0000:02:06.0:
> 	[   68.410515]  QLogic Fibre Channel HBA Driver: 8.00.02b5-k
> 	[   68.410517]   QLogic QLA2344 -
> 	[   68.410518]   ISP2312: PCI-X (133 MHz) @ 
> 0000:02:06.0 hdma+, host#=2, fw=3.03.08 IPX
> 	[   68.411144] ACPI: PCI Interrupt 0000:02:06.1[B] -> 
> GSI 28 (level, low) -> IRQ 28
> 	[   68.411413] qla2300 0000:02:06.1: Found an ISP2312, 
> irq 28, iobase 0xe881c000
> 	[   68.412024] qla2300 0000:02:06.1: Configuring PCI space...
> 	[   68.412311] qla2300 0000:02:06.1: Configure NVRAM 
> parameters...
> 	[   68.497424] qla2300 0000:02:06.1: Verifying loaded 
> RISC code...
> 	[   68.516876] qla2300 0000:02:06.1: Waiting for LIP to 
> complete...
> 	[   69.020063] qla2300 0000:02:06.1: LIP reset occured (f8f7).
> 	[   69.020220] qla2300 0000:02:06.1: LIP occured (f8f7).
> 	[   69.020370] qla2300 0000:02:06.1: LOOP UP detected (2 Gbps).
> 	[   69.020661] qla2300 0000:02:06.1: Topology - (Loop), 
> Host Loop address 0x0
> 	[   69.021595] scsi3 : qla2xxx
> 	[   69.021824] qla2300 0000:02:06.1:
> 	[   69.021825]  QLogic Fibre Channel HBA Driver: 8.00.02b5-k
> 	[   69.021826]   QLogic QLA2344 -
> 	[   69.021827]   ISP2312: PCI-X (133 MHz) @ 
> 0000:02:06.1 hdma+, host#=3, fw=3.03.08 IPX
> 	[   69.025082] mice: PS/2 mouse device common for all mice
> 	[   69.025227] md: md driver 0.90.1 MAX_MD_DEVS=256, 
> MD_SB_DISKS=27
> 	[   69.025434] NET: Registered protocol family 2
> 	[   69.025850]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.026240]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.027076] SCSI device sda: 131072 512-byte hdwr 
> sectors (67 MB)
> 	[   69.027919] SCSI device sda: drive cache: write through
> 	[   69.028521] SCSI device sda: 131072 512-byte hdwr 
> sectors (67 MB)
> 	[   69.029354] SCSI device sda: drive cache: write through
> 	[   69.029495]  sda: sda1
> 	[   69.030035] Attached scsi disk sda at scsi3, channel 
> 0, id 0, lun 0
> 	[   69.031081]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.031466]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.032195] SCSI device sdb: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.032943] SCSI device sdb: drive cache: write through
> 	[   69.033469] SCSI device sdb: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.034213] SCSI device sdb: drive cache: write through
> 	[   69.034353]  sdb: sdb1
> 	[   69.048548] Attached scsi disk sdb at scsi3, channel 
> 0, id 0, lun 1
> 	[   69.049188]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.049573]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.050305] SCSI device sdc: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.051056] SCSI device sdc: drive cache: write through
> 	[   69.051586] SCSI device sdc: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.052341] SCSI device sdc: drive cache: write through
> 	[   69.052481]  sdc: sdc1
> 	[   69.065097] Attached scsi disk sdc at scsi3, channel 
> 0, id 0, lun 2
> 	[   69.065589]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.065973]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.066583] SCSI device sdd: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.067279] SCSI device sdd: drive cache: write through
> 	[   69.067695] SCSI device sdd: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.068303] SCSI device sdd: drive cache: write through
> 	[   69.068442]  sdd: sdd1
> 	[   69.078452] Attached scsi disk sdd at scsi3, channel 
> 0, id 0, lun 3
> 	[   69.078969]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.079355]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.080403] SCSI device sde: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.081042] SCSI device sde: drive cache: write through
> 	[   69.081458] SCSI device sde: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.082098] SCSI device sde: drive cache: write through
> 	[   69.082237]  sde: sde1
> 	[   69.093087] Attached scsi disk sde at scsi3, channel 
> 0, id 0, lun 4
> 	[   69.093592]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.093976]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.094591] SCSI device sdf: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.095206] SCSI device sdf: drive cache: write through
> 	[   69.095615] SCSI device sdf: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.096234] SCSI device sdf: drive cache: write through
> 	[   69.096373]  sdf: sdf1
> 	[   69.108174] Attached scsi disk sdf at scsi3, channel 
> 0, id 0, lun 5
> 	[   69.108790]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.109175]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.110034] SCSI device sdg: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.110638] SCSI device sdg: drive cache: write through
> 	[   69.111046] SCSI device sdg: 12582912 512-byte hdwr 
> sectors (6442 MB)
> 	[   69.111645] SCSI device sdg: drive cache: write through
> 	[   69.111784]  sdg: sdg1
> 	[   69.122286] Attached scsi disk sdg at scsi3, channel 
> 0, id 0, lun 6
> 	[   69.122777]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.123163]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.123772] SCSI device sdh: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.124377] SCSI device sdh: drive cache: write through
> 	[   69.124789] SCSI device sdh: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.125393] SCSI device sdh: drive cache: write through
> 	[   69.125532]  sdh: sdh1
> 	[   69.134481] Attached scsi disk sdh at scsi3, channel 
> 0, id 0, lun 7
> 	[   69.134971]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.135355]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.135974] SCSI device sdi: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.136577] SCSI device sdi: drive cache: write through
> 	[   69.136994] SCSI device sdi: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.137597] SCSI device sdi: drive cache: write through
> 	[   69.137736]  sdi: sdi1
> 	[   69.142544] Attached scsi disk sdi at scsi3, channel 
> 0, id 0, lun 8
> 	[   69.143037]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.143421]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.144036] SCSI device sdj: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.144635] SCSI device sdj: drive cache: write through
> 	[   69.145044] SCSI device sdj: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.145640] SCSI device sdj: drive cache: write through
> 	[   69.145780]  sdj:<6>IP: routing cache hash table of 
> 8192 buckets, 64Kbytes
> 	[   69.150433] TCP established hash table entries: 
> 131072 (order: 8, 1048576 bytes)
> 	[   69.151333] TCP bind hash table entries: 65536 
> (order: 7, 524288 bytes)
> 	[   69.151870] TCP: Hash tables configured (established 
> 131072 bind 65536)
> 	[   69.152110] NET: Registered protocol family 1
> 	[   69.153802]  unknown partition table
> 	[   69.153959] Attached scsi disk sdj at scsi3, channel 
> 0, id 0, lun 9
> 	[   69.154482]   Vendor: DotHill   Model: SANnet II FC  
>     Rev: 327R
> 	[   69.154867]   Type:   Direct-Access                  
>     ANSI SCSI revision: 03
> 	[   69.155484] SCSI device sdk: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.156083] SCSI device sdk: drive cache: write through
> 	[   69.156502] SCSI device sdk: 2097152 512-byte hdwr 
> sectors (1074 MB)
> 	[   69.157095] SCSI device sdk: drive cache: write through
> 	[   69.157234]  sdk: unknown partition table
> 	[   69.168099] Attached scsi disk sdk at scsi3, channel 
> 0, id 0, lun 10
> 	
> 	
> 	
> 	
> 	
> 	On 10/5/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote: 
> 
> 
> 		Has anyone used xen succefully with a qla2300?
> 		
> 		What machines have this card?
> 		
> 		Ian
> 		
> 		> I've installed Xen 3.0-devel on SUSE Linux 
> without any problems.
> 		> But when i tryed to boot the system, i've got 
> a funny problem: 
> 		>
> 		> qla2300 0000:05:01.0: Found an ISP2312, irq 
> 185, iobase
> 		> 0xf8812000 qla2300 0000:05:01.0: Configuring 
> PCI space...
> 		> qla2300 0000:05:01.0: Configure NVRAM parameters...
> 		> qla2300 0000:05: 01.0: Verifying loaded RISC code...
> 		> qla2300 0000:05:01.0: Waiting for LIP to complete...
> 		>
> 		> until here all works fine, but then:
> 		>
> 		> input: PS/2 Generic Mouse on 
> synaptcs-pt/serio0 qla2300 
> 		> 0000:05:01.0: LIP reset occured (f7f7).
> 		> qla2300 0000:05:01.0: LOOP UP detected (2 Gbps).
> 		> qla2300 0000:05:01.0: Topology - (F_Port), 
> Host Loop address 0xffff
> 		> scsi3 : qla2xxx
> 		> qla2300 0000:04: 02.0:
> 		>   QLogic Fibre Channel HBA Driver: 8.01.00b5-k
> 		>   QLogic QLA2340 - 133MHz PCI-X to 2Gb FC, 
> Single Channel
> 		>   ISP2312: PCI-X (100 MHz) @ 0000:05:01.0 
> hdma+, host#=3,
> 		> fw=3.03.15 IPX
> 		> Loading kernel/fs/reiserfs/reiserfs.ko 
> 		> Waiting for device /dev/sda4 to appear: 
> .....not found ---
> 		> exiting to /bin/sh $
> 		>
> 		> if i use the standard (bigsmp) kernel the 
> normal massages are:
> 		>
> 		> SCSI device sda: 41943040 512-byte hdwr 
> sectors (21475 MB) 
> 		> SCSI device sda: drive cache: write back SCSI 
> device sda:
> 		> 41943040 512-byte hdwr sectors (21475 MB) 
> SCSI device sda:
> 		> drive cache: write back
> 		>  sda: sda1 sda2 sda3 sda4
> 		> ....usw.
> 		> 
> 		> Well, my qla2300 has the storage attached not 
> a generic mouse.
> 		> Of course it isn't possible to boot from this 
> mouse. :-(
> 		
> 		
> 		
> 		_______________________________________________
> 		Xen-users mailing list 
> 		Xen-users@lists.xensource.com
> 		http://lists.xensource.com/xen-users
> 		
> 
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread
* RE: Re: [Xen-users] xen 3.0 boot problem
@ 2005-10-11 10:39 Ian Pratt
  0 siblings, 0 replies; 4+ messages in thread
From: Ian Pratt @ 2005-10-11 10:39 UTC (permalink / raw)
  To: Stephan Böni; +Cc: xen-devel, xen-users

> > > Well, i'm using here the qla2340 on several boxes. It 
> works with Xen 
> > > 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0:
> > 
> > Interesting. If the driver really doews work flawlessly in 
> Xen 2, then 
> > I think the culprit has to be interrupt routeing.
> > 
> > Under Xen 3, does /proc/interrupts show you're receiving interrupts?
> 
> I cannot boot with Xen 3, because my boot device is attached 
> on the qla controller. Grub, xen.gz, initrd are starting 
> exactly from this device without any prolem until the qla 
> driver should be loaded. :-(

OK, there's a prototype CD that might be useful for debugging this:
http://tx.downloads.xensource.com/downloads/xentest.iso

Select the 32 bit xen kernel from the CD boot menu, then change virtual terminal to get to a shell and have a poke around.


Ian

^ permalink raw reply	[flat|nested] 4+ messages in thread
* RE: Re: [Xen-users] xen 3.0 boot problem
@ 2005-10-13 10:04 Ian Pratt
  0 siblings, 0 replies; 4+ messages in thread
From: Ian Pratt @ 2005-10-13 10:04 UTC (permalink / raw)
  To: Stephan Böni, githogori; +Cc: xen-devel

 
> > 	Attached is my config file for Xen 3.0 and QLogic as a module.
> 
> It does not work. The boot process hangs on mpt scsi 
> recovery, even before any qla adapter is configured.

Does your system actually need the mpt driver? Can you just compile it out or remove the module?

I note that you boot with acpi=off (for both xen and native). What goes wrong if you have it on?  Have you checked you have the latest BIOS for your system?

Ian

^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-10-13 10:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-10 22:10 Re: [Xen-users] xen 3.0 boot problem Ian Pratt
2005-10-10 22:15 ` Andrew Theurer
  -- strict thread matches above, loose matches on Subject: below --
2005-10-11 10:39 Ian Pratt
2005-10-13 10:04 Ian Pratt

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.