From: Chris Wright <chris@wirex.com>
To: Erik McKee <camhanaich99@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.17 Problem
Date: Fri, 24 May 2002 15:45:58 -0700 [thread overview]
Message-ID: <20020524154558.A6590@figure1.int.wirex.com> (raw)
In-Reply-To: <20020523150539.1059.qmail@web14201.mail.yahoo.com>
* Erik McKee (camhanaich99@yahoo.com) wrote:
> Ok, I am becoming a frequent poster here. Nothing in the logs on this one
> either. Left 2.5.17 running overnight on this box which used to be rock solid
> unser 2.4. kde was running, with a screensaver. On attempting to use the box,
> mouse mvement did dispell the screensaver. alt-ctrl-f2 to get to a vc however
> left me with a clean black screen. Nothing worked....alt-sysrq -s or
> alt-sysrq-u ddin't produce any disk activity. alt-sys-rq-b did however reboot
> the system. only issue was unclean raid array afterwards ;)
is this, by chance, a UP machine with:
CONFIG_SMP=y
CONFIG_PREEMPT=y
i've been seeing regular kernel hangs obtaining the BKL with this
configuration.
thanks,
-chris
prev parent reply other threads:[~2002-05-24 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 15:05 2.5.17 Problem Erik McKee
2002-05-24 22:45 ` Chris Wright [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=20020524154558.A6590@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=camhanaich99@yahoo.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;
as well as URLs for NNTP newsgroup(s).