On Wed, Feb 9, 2011 at 2:06 AM, Davide Mirtillo <[email protected]>wrote:
> Il 08/02/2011 15:11, Stan Hoeppner ha scritto: > >> I am currently running squeeze 2.6.32-5-686-bigmem. The machine has > > > > Why run the 32bit distro with the bigmem kernel on an AMD64 box? And why > run > > the bigmem kernel on a machine with only 1 GB RAM? The bigmem kernel is > only > > needed for PAE, which means machines with more than 3GB (IIRC) of RAM. > Anyway, > > you should always use the AMD64 kernel on supported CPUs as you get > better > > overall performance. > > I installed the 32bit OS because the 64bit ones i tried were crashing > miserably. I know i shouldnt be using the 32bit bigmem kernel, but it > was the default when i installed lenny using the preconfigured images > from the datacenter. I guess i could easily switch to the default > kernel, though. > > how were you able to install the os on a hosted server? > >> 1024MB of ram and 2x160Gb Sata HDDs. The NIC is a 100MBit realtek one, > >> with proper drivers from the firmware-realtek debian package. > > > >> I would love to have some opinions on how to deal with this. > > > > First thing I would do is completely disable all power saving features in > the > > system BIOS, the kernel, and user space. If you still get the freezes, > replace > > hardware. > > As i don't have physical access to the machine, i can't play around with > the bios. On topics about similar issues i saw replies close to this > one you gave me, but i don't really know which direction i should take > in order to "disable powersaving". Should i look for hardware specific > stuff (like cpu frequency scaling which is directly connected to the CPU > "Cool n Quiet" feature) or should i look for OS configuration? Do you > know where should i look for information on the matter? > > Server != VIA. ok, let me not be such an ass :) i'd get them to run memtest on it, or ask them to plug an ip-kvm up to it and put memtest in your grub and see what happens. after that fails, i'd ask for a few months free server for your trouble. that or go ahead and go elsewhere before you get too deep in with them - if it's messed up from the start, they should be bending over backward to get you up and running and make you happy than the other way around. give them a call. if they don't insist on figuring it out themselves, cancel and go elsewhere. > > The San Diego core is 5 years old, making your server 4-5 years old. Did > you > > ever see these system lock ups in the past? If you run straight Lenny > with the > > regular i386 kernel (not bigmem) do you get these lock ups? > > > > Is this a brand name server, white box, DIY? If the latter, what > motherboard? > > It's a low end dedicated server i am renting. I've had it for about a > week now. > > ..... > > I should add that limiting the rtorrent download bandwith to 5MBps has > managed to keep the server up, with all the services running for almost > a day now. The default setting was to limit the bandwith at 12MBps. > > hummm, i've never run 'torrent' software on a server and i wouldn't want to host anyone running such software either :) i've also never had a hosted server without ipmi (ilo, drac, etc) or access to ip-kvm. might want to look into that. if they charge for ip, look into a cisco asa5505 put there (i'm assuming you're doing this on the cheap).
