From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758540Ab0KPOmT (ORCPT ); Tue, 16 Nov 2010 09:42:19 -0500 Received: from mail.skyhub.de ([78.46.96.112]:44749 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758362Ab0KPOmS (ORCPT ); Tue, 16 Nov 2010 09:42:18 -0500 Date: Tue, 16 Nov 2010 15:42:13 +0100 From: Borislav Petkov To: Jody Bruchon Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" , Suresh Siddha Subject: Re: [REGRESSION] [BISECT] ACPI+Inspiron 1545 = crash at xrstor_state() Message-ID: <20101116144213.GA3715@a1.tnic> Mail-Followup-To: Borislav Petkov , Jody Bruchon , linux-kernel@vger.kernel.org, "H. Peter Anvin" , Suresh Siddha MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 16, 2010 at 04:56:06AM -0500, Jody Bruchon wrote: > I previously reported an early boot crash on an Inspiron 1545 laptop; > see previous posts for more details. I used the parameters "debug > vga=6 earlyprintk=vga" to catch these errors since they happen so > early in boot that the normal console has not yet initialized. > > A picture of the crash dump from 2.6.37-rc2 is available here (2.6.36 > crash is identical except for the reported kernel version): > http://c02ware.com/bugs/dump_c7ff0d9c92435e836e13aaa8d0e56d4000424bcc.jpg > > I have experienced similar problems on a small number of other systems > also. After confirming that the problem was introduced going from > 2.6.35 to 2.6.36, I have successfully bisected the kernel, and > narrowed down and tested to verify the commit which introduced the > problem. Reverting this commit fixes 2.6.36 but 2.6.37-rc2 has the > exact same crash even if I revert it. I don't know what to do from > here, but someone with more knowledge can surely guide me. I will > only have the unit to test with for another day or two. I have > attached a suitable .config for reference as well. The commit info is > below. I don't think this patch is at fault. Your oops photo above shows that the machine oopses at the first xrstor call in xstate_enable_boot_cpu(): 1c3: 0f 06 clts 1c5: 83 c8 ff or $0xffffffff,%eax 1c8: 89 c2 mov %eax,%edx 1ca: 0f ae 2f xrstor (%edi) <--------- 1cd: 8b 3d 54 00 00 00 mov 0x54,%edi 1d3: 0f ae 27 xsave (%edi) Adding more people to Cc. -- Regards/Gruss, Boris.