From: Badari Pulavarty <pbadari@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dave Airlie <airlied@linux.ie>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rc5: X spinning in the kernel [ Was: 2.6.14-rc5 GPF in radeon_cp_init_ring_buffer()]
Date: Thu, 27 Oct 2005 08:54:29 -0700 [thread overview]
Message-ID: <1130428469.23729.77.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0510270843100.4664@g5.osdl.org>
On Thu, 2005-10-27 at 08:45 -0700, Linus Torvalds wrote:
>
> On Thu, 27 Oct 2005, Badari Pulavarty wrote:
> >
> > sysrq-t shows nothing :(
>
> Use sysrq-p to show register state.
>
> On SMP, you may need to press it several times, to get the right CPU. And
> if you _never_ get the right CPU, that's likely an indication that it
> disabled interrupts, or your platform just sends all keyboard interrupts
> to the same CPU (try to see what happens with interrupt balancing).
>
> Linus
I tried that earlier, it never showed anything useful.
(2-proc EM64T machine).
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
SysRq : Show Regs
...
Thanks,
Badari
next prev parent reply other threads:[~2005-10-27 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 10:05 [PATCH] Fwd: 2.6.14-rc5 GPF in radeon_cp_init_ring_buffer() (fwd) Dave Airlie
2005-10-27 4:11 ` Badari Pulavarty
2005-10-27 15:25 ` 2.6.14-rc5: X spinning in the kernel [ Was: 2.6.14-rc5 GPF in radeon_cp_init_ring_buffer()] Badari Pulavarty
2005-10-27 15:45 ` Linus Torvalds
2005-10-27 15:54 ` Badari Pulavarty [this message]
2005-10-27 20:21 ` Dave Airlie
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=1130428469.23729.77.camel@localhost.localdomain \
--to=pbadari@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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