From: Shaya Potter <spotter@cs.columbia.edu>
To: Jeff Chua <jeffchua@silk.corp.fedex.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Thinkpad t21 hard lockup when left overnight
Date: 23 Nov 2001 10:19:13 -0500 [thread overview]
Message-ID: <1006528755.627.4.camel@zaphod> (raw)
In-Reply-To: <002b01c1742e$607e6ba0$bc5812bc@corp.fedex.com>
In-Reply-To: <Pine.LNX.4.42.0111231154580.16590-100000@boston.corp.fedex.com> <1006489548.10497.8.camel@zaphod> <1006507120.627.0.camel@zaphod> <002b01c1742e$607e6ba0$bc5812bc@corp.fedex.com>
hmm. I think so, but I'll check it on my next reboot. This machine
used to survive the night just fine. I might try booting it into a
2.2.19 which I still have on my system, though I'm pretty sure it used
to work in 2.4 as well. Unfortunatly, I don't keep all my kernels
around.
shaya
On Fri, 2001-11-23 at 09:50, Jeff Chua wrote:
> Have you tried setting bios to "never suspend".
>
>
> From: "Shaya Potter" <spotter@cs.columbia.edu>
> To: "Shaya Potter" <spotter@opus.cs.columbia.edu>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Friday, November 23, 2001 5:18 PM
> Subject: Re: Thinkpad t21 hard lockup when left overnight
>
>
> just woke up to a locked up solid machine. It seemed to have locked up
> after about 2 hours of inactivity on the machine.
>
> shaya
>
>
--
spotter@{cs.columbia.edu,yucs.org}
http://yucs.org/~spotter/
prev parent reply other threads:[~2001-11-23 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 22:39 Thinkpad t21 hard lockup when left overnight Shaya Potter
2001-11-23 2:27 ` Jeff Chua
2001-11-23 2:43 ` Shaya Potter
2001-11-23 4:14 ` Jeff Chua
2001-11-23 4:25 ` Shaya Potter
2001-11-23 9:18 ` Shaya Potter
[not found] ` <002b01c1742e$607e6ba0$bc5812bc@corp.fedex.com>
2001-11-23 15:19 ` Shaya Potter [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=1006528755.627.4.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=jeffchua@silk.corp.fedex.com \
--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