Re: Areca driver 2.6.19 on x86_64
With my distro hat on I'd also say that trying with acpi disabled is the first call when debugging problems with IRQ delivery. Alan - 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: Areca driver 2.6.19 on x86_64
> On Thu, 22 Feb 2007 20:04:07 -0800 (PST) pgf111000 <[EMAIL PROTECTED]> wrote: > > These solutions are laughable > > > > > Areca Support wrote: > > > > Dear Sir, > > > > This is Kevin Wang from Areca Technology, Tech-Support Team. > > regarding your problem, please trying to disable ACPI in kernel loader. > > if the problem happen as soon as driver loaded, it should be the IRQ > > releated issue. > > the motherboard bios didn't assigned a correct IRQ to controller, it makes > > the driver can't initialize controller. > > and in our experience, disable ACPI in kernel loader can solved this ussue > > in some distro. What we're probably looking at here are BIOS bugs. But areca's suggestions are good ones: if those things fix the problem then we probably need to fix Linus acpi or, more likely, add suitable workarounds for yet more BIOS bugs. So yes, please try the diagnostic steps which they suggested and if that helps, raise a report against acpi at bugzilla.kernel.org. - 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: Areca driver 2.6.19 on x86_64
On Thu, 22 Feb 2007 20:04:07 -0800 (PST) pgf111000 [EMAIL PROTECTED] wrote: These solutions are laughable Areca Support wrote: Dear Sir, This is Kevin Wang from Areca Technology, Tech-Support Team. regarding your problem, please trying to disable ACPI in kernel loader. if the problem happen as soon as driver loaded, it should be the IRQ releated issue. the motherboard bios didn't assigned a correct IRQ to controller, it makes the driver can't initialize controller. and in our experience, disable ACPI in kernel loader can solved this ussue in some distro. What we're probably looking at here are BIOS bugs. But areca's suggestions are good ones: if those things fix the problem then we probably need to fix Linus acpi or, more likely, add suitable workarounds for yet more BIOS bugs. So yes, please try the diagnostic steps which they suggested and if that helps, raise a report against acpi at bugzilla.kernel.org. - 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: Areca driver 2.6.19 on x86_64
With my distro hat on I'd also say that trying with acpi disabled is the first call when debugging problems with IRQ delivery. Alan - 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: Areca driver 2.6.19 on x86_64
These solutions are laughable Areca Support wrote: > > Dear Sir, > > This is Kevin Wang from Areca Technology, Tech-Support Team. > regarding your problem, please trying to disable ACPI in kernel loader. > if the problem happen as soon as driver loaded, it should be the IRQ > releated issue. > the motherboard bios didn't assigned a correct IRQ to controller, it makes > the driver can't initialize controller. > and in our experience, disable ACPI in kernel loader can solved this ussue > in some distro. > > > Best Regards, > > > Kevin Wang > > Areca Technology Tech-support Division > Tel : 886-2-87974060 Ext. 223 > Fax : 886-2-87975970 > Http://www.areca.com.tw > Ftp://ftp.areca.com.tw > > - Original Message - > From: "Bron Gondwana" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; ; > <[EMAIL PROTECTED]> > Sent: Thursday, December 07, 2006 7:09 AM > Subject: Re: Areca driver 2.6.19 on x86_64 > > >> On Wed, Dec 06, 2006 at 05:51:32PM +0100, [EMAIL PROTECTED] wrote: >> > OS distro used: >> > CentOS 4.4 x86_64 >> > Kernel 2.6.19 with hand-crafted config, that we are >> > able to use successfully with kernel 2.6.16.20. >> >> What patches were you applying to 2.6.16.20, since that didn't >> have an Areca driver in it I presume you're at least using that. >> >> > Have you any suggestions to resolve this issue ? >> >> 32 bit kernel? I'm somewhat serious here, depending what applications >> you're running on the machine. >> >> Otherwise, no clue sorry - we're running 32 bit kernels everywhere >> even on the couple of new Core machines we have. >> >> Bron. > > - > 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/ > > -- View this message in context: http://www.nabble.com/Areca-driver-2.6.19-on-x86_64-tf2769326.html#a9113207 Sent from the linux-kernel mailing list archive at Nabble.com. - 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: Areca driver 2.6.19 on x86_64
These solutions are laughable Areca Support wrote: Dear Sir, This is Kevin Wang from Areca Technology, Tech-Support Team. regarding your problem, please trying to disable ACPI in kernel loader. if the problem happen as soon as driver loaded, it should be the IRQ releated issue. the motherboard bios didn't assigned a correct IRQ to controller, it makes the driver can't initialize controller. and in our experience, disable ACPI in kernel loader can solved this ussue in some distro. Best Regards, Kevin Wang Areca Technology Tech-support Division Tel : 886-2-87974060 Ext. 223 Fax : 886-2-87975970 Http://www.areca.com.tw Ftp://ftp.areca.com.tw - Original Message - From: Bron Gondwana [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org; [EMAIL PROTECTED] Sent: Thursday, December 07, 2006 7:09 AM Subject: Re: Areca driver 2.6.19 on x86_64 On Wed, Dec 06, 2006 at 05:51:32PM +0100, [EMAIL PROTECTED] wrote: OS distro used: CentOS 4.4 x86_64 Kernel 2.6.19 with hand-crafted config, that we are able to use successfully with kernel 2.6.16.20. What patches were you applying to 2.6.16.20, since that didn't have an Areca driver in it I presume you're at least using that. Have you any suggestions to resolve this issue ? 32 bit kernel? I'm somewhat serious here, depending what applications you're running on the machine. Otherwise, no clue sorry - we're running 32 bit kernels everywhere even on the couple of new Core machines we have. Bron. - 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/ -- View this message in context: http://www.nabble.com/Areca-driver-2.6.19-on-x86_64-tf2769326.html#a9113207 Sent from the linux-kernel mailing list archive at Nabble.com. - 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: Areca driver 2.6.19 on x86_64
Dear Sir, This is Kevin Wang from Areca Technology, Tech-Support Team. regarding your problem, please trying to disable ACPI in kernel loader. if the problem happen as soon as driver loaded, it should be the IRQ releated issue. the motherboard bios didn't assigned a correct IRQ to controller, it makes the driver can't initialize controller. and in our experience, disable ACPI in kernel loader can solved this ussue in some distro. Best Regards, Kevin Wang Areca Technology Tech-support Division Tel : 886-2-87974060 Ext. 223 Fax : 886-2-87975970 Http://www.areca.com.tw Ftp://ftp.areca.com.tw - Original Message - From: "Bron Gondwana" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; ; <[EMAIL PROTECTED]> Sent: Thursday, December 07, 2006 7:09 AM Subject: Re: Areca driver 2.6.19 on x86_64 > On Wed, Dec 06, 2006 at 05:51:32PM +0100, [EMAIL PROTECTED] wrote: > > OS distro used: > > CentOS 4.4 x86_64 > > Kernel 2.6.19 with hand-crafted config, that we are > > able to use successfully with kernel 2.6.16.20. > > What patches were you applying to 2.6.16.20, since that didn't > have an Areca driver in it I presume you're at least using that. > > > Have you any suggestions to resolve this issue ? > > 32 bit kernel? I'm somewhat serious here, depending what applications > you're running on the machine. > > Otherwise, no clue sorry - we're running 32 bit kernels everywhere > even on the couple of new Core machines we have. > > Bron. - 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: Areca driver 2.6.19 on x86_64
On Wed, Dec 06, 2006 at 05:51:32PM +0100, [EMAIL PROTECTED] wrote: > OS distro used: > CentOS 4.4 x86_64 > Kernel 2.6.19 with hand-crafted config, that we are > able to use successfully with kernel 2.6.16.20. What patches were you applying to 2.6.16.20, since that didn't have an Areca driver in it I presume you're at least using that. > Have you any suggestions to resolve this issue ? 32 bit kernel? I'm somewhat serious here, depending what applications you're running on the machine. Otherwise, no clue sorry - we're running 32 bit kernels everywhere even on the couple of new Core machines we have. Bron. - 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/
Areca driver 2.6.19 on x86_64
We have a problem with the new areca driver included in kernel tree 2.6.19. During the boot sequence we get this output: Loading arcmsr.ko module ACPI: PCI Interrupt :05:0e.0[A] -> Link [LINKC] -> GSI 5 (level, low) -> IRQ 5 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.41 2006-5-24 scsi0: Areca SATA Host Adapter RAID Controller Driver Version 1.20.00.13 arcmsr0: abort device command of scsi id=0 lun=0 arcmsr0: scsi id=0 lun=0 ccb='0x810037f0' poll command abort successfully arcmsr0: abort device command of scsi id=1 lun=0 arcmsr0: scsi id=0 lun=0 ccb='0x810037f0' poll command abort successfully arcmsr0: abort device command of scsi id=2 lun=0 arcmsr0: scsi id=0 lun=0 ccb='0x810037f0' poll command abort successfully scsi 0:0:0:0: scsi: Device offlined - not ready after error recovery and keeps looping through all luns with different values of ccd at each loop. Till kernel panics because of the lack of root device. Here is our specs: HW used: ARC1220 ARC1110 on Supermicro X6DH8-XG2, Dual Xeon 3.0GHz OS distro used: CentOS 4.4 x86_64 Kernel 2.6.19 with hand-crafted config, that we are able to use successfully with kernel 2.6.16.20. Have you any suggestions to resolve this issue ? Thanks in advance, Filip Majewski - 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/
Areca driver 2.6.19 on x86_64
We have a problem with the new areca driver included in kernel tree 2.6.19. During the boot sequence we get this output: Loading arcmsr.ko module ACPI: PCI Interrupt :05:0e.0[A] - Link [LINKC] - GSI 5 (level, low) - IRQ 5 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.41 2006-5-24 scsi0: Areca SATA Host Adapter RAID Controller Driver Version 1.20.00.13 arcmsr0: abort device command of scsi id=0 lun=0 arcmsr0: scsi id=0 lun=0 ccb='0x810037f0' poll command abort successfully arcmsr0: abort device command of scsi id=1 lun=0 arcmsr0: scsi id=0 lun=0 ccb='0x810037f0' poll command abort successfully arcmsr0: abort device command of scsi id=2 lun=0 arcmsr0: scsi id=0 lun=0 ccb='0x810037f0' poll command abort successfully scsi 0:0:0:0: scsi: Device offlined - not ready after error recovery and keeps looping through all luns with different values of ccd at each loop. Till kernel panics because of the lack of root device. Here is our specs: HW used: ARC1220 ARC1110 on Supermicro X6DH8-XG2, Dual Xeon 3.0GHz OS distro used: CentOS 4.4 x86_64 Kernel 2.6.19 with hand-crafted config, that we are able to use successfully with kernel 2.6.16.20. Have you any suggestions to resolve this issue ? Thanks in advance, Filip Majewski - 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: Areca driver 2.6.19 on x86_64
On Wed, Dec 06, 2006 at 05:51:32PM +0100, [EMAIL PROTECTED] wrote: OS distro used: CentOS 4.4 x86_64 Kernel 2.6.19 with hand-crafted config, that we are able to use successfully with kernel 2.6.16.20. What patches were you applying to 2.6.16.20, since that didn't have an Areca driver in it I presume you're at least using that. Have you any suggestions to resolve this issue ? 32 bit kernel? I'm somewhat serious here, depending what applications you're running on the machine. Otherwise, no clue sorry - we're running 32 bit kernels everywhere even on the couple of new Core machines we have. Bron. - 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: Areca driver 2.6.19 on x86_64
Dear Sir, This is Kevin Wang from Areca Technology, Tech-Support Team. regarding your problem, please trying to disable ACPI in kernel loader. if the problem happen as soon as driver loaded, it should be the IRQ releated issue. the motherboard bios didn't assigned a correct IRQ to controller, it makes the driver can't initialize controller. and in our experience, disable ACPI in kernel loader can solved this ussue in some distro. Best Regards, Kevin Wang Areca Technology Tech-support Division Tel : 886-2-87974060 Ext. 223 Fax : 886-2-87975970 Http://www.areca.com.tw Ftp://ftp.areca.com.tw - Original Message - From: Bron Gondwana [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org; [EMAIL PROTECTED] Sent: Thursday, December 07, 2006 7:09 AM Subject: Re: Areca driver 2.6.19 on x86_64 On Wed, Dec 06, 2006 at 05:51:32PM +0100, [EMAIL PROTECTED] wrote: OS distro used: CentOS 4.4 x86_64 Kernel 2.6.19 with hand-crafted config, that we are able to use successfully with kernel 2.6.16.20. What patches were you applying to 2.6.16.20, since that didn't have an Areca driver in it I presume you're at least using that. Have you any suggestions to resolve this issue ? 32 bit kernel? I'm somewhat serious here, depending what applications you're running on the machine. Otherwise, no clue sorry - we're running 32 bit kernels everywhere even on the couple of new Core machines we have. Bron. - 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/
