public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Russell <ser@ser1.net>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1[01] freeze on x86_64
Date: Tue, 22 Mar 2005 02:02:05 -0500	[thread overview]
Message-ID: <423FC2ED.1090704@ser1.net> (raw)
In-Reply-To: <m13buo3vew.fsf@muc.de>

Andi Kleen wrote:

>Sean Russell <ser@ser1.net> writes:
>  
>
>>    acpi_thermal-0400 [23] acpi_thermal_get_trip_: Invalid active
>>threshold [0]
>>    
>>
>
>You mean you got this in /var/log/messages?
>  
>
Yes, in /var/log/messages.  The lock up occurs without warning, so the 
only opportunity I have to look for error messages is in the syslogs.

>Can you connect a serial console or netconsole and see if that 
>  
>
Er... by serial console, I assume you mean via a serial cable and some 
other device.  If so, then no, I don't have that capability.  I didn't 
know about netconsole before you mentioned it; I'll do some research and 
set it up.  I do have a second computer (well, my wife's laptop is also 
running Linux) that I could use to monitor UDP traffic, if I can figure 
out what to use as a client to capture the messages.  This may take me a 
couple of days.

I didn't post to the list earlier specifically because I knew the 
debugging process would rapidly exceed my knowledge about kernel 
debugging.  I appologize for making you walk me through the process.

>catches anything?  Also boot with oops=panic
>  
>
As a boot parameter?  I'll give that a try.

--- SER

  reply	other threads:[~2005-03-22 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 22:57 2.6.1[01] freeze on x86_64 Sean Russell
2005-03-22  9:02 ` Andi Kleen
2005-03-22  7:02   ` Sean Russell [this message]
2005-03-22 12:20     ` Jan Engelhardt
2005-03-22  8:15       ` Sean Russell
2005-03-22 13:11       ` Mark Nipper
2005-05-17 11:37         ` Sean E. Russell
2005-05-17 11:55           ` Andi Kleen

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=423FC2ED.1090704@ser1.net \
    --to=ser@ser1.net \
    --cc=ak@muc.de \
    --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