RE: Compaq proliant ML-350 - IDE & SCSI
On 04/07/2001 21:55:53, Alexandru Barloiu Nicolae wrote: > I am trying to use the DMA on the ide drives. After the reboot Dma is > enabled but if I don't disable it with hdparm the system freezes at heavy > work (copy something from a drive to the other). The SCSI works ok. Without > the DMA the system barely moves > > > > Any ideas what's wrong? Which kernel version are you using? The OSB4 ide driver prior to version 2.4.2-ac27 causes problems on SMP servers. You may want to try a more recent kernel or remove the OSB4-specific driver and use the standard IDE/ATA driver instead. Regards, John Cagle Principal Member Technical Staff ProLiant Servers, Compaq - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Compaq proliant ML-350 - IDE SCSI
On 04/07/2001 21:55:53, Alexandru Barloiu Nicolae wrote: I am trying to use the DMA on the ide drives. After the reboot Dma is enabled but if I don't disable it with hdparm the system freezes at heavy work (copy something from a drive to the other). The SCSI works ok. Without the DMA the system barely moves SNIP Any ideas what's wrong? Which kernel version are you using? The OSB4 ide driver prior to version 2.4.2-ac27 causes problems on SMP servers. You may want to try a more recent kernel or remove the OSB4-specific driver and use the standard IDE/ATA driver instead. Regards, John Cagle Principal Member Technical Staff ProLiant Servers, Compaq - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: cpqarray & 2.4.1+ hang
Marcus Meissner wrote: >> I have a problem with the 2.4 series kernel running on a number of >> Compaq ProLiant DL360 servers. The 2.2.x kernels and 2.4.0 work fine, >> however from 2.4.1 onwards the boxes just hang at the following position >> on bootup: > >> Partition check: >> ida/c0d0: > >> I have also tested with 2.4.2-ac20 and the same problem occurs. Doing a >> search on the web some people recommend changing the OS setting in the >> Compaq BIOS to Linux fixes this problem, however my servers are already >> running with this BIOS setting and I've also tested with numerous other >> OS's in the BIOS but the same problem occurs. > >Workaround: run the kernel with the 'noapic' option on its commandline. > >The ServerWorks chipset used in this Compaq Server somehow does not pass >the the relevant information to Linux mapping routines. :/ > The real problem lies in the OSB4 driver beginning with the 2.4.0 kernel. Its initialization of the OSB4 breaks APIC interrupt processing, causing a lockup during boot of any APIC-enabled server that uses the OSB4. Rolling back to the version in 2.4.0-prerelease will resolve your lockup during boot. Alternatively, you can set CONFIG_BLK_DEV_OSB4=n in your .config. This will revert to using the generic IDE driver instead of the OSB4-specific code that is broken. That's not a problem on ProLiants since the OSB4 is only used to access the CD-ROM drive, hence you don't need any enhanced performance. Regards, John Cagle Principal Member Technical Staff ProLiant Servers, Compaq - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: cpqarray 2.4.1+ hang
Marcus Meissner wrote: I have a problem with the 2.4 series kernel running on a number of Compaq ProLiant DL360 servers. The 2.2.x kernels and 2.4.0 work fine, however from 2.4.1 onwards the boxes just hang at the following position on bootup: Partition check: ida/c0d0: I have also tested with 2.4.2-ac20 and the same problem occurs. Doing a search on the web some people recommend changing the OS setting in the Compaq BIOS to Linux fixes this problem, however my servers are already running with this BIOS setting and I've also tested with numerous other OS's in the BIOS but the same problem occurs. Workaround: run the kernel with the 'noapic' option on its commandline. The ServerWorks chipset used in this Compaq Server somehow does not pass the the relevant information to Linux mapping routines. :/ The real problem lies in the OSB4 driver beginning with the 2.4.0 kernel. Its initialization of the OSB4 breaks APIC interrupt processing, causing a lockup during boot of any APIC-enabled server that uses the OSB4. Rolling back to the version in 2.4.0-prerelease will resolve your lockup during boot. Alternatively, you can set CONFIG_BLK_DEV_OSB4=n in your .config. This will revert to using the generic IDE driver instead of the OSB4-specific code that is broken. That's not a problem on ProLiants since the OSB4 is only used to access the CD-ROM drive, hence you don't need any enhanced performance. Regards, John Cagle Principal Member Technical Staff ProLiant Servers, Compaq - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
