All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Michael <mozstuff@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: DAC960 + sym53c8xx conflict
Date: Mon, 16 Aug 2004 12:20:34 +0100	[thread overview]
Message-ID: <20040816112034.GC28995@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1092628387.2548.14.camel@fs2>

On Sun, Aug 15, 2004 at 10:53:07PM -0500, Michael wrote:
> I've got a 4-processor Intel SC450NX-based system with motherboard
> Sym53c896 dual controller driven a Mylex Acceleraid 200. The motherboard
> also has a sym53c810a which drives a Sony SDT-9000 tape drive. This
> combo has always worked well until I tried updating to a 2.6 kernel.
> 
> When I load 2.6 (tried 2.6. - 2.6.8-rc4 (mm tree too)) every works OK
> until I load the sym53c8xx module. When that module is loaded all access
> to the drives connected to the DAC960 vanishes. I get no errors and the
> system is not locked up. Any attempt to access the disks on the DAC960
> simply hangs.
> 
> Any ideas? I hacked teh sym driver to remove all support for the 896
> chip, but it didn't.

On 2.4, did you get the message:

        printf_info("%s: not initializing, driven by RAID controller.\n",
                                            sym_name(device));

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-08-16 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  3:53 DAC960 + sym53c8xx conflict Michael
2004-08-16 11:20 ` Matthew Wilcox [this message]
     [not found]   ` <1092699047.6936.11.camel@fs2>
2004-08-17  0:09     ` Matthew Wilcox

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=20040816112034.GC28995@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mozstuff@yahoo.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.