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: Thu, 17 Aug 2006 18:12:24 -0600 [thread overview]
Message-ID: <200608171812.28727.joshua@rubixlinux.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
Hi Max,
I just realized that I never tried your last suggestions. I will try them
first thing when I get in to work tomorrow.
I have received some more info about this bug. It appears to be a timing
issue. Here is the link to the bug at kernel.org with an interesting
suggestion (that I have not tried):
http://bugzilla.kernel.org/show_bug.cgi?id=6921.
My company has inherited 5 racks of these compaq servers and it is very
important that debian etch work well on them :)
Thanks for all the help,
Joshua Rubin
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-08-18 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 0:12 Joshua Rubin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-18 17:14 Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays Joshua Rubin
2006-08-18 15:59 Joshua Rubin
2006-08-18 16:39 ` Kyle McMartin
2006-08-18 23:18 ` James Bottomley
2006-08-18 23:28 ` Kyle McMartin
2006-08-19 18:27 ` maximilian attems
2006-08-18 15:05 Joshua Rubin
2006-08-18 16:09 ` maximilian attems
2006-08-18 16:49 ` maximilian attems
[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=200608171812.28727.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 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.