From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Henrique de Moraes Holschuh" <hmh@hmh.eng.br>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Sysrq+B doesn't work on my box
Date: Thu, 31 Jul 2008 20:01:12 +0200 [thread overview]
Message-ID: <c4e36d110807311101h4fea377dsb4470c0935bbd419@mail.gmail.com> (raw)
In-Reply-To: <20080731143905.GF19665@khazad-dum.debian.net>
2008/7/31 Henrique de Moraes Holschuh <hmh@hmh.eng.br>:
> On Thu, 31 Jul 2008, Zdenek Kabelac wrote:
>> I'd like to get resolved this problem - my T61 machine doesn't reboot
>> with SysRQ+B key.
>> And I never remember if it was ever rebooting.
>>
>> This is all I know so far and I've no idea where could be the problem.
>
> Well, many of the different ThinkPad BIOSes are really sensitive to the
> proper boot/reboot/shutdown sequence (whatever it is). Otherwise, the thing
> gets stuck in SMBIOS limbo and hung. For exeample, we had major issues with
> boxes that only shut down half-way and ended up draining the cells to
> critical levels, a few months ago. I don't know what finally fixed THAT
> one, but it was ugly.
>
> Here is another example: you can't get the TCO watchdog to reboot all (any?)
> thinkpads properly on hardware. In my T43, the TCO watchdog IS hooked to
> something, but the BIOS hates it to trip and the entire box goes to
> neverland when it fires...
>
> If sysrq+b uses a different reboot path than the normal reboot path, it is
> the first hint of what is missing...
I've spend some time with tracking this issue more - and I've discovered this:
SysRQ+B doesn't work with right AltGr on my keyboard - but it does
work with the left Alt which I'm not normally using (It's somewhat
easier to use the right one)
Any idea why AltGR+SysRQ+b does not work on T61 ?
Blocking reboot goes through the arch/x86/kernel/reboot.c
native_machine_emergency_restart() case BOOT_KBD: (10 loop outb()
iteration)
and ends in case BOOT_TRIPLE: int3 - there it stays forever - during
the press of poweroff button it even visits that sysrq __handler.
if the kernel is started with init=/bin/sh - boot works without
problems - so it looks like that disabling reboot capability is the
result of Fedora's rc.sysinit process.
Yet I've no idea what that could be....
Zdenek
next prev parent reply other threads:[~2008-07-31 18:01 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 [this message]
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
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=c4e36d110807311101h4fea377dsb4470c0935bbd419@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=hmh@hmh.eng.br \
--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