stumpwm-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [STUMP] Recursive lock attempt error


From: Yann Ramin
Subject: Re: [STUMP] Recursive lock attempt error
Date: Mon, 22 Sep 2008 17:36:57 -0700
User-agent: Thunderbird 2.0.0.16 (X11/20080724)

I got this on my laptop quite a bit. I think I've managed to mask the
problem by setting the sbcl/stumpwm processor affinity to just include a
single processor. The syscall on Linux is sched_setaffinity

Interestingly, on my 8 processor workstation, I never run into this
problem. Only on the dual processor laptop. This may just be voodoo and
have nothing to do with anything :-)

Stefan Reichör wrote:
> Hi!
> 
> I use stumpwm daily at work. I get the following error 6-7 times a day.
> stumpwm restarts itself and I can continue to work with all my open
> applications.
> 
> But it would be nice to see this problem fixed.
> 
> 
> Thanks,
>   Stefan.
> 
> Recursive lock attempt #S(SB-THREAD:MUTEX
>                           :NAME "Scheduler lock"
>                           :%OWNER NIL
>                           :STATE 0).
> 0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {B3ADAED}>)[:EXTERNAL]
> 1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM {B3ADA99}>)
> 2: (STUMPWM::BACKTRACE-STRING)
> 3: ((LAMBDA (STUMPWM::C)) #<SIMPLE-ERROR {B3AD861}>)
> 4: (SIGNAL #<SIMPLE-ERROR {B3AD861}>)[:EXTERNAL]
> 5: (ERROR "Recursive lock attempt ~S.")[:EXTERNAL]
> 6: (SB-THREAD:GET-MUTEX
>     #<unavailable argument>
>     #<unavailable argument>
>     #<unavailable argument>)
> 7: ((FLET SB-THREAD::%CALL-WITH-SYSTEM-MUTEX))
> 8: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-SYSTEM-MUTEX]268))
> 9: ((FLET #:CLEANUP-FUN-[RUN-EXPIRED-TIMERS]636))[:CLEANUP]
> 10: (SB-IMPL::RUN-EXPIRED-TIMERS)
> 11: ((FLET #:WITHOUT-INTERRUPTS-BODY-[INVOKE-INTERRUPTION]11))
> 12: (SB-SYS:INVOKE-INTERRUPTION
>      #<CLOSURE (FLET SB-UNIX::INTERRUPTION) {A9CFDD}>)
> 13: ((FLET SB-UNIX::RUN-HANDLER)
>      14
>      #.(SB-SYS:INT-SAP #X00238008)
>      #.(SB-SYS:INT-SAP #X00A9D5B8))
> 14: ("foreign function: call_into_lisp")
> 15: ("foreign function: funcall3")
> 16: ("foreign function: interrupt_handle_now")
> 17: ("foreign function: interrupt_handle_pending")
> 18: ("foreign function: handle_trap")
> 19: ("foreign function: #x8053F7A")
> 20: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]469))
> 21: ((LAMBDA ()))
> 22: ((LAMBDA ()))
> 23: ((FLET SB-THREAD::%CALL-WITH-SYSTEM-MUTEX))
> 24: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-SYSTEM-MUTEX]268))
> 25: (SB-THREAD::CALL-WITH-SYSTEM-MUTEX
>      #<CLOSURE (LAMBDA #) {B352E5D}>
>      #S(SB-THREAD:MUTEX
>         :NAME "Scheduler lock"
>         :%OWNER #<SB-THREAD:THREAD "initial thread" {B2635A9}>
>         :STATE 1)
>      NIL)
> 26: (SB-EXT:UNSCHEDULE-TIMER #<SB-EXT:TIMER {B34D051}>)
> 27: ((FLET #:|CLEANUP-FUN-[#:G1102]1106|))[:CLEANUP]
> 28: (XLIB:EVENT-LISTEN #<XLIB:DISPLAY :0 (The X.Org Foundation R60802000)> 59)
> 29: (STUMPWM::STUMPWM-INTERNAL-LOOP)
> 30: (STUMPWM::STUMPWM-INTERNAL-LOOP)[:EXTERNAL]
> 31: (STUMPWM::STUMPWM-INTERNAL ":0")
> 32: (STUMPWM ":0")
> 33: ((LAMBDA ()))
> 34: ((LABELS SB-IMPL::RESTART-LISP))
> 
> 
> _______________________________________________
> Stumpwm-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/stumpwm-devel

-- 

     < Your System ate a SPARC! Gah! >
      -------------------------------
             \   ^__^
              \  (xx)\_______
                 (__)\       )\/\
                  U  ||----w |
                     ||     ||





reply via email to

[Prev in Thread] Current Thread [Next in Thread]