| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20070223020914.4a9a7ece.akpm@linux-foundation.org> Date: Fri, 23 Feb 2007 02:09:14 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: pgf111000 <junkmail@...ergfrazier.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Areca driver 2.6.19 on x86_64 > On Thu, 22 Feb 2007 20:04:07 -0800 (PST) pgf111000 <junkmail@...ergfrazier.com> 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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists