Michael Lorenz | 1 Jun 01:00 2008
Picon

Re: bad wsmouse event


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)

raymond.meyer | 1 Jun 03:58 2008
X-Face
Picon

Re: bad wsmouse event

On Sunday 01 June 2008 00:00:53 Michael Lorenz wrote:
> You don't have an ffb1, do you?
>
No, this is FFB2+
The Xserver crashes are rare, but when it does happen most of the screen gets 
garbled, i.e. I see coloured horizontal stripes across the screen. 

Michael Lorenz | 1 Jun 04:16 2008
Picon

Re: bad wsmouse event


Hello,

On May 31, 2008, at 21:58, raymond.meyer <at> rambler.ru wrote:

> On Sunday 01 June 2008 00:00:53 Michael Lorenz wrote:
>> You don't have an ffb1, do you?
>>
> No, this is FFB2+

Damn, it's never the easy explanation ;)

> The Xserver crashes are rare, but when it does happen most of the  
> screen gets
> garbled, i.e. I see coloured horizontal stripes across the screen.

I've never seen anything like that. Is it only the Xserver or does  
the whole machine crash? ( as in - can you still ssh into the machine  
and look around? If you can please attach a gdb to the running  
Xserver and try to provoke the crash, then see what gdb thinks  
happened )

have fun
Michael

Michael Lorenz | 1 Jun 04:27 2008
Picon

Re: bad wsmouse event


Hello,

On May 31, 2008, at 21:58, raymond.meyer <at> rambler.ru wrote:

> On Sunday 01 June 2008 00:00:53 Michael Lorenz wrote:
>> You don't have an ffb1, do you?
>>
> No, this is FFB2+

Damn, it's never the easy explanation ;)

> The Xserver crashes are rare, but when it does happen most of the  
> screen gets
> garbled, i.e. I see coloured horizontal stripes across the screen.

I've never seen anything like that. Is it only the Xserver or does  
the whole machine crash? ( as in - can you still ssh into the machine  
and look around? If you can please attach a gdb to the running  
Xserver and try to provoke the crash, then see what gdb thinks  
happened )

have fun
Michael

raymond.meyer | 1 Jun 13:36 2008
X-Face
Picon

Re: bad wsmouse event

> I've never seen anything like that. Is it only the Xserver or does
> the whole machine crash? ( as in - can you still ssh into the machine
> and look around? If you can please attach a gdb to the running
> Xserver and try to provoke the crash, then see what gdb thinks
> happened )

I think it's just the Xserver, everything else is unaffected. Similar crash 
happened a few days ago, I was playing music via mpd daemon, then I moved a 
mouse to the top menu in konqueror and the screen got corrupted and froze, 
but the daemon was still playing music normally.

How do I cause gdb to provoke a crash on the attached process?

Michael Lorenz | 1 Jun 14:37 2008
Picon

Re: bad wsmouse event


Hello,

On Jun 1, 2008, at 07:36, raymond.meyer <at> rambler.ru wrote:

>> I've never seen anything like that. Is it only the Xserver or does
>> the whole machine crash? ( as in - can you still ssh into the machine
>> and look around? If you can please attach a gdb to the running
>> Xserver and try to provoke the crash, then see what gdb thinks
>> happened )
>
> I think it's just the Xserver, everything else is unaffected.  
> Similar crash
> happened a few days ago, I was playing music via mpd daemon, then I  
> moved a
> mouse to the top menu in konqueror and the screen got corrupted and  
> froze,
> but the daemon was still playing music normally.

Ok, so it's really just the Xserver.

> How do I cause gdb to provoke a crash on the attached process?

You don't. All gdb will do is to tell you what crashed where and how.  
Attach gdb, see if you can provoke the crash somehow, let gdb catch  
it and hope it gives us something useful.

Are you using XFree86 from xsrc or something home-built or Xorg?

have fun
(Continue reading)

raymond.meyer | 1 Jun 14:46 2008
X-Face
Picon

Re: bad wsmouse event

On Sunday 01 June 2008 13:37:42 Michael Lorenz wrote:
> You don't. All gdb will do is to tell you what crashed where and how.
> Attach gdb, see if you can provoke the crash somehow, let gdb catch
> it and hope it gives us something useful.
>
> Are you using XFree86 from xsrc or something home-built or Xorg?

Yeah it's XFree86 from xsrc, I'll see if I can get some info with gdb

Yves Donkof | 2 Jun 11:25 2008

order

Hello,

We are Donkof S.A.R.L in Ivory Coast and we contact you with an aim of weaving a business connection with your company.
We wish to buy articles with you and to be delivered by UPS or Fedex

Our order will be paid in advance by credit card Visa or Mastercard.

Cordially

ETS DONKOF S.A.R.L
01 BP 1236 ABJ01
TEL  225 01262608
RUE DE LA JAT

El cine latino llega al Festival de Cannes. ¡No te pierdas la gran cita del entretenimiento! http://mx.starmedia.com/entretenimiento/especiales/cannes.html
Jan-Hinrich Fessel | 2 Jun 22:10 2008

Re: mlx on sparc?

Now that I was donated a set of mlx boards with newer firmware ;-) 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  
(Continue reading)

Andrew Doran | 2 Jun 22:30 2008
Picon

Re: mlx on sparc?

On Mon, Jun 02, 2008 at 10:10:55PM +0200, Jan-Hinrich Fessel wrote:

> Now that I was donated a set of mlx boards with newer firmware ;-) 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

Seems ok, it needs a configuration (and some disks by the look of it).

> 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
> 
> basically the whole setup looks fishy to me. mlx0 gets initialized,  
> mlx1 not.

(Continue reading)


Gmane