From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Alistair John Strachan" <alistair@devzero.co.uk>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Sysrq+B doesn't work on my box
Date: Fri, 1 Aug 2008 15:22:40 +0200 [thread overview]
Message-ID: <c4e36d110808010622w74d61378ud9624a6ea38357a4@mail.gmail.com> (raw)
In-Reply-To: <200808011356.19027.alistair@devzero.co.uk>
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.
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
next prev parent reply other threads:[~2008-08-01 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 13:45 Zdenek Kabelac
2008-07-31 13:50 ` Alexey Dobriyan
2008-07-31 14:27 ` Zdenek Kabelac
2008-07-31 14:39 ` Henrique de Moraes Holschuh
2008-07-31 18:01 ` Zdenek Kabelac
2008-07-31 19:22 ` Henrique de Moraes Holschuh
2008-07-31 20:01 ` Jeremy Fitzhardinge
2008-08-01 9:54 ` Zdenek Kabelac
2008-08-01 12:56 ` Alistair John Strachan
2008-08-01 13:22 ` Zdenek Kabelac [this message]
2008-08-01 20:25 ` Zdenek Kabelac
2008-08-01 21:17 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4e36d110808010622w74d61378ud9624a6ea38357a4@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=alistair@devzero.co.uk \
--cc=hmh@hmh.eng.br \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome