Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752340AbZCXUtH (ORCPT ); Tue, 24 Mar 2009 16:49:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751934AbZCXUst (ORCPT ); Tue, 24 Mar 2009 16:48:49 -0400 Received: from mx2.redhat.com ([66.187.237.31]:51623 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751068AbZCXUss (ORCPT ); Tue, 24 Mar 2009 16:48:48 -0400 Date: Tue, 24 Mar 2009 16:40:28 -0400 From: Kyle McMartin To: "Yu, Fenghua" Cc: "'Ingo Molnar'" , "'Andrew Lutomirski'" , "'David Woodhouse'" , "'Jesse Barnes'" , "'Kyle McMartin'" , "Siddha, Suresh B" , "'Yinghai Lu'" , "Woodhouse, David" , "'Mark Gross'" , "'LKML'" Subject: Re: 2.6.29: can't resume from suspend with DMAR (intel iommu) enabled Message-ID: <20090324204028.GE11771@kibblesnbits.boston.devel.redhat.com> References: <20090324203259.GC26930@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1546 Lines: 39 On Tue, Mar 24, 2009 at 01:36:46PM -0700, Yu, Fenghua wrote: > > > >(Cc:s added) > > > >* Andrew Lutomirski 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 > > > >So i dont get to test suspend/resume ;-) > > > Current kernel doesn't have iommu suspend/resume support yet. I'll send out suspend/resume patches today or tomorrow. Hope that will help. > Heh, awesome, someone could have brought this, uhm, subtle, weakness when things were getting defaulted on... regards, Kyle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/