ksock_rw is part of the Hijack FTP/HTTP daemon.

That's the problem - you have more RAM. The caching routine is designed around the normal 16MB. It is extremely aggressive, in that it completely tries to fill the cache each time. The issue is that it performs the disk reads and buffers the data into the kernel memory space, flooding out other processes. While memory support was added to the 2.01 kernel, there were no known changes to the caching mechanism. Thus the aggressive caching tuned to 16MB becomes a psychotic serial killer with 64MB.

The error you are seeing might be another symptom of this memory limitation. Question - do you notice the same behavior if the player is paused? This is just a test to see if it is the cache (assuming that the paused player fills the cache and then rests once it is full) or the player application in general.

How about if I have an even larger ReserveCache and only leave the player about 16mb or so?

Putting the playing into Pause resolves the issue. Emplode finds it just fine. Of course, I can only put the play into Pause via the player itself because hitting the pause button in emplode or empegface doesn't work.

So am I basically out of luck until a software release takes advantage of the extra memory?

The W's indicate that a thread is waiting for disk. It implies you either have a remarkably slow disk (like the original Toshibas shipped in 1999) or that the disk is generating a lot of errors. It has very little to do with the amount of memory you have installed, or the amount you are reserving for cache.

If you get audio stutters, the most likely place for this to happen is near the start of a track, within the first 5 seconds of playback. The playback cache spits out what it has cached and is expecting more data from the disk, which it is not getting in time - hence a brief pause. No amount of reserved memory will help in this situation if the data is simply not being delivered on time.

Other, continuous audio stutters occuring rapidly during playback also point to a failing disk or one with high latency.

ksock is a kernel socket operation. The socket error -32 is FFE0, the meaning of which as an Errno in Unix escapes me at the moment.

This implies you have an IP stack fault of some sort. Have you had serious electrical problems on this unit? It may imply subtle electronic damage which may also account for the apparent slowness of the disk, as the ethernet chip and the IDE interface are on the same buffered databus/5V power rail. You may have a damaged bi-directional databus buffer chip which is causing data corruption.

Well crap.

Things are fine with 2.00 except for serial output giving me memory errors... Maybe I can fence some stuff on eBay and afford to mail it to you... If only the damn Euro would fall.

What kind of memory errors with 2.00???

Quote:
If only the damn Euro would fall

Well, you'd need to talk to Mr. Bush about that I'm afraid....

Isn't this just part of the notify option from config.ini? Or perhaps some debugging data? It does not seem like an error.

Well, I still think the memory upgrade is a good thing. It is great if you use third party applications, or if you use the HTML interface a lot. I have a bunch of people at the office streaming from my player at the same time, and they do not seem to be stepping on each other. It is also great for big fsck runs...

But, yes, the player application itself does not make good use of the memory yet. At least not the 2.0x class players. I have not tried the alphas yet.

I know what you mean about the LEDs - I have one I need to get fixed as well. The more modifications, certainly the more things can (and usually do) go wrong. But I still think that it is worth it.

And, yes, that button hack is still extremely impressive!!!