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, 14 Feb 2008 22:23:00 +0100 (CET)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	linux-kernel@...r.kernel.org
Subject: Re: [ACPI X86_64] 2.6.24 doesn't boot on a Core 2 Duo

On Thu, 14 Feb 2008, Guennadi Liakhovetski wrote:

> 2.6.24.2 fails to boot on the above system with an Intel DQ35JO 
> motherboard, as do Debian install kernels - both stock etch amd64 and 
> updated image from Kenshi Muto (kmuto.jp). The only way to boot was with 
> "acpi=off". Whereas ubuntu 7.10 amd64 2.6.22-based boot-CD boots without 
> problems. Below is ubuntu's dmesg with a place marked where Debian and 
> self-compiled vanilla 2.6.24.2 kernels hang. Tried "pci=noacpi", 
> "acpi=noirq", "noapic", "nolapic", "pci=routeirq" with no success.

Found this page:

http://www.linuxquestions.org/questions/slackware-installation-40/cddvd-not-found-584582/page2.html

and a solution therein: "pci=nommconf" or disable CONFIG_PCI_MMCONFIG. 
Now, I don't understand why PCI_MMCONFIG is twice in ./arch/x86/Kconfig 
and maybe one has to be a bit more careful when defaulting it to "y".

Thanks
Guennadi
---
Guennadi Liakhovetski
--
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