1 Jun 2008 01:00
Re: bad wsmouse event
Michael Lorenz <macallan <at> netbsd.org>
2008-05-31 23:00:53 GMT
2008-05-31 23:00:53 GMT
Hello, On May 31, 2008, at 09:24, raymond.meyer <at> rambler.ru wrote: > Hi, I sometimes experience Xserver crashes on Ultra10 with Creator3D > framebuffer, maybe it's something to do with sunffb driver or > something else. > The screen gets garbled and frozen, this always happens due to some > action, > like moving a mouse (I use a USB mouse and keyboard). You don't have an ffb1, do you? > I looked at my XFree86.log file and noticed the following lines > > WW) Mouse0: bad wsmouse event type=1792 > (WW) Mouse0: bad wsmouse event type=1536 > (WW) Mouse0: bad wsmouse event type=1792 > (WW) Mouse0: bad wsmouse event type=1536 > ... > (WW) Mouse0: bad wsmouse event type=458751 > (WW) Mouse0: bad wsmouse event type=458751 > (WW) Mouse0: bad wsmouse event type=458751 > (WW) Mouse0: bad wsmouse event type=458751 > ... > (WW) Mouse0: bad wsmouse event type=117440511 > (WW) Mouse0: bad wsmouse event type=117440511 > (WW) Mouse0: bad wsmouse event type=117440511 > (WW) Mouse0: bad wsmouse event type=117440512(Continue reading)



I
get the following:
mlx0 at pci0 dev 2 function 0: Mylex RAID (v3 interface)
mlx0: interrupting at ivec 10
mlx0: initializing (may take some time)...
mlx0: physical drive 2:0 not responding
mlx0: physical drive 2:1 not responding
mlx0: physical drive 2:2 not responding
mlx0: physical drive 2:3 not responding
mlx0: logical drive installation aborted
mlx0: initialization complete
mlx0: DAC960P/PD, 3 channels, firmware 3.51-0-09, 4MB RAM
ppb0 at pci0 dev 4 function 0: Intel product 0x0960 (rev. 0x03)
pci1 at ppb0 bus 1
mlx1 at pci0 dev 4 function 1: Mylex RAID (v4 interface)
mlx1: interrupting at ivec 18
mlx1: DAC960PG, 2 channels, firmware 4.06-0-85, 16MB RAM
ppb1 at pci0 dev 5 function 0: Digital Equipment DC21154 PCI-PCI
Bridge (rev. 0x02)
pci2 at ppb1 bus 2
Distributed Processing Technology Memory Controller (miscellaneous
memory, revision 0x02) at pci2 dev 3 function 0 not configured
iop0 at pci2 dev 4 function 0: I2O adapteriop0: reset rejected, status
0x0
iop0: not responding (reset)
basically the whole setup looks fishy to me. mlx0 gets initialized,
mlx1 not. And the DPT PM3755U2B controller (which is basically the
single channel version of the SUN SRC/P controller) is not accessible
RSS Feed