From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753787AbZHKPs7 (ORCPT ); Tue, 11 Aug 2009 11:48:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751846AbZHKPs6 (ORCPT ); Tue, 11 Aug 2009 11:48:58 -0400 Received: from relay1.sgi.com ([192.48.179.29]:60251 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751976AbZHKPs5 (ORCPT ); Tue, 11 Aug 2009 11:48:57 -0400 Date: Tue, 11 Aug 2009 10:48:53 -0500 From: Robin Holt To: Zdenek Kabelac Cc: Christoph Lameter , Linux Kernel Mailing List , Pekka Enberg Subject: Re: System freeze on reboot - general protection fault Message-ID: <20090811154853.GF2763@sgi.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 11, 2009 at 05:32:16PM +0200, Zdenek Kabelac wrote: > 2009/8/11 Christoph Lameter : > > On Tue, 11 Aug 2009, Zdenek Kabelac wrote: > > > >> Well - I've tried to switch from  'slub' allocator to  old 'slab' > >> allocator and the problem is gone - shutdown goes without any problem. > >> > >> So it's probably related to 'slub' allocator only? > > > > The slab allocator does not have all the diagnostics of slub. The issue > > may simply not be detected in slab. If you switch off diagnostics in slub > > then everything will seem to work fine as well. But we need to figure out > > what is going wrong here. > > Hmm - but there are few things - > > My machine runs Fedora Rawhide. If I run the same kernel within KVM > running Debian unstable I could easily reboot this guest machine > without any problems. > > Also if I boot Rawhide only to single mode - I could also reboot > machine without this oops. > The problem seems to be - when I do full machine startup to the > multiuser runlevel 3 Try booting all the way and recording you output from lsmod. Reboot single user mode and modprobe each of the modules in that original lists. Test shutdown from single user mode. This might identify if it is one of your loaded modules. If so, effectively bisect the modprobes until you find the offending module(s). Robin