All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry LeBlanc <leblanc@inmotiontechnology.com>
To: Larry LeBlanc <leblanc@inmotiontechnology.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Power Management/PCMCIA conflict causes system freeze
Date: Tue, 22 Jul 2003 12:39:39 -0700	[thread overview]
Message-ID: <3F1D92FB.5040504@inmotiontechnology.com> (raw)
In-Reply-To: 3F1D91AB.3030707@inmotiontechnology.com



Larry LeBlanc wrote:

> Hi Russell,
>
> No luck...I enabled sysrq and verified it was working by issuing 
> sysrq-t and sysrq-p while the system was healthy. But when I cause the 
> hang sysrq-t and sysrq-p no longer do anything. One source I looked up 
> indicated that "Since it [Magic SysRq] is implemented as a part of the 
> keyboard driver, it is guaranteed to work most of the time, unless the 
> kernel itself is dead." So my conclusion is that my kernel is dead.
>
> Note: I tried sysrq-b on my system when it is healthy and it causes 
> the same hang.
>
> Larry
>
> Russell King wrote:
>
>>On Tue, Jul 22, 2003 at 11:24:25AM -0700, Larry LeBlanc wrote:
>>  
>>
>>>Any ideas? I've tried turning on debug in apm but all that happens is 
>>>the debug messages freeze with the rest of the system. Is there any 
>>>other location I should turn on debug messages to try to get an idea of 
>>>where the system is hanging?
>>>    
>>>
>>
>>You need to enable sysrq, cause a hang, and then issue a sysrq-t and
>>sysrq-p to find out where you're hanging.
>>
>>Note that if you're using a serial console, you need to hold the serial
>>port open for sysrq requests to be processed.
>>
>>  
>>
>




      parent reply	other threads:[~2003-07-22 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 18:24 Power Management/PCMCIA conflict causes system freeze Larry LeBlanc
2003-07-22 18:34 ` Russell King
     [not found]   ` <3F1D91AB.3030707@inmotiontechnology.com>
2003-07-22 19:39     ` Larry LeBlanc [this message]

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=3F1D92FB.5040504@inmotiontechnology.com \
    --to=leblanc@inmotiontechnology.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.