On Thu, Oct 14, 2004 at 08:57:02AM -0400, Kenneth E. Lussier wrote: > On Wed, 2004-10-13 at 23:06 -0400, Fred wrote: > > When all else fails, try swapping out the network card for a known good > > one. > > This is my next step. I just haven't had time. Since the system in > question is my worstation at work, I can't keep rebooting it, so I'm > working on it at a slow pace. > > The card that I have is an Intel e1000 in a fairly new Dell which has > worked perfectly under 2.6.7. And it seems to work fine under 2.6.8.1 > when X isn't running. So, I'm leaning toward something being wrong in X > that the new kernel doesn't like. I might just wait until 2.6.9 :-)
Are you getting any OOM-killer messages in dmesg or the logs? There's at least one problem with the CFQ scheduler that really can slag a system - my workstation won't boot into 2.6.8.1, and one other grinds to a halt after about 15 minutes. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131251 http://lkml.org/lkml/2004/8/27/102 The fix seems to be adding "elevator=deadline" or "elevator=as" as options to the kernel at boot time. I haven't had enough time to test it to see if that's the solution. -Mark
signature.asc
Description: Digital signature
