Jiri - I have just started the build on the 2.6.24-git16 product and when it is done I will come up with just the nohpet parameter - forgoing the previouosly used taskset command.
Do you want me to do this using the git15 kernel I built yesterday, or the new git16 kernel? (I was not sure if you wanted me to introduce the variable of a new kernel into the process while you are trying to diagnose the failure) On the topic of doing a git bisect - I am recovering from heart surgery last week and other than keeping up with the never ending stream of email from the office, I am pretty much confined to the house - so I have nothing but time on my hands. However, I do my daily builds from the main tarball merged with the daily git patch and don't have the infrustructure set up to do a git bisect. If you can point me to a "how to" on how to set up and use git I am more than willing to give it a shot. Chris On Thu, 2008-02-07 at 10:18 +0100, Jiri Kosina wrote: > On Wed, 6 Feb 2008, Chris Holvenstot wrote: > > > I have several hours of running aith nohpet and X's affinity set to 2 > > instead of 3 and so far everything is running flawlessly. > > Great, so this definitely is some kind of timing issue, thanks for > verifying that. > > > which has the same suggestion (taskset) as you made, for me this was > > something new starting with 2.6.24-git15 - maybe something made a timing > > issue fall a little closer to the edge. > > Yes, could be some scheduler update that made the problem more visible. If > you'd had time to use git-bisect to find the exact commit that exposes > your problem, that might be interesting. But as you said that this is not > immediately reproducible, it might take ages. > > > Would you like me to try and further isolate things for you here by > > either running with just nohpet OR just the taskset to change X's > > affinity? > > Yes, that would help. Especially knowing whether running with 'nohpet' > fixes the problem would be nice. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
