I have a 1.6 Ghz, 512Mb Athon server running Linux 2.6.10 from an FC3 install.
This system is rock solid and runs for months without reboot.

I own two slimp3s that are kept sync-ed. one is at 2.3 firmware, the other 2.2 (
for some reason upgrades stopped working on that one a while ago)

The network is a pure wired network. 

THE PROBLEM: I keep trying to upgrade to version 6.XX of the slimserver
after running previous versions happily but each time I end
up having to back off to 5.4.1. I'm worried about getting left
behind and not every being able to buy a squeezebox and mix that
in if I don't get this probelm fixed...

The reason or the problem (I think) : I have a large music collection. 
There are about 5700 CDs
of music on my server on two 250Gb disks (isn't it amazing that you can
store a zillion dollars worth of CDs on two $130 disks?)
When I start any version 6 server, my cpu pegs out at full cpu (about
half user state and half system ) . the server takes *forever* to respond
to a web browzer...typically 30-45 seconds, and if music is playing
during a web browse it will stop. All this is because of the library
scanning

You have to wait until the music is scanned (takes a long time) or
what I usually do after I finally get the home page is to klick through
to turn on "rescan only playlists" and then hit the rescan button. That
will initiate a tiny rescan and this ends in 10-15 seconds.

I don't really need the slimserver database features at all as I have
my own older mysql/python/apache thing which I'm used to that
forwards queing and playing commands to the slimserver via URLs

 That software
is able to scan all the files and build a mysql database in about 4
minutes...and it's not using full cpu since its disk limited...
so I think the hardware is ok. 

As a workaround I could live wiht the slimserver  NOT scanning my 
libraries if there was a way to prevent this.

However, for the greater good of Sean and Co, I would not mind
helping to debug this and figure out what is really going on here.

So, do you have any ideas on how we can track this down? It's very 
very easy to repeat.

Another clue: when I try to use the remote to riffle through the
playlists, the server also pegs out cpu for a long while. If you
leave it alone it comes back eventually (after many many minutes) 
Dunno if this is realated or not

Thanks in advance for helping with this...

-paul