From: Joshua Rubin <joshua@rubixlinux.org>
To: 380272@bugs.debian.org
Cc: maximilian attems <maks@sternwelten.at>,
Matthew Wilcox <matthew@wil.cx>,
linux-scsi@vger.kernel.org
Subject: Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Date: Fri, 18 Aug 2006 09:59:16 -0600 [thread overview]
Message-ID: <200608180959.16889.joshua@rubixlinux.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
Hi Maks,
I have confirmed that loading cpqarray first fixes the problem on several
systems now. I have also realized that when this is the case, the sym53c8xx
driver is not needed or loaded. I thought this was noteworthy. It appears
that your presumption was correct that the sym53c8xx and cpqarray modules do
not play nicely.
Is this something that can be handled in the initramfs automatically instead
of forcing everyone running these systems to update
their /etc/initramfs-tools/modules file?
Thanks again!!!
Joshua
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-08-18 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 15:59 Joshua Rubin [this message]
2006-08-18 16:39 ` Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays Kyle McMartin
2006-08-18 23:18 ` James Bottomley
2006-08-18 23:28 ` Kyle McMartin
2006-08-19 18:27 ` maximilian attems
-- strict thread matches above, loose matches on Subject: below --
2006-08-18 17:14 Joshua Rubin
2006-08-18 15:05 Joshua Rubin
2006-08-18 16:09 ` maximilian attems
2006-08-18 16:49 ` maximilian attems
2006-08-18 0:12 Joshua Rubin
[not found] <200607281800.59516.joshua@rubixlinux.org>
[not found] ` <200607301140.25691.joshua@rubixlinux.org>
[not found] ` <20060730200559.GO10814@baikonur.stro.at>
[not found] ` <200607301433.02983.joshua@rubixlinux.org>
2006-08-04 18:21 ` maximilian attems
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=200608180959.16889.joshua@rubixlinux.org \
--to=joshua@rubixlinux.org \
--cc=380272@bugs.debian.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maks@sternwelten.at \
--cc=matthew@wil.cx \
/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