linux-kernel - Re: System freeze on reboot

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]

Message-ID: <20090811154853.GF2763@sgi.com>
Date:	Tue, 11 Aug 2009 10:48:53 -0500
From:	Robin Holt <holt@....com>
To:	Zdenek Kabelac <zdenek.kabelac@...il.com>
Cc:	Christoph Lameter <cl@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: System freeze on reboot - general protection fault

On Tue, Aug 11, 2009 at 05:32:16PM +0200, Zdenek Kabelac wrote:
> 2009/8/11 Christoph Lameter <cl@...ux-foundation.org>:
> > 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
--
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/