From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [Bug #13941] x86 Geode issue Date: Thu, 13 Aug 2009 11:07:43 +0200 Message-ID: <20090813090743.GA14352@elte.hu> References: <11fae7c70908130152j21f9f183m4f1c49d91fc7a7f9@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <11fae7c70908130152j21f9f183m4f1c49d91fc7a7f9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: =?iso-8859-1?Q?Martin-=C9ric?= Racine , Alexander Viro Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List * Martin-=C9ric Racine wrote: > Yes, this bug is still valid. >=20 > Ubuntu kernel team member Leann Ogasawara and I are slowly=20 > bisecting our way through the changes that took place since 2.6.30=20 > to find the commit that introduced this regression. Please stay=20 > tuned. hm, the only outright Geode related commit was: d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failu= re the jpg at: http://launchpadlibrarian.net/28892781/00002.jpg is very out of focus - but what i could decypher suggests a=20 pagefault crash in the VFS code, in generic_delete_inode(). Which could be a VFS bug, or a filesystem bug, or some unrelated=20 memory corruption hitting the inode data structure. Ingo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753853AbZHMJH4 (ORCPT ); Thu, 13 Aug 2009 05:07:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753704AbZHMJHz (ORCPT ); Thu, 13 Aug 2009 05:07:55 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:58135 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751336AbZHMJHz (ORCPT ); Thu, 13 Aug 2009 05:07:55 -0400 Date: Thu, 13 Aug 2009 11:07:43 +0200 From: Ingo Molnar To: =?iso-8859-1?Q?Martin-=C9ric?= Racine , Alexander Viro Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List Subject: Re: [Bug #13941] x86 Geode issue Message-ID: <20090813090743.GA14352@elte.hu> References: <11fae7c70908130152j21f9f183m4f1c49d91fc7a7f9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <11fae7c70908130152j21f9f183m4f1c49d91fc7a7f9@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Martin-Éric Racine wrote: > Yes, this bug is still valid. > > Ubuntu kernel team member Leann Ogasawara and I are slowly > bisecting our way through the changes that took place since 2.6.30 > to find the commit that introduced this regression. Please stay > tuned. hm, the only outright Geode related commit was: d6c585a: x86: geode: Mark mfgpt irq IRQF_TIMER to prevent resume failure the jpg at: http://launchpadlibrarian.net/28892781/00002.jpg is very out of focus - but what i could decypher suggests a pagefault crash in the VFS code, in generic_delete_inode(). Which could be a VFS bug, or a filesystem bug, or some unrelated memory corruption hitting the inode data structure. Ingo