| 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: <alpine.DEB.2.00.1003120556590.15732@p34.internal.lan> Date: Fri, 12 Mar 2010 05:57:53 -0500 (EST) From: Justin Piszcz <jpiszcz@...idpixels.com> To: linux-kernel@...r.kernel.org Subject: Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots On Fri, 12 Mar 2010, Justin Piszcz wrote: > > > On Fri, 12 Mar 2010, Justin Piszcz wrote: > >> Hello, >> >> I am trying to figure out why a particular host using a Gigabyte >> motherboard >> (AMD) continues to crash, memory/CPU OK, voltages normal, I see this in >> the kernel log: >> >> [ 0.138774] PCI: Using ACPI for IRQ routing >> [ 0.138825] PCI: pci_cache_line_size set to 64 bytes >> [ 0.138830] pci 0000:00:00.0: address space collision: [mem >> 0xe0000000-0xffffffff 64bit] already in use >> >> If memory gets mapped into this space somehow, can that cause a spontaenous >> reboot? What is the workaround for this problem? >> >> There are no PCI cards in this system, only a graphics card. >> >> I suppose the next things to try: >> apic=off >> lapic=off > > Correction- > noapic > nolapic > -- [ 0.029932] pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them After booting with pci=use_crs, the collision goes away, as does another problem with the jmicron controller, will see if this fixes it. Justin. -- 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