mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Steven Cole <elenstev@mesatop.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.67, 2.5-bk lock up with RH 9 and graphical log out.
Date: 09 Apr 2003 22:43:34 +0200	[thread overview]
Message-ID: <1049921014.592.0.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <1049904293.24463.25.camel@spc9.esa.lanl.gov>

On Wed, 2003-04-09 at 18:04, Steven Cole wrote:
> With kernel 2.5.67 or 2.5-bk-current and Red Hat 9, if I try to do a
> graphical log out from either KDE or Gnome, the test machine locks up
> hard, not responding to pings, or alt-sysrq-anything. (and yes,
> /proc/sys/kernel/sysrq is 1 and I "fixed" /etc/sysctl.conf, line 13)
> 
> The same lockup happens with ctrl-alt-backspace from KDE or Gnome.
> 
> Doing an /sbin/init 3 works fine.  Harsh way to log out however.
> Subsequent cycles of startx and graphical "Log Out" do _not_ lock up
> the box, but work just fine.
> 
> Needless to say, with the vendor kernel, everything works perfectly. 
> Alt-sysrq-various behaves as expected. Ctrl-alt-backspace does not
> lock up the box.
> 
> If I get time, I'll try some older 2.5.x kernels to see if this is a
> recently introduced behavior.

.config? Are you using Framebuffer console support?
-- 
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198


  reply	other threads:[~2003-04-09 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 16:04 Steven Cole
2003-04-09 20:43 ` Felipe Alfaro Solana [this message]
2003-04-09 21:11   ` Steven Cole
2003-04-09 21:36     ` Steven Cole
2003-04-09 21:49       ` Andrew Morton
2003-04-09 22:25         ` Steven Cole

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=1049921014.592.0.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=elenstev@mesatop.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

all inboxes | Powered by JetHome®