linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Fenzi <kevin@tummy.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux aacraid devel <linux-aacraid-devel@dell.com>
Subject: Re: aacraid and large memory problem (2.6.0-test11)
Date: Thu, 11 Dec 2003 10:53:39 -0700	[thread overview]
Message-ID: <20031211175342.1D94DF7C86@voldemort.scrye.com> (raw)
In-Reply-To: <1070493945.25617.9.camel@markh1.pdx.osdl.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Mark" == Mark Haverkamp <markh@osdl.org> writes:

Mark> On Wed, 2003-12-03 at 14:28, Kevin Fenzi wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> >>>>> "Mark" == Mark Haverkamp <markh@osdl.org> writes:
>> 
Mark> I set up my machine to boot on the aacraid disk and it booted OK
Mark> for me.  Maybe its a problem with a particular model?
>>
Mark> lspci on mine says:
>>
Mark> 02:04.0 RAID bus controller: Digital Equipment Corporation
Mark> DECchip 21554 (rev 01) Subsystem: Adaptec Adaptec 5400S
>> This one says:
>> 
>> 05:01.0 RAID bus controller: Adaptec AAC-RAID (rev 01) Subsystem:
>> Adaptec AAC-RAID Flags: bus master, fast Back2Back, 66Mhz, slow
>> devsel, latency 64, IRQ 96 Memory at f8000000 (32-bit,
>> prefetchable) [size=64M] Expansion ROM at <unassigned> [disabled]
>> [size=64K] Capabilities: [80] Power Management version 2
>> 
>> It's a 2200S controller. bios version 6008
>> 
Mark> Could you try this patch?  I took the code from the adaptec
Mark> version of the driver.  It fiddles with the dma mask on the
Mark> 2200S controller among others.

Sorry it took me so long to try it. ;) 

Just applied to a 2.6.0-test11 kernel and rebooted and it worked!
Boot came up fine and it sees all 8GB of memory. 

free
             total       used       free     shared    buffers     cached
Mem:       8290996     712380    7578616          0      20956     569352
- -/+ buffers/cache:     122072    8168924
Swap:      8385920          0    8385920

Red Hat/Adaptec aacraid driver (1.1.2 Dec 10 2003)
AAC0: kernel 4.0.4 build 6008
AAC0: monitor 4.0.4 build 6008
AAC0: bios 4.0.0 build 6008
AAC0: serial b7e06ffafaf001
AAC0: 64 Bit PAE enabled
scsi0 : aacraid

This looks like a good patch here. 

Mark> Mark.

kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQE/2K8l3imCezTjY0ERAr0aAJkBLLGSLT5f4XygLR7uTwvQ6bQWSwCeIpUQ
GNFgepA9aOlk0MMUGDNHGmY=
=wOp5
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-12-11 17:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 19:35 aacraid and large memory problem (2.6.0-test11) Kevin Fenzi
2003-12-02 20:21 ` Mark Haverkamp
2003-12-03 16:16   ` bill davidsen
2003-12-03 20:51   ` Kevin Fenzi
2003-12-03 21:57     ` Mark Haverkamp
2003-12-03 22:28       ` Kevin Fenzi
2003-12-03 22:53         ` bill davidsen
2003-12-03 23:25         ` Mark Haverkamp
2003-12-11 17:53           ` Kevin Fenzi [this message]
2003-12-03 20:57 Kevin Fenzi
2003-12-03 21:26 ` bill davidsen

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=20031211175342.1D94DF7C86@voldemort.scrye.com \
    --to=kevin@tummy.com \
    --cc=linux-aacraid-devel@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@osdl.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;
as well as URLs for NNTP newsgroup(s).