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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 15 May 2008 21:00:07 +0200
From:	Robert Goldner <robert@...79.de>
To:	linux-kernel@...r.kernel.org
CC:	Robert Hancock <hancockr@...w.ca>
Subject: Re: Problems with mainboard INTEL D201GLY2A, pci devices only available
 with acpi=noirq

Robert Hancock schrieb:
> Robert Goldner wrote:
>> Hi everyone,
>>
>> I use a INTEL D201GLY2A mainboard, and after serveral trys PCI devices 
>> were only useable (not visable) with the boot-parameter acpi=noirq (or 
>> noacpi). I tryed several kernel-versions (stated with 2.6.22), and no 
>> sucess without his parameter.
>> Without acpi=noirq all pci devices are deteced well, but if you want 
>> to use them, there is no response.
> 
> Do you have the latest BIOS on this board? Any nonstandard BIOS 
> settings? It looks like the board is not using APIC but the ACPI IRQ 
> information is giving out IRQs over 15, which doesn't make any sense. 
> Maybe you're running in some kind of broken/untested BIOS configuration.


Yes, it was the latest BIOS for this board, but Intel put a new to the 
Internet these days. I updated the Bios, but no change at all.
There is only one ACPI-Relevant switch in the Bios, so I don´t think 
that the Bios configuration is the problem. The only on ACPI-relevant 
option is:
"Resume from S5 by LAN". But I don´t belive that this makes the problem 
(and I tryed both: on and off). There is no way to modify/reservate 
interrups in the Bios.

It looks like very buggy ACPI-tables in the Bios.

Robert
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ