On Tue, Jun 13, 2000 at 01:12:10PM -0500, W Bauske wrote:
>
> They happen alot on my UP2K's in production.
>
> socket.c:43 spinlock grabbed in pvmd3 at fffffc00003c4368(0) 2032 ticks
> select.c:43 spinlock stuck in pvmd3 at fffffc000035f630(0) owner zm32mig_s_pvm
> at fffffc000034fb78(1) read_write.c:43
> select.c:43 spinlock grabbed in pvmd3 at fffffc000035f630(0) 2033 ticks
> select.c:43 spinlock stuck in pvmd3 at fffffc000035f630(0) owner zm32mig_s_pvm
> at fffffc000034fb78(1) read_write.c:43
Sigh...
Not knowing whether x86/sparc/whatever code has any sort of similar
debug output, it's hard to know if this is "normal" behavior".
Perhaps the PVM stuff could be better organized or rewritten to cause
the holding of locks (at its behest) to be shorter?
As a last resort, if one tires of seeing those messages, one could up
the default "timeout" value in the debugging locks code to wait for a
longer time before giving the message... :-\
--Jay++
-----------------------------------------------------------------------------
Jay A Estabrook Alpha Engineering - LINUX Project
Compaq Computer Corp. - MRO1-2/K20 (508) 467-2080
200 Forest Street, Marlboro MA 01752 Jay.Estabrook@compaq.com
-----------------------------------------------------------------------------
-- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
This archive was generated by hypermail version 2a22 on Sat Jul 1 05:31:30 2000 PDT
Send any problems or questions about this archive to webmaster@alphalinux.org.