Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] sim700 Driver and 715/50's
Date: Tue, 29 Jan 2002 17:27:56 -0500	[thread overview]
Message-ID: <20020129172756.J1945@systemhalted> (raw)

parisc'ers,

I was recently playing with the SCSI drivers for the
LASI and without much sucess on some fronts.

After staring at some source for a few minutes, I changed
CONFIG_SCSI_LASI700 to CONFIG_SCSI_LASI to get the
older sim700 driver to compile for the latest kernel.

This is really only phase 1 of 2 steps:

1. Test new kernel with old driver
2. Test new kernel with new driver (but with tag queue tweaks)

The reason was to determine:

a. Random hangs on 715/50's (attributed to scsi driver)
	= Diskless nodes just keep on trucking.
b. Why certain scsi drives failed to work with new 53c700
   driver, but work with the old sim700.

--- Kernel with CONFIG_SCSI_LASI gives ---

sim700: Configuring 53c700 (SCSI-ID 7) at f0825100, IRQ 86, options 1
scsi0: Revision 0x0
scsi0: test 1 FAILED: dsps: exp 0xab93001d, got 0x00000002
scsi0: Chip register contents:
 (script[0] at virt 10070000, bus 70000)
 00  sien:  af  sdid:  00  scntl1:20  scntl0:c4
 04  socl:  02  sodl:  00  sxfer: 00  scid:  80
 08  sbcl:  00  sbdl:  00  sidl:  00  sfbr:  00
 0C  sstat2:00  sstat1:00  sstat0:00  dstat: 80
 10
 14  ctest3:ae  ctest2:31  ctest1:f0  ctest0:00
 18  ctest7:00  ctest6:da  ctest5:00  ctest4:00
 1C  temp:  00000000
 20              ctest8:ff  istat: 04  dfifo: 00
 24  dbc:   00000002  dnad:  00000002  dsp:   080774ac
 30  dsps:  00000002
 34  dmode: 80
 38  dcntl: 80  dwt:   00  dien:  1d
 3C
scsi0: could not halt NCR chip, stage 2
Warning : device (10, 0xb, 0x0, 0x71) NOT claimed by Lasi SCSI

Tested on another machines also gives:

sim700: Configuring 53c700 (SCSI-ID 7) at f0825100, IRQ 86, options 1
scsi0: Revision 0x0
scsi0: test 1 FAILED: dsps: exp 0xab93001d, got 0x00000002
scsi0: Chip register contents:
 (script[0] at virt 10070000, bus 70000)
 00  sien:  af  sdid:  00  scntl1:20  scntl0:c4
 04  socl:  02  sodl:  00  sxfer: 00  scid:  80
 08  sbcl:  00  sbdl:  00  sidl:  00  sfbr:  00
 0C  sstat2:00  sstat1:00  sstat0:00  dstat: 80
 10
 14  ctest3:00  ctest2:21  ctest1:f0  ctest0:00
 18  ctest7:00  ctest6:00  ctest5:00  ctest4:00
 1C  temp:  00000000
 20              ctest8:ff  istat: 04  dfifo: 00
 24  dbc:   00000002  dnad:  00000002  dsp:   080774ac
 30  dsps:  00000002
 34  dmode: 80
 38  dcntl: 80  dwt:   00  dien:  1d
 3C
scsi0: could not halt NCR chip, stage 2
Warning : device (10, 0x7, 0x0, 0x71) NOT claimed by Lasi SCSI

I'm not really sure what is going on here?

Does this mean:

- sim700 driver is not quite working proplerly with new kernel

I'm going to move into my second phase of testing, and
see if the new driver can hack it :)

Any suggestions would be appreciated.

c.

             reply	other threads:[~2002-01-29 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 22:27 Carlos O'Donell Jr. [this message]
2002-01-29 23:35 ` [parisc-linux] sim700 Driver and 715/50's Richard Hirst

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=20020129172756.J1945@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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