From: Mike Fedyk <mfedyk@matchmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-aacraid-devel@dell.com,
aacraid@adaptec.com
Subject: Re: Aacraid driver 0.9.9ac
Date: Tue, 4 Dec 2001 01:30:52 -0800 [thread overview]
Message-ID: <20011204013052.G5320@mikef-linux.matchmail.com> (raw)
In-Reply-To: <E16ArGD-0006XU-00@the-village.bc.nu>
In-Reply-To: <E16ArGD-0006XU-00@the-village.bc.nu>
On Mon, Dec 03, 2001 at 11:27:44AM +0000, Alan Cox wrote:
> This should be everything needed. It tidies up all the loose ends. This
> driver is IMHO now ready to go into the mainstream with an experimental tag.
>
> ftp://ftp.linux.org.uk/pub/linux/alan/aacraid-0.99ac1.diff
>
> give it a good hammering.
Dell 2400
00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 05)
00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 05)
00:02.0 PCI bridge: Intel Corp.: Unknown device 0962 (rev 01)
00:02.1 Memory controller: Dell Computer Corporation PowerEdge Expandable
RAID Controller 2/Si (rev 01)
00:08.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 08)
00:0e.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC (rev 7a)
00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 4f)
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04)
01:06.0 SCSI storage controller: Adaptec AIC-7880U (rev 01)
It hung right after printing "Red Hat raid driver"
Interrupts seem to be off. no keyboard response to caps lock or sysrq.
I can supply .config if desired...
mf
next prev parent reply other threads:[~2001-12-04 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 11:27 Aacraid driver 0.9.9ac Alan Cox
2001-12-04 9:30 ` Mike Fedyk [this message]
2001-12-04 9:46 ` Alan Cox
2001-12-04 19:14 ` Mike Fedyk
2001-12-05 4:54 ` Mike Fedyk
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=20011204013052.G5320@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=aacraid@adaptec.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-aacraid-devel@dell.com \
--cc=linux-kernel@vger.kernel.org \
/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