public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: terje.rosten@ntnu.no, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Fwd: Re: Problem with Linux aic94xx driver
Date: Fri, 29 Dec 2006 12:18:27 -0800 (PST)	[thread overview]
Message-ID: <203581.7076.qm@web31806.mail.mud.yahoo.com> (raw)

--- Terje Røsten <terje.rosten@ntnu.no> wrote:
> Hi!
> 
> I have a Tyan Transport TA26 barebone, with an addon card that I think 
> has a AIC-94xx chip.
> I am using Fedora Core 6 with a kernel from Fedora rawhide (development):
> 
> $ uname -a
> Linux randi.phys.ntnu.no 2.6.19-1.2891.fc7 #1 SMP Thu Dec 21 10:59:56 
> EST 2006 x86_64 x86_64 x86_64 GNU/Linux
> 
> It's 2.6.20rc1-git5 kernel with some patches.
> 
> When I load the module I get:
> 
> aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.2 loaded
> ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 25 (level, low) -> IRQ 25
> aic94xx: found Adaptec AIC-9410W SAS/SATA Host Adapter, device 0000:03:05.0
> scsi7 : aic94xx
> aic94xx: using sequencer V17/10c6
> aic94xx: device 0000:03:05.0: SAS addr 500e081000011470, PCBA SN , 8 
> phys, 8 enabled phys, flash present, BIOS build 1608
> ERROR: Unidentified device type 5
> ERROR: Unidentified device type 5
> ERROR: Unidentified device type 5
> ERROR: Unidentified device type 5
> 
> (It's 4 Western Digital RE2 WD5000YS with NCQ (500 GB SATA) on the 
> controller,
> set up in RAID BIOS  to one RAID 1+0 logical drive).
> 
> Seems like I end up here:
> 
> drivers/scsi/libsas/sas_discover.c: sas_get_port_device() :
> 
> 256   switch (dev->dev_type) {
> 257         case SAS_END_DEV:
> 258                 rphy = sas_end_device_alloc(port->port);
> 259                 break;
> 260         case EDGE_DEV:
> 261                 rphy = sas_expander_alloc(port->port,
> 262                                           SAS_EDGE_EXPANDER_DEVICE);
> 263                 break;
> 264         case FANOUT_DEV:
> 265                 rphy = sas_expander_alloc(port->port,
> 266                                           SAS_FANOUT_EXPANDER_DEVICE);
> 267                 break;
> 268         case SATA_DEV:
> 269         default:
> 270                 printk("ERROR: Unidentified device type %d\n", 
> dev->dev_type);
> 271                 rphy = NULL;
> 272                 break;
> 273         }
> 
> Any ideas?

Terje,

In my SAS Stack, I _do not_ have that switch statement in that
function.  Apparently you are using "libsas", which is based
on an early, early version of my code, which bottomley and his
gang of SAS experts appropriated to "maintain".  And as your
problem shows has been "fixed" in many ways.

You should complain to them -- I've CC-ed the linux-scsi mailing
list.

BTW, I don't experience this bug with the SAS Stack as I maintain it.

    Luben

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2006-12-29 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 20:18 Luben Tuikov [this message]
2006-12-30 21:23 ` Fwd: Re: Problem with Linux aic94xx driver Darrick J. Wong
2006-12-31  2:40   ` Luben Tuikov
2007-01-02  7:17     ` Darrick J. Wong

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=203581.7076.qm@web31806.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=terje.rosten@ntnu.no \
    /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