mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Samuel M. Stringham" <sams@e-sa.com>
To: Jorge Nerin <comandante@zaralinux.com>
Cc: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>,
	linux-kernel@vger.kernel.org
Subject: Re: funny console prob w/2.4.18-pre[479]+kpreempt+sched-o(1)
Date: 15 Feb 2002 14:07:47 -0500	[thread overview]
Message-ID: <1013800067.6448.11.camel@linux-admin.esa-hq.e-sa.com> (raw)
In-Reply-To: <3C6D34B5.3050900@zaralinux.com>
In-Reply-To: <3C66743C.9BA03219@folkwang-hochschule.de>  <3C6D34B5.3050900@zaralinux.com>

[-- Attachment #1: Type: text/plain, Size: 2921 bytes --]


On Fri, 2002-02-15 at 11:17, Jorge Nerin wrote:
> 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)
> 
hmm... I had the same problem as the original poster with 4.0, not with
4.1 and rawhides 4.2 XFree86 packages won't even let me start up with
dri+OpenGL (different problem).  I will try to rebuild X from source
tonight see if I can garner some insight.
> > 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.
> 
yes, I get/got this too, hasn't happened recently, but then again X
hasn't crashed recently.  Another thing (I believe was fbdev related)
was the screwing up of the fonts (! missing the dot at the bottom,
etc.).  I believe that was fixed circa 2.4.17/2.5.2 .
> > 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.
> 
yes, same as above, this is a rather coincidental about the HW configs.
I have a dual celeron (famous bp6 config) with vodoo3 with dri and agp
enabled.
> > best wishes,
> > 
> > jörn
> > 
> > 
> > please keep be cc:ed, i only read lkml archives.
> > 
> 
> I'm doing
> 
> 
> -- 
> Jorge Nerin
> <comandante@zaralinux.com>
> 
> -

Samuel Stringham
Network Administrator
www.e-sa.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

      parent reply	other threads:[~2002-02-15 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10 13:23 Jörn Nettingsmeier
2002-02-10 13:44 ` Marc Recht
2002-02-15 16:17 ` Jorge Nerin
2002-02-15 18:09   ` Fernando Korndorfer
2002-02-15 19:07 ` Samuel M. Stringham [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=1013800067.6448.11.camel@linux-admin.esa-hq.e-sa.com \
    --to=sams@e-sa.com \
    --cc=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

all inboxes | Powered by JetHome®