linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Polymorphic Anomaly <linux.geeke@verizon.net>
To: Tobias Diedrich <ranma@gmx.at>
Cc: Jeffrey Ingber <jhingber@ix.netcom.com>,
	linux-kernel@vger.kernel.org, xpert@XFree86.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [FIXED] Random Sig'11 in XF864 with kernel > 2.2.x
Date: Tue, 18 Sep 2001 05:28:15 -0500	[thread overview]
Message-ID: <3BA721BF.30C37C52@verizon.net> (raw)
In-Reply-To: <3BA6D4C0.1010309@ix.netcom.com> <20010918103121.B763@router.ranmachan.dyndns.org>

I have had this problem as well, and i finally gave up until i could get a Voodoo
or Rage 128, which have DRM, etc etc. My current card is a savage 4.  After
tryintg all the patches and everything. i finally just disabled the nice
framebuffer consoles so that when X crashes it doesnt take the consoles with it..
does anyone knoe of a real fix?

Poly


Tobias Diedrich wrote:

> Jeffrey Ingber wrote:
>
> > The problem mentioned in the following threads:
> >
> > http://www.uwsg.indiana.edu/hypermail/linux/kernel/0109.1/0932.html
> > http://www.xfree86.org/pipermail/xpert/2001-September/011055.html
> > http://www.xfree86.org/pipermail/xpert/2001-September/011230.html
> >
> > Is fixed in at least 2.4.9-ac10.  I haven't been a regular user of the
> > -ac series so I can't say when exactly this was fixed.  However, this
> > problem still persists in Linus 2.4.10-pre10.  Can anyone who chimed in
> > with similar problems to mine try said kernel (2.4.9-ac10) and provide
> > any feedback?  It would excellent if the exact fix could be identified.
>
> I'm using ac-10 with the preempt patch at the moment and still have
> trouble with the X server segfaulting sometimes.
> Usually it does this not that often (once a day to once every few days),
> it seems more likely to happen when switching between text mode console
> and X, I can increase the likelyhood of this by running the wmcpu and
> wmsysmon applets, which will often make it segfault after only a few minutes.
> System is Dual Celeron 433 on an ABIT BP6 board. XFree 4.1.0. Debian
> unstable. Riva TNT, using the nv driver. (I sometimes switch to the
> nvidia driver because this supports the xvideo extensions, but have not
> since the last reboot, so the proprietary module should not have been
> loaded)
> The most annoying thing is that the console is stuck in graphics mode
> after the server crashed...
>
> --
> Tobias                                                          PGP: 0x9AC7E0BC
> Hannover Fantreffen ML: mailto:fantreffen-request@mantrha.de?subject=subscribe
> Manga & Anime Treff Hannover: http://www.mantrha.de/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      reply	other threads:[~2001-09-18 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18  4:59 [FIXED] Random Sig'11 in XF864 with kernel > 2.2.x Jeffrey Ingber
2001-09-18  8:31 ` Tobias Diedrich
2001-09-18 10:28   ` Polymorphic Anomaly [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=3BA721BF.30C37C52@verizon.net \
    --to=linux.geeke@verizon.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jhingber@ix.netcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranma@gmx.at \
    --cc=xpert@XFree86.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).