From: Mark Nipper <nipsy@bitgnome.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Sean Russell <ser@ser1.net>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.1[01] freeze on x86_64
Date: Tue, 22 Mar 2005 07:11:16 -0600 [thread overview]
Message-ID: <20050322131116.GA15512@king.bitgnome.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0503221317220.10134@yvahk01.tjqt.qr>
On 22 Mar 2005, Jan Engelhardt wrote:
> >> > 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.
>
> Serial console -- only requires a serial cable, available in the next computer
> store -- also works with non-Linux, non-x86 and (mostly) systems-w/o-compiler.
>
>
> Jan Engelhardt
I've actually got old dumb terminals sitting around.
I'll hook one up and set the oops=panic option also. Maybe we
can nail this down as I've pretty much avoided using my x86-64
desktop ever since. I'd been torn trying to decide whether or
not to migrate to a different file system.
--
Mark Nipper e-contacts:
4475 Carter Creek Parkway nipsy@bitgnome.net
Apartment 724 http://nipsy.bitgnome.net/
Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617
(979)575-3193 MSN: nipsy@tamu.edu
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
He hoped and prayed that there wasn't an afterlife. Then he
realized there was a contradiction involved here and merely
hoped that there wasn't an afterlife.
-- Douglas Adams
----end random quote of the moment----
next prev parent reply other threads:[~2005-03-22 13:11 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
2005-03-22 12:20 ` Jan Engelhardt
2005-03-22 8:15 ` Sean Russell
2005-03-22 13:11 ` Mark Nipper [this message]
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=20050322131116.GA15512@king.bitgnome.net \
--to=nipsy@bitgnome.net \
--cc=ak@muc.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ser@ser1.net \
/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