All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Greg Ingram <ingram@symsys.com>
Cc: Grant Grundler <grundler@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] C100 and newest CVS bits
Date: Wed, 24 Jan 2001 19:14:57 +0000	[thread overview]
Message-ID: <20010124191457.H3571@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101241157050.25744-100000@maestro.symsys.com>; from ingram@symsys.com on Wed, Jan 24, 2001 at 12:06:23PM -0600

On Wed, Jan 24, 2001 at 12:06:23PM -0600, Greg Ingram wrote:
> I've appended messages again.  Is the message from sim700 important?  Or
> is it just telling me that I don't have that hardware?  The very last line
> is different too.
> 
> - Greg
> 
> SCSI subsystem driver Revision: 1.00
> sim700: Configuring 53c710 (SCSI-ID 7) at ffd06100, IRQ 86, options 0
> scsi0: Revision 0x2
> Post test1, istat 01, sstat0 00, dstat 84
> sim700: WARNING IRQ probe failed, (returned 0)
> scsi0: Good, target data areas are dma coherent
> scsi0: test 1 completed ok.
> scsi0 : LASI/Simple 53c7xx
>   Vendor: SEAGATE   Model: ST11200N SUN1.05  Rev: 8358
>   Type:   Direct-Access                      ANSI SCSI revision: 02

That lot was from sim700, and is ok.

We are now entering the zalon (ncr53c8xx.c/zalon.c) driver.

> zalon_scsi_callback: Zalon vers field is 0x1, IRQ 34
> ncr53c8xx: 53c720 detected
> ncr53c720-0: ID 7, Fast-10, Parity Checking, Differential
> ncr53c720-0: restart (scsi reset).
> scsi1 : ncr53c8xx - version 3.3b
>   Vendor: SEAGATE   Model: ST32430W          Rev: HP05
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> ncr53c720-0-<6,0>: tagged command queue depth set to 8

Now we are probing the sim700 scsi bus

> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0

Now we are probing the FWD (zalon) scsi bus 

> Detected scsi disk sdb at scsi1, channel 0, id 6, lun 0

Now the system will try to access these disks looking for partition
tables.

> ccio-dma.c:460: Assertion pages_mapped failed!

Your original message (assert size > 0) implies that one of the scsi
drivers has passed down a request to map a zero length buffer.  That
is quite possible - a Test Unit Ready will likely have a zero length
buffer as there is no data phase, and a driver might just try and map
it anyway.  I'll have a look at the drivers shortly.  I cant explain
why it used to work though, unless previous versions of ccio-dma.c
handled zero length requests differently.

Richard

  parent reply	other threads:[~2001-01-24 19:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19 18:28 [parisc-linux] palo, update to README.INSTALL Paul Bame
2001-01-19 20:31 ` Grant Grundler
2001-01-20 12:54   ` marteau
2001-01-24 15:43     ` [parisc-linux] C100 and newest CVS bits Greg Ingram
2001-01-24 17:08       ` Grant Grundler
2001-01-24 18:06         ` Greg Ingram
2001-01-24 18:33           ` Grant Grundler
2001-01-24 18:42             ` Greg Ingram
2001-01-24 19:14           ` Richard Hirst [this message]
2001-01-24 20:22             ` Grant Grundler
2001-01-25  9:44             ` Richard Hirst
2001-01-24 15:46     ` [parisc-linux] [PATCH] typo fix Greg Ingram
2001-01-25  2:03       ` Ryan Bradetich

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=20010124191457.H3571@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=grundler@cup.hp.com \
    --cc=ingram@symsys.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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.