Bug 15143 - Only 2 seconds of alarm sound, then "nb alloc failed in slimproto" and a reboot
: Only 2 seconds of alarm sound, then "nb alloc failed in slimproto" and a reboot
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Alarm
: 7.4.1
: PC Windows Server 2003
: P3 normal with 3 votes (vote)
: ---
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-19 11:29 UTC by Walter ter Maten
Modified: 2011-05-25 18:54 UTC (History)
6 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Walter ter Maten 2009-11-19 11:29:06 UTC
I've got two Squeezeboxes at home (a classic V3 and a Boom), both connected to the same Slimserver, running on a 32bit Windows 2003 Enterprise Atom based server with 2 gig RAM, no firewall. Both players are wired connected.

I'm trying to setup the alarm clock. It doesn't matter which sound I choose (playlist, radio, sound effect, nature sound), when it tries to ring (both, it only plays about 2 seconds of the selected wakeup sound, then it gives a "nb alloc failed in slimproto" error, and the player (Boom and Classic, the one which tries to ring) reboots. After that, the player plays the backup alarm.

Tried it with 7.4.1 and the latest 7.4.2 build, both give the same problem.

There are no problems with listening to mp3's, radio stations or the Sound & Effects sounds directly from the main menu.

Squeezebox
Player Model: squeezebox3
Firmware: 130
Player IP Address: 192.168.1.14
Player MAC Address: 00:04:20:12:14:c1

Squeezebox Boom
Player Model: boom
Firmware: 50
Player IP Address: 192.168.1.18
Player MAC Address: 00:04:20:1f:02:41
Comment 1 Mark Fern 2009-11-20 20:43:37 UTC
I'm glad I saw this before upgrading from SC 7.3.  If the alarm doesn't ring, or in my case, the piano jazz music list, I might miss work.  Well, I wouldn't actually 'miss' work, but you get the idea.  Please take this bug, won't you, for our economy's sake??!
Comment 2 Walter ter Maten 2009-11-21 02:25:24 UTC
Well, it doesn't say you will have the same problem, because yesterday I tested it with running a Squeezeserver (7.4.1) on my laptop (Windows 7 Enterprise), and connected the Classic and the Boom to it: no problems at all with the alarm. So one of possibilities is that it has something to do with Windows 2003.

What I also tried: reducing my network, so only my Boom, server and internet router where physically connected to it (all wired, to exclude the fact that for example my accesspoint or mediacenter pc was messing something up), no result, still the same problem.
Comment 3 wbelectronics 2009-12-15 12:10:17 UTC
I have a similar problem, running 7.4.1 on a Windows 2003 R2 server, based on an Atom 1.6GHz / 2GB Ram machine.

3 x SB3 and 1 Boom attached, getting "nb alloc failed in slimproto" when pressing "Pause" on one of the SB3, and navigating the Boom often produces the same error, always followed by a reset-cycle.  Very annoying.

Running the exact same setup on a Win2k server (dual xeon, 2GB Ram) with 7.3.x before, with no problems for several years, then changed server-hardware and OS and at the same time upgrading to 7.4.1. Difficult to say if the problem is caused by 7.4.1 or Win2003 server.
Comment 4 Chris Owens 2010-02-11 18:00:16 UTC
I can't find this string in the server source.  Is this in the ip3k firmware, Felix?  What does it mean?  Any clues how I might be able to repro?
Comment 5 Felix Mueller 2010-02-11 20:39:07 UTC
Yes, that string is in ip3k firmware. Looking through the comments it strongly looks like it only happens when using together with Windows 2003.
Comment 6 Chris Owens 2010-03-08 11:17:16 UTC
Moving P3 and lower bugs to next release target
Comment 7 Jon Pawley 2011-05-25 18:53:56 UTC
The following bug also shows similar symptoms: https://bugs-archive.lyrion.org/show_bug.cgi?id=17259