From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200304042152.h34LqF224782@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24743.1049493134.1@zamenhof.cs.utwente.nl> Subject: [9fans] lock loop messages (anything particular I should do?) Date: Fri, 4 Apr 2003 23:52:14 +0200 Topicbox-Message-UUID: 8a5a2428-eacb-11e9-9e20-41e7f4b1d025 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.