linux-kernel - Re: Sysrq+B doesn't work on my box

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]

Date:	Fri, 1 Aug 2008 15:22:40 +0200
From:	"Zdenek Kabelac" <zdenek.kabelac@...il.com>
To:	"Alistair John Strachan" <alistair@...zero.co.uk>
Cc:	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	"Henrique de Moraes Holschuh" <hmh@....eng.br>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Sysrq+B doesn't work on my box

2008/8/1 Alistair John Strachan <alistair@...zero.co.uk>:
> On Friday 01 August 2008 10:54:19 Zdenek Kabelac wrote:
>> 2008/7/31 Jeremy Fitzhardinge <jeremy@...p.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.

So it could be the some initialization steps are different so maybe a
slightly different set of modules
is installed or they are initialized on different order - I'll check this.

Zdenek
--
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/