On Sun, 2009-11-08 at 14:30 -0600, Robert G. (Doc) Savage wrote: > On Sun, 2009-11-08 at 11:26 -0800, Adam Williamson wrote: > > On Sun, 2009-11-08 at 11:16 -0600, Robert G. (Doc) Savage wrote: > > > The first step in finding and fixing a problem is coming up with a > > > description of the fault that helps you identify and focus on the > > > misbehaving component. That's what I've been struggling with since F12's > > > alpha release. > > > > > > The sympton is a ThinkPad W700 uber-laptop that seems to "nap" > > > constantly. An example of a "nap" is a long pause -- several minutes -- > > > in one of the steps during a non-graphical startup. For example: between > > > "Starting NFS statd:" and its "[ OK ]" completion. If I don't want to > > > wait for the timeout, I can generate a hardware interrupt by > > > left-clicking or touching the mouse or touchpad. I see from two to five > > > such pause episodes during every startup, but they never occur at the > > > same startup events. > > > > Try booting with the kernel parameter 'nohz=off', does that help? > > <stunned> > > Adam, > > How in the world did you know which hat to pull that rabbit from? I AM > VERY IMPRESSED. :-) oh, same method I always use - I stole it from someone smarter :) my laptop had the same problem; I was advised by Matthew Garrett that this was likely a tickless timer issue and nohz=off should work around it. He also advised me that the kernel folks would like to know about all cases like this, so I should file a bug. Same advice goes for you. Here's my bug as a guide: https://bugzilla.redhat.com/show_bug.cgi?id=516870 note that they haven't got around to it yet. There's probably more important stuff to fix :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
