All of lore.kernel.org
 help / color / mirror / Atom feed
From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] FC driver?
Date: Mon, 17 Mar 2003 09:38:04 -0700	[thread overview]
Message-ID: <20030317163804.GC31378@dsl2.external.hp.com> (raw)
In-Reply-To: <1047918143.14507.18.camel@beavis.ybsoft.com>

On Mon, Mar 17, 2003 at 09:22:23AM -0700, Ryan Bradetich wrote:
> On parisc?  I've had trouble with it running on my C200.  Maybe
> it is time to try it again.  I know Jes and Martin worked on it 
> for i386..

my bad - you are right. It still doesn' work. Details follow.

I just tried it again with:
20:00.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02)
21:04.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel
Host Adapter (rev 0a)
21:05.0 Fibre Channel: Hewlett-Packard Company Tach TL Fibre Channel
Host Adapter (rev 0a)

20:00.0 Class 0604: 1011:0026 (rev 02)
21:04.0 Class 0c04: 103c:1028 (rev 0a)
21:05.0 Class 0c04: 103c:1028 (rev 0a)

cpqfc driver loads but still finds no devices on the FC hub.

gsyprf11:~# modprobe cpqfc
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 256
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= 20000
  PciDev->baseaddress[2]= 20100
  PciDev->baseaddress[3]= fffffffffa040000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = 20000
    IOBaseU = 20100
 ioremap'd Membase: fffffffffa040000
    SFQconsumerIndex.address = fffffffffa040058
    ERQproducerIndex.address = fffffffffa040008
    TYconfig.address = fffffffffa040184
    FMconfig.address = fffffffffa0401c0
    FMcontrol.address = fffffffffa0401c4
  Requesting 255 I/O addresses @ 20000
  Requesting 255 I/O addresses @ 20100
 ResetTachyon
  HBA Tachyon RevId 2.2
Allocating 129024 for 576 Exchanges @ 00000000355e0000
Allocating 112904 for LinkQ @ 00000000355c0000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 7580000h    PI 7584000h
  cpqfcTS: SEST 000000004be80000(virt): Wrote base 75A0000h @
fffffffffa040140
cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 51044F1044556677
  Waiting for broken Brocade switch...
 scsi_register allocating 6640 bytes for FC HBA
  HBA found!
  HostAdapter->PciDev->irq = 257
  PciDev->baseaddress[0]= 0
  PciDev->baseaddress[1]= 20200
  PciDev->baseaddress[2]= 20300
  PciDev->baseaddress[3]= fffffffffa041000
  cpqfcHBAdata->fcChip.Registers. :
    IOBaseL = 20200
    IOBaseU = 20300
 ioremap'd Membase: fffffffffa041000
    SFQconsumerIndex.address = fffffffffa041058
    ERQproducerIndex.address = fffffffffa041008
    TYconfig.address = fffffffffa041184
    FMconfig.address = fffffffffa0411c0
    FMcontrol.address = fffffffffa0411c4
  Requesting 255 I/O addresses @ 20200
  Requesting 255 I/O addresses @ 20300
 ResetTachyon
  HBA Tachyon RevId 2.2
Allocating 129024 for 576 Exchanges @ 000000004be60000
Allocating 112904 for LinkQ @ 000000004be40000 (576 elements)
Allocating 106504 for TachSEST for 512 Exchanges
  cpqfcTS: writing IMQ BASE 7800000h    PI 7804000h
  cpqfcTS: SEST 000000004be20000(virt): Wrote base 7820000h @
fffffffffa041140
cpqfcTS: NVRAM read failed
 WARNING! HBA NVRAM WWN read failed - make alias
  WWN 510450E844556677
  Waiting for broken Brocade switch...
scsi6 : Agilent FC HBA, Tachyon XL2 HPFC-5200B/2.2: WWN 51044F1044556677
 on PCI bus 33 device 0x1028 irq 256 IObaseL 0x20000, MEMBASE 0xfa040000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: Unknown.  LPSM 0h Monitor
scsi7 : Agilent FC HBA, Tachyon XL2 HPFC-5200B/2.2: WWN 510450E844556677
 on PCI bus 33 device 0x1028 irq 257 IObaseL 0x20200, MEMBASE 0xfa041000
PCI bus width 64 bits, bus speed 66 MHz
FCP-SCSI Driver v2.1.1
GBIC detected: Short-wave.  LPSM 0h Monitor
gsyprf11:~#

The "NVRAM read failed" msg seems to be a problem still.
Fixing that would be a next step. The GBIC detection is the
next problem that would need work. Looks like a timing problem
since the first GBIC was not detected and the second one was.

grant

  parent reply	other threads:[~2003-03-17 16:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 11:05 [parisc-linux] FC driver? Joel Soete
2003-03-17 11:18 ` Jan-Benedict Glaw
2003-03-17 13:58   ` Joel Soete
2003-03-17 15:52     ` Randolph Chung
2003-03-17 16:21       ` Grant Grundler
2003-03-17 16:34         ` Jan-Benedict Glaw
2003-03-18  9:16           ` Jan-Benedict Glaw
2003-03-17 16:14   ` Grant Grundler
2003-03-17 16:22     ` Ryan Bradetich
2003-03-17 16:36       ` Martin K. Petersen
2003-03-17 16:38       ` Grant Grundler [this message]
2003-03-18 15:18         ` Joel Soete
2003-03-21 15:24           ` Joel Soete
2003-03-22 21:58         ` Joel Soete
2003-03-23  6:24           ` Grant Grundler
2003-03-24  7:22             ` Joel Soete

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=20030317163804.GC31378@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=jbglaw@lug-owl.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rbradetich@uswest.net \
    /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 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.