9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] lock loop messages (anything particular I should do?)
Date: Fri,  4 Apr 2003 23:52:14 +0200	[thread overview]
Message-ID: <200304042152.h34LqF224782@zamenhof.cs.utwente.nl> (raw)

Just got a scrolling screen of 'lock loop' messages (for playlistfs).
Not having seen this before I was just wondering if there was something
someone might want me to do/look at before (or after?) I just switch
off the machine (and, later, try to fix my bugs).
I don't care about (rebooting) the machine.


Background:
I have been playing with Sape's classic/srv/juke, to add in support
for ogg and probably overlooked something. At least I succeeded to
break the update from playlistfs to the Error pane of classicjuke,
at least that I guess from the debugging output I got.
However, I suppose I will be able to fix that, that's not the
reason I'm posting this.

I'm testing what I did on a diskless terminal at home (booted over
the net of the office fs).  The terminal now seems to hang, more or less,
apart from the following text scrolling (slowly) over the screen:

lock 0x8029bd68 loop key 0xdeaddead pc 0x80104e08 held by pc 0x0104e08 proc 486
486: playlistfs pc 5311 dbgpc 139a Fault(Running) ut 0 st 0 bss c3000 qpc 0 nl 1 nd 0 lpc 80125c4e
486: playlistfs pc 5311 dbgpc 139a Fault(Running) ut 0 st 0 bss c3000 qpc 0 nl 1 nd 0 lpc 80125c4e
(and here it repeats with the 'lock' line)

I got that after in the player program the decoder (vorbisdec) died,
maybe several times in a row, each for a different song.


Axel.


             reply	other threads:[~2003-04-04 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 21:52 Axel Belinfante [this message]
2003-04-04 22:03 ` Sape Mullender
2003-04-04 22:03 ` Axel Belinfante
2003-04-04 22:12   ` Sape Mullender
2003-04-04 22:51     ` Axel Belinfante
2003-04-05  2:00       ` David Presotto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304042152.h34LqF224782@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).