public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "K.R. Foley" <kr@cybsft.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.12-rc3 won't boot from aic7899
Date: Thu, 28 Apr 2005 15:26:27 -0500	[thread overview]
Message-ID: <427146F3.5060605@cybsft.com> (raw)
In-Reply-To: <1114719624.5022.14.camel@mulgrave>

James Bottomley wrote:
> On Thu, 2005-04-28 at 15:02 -0500, K.R. Foley wrote:
> 
>>I am attaching the relevant part of the successful boot log from 
>>2.6.12-rc2. I don't have a 2.6.11 boot log handy. I can boot it when I 
>>get home if it will help. I don't know if it is worth mentioning or not, 
>>but I have had to compile in the SCSI drivers since 2.6.12-rc1. Don't 
>>know if it's related to this or not.
>>
>>One other note: I spent enough time tracing this to find that the 
>>message "target1:0:0: Beginning Domain Validation" seems to be generated 
>>by code that is in aic79xx_osm. Is this common code or should this code 
>>not be getting executed for aic7899 cards?
> 
> 
> Actually, the code is in the scsi_transport_spi class.  aic79xx still
> has its own internal domain validation.
> 
> 
>>I'll be happy to try this when I get home.
> 
> 
> Thanks ... it may not work; I don't have access to any drives with the
> problem yours exhibits.
> 
> 
>>Apr 24 23:23:30 porky kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>>Apr 24 23:23:30 porky kernel:         <Adaptec aic7899 Ultra160 SCSI adapter>
>>Apr 24 23:23:30 porky kernel:         aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
>>Apr 24 23:23:30 porky kernel: 
>>Apr 24 23:23:30 porky kernel: (scsi1:A:0): 20.000MB/s transfers (20.000MHz, offset 15)
>>Apr 24 23:23:31 porky kernel:   Vendor: SEAGATE   Model: SX118273LC        Rev: 6679
> 
> 
> Yes, that's what I suspected.  Here the internal aic7xxx DV has silently
> configured the drive to be narrow.  Probably because of cable damage or
> something else.
> 
Sorry I missed this before. The reason it is doing this is because this 
drive is connected using an adapter that converts an LC/LV (is this 
correct, off the top of my head) interface into a standard SCSI (narrow) 
interface. Could this be HELPING me here? :)

> James
> 
> 
> 


-- 
    kr

  reply	other threads:[~2005-04-28 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23  3:50 2.6.12-rc3 won't boot from aic7899 K.R. Foley
2005-04-28 19:30 ` James Bottomley
2005-04-28 20:02   ` K.R. Foley
2005-04-28 20:20     ` James Bottomley
2005-04-28 20:26       ` K.R. Foley [this message]
2005-05-01 23:35         ` Mogens Valentin
2005-04-29 10:54       ` K.R. Foley
2005-05-01 20:29         ` James Bottomley

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=427146F3.5060605@cybsft.com \
    --to=kr@cybsft.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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