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]
Date:	Wed, 25 Mar 2009 10:32:12 -0700
From:	mark gross <mgross@...ux.intel.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Lutomirski <amluto@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	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>,
	David Woodhouse <David.Woodhouse@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.29: can't resume from suspend with DMAR (intel iommu)
	enabled

On Tue, Mar 24, 2009 at 09:32:59PM +0100, Ingo Molnar wrote:
> 
> (Cc:s added)
> 
> * Andrew Lutomirski <amluto@...il.com> wrote:
> 
> > On vanilla 2.6.29 (on Ubuntu 8.10), on a Lenovo x200s, my system 
> > is completely hosed on resume.  It appears that even hard disk IO 
> > didn't work (trying to do *anything* including getting a dmesg 
> > trace just spewed sda io errors to the console).  Hence no trace.  
> > I did an alt-sysrq-b and the screen went blank and the machine 
> > just started beeping at me.
> > 
> > Resume works much better with intel_iommu=off.  (I remember seeing 
> > a patch go by that purported to fix resume with IOMMU enabled, but 
> > it didn't work for me.)
> > 
> > I'd be happy to try to make a better bug report if anyone has any 
> > bright ideas.
> 
> i have a Lenovo T500 that does not even boot with with DMAR enabled 
> in the BIOS (it's default-off), i get this panic in early bootup:
> 
>     DMAR hardware is malfunctioning

That happens when the polling of the IOMMU registers fail to behave as
expected in the VT-d specification.  Typically its been a bios issue
when this happens.

> 
> So i dont get to test suspend/resume ;-)
> 
> 	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ