From: Jorge Nerin <comandante@zaralinux.com>
To: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: funny console prob w/2.4.18-pre[479]+kpreempt+sched-o(1)
Date: Fri, 15 Feb 2002 17:17:57 +0100 [thread overview]
Message-ID: <3C6D34B5.3050900@zaralinux.com> (raw)
In-Reply-To: <3C66743C.9BA03219@folkwang-hochschule.de>
Jörn Nettingsmeier wrote:
> hello *
>
> it happens to me regularly that the x server dies without any
> obvious reason.
I remeber that some time ago, around XFree 4.0 I also had this issues.
> funny thing is, it takes the virtual text consoles with it, which is
> why i'm posting here.
>
Yes, the same issues, now it almost never dies, and if it dies the
consoles work ok (I'm using FB at 1024x768 and Xfree at 1152x864)
> i end up in kdm and i can restart x alright, but when i switch vc's,
> all i see is a frozen image of the x screen. i can switch back to x,
> and it runs.
>
When this happened to me I saw garbage from the X screen from the time
it died, let's see, X dies, I get dropped to the console (seeing garbage
colors of the scren) gdm restarts, everything seems ok, but going back
to the console you see the same garbage as before.
> all tasks i started on the vc's before keep running, the mingettys
> are there, the bashes are there, and i can even blind-type commands
> that will run correctly. only the display is messed up.
> a blind-typed "reset" has no effect.
>
I also found that enebling the xv extension in my XFree causes the
consoles to be lost, but in a different way.
After enabling it and entering X if I switch to a console I see the
console image, but no matter what I do the console stays the same, as
you say I can type blindly.
> any clues ?
> i'm using x version 4.2.0 with a voodoo3 card (dri and agp enabled).
> this is an smp box with 2 p3/600 katmai.
> might this be not a kernel issue, but an x11 problem ?
>
We have too many things in common to stablish a pattern, I'm using XFree
4.2.0, a voodoo 3 2000 pci card, and I also have a smp box, but it's a
2x200mmx.
I think it's a X issue by not leaving the console state consitent.
> best wishes,
>
> jörn
>
>
> please keep be cc:ed, i only read lkml archives.
>
I'm doing
--
Jorge Nerin
<comandante@zaralinux.com>
next prev parent reply other threads:[~2002-02-15 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 13:23 funny console prob w/2.4.18-pre[479]+kpreempt+sched-o(1) Jörn Nettingsmeier
2002-02-10 13:44 ` Marc Recht
2002-02-15 16:17 ` Jorge Nerin [this message]
2002-02-15 18:09 ` Fernando Korndorfer
2002-02-15 19:07 ` Samuel M. Stringham
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=3C6D34B5.3050900@zaralinux.com \
--to=comandante@zaralinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nettings@folkwang-hochschule.de \
/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