linux-kernel - Re: Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM)

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1158320742.29932.20.camel@localhost.localdomain>
Date:	Fri, 15 Sep 2006 12:45:42 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Robin Lee Powell <rlpowell@...italkingdom.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Same MCE on 4 working machines (was Re: Early boot hang on
	recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM)

Ar Iau, 2006-09-14 am 12:05 -0700, ysgrifennodd Robin Lee Powell:
> NET: Registered protocol family 16
> CPU 0: Machine Check Exception:                7 Bank 3: b40000000000083b
> RIP 10:<ffffffff8023a44c> {pci_conf1_read+0xac/0xe0}
> TSC d189cea ADDR fdfc000cfe

We went to do a PCI configuration cycle and your box blew up. Thats
pretty clear. Could be down to the various changes in how we do PCI
accesses tripping up a problem box, or triggering a bug.

See what effect 

	pci=bios
	pci=conf1
	pci=conf2

	pci=nommconf
	pci=nomsi

have and report back.

What drivers do you have enabled and what pci devices are present ?

Alan

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