Messages in this thread | | | From | Alistair John Strachan <> | Subject | Re: Sysrq+B doesn't work on my box | Date | Fri, 1 Aug 2008 22:17:53 +0100 |
| |
> 2008/8/1 Zdenek Kabelac <zdenek.kabelac@gmail.com>: > > 2008/8/1 Alistair John Strachan <alistair@devzero.co.uk>: > >> On Friday 01 August 2008 10:54:19 Zdenek Kabelac wrote: > >>> 2008/7/31 Jeremy Fitzhardinge <jeremy@goop.org>: > >>> > 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)?
Obviously not :-) Added Avi to CC.
Avi, Zdenek is having a problem on his T61 where the Alt-SysRq-B emergency reboot mechanism stops working after he loads the KVM module. Any ideas?
-- Cheers, Alistair.
| |