From: Matthew Wilcox <willy@debian.org>
To: Michael <mozstuff@yahoo.com>
Cc: Matthew Wilcox <willy@debian.org>, linux-scsi@vger.kernel.org
Subject: Re: DAC960 + sym53c8xx conflict
Date: Tue, 17 Aug 2004 01:09:51 +0100 [thread overview]
Message-ID: <20040817000951.GI28995@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1092699047.6936.11.camel@fs2>
On Mon, Aug 16, 2004 at 06:30:47PM -0500, Michael wrote:
> On 2.6 I get the message you list as well. I thought maybe 2.6 wasn't
> actually recognizing the raid controller, so I disabled support for the
> 896 chip in the driver so it gives an "unsupported" message, but I still
> lose the dac960 drives.
Crap, I see the problem. When we fail initialisation, we disable the
device, so DAC960 stops working. Either we need to not disable the device
when exiting or we need to claim the sym2 device in the dac960 driver
so the sym2 driver never gets called.
I'm going to be away till the end of the week, but for the moment, deleting
pci_release_regions(pdev);
and
pci_disable_device(pdev);
from sym2_probe() in drivers/scsi/sym53c8xx_2/sym_glue.c should fix
your problem.
--
"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
prev parent reply other threads:[~2004-08-17 0:09 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
[not found] ` <1092699047.6936.11.camel@fs2>
2004-08-17 0:09 ` Matthew Wilcox [this message]
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=20040817000951.GI28995@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox