Hi Karl, That's an excellent suggestion. I did not know you could do that. How does the fallback system work? Oh, nvm, I'll RTFM. :-)
Just for the record, I tried to restart it at the colo without the 'acpi=noirq noapic' bit and it panicked. It suggested trying it with noapic, but tbh, I just wanted to get the hell out of there (1 year old daughter was in the car with the dog, so could only pop in for a couple of minutes). I've set it back to the standard kernel boot settings. I haven't actually noticed the timings being wrong anyway, but will check soon. If there is a problem then next week the virtual kvm will let me test all this stuff out easily anyway. In case it helps anyone else out -- the setup that died with the mods suggested earlier in this thread was an FC3, kernel 2.6.12-1.1378_FC3smp, Opteron 270, on an MSI K8D-Master3-FA4R with the German BIOS update to support DC on that board. Cheers Andrew On Thu, 2005-09-29 at 01:28 +0100, Karl Shrubb wrote: > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Hi Andrew, > > > > If you wish to try this before they install their KVM units. You could set > your grub configuration file to have a fallback option. > > > > In detail, this basically means if it kernel panic's, it will boot with a > working kernel option. So you could have one with the parameter > "no_timer_check=0" and another one with the default kernel parameter you had > before you edited. > > > > So in therapy, it should return from a failure without having to be in front > of the server. > ... _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
