From: Andrew Patterson <andrew.patterson@hp.com>
To: Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org, Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: Q: PCI-X @ 266MHz on HP rx6600 (Qlogic 4Gb FC HBA)
Date: Thu, 26 Jul 2007 16:03:38 -0600 [thread overview]
Message-ID: <1185487419.7134.485.camel@bluto.andrew> (raw)
In-Reply-To: <46A8BF75.161.5C8424A@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
On Thu, 2007-07-26 at 15:36 +0200, Ulrich Windl wrote:
> Hi,
>
> I have a question: The Qlogic ISP2422 chip is said to handle PCI-X 266MHz. So does
> the HP Itanium2 server rx6600. Basically that was the reason to select that
> server. The FC-HBA is in a 266 MHz capable slot. However when booting SLES10 SP1
> for IA64, the logs say:
>
> <6>QLogic Fibre Channel HBA Driver
> <6>GSI 49 (level, low) -> CPU 3 (0x0300) vector 51
> <6>ACPI: PCI Interrupt 0000:0f:01.0[A] -> GSI 49 (level, low) -> IRQ 51
> <6>qla2xxx 0000:0f:01.0: Found an ISP2422, irq 51, iobase 0xc0000000b0040000
> [...]
> <6>qla2xxx 0000:0f:01.0: LOOP UP detected (4 Gbps).
> <6>qla2xxx 0000:0f:01.0: Topology - (F_Port), Host Loop address 0x0
> <6>scsi0 : qla2xxx
> <6>qla2xxx 0000:0f:01.0:
> <4> QLogic Fibre Channel HBA Driver: 8.01.07-k3
> <4> QLogic HP AB378-60001 -
> <4> ISP2422: PCI-X Mode 2 (133 MH4.00.26 [IP] @ 0000:0f:01.0 hdma+, host#=0,
> fw=4.00.26 [IP]
> <5> Vendor: HP Model: HSV200 Rev: 6100
> <5> Type: RAID ANSI SCSI revision: 02
> <5> 0:0:0:0: Attached scsi generic sg0 type 12
>
> Now does Linux support the speed of 266 MHz, and is it just displayed incorrectly,
> or doesn't Linux support the speed of 266MHz yet?
This is a bug in the driver. The lookup table only goes to 133 MHz.
static char *pci_bus_modes[] = {
"33", "66", "100", "133",
The same problem exists in the scsi_misc tree.
> "lspci -v" says:
> 0f:01.0 Fibre Channel: QLogic Corp. ISP2422-based 4Gb Fibre Channel to PCI-X HBA
> (rev 02)
> Subsystem: Hewlett-Packard Company Unknown device 12d6
> Flags: bus master, 66MHz, medium devsel, latency 128, IRQ 51
> I/O ports at 6000 [size=256]
> Memory at b0040000 (64-bit, non-prefetchable) [size=4K]
> Expansion ROM at b0000000 [disabled] [size=256K]
> Capabilities: [44] Power Management version 2
> Capabilities: [4c] PCI-X non-bridge device
> Capabilities: [64] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3
> Enable-
> Capabilities: [74] Vital Product Data
>
lspci only tells you capabilities, not the speed that the card is
running at. I think you have to query the PCI bridge chipset to get
this information. I have run a proprietary tool on this configuration
that does this and confirmed that the card is indeed running at 266 MHz.
> Please CC: any replies to my address as I'm not subscribed to the kernel list.
>
> Regards,
> Ulrich Windl
Andrew
--
Andrew Patterson
Hewlett-Packard Company
next prev parent reply other threads:[~2007-07-26 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 13:36 Ulrich Windl
2007-07-26 22:03 ` Andrew Patterson [this message]
2007-07-27 6:23 ` Andrew Vasquez
2007-07-27 15:46 ` Andrew Patterson
2007-07-27 16:11 ` Andrew Vasquez
2007-07-31 16:50 ` Andrew Vasquez
2007-08-01 6:13 ` Ulrich Windl
2007-07-30 6:40 ` Ulrich Windl
2007-08-01 22:13 ` [PATCH] qla2xxx: allocate enough space for the full PCI descriptor Andrew Vasquez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1185487419.7134.485.camel@bluto.andrew \
--to=andrew.patterson@hp.com \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ulrich.windl@rz.uni-regensburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®