* aacraid and large memory problem (2.6.0-test11) @ 2003-12-02 19:35 Kevin Fenzi 2003-12-02 20:21 ` Mark Haverkamp 0 siblings, 1 reply; 11+ messages in thread From: Kevin Fenzi @ 2003-12-02 19:35 UTC (permalink / raw) To: linux-kernel, linux-aacraid-devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Booting 2.6.0-test11 on a machine with 8GB memory and using the aacraid driver results in a hang on boot. Passing mem=2048M causes it to boot normally. 4GB also hangs. 2.6.0-test8 booted normally on this same hardware. 8GB memory, dual xeon 3.06mhz with hyperthreading, RedHat 9 on it currently. Happy to provide details on setup/software, etc. Perhaps this patch in 2.6.0-test9 is the culprit? http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c On normal boot: SCSI subsystem initialized Red Hat/Adaptec aacraid driver (1.1.2 Nov 26 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 Vendor: ADAPTEC Model: Adaptec RAID5 Rev: V1.0 Type: Direct-Access ANSI SCSI revision: 02 On the hangs: SCSI subsystem initialized Loading sd_mod.ko module Loading aacraid.ko module Red Hat/Adaptec aacraid driver (1.1.2 Nov 26 2003) aacraid: NMI ISR: NMI_BUS_INTERFACE_UNIT_ERROR aacraid: <...repeats 7 more times> aacraid: NormPrioCommand was received with Fib StructType = 0xff <hangs> Thanks for any ideas. kevin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD4DBQE/zOl43imCezTjY0ERAsH1AKCQ/xzLEEysLF+ewdEKXr5AGWplrgCWOs8f rXbYWCZSyPGSGrKQEq6z6w== =xAVH -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 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 0 siblings, 2 replies; 11+ messages in thread From: Mark Haverkamp @ 2003-12-02 20:21 UTC (permalink / raw) To: Kevin Fenzi; +Cc: linux-kernel, linux aacraid devel On Tue, 2003-12-02 at 11:35, Kevin Fenzi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Greetings, > > Booting 2.6.0-test11 on a machine with 8GB memory and using the > aacraid driver results in a hang on boot. Passing mem=2048M causes it > to boot normally. 4GB also hangs. 2.6.0-test8 booted normally on this > same hardware. > > 8GB memory, dual xeon 3.06mhz with hyperthreading, RedHat 9 on it > currently. > > Happy to provide details on setup/software, etc. > > Perhaps this patch in 2.6.0-test9 is the culprit? > http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c This patch is what made aacraid work with over 4 gig of memory for me. I have an 8 proc system with 16gig of memory and without this patch I get data corruption in high memory. I don't boot on the aacraid though. -- Mark Haverkamp <markh@osdl.org> ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 2003-12-02 20:21 ` Mark Haverkamp @ 2003-12-03 16:16 ` bill davidsen 2003-12-03 20:51 ` Kevin Fenzi 1 sibling, 0 replies; 11+ messages in thread From: bill davidsen @ 2003-12-03 16:16 UTC (permalink / raw) To: linux-kernel In article <1070396482.16903.11.camel@markh1.pdx.osdl.net>, Mark Haverkamp <markh@osdl.org> wrote: | On Tue, 2003-12-02 at 11:35, Kevin Fenzi wrote: | > -----BEGIN PGP SIGNED MESSAGE----- | > Hash: SHA1 | > | > | > Greetings, | > | > Booting 2.6.0-test11 on a machine with 8GB memory and using the | > aacraid driver results in a hang on boot. Passing mem=2048M causes it | > to boot normally. 4GB also hangs. 2.6.0-test8 booted normally on this | > same hardware. | > | > 8GB memory, dual xeon 3.06mhz with hyperthreading, RedHat 9 on it | > currently. | > | > Happy to provide details on setup/software, etc. | > | > Perhaps this patch in 2.6.0-test9 is the culprit? | > http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c | | This patch is what made aacraid work with over 4 gig of memory for me. | I have an 8 proc system with 16gig of memory and without this patch I | get data corruption in high memory. | | I don't boot on the aacraid though. It would be interesting to know what memory model is being used in each case. Both CONFIG_HIGHMEM* and maybe user/kernel split might play. Based on one boot with one machine, 4G RAM, it didn't hang. Unfortunately a production machine, I was playing following some "unscheduled maintenence." -- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 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 1 sibling, 1 reply; 11+ messages in thread From: Kevin Fenzi @ 2003-12-03 20:51 UTC (permalink / raw) To: Mark Haverkamp; +Cc: linux-kernel, linux aacraid devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Mark" == Mark Haverkamp <markh@osdl.org> writes: Mark> On Tue, 2003-12-02 at 11:35, Kevin Fenzi wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> >> Greetings, >> >> Booting 2.6.0-test11 on a machine with 8GB memory and using the >> aacraid driver results in a hang on boot. Passing mem=2048M causes >> it to boot normally. 4GB also hangs. 2.6.0-test8 booted normally on >> this same hardware. >> >> 8GB memory, dual xeon 3.06mhz with hyperthreading, RedHat 9 on it >> currently. >> >> Happy to provide details on setup/software, etc. >> >> Perhaps this patch in 2.6.0-test9 is the culprit? >> http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c Mark> This patch is what made aacraid work with over 4 gig of memory Mark> for me. I have an 8 proc system with 16gig of memory and without Mark> this patch I get data corruption in high memory. Mark> I don't boot on the aacraid though. Is there any way you can try booting from it and see if it's a boot issue for you as well? I can try booting the one here from something else and see if it works with that. kevin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQE/zkzd3imCezTjY0ERAtdRAJ9NIp56DWRFI6zxpbgyLtKQzkYcIACfYKil Z6XcmnrXQ9Qsiy24d7ac044= =a+PX -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 2003-12-03 20:51 ` Kevin Fenzi @ 2003-12-03 21:57 ` Mark Haverkamp 2003-12-03 22:28 ` Kevin Fenzi 0 siblings, 1 reply; 11+ messages in thread From: Mark Haverkamp @ 2003-12-03 21:57 UTC (permalink / raw) To: Kevin Fenzi; +Cc: linux-kernel, linux aacraid devel On Wed, 2003-12-03 at 12:51, Kevin Fenzi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >>>>> "Mark" == Mark Haverkamp <markh@osdl.org> writes: > > Mark> On Tue, 2003-12-02 at 11:35, Kevin Fenzi wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > >> > >> > >> Greetings, > >> > >> Booting 2.6.0-test11 on a machine with 8GB memory and using the > >> aacraid driver results in a hang on boot. Passing mem=2048M causes > >> it to boot normally. 4GB also hangs. 2.6.0-test8 booted normally on > >> this same hardware. > >> > >> 8GB memory, dual xeon 3.06mhz with hyperthreading, RedHat 9 on it > >> currently. > >> > >> Happy to provide details on setup/software, etc. > >> > >> Perhaps this patch in 2.6.0-test9 is the culprit? > >> http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c > > Mark> This patch is what made aacraid work with over 4 gig of memory > Mark> for me. I have an 8 proc system with 16gig of memory and without > Mark> this patch I get data corruption in high memory. > > Mark> I don't boot on the aacraid though. > > Is there any way you can try booting from it and see if it's a boot > issue for you as well? I set up my machine to boot on the aacraid disk and it booted OK for me. Maybe its a problem with a particular model? lspci on mine says: 02:04.0 RAID bus controller: Digital Equipment Corporation DECchip 21554 (rev 01) Subsystem: Adaptec Adaptec 5400S > > I can try booting the one here from something else and see if it works > with that. > > kevin > -- Mark Haverkamp <markh@osdl.org> ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 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 0 siblings, 2 replies; 11+ messages in thread From: Kevin Fenzi @ 2003-12-03 22:28 UTC (permalink / raw) To: Mark Haverkamp; +Cc: linux-kernel, linux aacraid devel -----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> -- Mark Haverkamp <markh@osdl.org> kevin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQE/zmOY3imCezTjY0ERAtOeAKCCCos81FiV0oy89ojnJQiTCK212QCgkO8/ 1rARggxxE7xP8YVggM2f6vI= =+t3d -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 2003-12-03 22:28 ` Kevin Fenzi @ 2003-12-03 22:53 ` bill davidsen 2003-12-03 23:25 ` Mark Haverkamp 1 sibling, 0 replies; 11+ messages in thread From: bill davidsen @ 2003-12-03 22:53 UTC (permalink / raw) To: linux-kernel In article <20031203222840.6A4E6F7C86@voldemort.scrye.com>, Kevin Fenzi <kevin@tummy.com> wrote: | | >>>>> "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> -- Mark Haverkamp <markh@osdl.org> | | kevin 02:03.0 RAID bus controller: Digital Equipment Corporation DECchip 21554 (rev 01) Subsystem: Adaptec Dell PowerEdge RAID Controller 2 Flags: bus master, medium devsel, latency 32, IRQ 18 Memory at fe200000 (32-bit, non-prefetchable) [size=8K] I/O ports at f800 [size=256] Expansion ROM at fd000000 [disabled] [size=128K] Capabilities: <available only to root> Sorry - it's back on 2.4, just thought this might be useful. -- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 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 1 sibling, 1 reply; 11+ messages in thread From: Mark Haverkamp @ 2003-12-03 23:25 UTC (permalink / raw) To: Kevin Fenzi; +Cc: linux-kernel, linux aacraid devel 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 > Could you try this patch? I took the code from the adaptec version of the driver. It fiddles with the dma mask on the 2200S controller among others. Mark. ===== drivers/scsi/aacraid/aachba.c 1.20 vs edited ===== --- 1.20/drivers/scsi/aacraid/aachba.c Fri May 2 12:30:49 2003 +++ edited/drivers/scsi/aacraid/aachba.c Wed Dec 3 15:10:22 2003 @@ -525,6 +525,14 @@ if(dev->pae_support != 0) { printk(KERN_INFO"%s%d: 64 Bit PAE enabled\n", dev->name, dev->id); pci_set_dma_mask(dev->pdev, (dma_addr_t)0xFFFFFFFFFFFFFFFFULL); + } else { + /* + * Reset if Quirk 31 was used, since data + * transfers are ok. + */ + if (pci_set_dma_mask(dev->pdev, 0xFFFFFFFFULL)) { + printk(KERN_INFO"aacraid: Can't reset DMA mask.\n"); + } } fib_complete(fibptr); ===== drivers/scsi/aacraid/aacraid.h 1.9 vs edited ===== --- 1.9/drivers/scsi/aacraid/aacraid.h Wed Oct 22 02:52:43 2003 +++ edited/drivers/scsi/aacraid/aacraid.h Wed Dec 3 15:21:48 2003 @@ -529,6 +529,8 @@ char * vname; char * model; u16 channels; + int quirks; +#define AAC_QUIRK_31BIT 1 }; /* ===== drivers/scsi/aacraid/linit.c 1.22 vs edited ===== --- 1.22/drivers/scsi/aacraid/linit.c Tue Aug 26 09:25:41 2003 +++ edited/drivers/scsi/aacraid/linit.c Wed Dec 3 15:22:42 2003 @@ -86,36 +86,47 @@ * for the card. At that time we can remove the channels from here */ static struct aac_driver_ident aac_drivers[] = { - { 0x1028, 0x0001, 0x1028, 0x0001, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 2/Si */ - { 0x1028, 0x0002, 0x1028, 0x0002, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Di */ - { 0x1028, 0x0003, 0x1028, 0x0003, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Si */ - { 0x1028, 0x0004, 0x1028, 0x00d0, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Si */ - { 0x1028, 0x0002, 0x1028, 0x00d1, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Di */ - { 0x1028, 0x0002, 0x1028, 0x00d9, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Di */ - { 0x1028, 0x000a, 0x1028, 0x0106, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Di */ - { 0x1028, 0x000a, 0x1028, 0x011b, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Di */ - { 0x1028, 0x000a, 0x1028, 0x0121, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2 }, /* PERC 3/Di */ - { 0x9005, 0x0283, 0x9005, 0x0283, aac_rx_init, "aacraid", "ADAPTEC ", "catapult ", 2 }, /* catapult*/ - { 0x9005, 0x0284, 0x9005, 0x0284, aac_rx_init, "aacraid", "ADAPTEC ", "tomcat ", 2 }, /* tomcat*/ - { 0x9005, 0x0285, 0x9005, 0x0286, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 2120S ", 1 }, /* Adaptec 2120S (Crusader)*/ - { 0x9005, 0x0285, 0x9005, 0x0285, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 2200S ", 2 }, /* Adaptec 2200S (Vulcan)*/ - { 0x9005, 0x0285, 0x9005, 0x0287, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 2200S ", 2 }, /* Adaptec 2200S (Vulcan-2m)*/ - { 0x9005, 0x0285, 0x17aa, 0x0286, aac_rx_init, "aacraid", "Legend ", "Legend S220 ", 1 }, /* Legend S220*/ - { 0x9005, 0x0285, 0x17aa, 0x0287, aac_rx_init, "aacraid", "Legend ", "Legend S230 ", 2 }, /* Legend S230*/ - - { 0x9005, 0x0285, 0x9005, 0x0288, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 3230S ", 2 }, /* Adaptec 3230S (Harrier)*/ - { 0x9005, 0x0285, 0x9005, 0x0289, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 3240S ", 2 }, /* Adaptec 3240S (Tornado)*/ - { 0x9005, 0x0285, 0x9005, 0x028a, aac_rx_init, "aacraid", "ADAPTEC ", "ASR-2020S PCI-X ", 2 }, /* ASR-2020S PCI-X ZCR (Skyhawk)*/ - { 0x9005, 0x0285, 0x9005, 0x028b, aac_rx_init, "aacraid", "ADAPTEC ", "ASR-2020S PCI-X ", 2 }, /* ASR-2020S SO-DIMM PCI-X ZCR(Terminator)*/ - { 0x9005, 0x0285, 0x9005, 0x0290, aac_rx_init, "aacraid", "ADAPTEC ", "AAR-2410SA SATA ", 2 }, /* AAR-2410SA PCI SATA 4ch (Jaguar II)*/ - { 0x9005, 0x0250, 0x1014, 0x0279, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec ", 2 }, /* (Marco)*/ - { 0x9005, 0x0250, 0x1014, 0x028c, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec ", 2 }, /* (Sebring)*/ + { 0x1028, 0x0001, 0x1028, 0x0001, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 2/Si (Iguana/PERC2Si) */ + { 0x1028, 0x0002, 0x1028, 0x0002, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Di (Opal/PERC3Di) */ + { 0x1028, 0x0003, 0x1028, 0x0003, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Si (SlimFast/PERC3Si */ + { 0x1028, 0x0004, 0x1028, 0x00d0, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Di (Iguana FlipChip/PERC3DiF */ + { 0x1028, 0x0002, 0x1028, 0x00d1, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Di (Viper/PERC3DiV) */ + { 0x1028, 0x0002, 0x1028, 0x00d9, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Di (Lexus/PERC3DiL) */ + { 0x1028, 0x000a, 0x1028, 0x0106, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 1, AAC_QUIRK_31BIT }, /* PERC 3/Di (Jaguar/PERC3DiJ) */ + { 0x1028, 0x000a, 0x1028, 0x011b, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Di (Dagger/PERC3DiD) */ + { 0x1028, 0x000a, 0x1028, 0x0121, aac_rx_init, "percraid", "DELL ", "PERCRAID ", 2, AAC_QUIRK_31BIT }, /* PERC 3/Di (Boxster/PERC3DiB) */ + { 0x9005, 0x0283, 0x9005, 0x0283, aac_rx_init, "aacraid", "ADAPTEC ", "catapult ", 2, AAC_QUIRK_31BIT }, /* catapult */ + { 0x9005, 0x0284, 0x9005, 0x0284, aac_rx_init, "aacraid", "ADAPTEC ", "tomcat ", 2, AAC_QUIRK_31BIT }, /* tomcat */ + { 0x9005, 0x0285, 0x9005, 0x0286, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 2120S ", 1, AAC_QUIRK_31BIT }, /* Adaptec 2120S (Crusader) */ + { 0x9005, 0x0285, 0x9005, 0x0285, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 2200S ", 2, AAC_QUIRK_31BIT }, /* Adaptec 2200S (Vulcan) */ + { 0x9005, 0x0285, 0x9005, 0x0287, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 2200S ", 2, AAC_QUIRK_31BIT }, /* Adaptec 2200S (Vulcan-2m) */ + { 0x9005, 0x0285, 0x17aa, 0x0286, aac_rx_init, "aacraid", "Legend ", "Legend S220 ", 1, AAC_QUIRK_31BIT }, /* Legend S220 (Legend Crusader) */ + { 0x9005, 0x0285, 0x17aa, 0x0287, aac_rx_init, "aacraid", "Legend ", "Legend S230 ", 2, AAC_QUIRK_31BIT }, /* Legend S230 (Legend Vulcan) */ + + { 0x9005, 0x0285, 0x9005, 0x0288, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 3230S ", 2 }, /* Adaptec 3230S (Harrier) */ + { 0x9005, 0x0285, 0x9005, 0x0289, aac_rx_init, "aacraid", "ADAPTEC ", "Adaptec 3240S ", 2 }, /* Adaptec 3240S (Tornado) */ + { 0x9005, 0x0285, 0x9005, 0x028a, aac_rx_init, "aacraid", "ADAPTEC ", "ASR-2020S PCI-X ", 2 }, /* ASR-2020S PCI-X ZCR (Skyhawk) */ + { 0x9005, 0x0285, 0x9005, 0x028b, aac_rx_init, "aacraid", "ADAPTEC ", "ASR-2020S PCI-X ", 2 }, /* ASR-2020S SO-DIMM PCI-X ZCR (Terminator) */ +/* { 0x9005, 0x0286, 0x9005, 0x028c, aac_rx_init, "aacraid", "ADAPTEC ", "ASR-2230S PCI-X ", 2 }, */ /* ASR-2230S PCI-X (Lancer pre-production) */ + { 0x9005, 0x0285, 0x9005, 0x0290, aac_rx_init, "aacraid", "ADAPTEC ", "AAR-2410SA SATA ", 1 }, /* AAR-2410SA PCI SATA 4ch (Jaguar II) */ + { 0x9005, 0x0285, 0x1028, 0x0291, aac_rx_init, "aacraid", "DELL ", "CERC SR2 ", 1 }, /* CERC SATA RAID 2 PCI SATA 6ch (DellCorsair) */ + { 0x9005, 0x0285, 0x9005, 0x0292, aac_rx_init, "aacraid", "ADAPTEC ", "AAR-2810SA SATA ", 1 }, /* AAR-2810SA PCI SATA 8ch (Corsair-8) */ + { 0x9005, 0x0285, 0x9005, 0x0293, aac_rx_init, "aacraid", "ADAPTEC ", "AAR-21610SA SATA", 1 }, /* AAR-21610SA PCI SATA 16ch (Corsair-16) */ + { 0x9005, 0x0285, 0x9005, 0x0294, aac_rx_init, "aacraid", "ADAPTEC ", "SO-DIMM SATA ZCR", 1 }, /* ESD SO-DIMM PCI-X SATA ZCR (Prowler) */ + { 0x9005, 0x0285, 0x0E11, 0x0295, aac_rx_init, "aacraid", "ADAPTEC ", "SATA 6Channel ", 1 }, /* SATA 6Ch (Bearcat) */ - { 0x9005, 0x0285, 0x1028, 0x0287, aac_rx_init, "percraid", "DELL ", "PERC 320/DC ", 2 }, /* Perc 320/DC*/ + { 0x9005, 0x0285, 0x1028, 0x0287, aac_rx_init, "percraid", "DELL ", "PERC 320/DC ", 2, AAC_QUIRK_31BIT }, /* Perc 320/DC*/ { 0x1011, 0x0046, 0x9005, 0x0365, aac_sa_init, "aacraid", "ADAPTEC ", "Adaptec 5400S ", 4 }, /* Adaptec 5400S (Mustang)*/ { 0x1011, 0x0046, 0x9005, 0x0364, aac_sa_init, "aacraid", "ADAPTEC ", "AAC-364 ", 4 }, /* Adaptec 5400S (Mustang)*/ - { 0x1011, 0x0046, 0x9005, 0x1364, aac_sa_init, "percraid", "DELL ", "PERCRAID ", 4 }, /* Dell PERC2 "Quad Channel" */ - { 0x1011, 0x0046, 0x103c, 0x10c2, aac_sa_init, "hpnraid", "HP ", "NetRAID ", 4 } /* HP NetRAID-4M */ + { 0x1011, 0x0046, 0x9005, 0x1364, aac_sa_init, "percraid", "DELL ", "PERCRAID ", 4, AAC_QUIRK_31BIT }, /* Dell PERC2/QC */ + { 0x1011, 0x0046, 0x103c, 0x10c2, aac_sa_init, "hpnraid", "HP ", "NetRAID ", 4 }, /* HP NetRAID-4M */ + + { 0x9005, 0x0285, 0x1028, PCI_ANY_ID, + aac_rx_init, "aacraid", "DELL ", "RAID ", 2, AAC_QUIRK_31BIT }, /* Dell Catchall */ + { 0x9005, 0x0285, 0x17aa, PCI_ANY_ID, + aac_rx_init, "aacraid", "Legend ", "RAID ", 2, AAC_QUIRK_31BIT }, /* Legend Catchall */ + { 0x9005, 0x0285, PCI_ANY_ID, PCI_ANY_ID, + aac_rx_init, "aacraid", "ADAPTEC ", "RAID ", 2, AAC_QUIRK_31BIT }, /* Adaptec Catch All */ }; #define NUM_AACTYPES (sizeof(aac_drivers) / sizeof(struct aac_driver_ident)) @@ -174,6 +185,7 @@ struct aac_dev *aac; struct fsa_scsi_hba *fsa_dev_ptr; char *name = NULL; + int ret; printk(KERN_INFO "Red Hat/Adaptec aacraid driver (%s %s)\n", AAC_DRIVER_VERSION, AAC_DRIVER_BUILD_DATE); @@ -194,7 +206,15 @@ if (pci_enable_device(dev)) continue; pci_set_master(dev); - pci_set_dma_mask(dev, 0xFFFFFFFFULL); + if (aac_drivers[index].quirks & AAC_QUIRK_31BIT) + ret = pci_set_dma_mask(dev, 0x7FFFFFFFULL); + else + ret = pci_set_dma_mask(dev, 0xFFFFFFFFULL); + + if (ret) { + printk(KERN_WARNING "aacraid: Can't set DMA mask.\n"); + continue; + } if((dev->subsystem_vendor != aac_drivers[index].subsystem_vendor) || (dev->subsystem_device != aac_drivers[index].subsystem_device)) -- Mark Haverkamp <markh@osdl.org> ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 2003-12-03 23:25 ` Mark Haverkamp @ 2003-12-11 17:53 ` Kevin Fenzi 0 siblings, 0 replies; 11+ messages in thread From: Kevin Fenzi @ 2003-12-11 17:53 UTC (permalink / raw) To: Mark Haverkamp; +Cc: linux-kernel, linux aacraid devel -----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----- ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) @ 2003-12-03 20:57 Kevin Fenzi 2003-12-03 21:26 ` bill davidsen 0 siblings, 1 reply; 11+ messages in thread From: Kevin Fenzi @ 2003-12-03 20:57 UTC (permalink / raw) To: linux-kernel, linux aacraid devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bill> | > Perhaps this patch in 2.6.0-test9 is the culprit? | > Bill> http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c Bill> | | This patch is what made aacraid work with over 4 gig of Bill> memory for me. | I have an 8 proc system with 16gig of memory Bill> and without this patch I | get data corruption in high memory. Bill> | | I don't boot on the aacraid though. Bill> It would be interesting to know what memory model is being used Bill> in each case. Both CONFIG_HIGHMEM* and maybe user/kernel split Bill> might play. I am using the 2.6.0 rpms from: http://people.redhat.com/arjanv/2.5/ Specifically its: http://people.redhat.com/arjanv/2.5/RPMS.kernel/kernel-smp-2.6.0-0.test11.1.99.i686.rpm The kernel-2.6.0-test11-i686-smp.config says: # CONFIG_NOHIGHMEM is not set # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y CONFIG_HIGHMEM=y CONFIG_BLK_DEV_UMEM=m CONFIG_DEBUG_HIGHMEM=y Bill> Based on one boot with one machine, 4G RAM, it didn't hang. Bill> Unfortunately a production machine, I was playing following some Bill> "unscheduled maintenence." Did you have HIGHMEM set? kevin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQE/zk463imCezTjY0ERAuboAKCN4XxByy8NO7UUK2h1eyXtbBIjZgCfSj9M budyunjfaRG+UhhSHR3IZss= =uXXJ -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: aacraid and large memory problem (2.6.0-test11) 2003-12-03 20:57 Kevin Fenzi @ 2003-12-03 21:26 ` bill davidsen 0 siblings, 0 replies; 11+ messages in thread From: bill davidsen @ 2003-12-03 21:26 UTC (permalink / raw) To: linux-kernel In article <20031203205730.88B7EF7C86@voldemort.scrye.com>, Kevin Fenzi <kevin@tummy.com> wrote: | Bill> | > Perhaps this patch in 2.6.0-test9 is the culprit? | > | Bill> http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c | Bill> | | This patch is what made aacraid work with over 4 gig of | Bill> memory for me. | I have an 8 proc system with 16gig of memory | Bill> and without this patch I | get data corruption in high memory. | Bill> | | I don't boot on the aacraid though. | | Bill> It would be interesting to know what memory model is being used | Bill> in each case. Both CONFIG_HIGHMEM* and maybe user/kernel split | Bill> might play. | | I am using the 2.6.0 rpms from: | | http://people.redhat.com/arjanv/2.5/ | | Specifically its: | | http://people.redhat.com/arjanv/2.5/RPMS.kernel/kernel-smp-2.6.0-0.test11.1.99.i686.rpm | | The kernel-2.6.0-test11-i686-smp.config | says: | | # CONFIG_NOHIGHMEM is not set | # CONFIG_HIGHMEM4G is not set | CONFIG_HIGHMEM64G=y | CONFIG_HIGHMEM=y | CONFIG_BLK_DEV_UMEM=m | CONFIG_DEBUG_HIGHMEM=y | | Bill> Based on one boot with one machine, 4G RAM, it didn't hang. | Bill> Unfortunately a production machine, I was playing following some | Bill> "unscheduled maintenence." | | Did you have HIGHMEM set? root> grep HIGHMEM .config CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set | kevin I don't know that this sheds any light, one is a fairly small sample set. -- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2003-12-11 17:55 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 2003-12-03 20:57 Kevin Fenzi 2003-12-03 21:26 ` bill davidsen
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).