Jay Estabrook wrote:
>
> That's important - that you see them primarily during boot, rather
> than often during normal operation. That's indicative of boot tasks
> that simply take a long time and happen to need to hold a lock during
> that time. I'd be much more concerned if these happened frequently
> during normal operation.
>
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
select.c:43 spinlock grabbed in pvmd3 at fffffc000035f630(0) 1949 ticks
socket.c:43 spinlock stuck in pvmd3 at fffffc00003c4368(1) owner zm32mig_s_pvm
at fffffc000034fb78(0) read_write.c:43
socket.c:43 spinlock grabbed in pvmd3 at fffffc00003c4368(1) 2024 ticks
sched.c:30 spinlock stuck in pvmd3 at fffffc000032cea4(1) owner zm32mig_s_pvm at
fffffc000034fb78(0) read_write.c:43
sched.c:30 spinlock grabbed in pvmd3 at fffffc000032cea4(1) 1943 ticks
socket.c:43 spinlock stuck in pvmd3 at fffffc00003c4368(1) owner zm32mig_s_pvm
at fffffc000034fb78(0) read_write.c:43
socket.c:43 spinlock grabbed in pvmd3 at fffffc00003c4368(1) 2062 ticks
socket.c:43 spinlock stuck in pvmd3 at fffffc00003c4368(0) owner zm32mig_s_pvm
at fffffc000034fb78(1) read_write.c:43
socket.c:43 spinlock grabbed in pvmd3 at fffffc00003c4368(0) 2267 ticks
Wes
-- 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.