From: Len Brown <len.brown@intel.com>
To: Marcel Sebek <sebek64@post.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: register dump when press scroll lock
Date: 05 Jul 2004 15:18:42 -0400 [thread overview]
Message-ID: <1089055122.15671.65.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FF669@hdsmsx403.hd.intel.com>
On Sat, 2004-07-03 at 06:25, Marcel Sebek wrote:
> I run 2.6.7 kernel.
>
> Steps to reproduce:
> Switch keyboard by "Pause/Break" key from English to Czech map (or
> another
> second keymap, I also tried Slovak). Then press scrolllock. The
> following
> is printed out and scrlock led state is untouched:
>
> Pid: 0, comm: swapper
> EIP: 0060:[<c01e5382>] CPU: 0
> EIP is at acpi_processor_idle+0xd4/0x1c7
> EFLAGS: 00000212 Not tainted (2.6.7)
> EAX: 00cf9366 EBX: 00004008 ECX: 00cf90da EDX: 00004008
> ESI: cffd28b0 EDI: c0467e80 EBP: cffd2800 DS: 007b ES: 007b
> CR0: 8005003b CR2: 080b7f40 CR3: 0ca85000 CR4: 000002d0
> [<c0101f3c>] cpu_idle+0x2c/0x40
> [<c043d5fc>] start_kernel+0x13c/0x160
> [<c043d370>] unknown_bootoption+0x0/0x110
>
> EIP is at c01e5382 or c01e5361. Here is the asm code from gdb:
>
> 0xc01e5355 <acpi_processor_idle+167>: cmp $0x3,%eax
> 0xc01e5358 <acpi_processor_idle+170>: je 0xc01e539f
> <acpi_processor_idle+241>
...
You're in the ACPI idle loop, which is normal.
Why it prints this stuff out is probably
answered someplace in the CONFIG_MAGIC_SYSRQ code.
-Len
next parent reply other threads:[~2004-07-05 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FF669@hdsmsx403.hd.intel.com>
2004-07-05 19:18 ` Len Brown [this message]
2004-07-05 19:35 ` Marcel Sebek
2004-07-03 10:25 Marcel Sebek
[not found] ` <200407040219.32581.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-04 12:17 ` Marcel Sebek
2004-07-04 12:50 ` Andries Brouwer
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=1089055122.15671.65.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebek64@post.cz \
/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
all inboxes | Powered by JetHome®