linux-kernel - Re: 2.6.29: can't resume from suspend with DMAR (intel iommu) enabled

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: <20090325180720.GA28366@elte.hu>
Date:	Wed, 25 Mar 2009 19:07:20 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Andrew Lutomirski <amluto@...il.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Kyle McMartin <kyle@...hat.com>,
	Fenghua Yu <fenghua.yu@...el.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Yinghai Lu <yinghai@...nel.org>,
	Mark Gross <mgross@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.29: can't resume from suspend with DMAR (intel iommu)
	enabled


* David Woodhouse <dwmw2@...radead.org> wrote:

> On Wed, 2009-03-25 at 18:59 +0100, Ingo Molnar wrote:
> > 
> > that's not easy - i use it right now :)
> > 
> > That's another reason why warnings and non-panic() behavior are 
> > better for developers too. Had it not crashed i could have sent you 
> > my dmesg and i would not have turned off DMAR in the BIOS.
> > 
> > Now it's turned off in my BIOS (first barrier) and i need to reboot 
> > the kernel (second barrier) and i need to hack up a kernel in a 
> > certain way to produce debug info (third barrier) - in the merge 
> > window (fourth barrier ;-).
> 
> Yeah, trusting BIOS monkeys for this was always going to be a bad 
> plan. We should have just known how to set/read the damn hardware 
> BARs -- the most likely explanation for this is that your BIOS is 
> just lying to you about where it put the registers, I believe.
> 
> I'd like to put in a basic sanity check when we first ioremap the 
> (alleged) DMAR registers. Hopefully, the output I asked for will 
> confirm that there's a simple way to do that...

Could you please fix the panic() and add the debug output you'd like 
to see? That would give me a kernel to run straight away. Without me 
having to think much about what i should run and when.

(unless you really need this pr_debug info to proceed)

But it will be some time really. The laptop has 8 days uptime and is 
not set up to run custom kernels at all.

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