xset r rate -> memory fault

xset r rate -> memory fault

Post by Jan Schauman » Sun, 24 Feb 2002 00:48:38



Hi all,

I'm puzzled by the fact that "xset r rate 500 30" gives me a
memory-fault (with core dump), but at the same time, if I start the X
server with "-ar1 500 -ar2 30" everything works as expected.

Does this ring a bell with anybody?  Anybody know a solution, a
workaround, or where to look?

This is on a NetBSD 1.5.3_ALPHA/i386 with XFree86 Version 4.0.99.3, and a
"set -q" as follows:


Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  auto repeat delay:  500    repeat rate:  30
  auto repeating keys:  00ffffffdffffbbf
                        fa9fffffffdffdff
                        ffffffffffffffff
                        ffffffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100

[...]

DPMS (Energy Star):
  Standby: 0    Suspend: 900    Off: 7200
  DPMS is Enabled
  Monitor is On
Font cache:
  hi-mark (KB): 1024  low-mark (KB): 768  balance (%): 70

TIA for all pointers,

-Jan

--
Jan Schaumann <http://www.netmeister.org>

"Life," said Marvin dolefully, "loathe it or ignore it, you can't like it."

 
 
 

xset r rate -> memory fault

Post by Jan Schauman » Mon, 25 Feb 2002 01:11:34



>  I'm puzzled by the fact that "xset r rate 500 30" gives me a
>  memory-fault (with core dump), but at the same time, if I start the X
>  server with "-ar1 500 -ar2 30" everything works as expected.

Yikes!  Wrong group!

I don't know how the hell that happened.  Sorry folks.

(FWIW, upgrading to XFree86 4.1.0 fixed the problem.)

-Jan

--
Jan Schaumann <http://www.netmeister.org>

unless ($humorEnabled || $canDetectSarcasm)
    {printf "Please add Smileys where appropriate.";}

 
 
 

1. Kernel 1.1.52==>memory problems-->segmentation fault

BACKGROUND:
I just upgraded from slackware's standard kernel to 1.1.52.  My kernel
compiled fine, it boots with no error messages, I can login, and I can
run XWindows (I'm using it now).

PROBLEM:
When I run "top" I get a "segmentation fault" message only (no other
information).

When I run sasteroids I get "svgalib:  Cannot open /dev/mem".

What have I done wrong?  Both of the above worked with my original kernel.  
E-mail or post here.  Thanks in advance.

Regards,

Albert

2. NGS's Oval server problems

3. mozilla -> compiled + Memory Faults

4. Message Log Question

5. sh error message -> sh: 6919 memory fault

6. gpm/Mouse doesn't work correctly

7. Get >>> 1GB / 2GB <<<< USB Flash Memory Drive

8. Network failure during heavy traffic

9. >>DCI Conferences at Discount Rates

10. xset +fp /tcp/<hp-ux_server_name>:7000 hangs on Solaris 10

11. wake_up_interruptible(&tty->read_wait) => seg-fault?