John D. Baker | 11 Nov 2004 19:28

keyboard problems with X11

I've been experiencing some strange problems with the keyboard on my
SPARCstation 5 when X is active.

At the xdm login widget, the keyboard beeps for every keypress, as if
it's experiencing buffer overflow.  Login is not affected, however.

Once logged in, the keyboard no longer beeps, but it will not autorepeat,
although 'xset q' reports that autorepeat is enabled.

At the text/raster console, the above problems do not appear.  The
keyboard is silent and it autorepeats normally.

The problems also do not appear when running Solaris 9, with or
without X11 active.

I first encountered these problems when I updated to NetBSD/sparc v1.6Q
and it has persisted through every update through the 2.0G snapshot of
15 July 2004 (the most recent Xserver installed).  I'm now running
2.99.10 (except for src/xsrc which I did not rebuild).

Has anyone else experienced either of these problems?  Any suggestions
about what may be causing them and how to correct it (if it isn't a
software problem)?

--

-- 
John D. Baker, KN5UKS                    NetBSD     Darwin/MacOS X
jdbaker(at)mylinuxisp(dot)com                 OpenBSD            FreeBSD
BSD -- It just sits there and _works_!

(Continue reading)

Brett Lymn | 12 Nov 2004 01:05
Picon

Re: keyboard problems with X11

On Thu, Nov 11, 2004 at 12:28:58PM -0600, John D. Baker wrote:
> 
> At the xdm login widget, the keyboard beeps for every keypress, as if
> it's experiencing buffer overflow.  Login is not affected, however.
> 

It sounds like you have login and getty fighting over the keyboard.  Have
you set up your xdm to use a different vt (or am I thinking i386 here...
I cannot recall if sparc has virtual terminals or not).  Something to
check anyway.

--

-- 
Brett Lymn

Robert Mohr | 13 Nov 2004 01:19
Favicon

FW: keyboard problems with X11


I have experienced the exact same symptoms since upgrading from 1.6.2 stable
to 2.0RC3 and then 2.0RC4.  System is also a SPARCStation 5.

I had attributed it to changes in/to xfree86.  The XDM login dialog changed
significantly from 1.6.2 to 2.0RC3.

Rob

-----Original Message-----
From: port-sparc-owner <at> NetBSD.org [mailto:port-sparc-owner <at> NetBSD.org] On
Behalf Of John D. Baker
Sent: Thursday, November 11, 2004 1:29 PM
To: port-sparc <at> NetBSD.org
Subject: keyboard problems with X11

I've been experiencing some strange problems with the keyboard on my
SPARCstation 5 when X is active.

At the xdm login widget, the keyboard beeps for every keypress, as if
it's experiencing buffer overflow.  Login is not affected, however.

Once logged in, the keyboard no longer beeps, but it will not autorepeat,
although 'xset q' reports that autorepeat is enabled.

At the text/raster console, the above problems do not appear.  The
keyboard is silent and it autorepeats normally.

The problems also do not appear when running Solaris 9, with or
without X11 active.
(Continue reading)

John D. Baker | 14 Nov 2004 21:20

Re: keyboard problems with X11

I did some poking around with 'xset' and noticed that the values shown
for autorepeat delay/rate were 660/25.  This seemed a little odd, so I
reprogrammed the delay/rate to something more common:

    xset r rate 250 10

and autorepeat started working again.  Adding this command to Xsetup_0
or GiveConsole did not affect the state of the server once the session
had started, but adding it to my .xsession file enables autorepeat when
I log in.  If the delay/rate are reprogrammed back to 660/25, autorepeat
stops working again.

Based on what I observed, I suspected that the beep-on-every-keypress
problem may be related to having 'keyclick' enabled somehow.  Adding:

    xset c 0

to Xsetup_0 did not change the behavior.  Once the user has logged in,
the keyboard no-longer beeps on keypress, so there's no need to add
anything to .xsession.

Maybe this can point to what's going on?

--

-- 
John D. Baker, KN5UKS                    NetBSD     Darwin/MacOS X
jdbaker(at)mylinuxisp(dot)com                 OpenBSD            FreeBSD
BSD -- It just sits there and _works_!

Matthias Scheler | 16 Nov 2004 06:09
Picon
Favicon

Re: Performance?

In article <20041023082648.GA26133 <at> yuba.kcn.ne.jp>,
	Henry Nelson <netb <at> yuba.kcn.ne.jp> writes:
>> gcc -mcpu=v8 -mtune=supersparc
> May I assume this is good for the SPARCclassic, which is also sun4m?

No, because it has only a MicroSPARC and not a SuperSPARC CPU. Use only
"-mcpu=v8" in this case.

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Matthias Scheler | 16 Nov 2004 06:10
Picon
Favicon

Re: Performance?

In article <20041023.180055.2004144808.johan <at> giantfoo.org>,
	"Johan A.van Zanten" <johan <at> giantfoo.org> writes:
> I would put them in CFLAGS.

It's never a good idea to predefine "CFLAGS". The correct variable
is "CPUFLAGS".

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Christian Corti | 16 Nov 2004 11:16
Picon
Picon
Favicon

Memory leaks

I've still got severe memory leaks with NetBSD on a SMP SS10 with 320MB of 
RAM. The machine is only running as a mail server with Postfix as the MTA. 
The current kernel is 2.0_RC4, and in my opinion the problem got much 
worse than with previous releases. I still have to reboot the machine once 
a day otherwise it will stop with errors such as "out of buffer space" and 
the like. vmstat -m  reports about 10MB allocated and will grow up to 
nearly 70MB without ever decreasing. This kernel is definitely *NOT* a 
release candidate!
For more details please look at my previous postings to this group.

Christian Corti

Havard Eidnes | 16 Nov 2004 17:30
Picon
Picon

Re: Memory leaks

> I've still got severe memory leaks with NetBSD on a SMP SS10
> with 320MB of RAM. The machine is only running as a mail server
> with Postfix as the MTA.  The current kernel is 2.0_RC4, and in
> my opinion the problem got much worse than with previous
> releases. I still have to reboot the machine once a day
> otherwise it will stop with errors such as "out of buffer
> space" and the like. vmstat -m reports about 10MB allocated and
> will grow up to nearly 70MB without ever decreasing. This
> kernel is definitely *NOT* a release candidate!  For more
> details please look at my previous postings to this group.

It would probably/hopefully help if you logged this as a formal
problem report.

Please make sure to include in the problem report the output from
"vmstat -m" on a fresh boot and after a day's operation.

Alternatively, if you don't want to log a formal problem report,
at least include those two outputs in a reply to this message.

Hopefully that will help narrow down the problem somewhat (it's
probably not sufficient to find the bug, but it'll hopefully
bring us a little closer).

Please also include the dmesg from your system.

Regards,

- Håvard

(Continue reading)

Havard Eidnes | 16 Nov 2004 20:39
Picon

Re: Memory leaks

Hi again, replying to my own message:

> Please make sure to include in the problem report the output from
> "vmstat -m" on a fresh boot and after a day's operation.

I notice that if it's not too burdensome, it would probably help
to do this with a kernel compiled with the KMEMSTATS option
turned on.  Note that this will have some negative performance
impact; hopefully your machine can cope with the added workload.

Regards,

- Håvard

Greg Earle | 17 Nov 2004 16:07
Picon
Picon

Can't unmount NFS mount - "permission denied"?!?

I tried my first-ever NFS mount, mounting a directory from my
Ultra 60 running Solaris 9 onto my SPARCserver 20 running NetBSD 1.6.2.

It mounted OK, but accesses to the mount point hang:

isolar# mount
/dev/sd2a on / type ffs (local)
/dev/sd2d on /var type ffs (local)
/dev/sd2g on /usr type ffs (local)
/dev/sd2f on /home type ffs (local)
/dev/cd0a on /cdrom type cd9660 (read-only, local)
mfs:129 on /tmp type mfs (synchronous, local)
procfs on /proc type procfs (read-only, local)
solaris9box:/export/home/earle/Maildir/.SPAM/cur on /mnt type nfs 
(read-only)

[7:00] isolar:~ % /bin/ls /mnt
[... hangs ...]

Even more worrisome, I can't unmount it:

isolar# umount /mnt
umount: /mnt: Permission denied
isolar# umount -f /mnt
umount: /mnt: Permission denied
isolar#

The mounted directory is only readable by me on the other end:

isolar# ls -l / | grep mnt
(Continue reading)


Gmane