SIGSEGV kills X -bpp 16 on switch to VT

Thread View: comp.os.linux.x

4 messages

[T] Back to Threads [V] Tree View [G] Group Articles

4 total messages Started by Peter B. West Wed, 02 Apr 1997 00:00

#105

Author: Peter B. West
Date: Wed, 02 Apr 1997 00:00

16 lines
1028 bytes

Has anyone else had the problem of X being killed by a SIGSEGV when they
switch to a virtual terminal?  It only happens when I am running 16 bit
colour; 8 bit is OK.  It doesn't usually happen immediately I switch,
but fairly soon after.  My startup is via xdm.

I am running version 3.1.2 on an AST Bravo Pentium with an on-board
CL5434 controller.  OS is from RedHat 4.0; don't know the kernel version
off hand.

TIA,
Peter

 __ /__   Peter B. West
   /     p.west@mailbox.uq.edu.au
  /    "Master, to whom shall we go?"

Re: SIGSEGV kills X -bpp 16 on switch to VT

#102

Author: Albert K. Lee
Date: Sun, 06 Apr 1997 00:00

51 lines
2199 bytes

On 02 Apr 1997 18:13:33 GMT, Peter B. West <p.west@mailbox.uq.edu.au> wrote:
>Has anyone else had the problem of X being killed by a SIGSEGV when they
>switch to a virtual terminal?  It only happens when I am running 16 bit
>colour; 8 bit is OK.  It doesn't usually happen immediately I switch,
>but fairly soon after.  My startup is via xdm.
>
>I am running version 3.1.2 on an AST Bravo Pentium with an on-board
>CL5434 controller.  OS is from RedHat 4.0; don't know the kernel version
>off hand.
>
>TIA,
>Peter

I'm having the exact same problem.  And it'd be nice to know if there
are any fixes.  =)  Tho there are some situations where it'll segfault
and others where it won't.  Symptoms:

Let's say I start X with:

	bash$ X &

No problems so far ... I can switch between X and my VT just fine.
Now at my prompt, I type:

	xterm -display :0

and everything bombs.  When I'm using Netscape and I click on a text
field (like the "open location" box), then switch, X segfaults.  When
I'm using Netscape and there's nothing blinking but the "N" logo, VT
switches are fine.

Thus, it must have something to do with the X server's screen updates.
I tried this under twm, fvwm, and AfterStep with similar results, so
it's not the window manager's fault.

System Info?

I went for the X Consortium's release and compiled X11R6.3 (patched
w./ the first set of fixes) using a P5/100 with an STB Trio64 (vanilla
version).  Linux 2.0.29.  Used to be slackware 3.0, until I started
playing with its guts.  ;)  Oh, btw, I'm using the accelerated S3
server.

Anybody have any insights into this problem?

-Albert
 aklee@interport.net

Re: SIGSEGV kills X -bpp 16 on switch to VT

#103

Author: James Harper
Date: Mon, 07 Apr 1997 00:00

17 lines
1343 bytes

Peter B. West (p.west@mailbox.uq.edu.au) wrote:
: Has anyone else had the problem of X being killed by a SIGSEGV when they
: switch to a virtual terminal?  It only happens when I am running 16 bit
: colour; 8 bit is OK.  It doesn't usually happen immediately I switch,
: but fairly soon after.  My startup is via xdm.

: I am running version 3.1.2 on an AST Bravo Pentium with an on-board
: CL5434 controller.  OS is from RedHat 4.0; don't know the kernel version
: off hand.

i have a hippo 15 486DX4/100 with a pci cl5434 and experience exactly the same
problem. i always run 16bpp so i cannot say if it doesn't happen in other modes

bit of a pain sometimes, but there is something newer than 3.1.2 isn't there?

james

Re: SIGSEGV kills X -bpp 16 on switch to VT

#104

Author: Nelson Tibbitt
Date: Wed, 09 Apr 1997 00:00

46 lines
2547 bytes

> On 02 Apr 1997 18:13:33 GMT, Peter B. West <p.west@mailbox.uq.edu.au> wrote:
>>Has anyone else had the problem of X being killed by a SIGSEGV when they
>>switch to a virtual terminal?  It only happens when I am running 16 bit
>>colour; 8 bit is OK.  It doesn't usually happen immediately I switch,
>>but fairly soon after.  My startup is via xdm.
> 
> I'm having the exact same problem.  And it'd be nice to know if there
> are any fixes.  =)  Tho there are some situations where it'll segfault
> and others where it won't.  Symptoms:
> Let's say I start X with:
> 	bash$ X &
> No problems so far ... I can switch between X and my VT just fine.
> Now at my prompt, I type:
> 	xterm -display :0
> and everything bombs.  When I'm using Netscape and I click on a text
> field (like the "open location" box), then switch, X segfaults.  When
> I'm using Netscape and there's nothing blinking but the "N" logo, VT
> switches are fine.
> Thus, it must have something to do with the X server's screen updates.

I've had this problem throughout 3 different XFree86 versions 
(3.1.2, 3.2, and now 3.2A).  Using Linux 2.0.29 (was Red Hat 4.0),
a Panasonic CF-41 laptop with C&T65548 video, and the XF86_SVGA server.  

Mine will SIGSEGV consistently - 9 out of 10 times I switch from 
X to another tty.  This happens both in 8-bit and 16-bit color modes, 
apparently regardless of what is running. AHHH!!

It would be nice if, like everyone else, I could access the virtual 
consoles while running X.  

Does anyone have any insight as to the nature of this beast?

Thanks ahead of time,

Nelson Tibbitt

-----BEGIN GEEK CODE BLOCK-----
GAT d- s:+ !a C+(+++) UI/L/S/B++(+++) P>+ L+(++) E---- W+++ N+ o? K?
w++++ O--- M-- V PS+++@ PE Y-- PGP+ t++ 5 X++ R- tv+ b DI++ D+ G e>* 
h*(!) r- y*(+)
------END GEEK CODE BLOCK------
"Nobody goes there anymore - it's too crowded."

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads