X and/or powerflip and/or Elan (and/or user?) brain damage

Thread View: comp.sys.sgi.misc

2 messages

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

2 total messages Started by Jim Diamond Mon, 11 Jan 1993 22:20

#219

Author: Jim Diamond
Date: Mon, 11 Jan 1993 22:20

37 lines
2330 bytes

With an Indigo R3000 Elan running 4.0.5F:

I've had problems when using the powerflip / SGI logo combination as the
screen saver. Occasionally, this program hangs and I have to reset
the graphics system. After describing my woes to the hot line (sorry,
I guess that's an old name?), I've gotten two new graphics boards and
one new CPU board.

Since the new CPU board (most recent change), it has not yet hung the
graphics system, but it only happened sporadically anyway.

Today, I wanted to let it run overnight by starting it from
my toolchest. The line in the toolchest is

"SGI Logo" f.checkexpr "test -x /usr/sbin/haven -a -x /usr/demos/bin/powerflip -a -r /usr/demos/data/yaodl/logo.ydl" "/usr/sbin/haven /usr/demos/bin/powerflip -z /usr/demos/data/yaodl/logo.ydl"

But instead of the logo appearing for a moment (right after I choose
that entry from the toolchest) and then going away, a window occupying
about 95% of the screen stays there. (This window, except for not
occupying the whole screen, looks like what one expects to see when
this screen saver is in operation.) In /usr/adm/SYSLOG I find

Jan 11 16:52:55 axe Xsession: zsd: X Error of failed request: BadWindow (invalid Window parameter)
Jan 11 16:52:55 axe Xsession: zsd: Major opcode of failed request: 20 (X_GetProperty)
Jan 11 16:52:55 axe Xsession: zsd: Resource id in failed request: 0x34
Jan 11 16:52:55 axe Xsession: zsd: Serial number of failed request: 160
Jan 11 16:52:55 axe Xsession: zsd: Current serial number in output stream: 160

Can anyone shed some light on why this is happening? In previous
cases, logging out and in again fixes (temporarily) this problem.
But what is causing this problem? Should I ask for a new backplane?
Maybe a new power supply? ("Collect the whole set.")

Thanks.

Jim Diamond
zsd@axe.drea.dnd.ca

Re: X and/or powerflip and/or Elan (and/or user?) brain damage

#221

Author: Michael Toy
Date: Tue, 12 Jan 1993 01:03

17 lines
1550 bytes

In article <34956@adm.brl.mil> zsd@axe.drea.dnd.ca (Jim Diamond) writes:
>... /usr/adm/SYSLOG I find
>Jan 11 16:52:55 axe Xsession: zsd: X Error of failed request:  BadWindow (invalid Window parameter)
>Jan 11 16:52:55 axe Xsession: zsd:   Major opcode of failed request:  20 (X_GetProperty)
>Jan 11 16:52:55 axe Xsession: zsd:   Resource id in failed request:  0x34
>Jan 11 16:52:55 axe Xsession: zsd:   Serial number of failed request:  160
>Jan 11 16:52:55 axe Xsession: zsd:   Current serial number in output stream:  160
>
>Can anyone shed some light on why this is happening?  In previous
>cases, logging out and in again fixes (temporarily) this problem.
>But what is causing this problem?  Should I ask for a new backplane?
>Maybe a new power supply?  ("Collect the whole set.")

This is a bug in the X server.  When it gets in this mode, the only
solution is to kill the X server and the new one will come up
in the non-buggy state.  I am not responsible for the X server,
so I am not sure about this, but I believe this is not fixed in 4.anything.

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