Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758956AbYHAUZ3 (ORCPT ); Fri, 1 Aug 2008 16:25:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752560AbYHAUZW (ORCPT ); Fri, 1 Aug 2008 16:25:22 -0400 Received: from rv-out-0506.google.com ([209.85.198.226]:34575 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751471AbYHAUZV (ORCPT ); Fri, 1 Aug 2008 16:25:21 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XVg53s2J1CO4IlbQMcI6ceBPmdw5iIUTDBJFhC3/XIB2Xjveg4pIcOGIt3lGSFQPGH LkIb37UT9VK18ap9uP0aEvZGOuN5/0O4X+/pJ3vYTVbNS0DgI3PHF8okrMgTWjak7ta3 jbXHmBF48qJhq8f4pTaZm3JO07ED9IwB+alqc= Message-ID: Date: Fri, 1 Aug 2008 22:25:19 +0200 From: "Zdenek Kabelac" To: "Alistair John Strachan" Subject: Re: Sysrq+B doesn't work on my box Cc: "Jeremy Fitzhardinge" , "Henrique de Moraes Holschuh" , "Linux Kernel Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48921A0C.7020909@goop.org> <200808011356.19027.alistair@devzero.co.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1305 Lines: 33 2008/8/1 Zdenek Kabelac : > 2008/8/1 Alistair John Strachan : >> On Friday 01 August 2008 10:54:19 Zdenek Kabelac wrote: >>> 2008/7/31 Jeremy Fitzhardinge : >>> > Zdenek Kabelac wrote: >>> I'll probably try to bisect rc.sysinit script to check what is the >>> first command >>> that breaks the reboot - but if there is any idea what should I test >>> first.? >> >> Are you using modules? Maybe a driver is loaded and this upsets the BIOS >> somehow? If that was the case, the driver wouldn't be loaded in an >> init=/bin/sh situation, as you described before. >> > > > Yes - except as I've checked the exactly same modularized kernel > running Debian on the same box > has no boot problem. Ok - idea with checking loaded modules was actually the right way to a very quick discovery that KVM loaded in my Fedora are the source of troubles - without them the second mystery is also a history :) So - is it normal, that loaded KVM modules eliminate emergency reboot (bug or feature)? Zdenek -- 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/