On Sat, 9 Feb 2008, Chris Holvenstot wrote:
> Thomas -
>
> Attached is the output I believe you requested (standard boot - ommiting
> the NOHPET directive)
>
> Unless you want to try something else i will run in this configuration
> today to try and verify that the problem is still with us.
>
Thomas -
Attached is the output I believe you requested (standard boot - ommiting
the NOHPET directive)
Unless you want to try something else i will run in this configuration
today to try and verify that the problem is still with us.
Thanks for th good wishes - it is going to be a while - I
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
> I believe that the following is the output you are looking for - sorry
> for the delay - between doctors and grandkids I was ready for a few pain
> pills and a long nap.
Hope you feel better again !
> I suspect you often feel the same way after
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
I believe that the following is the output you are looking for - sorry
for the delay - between doctors and grandkids I was ready for a few pain
pills and a long nap.
Hope you feel better again !
I suspect you often feel the same way after
Thomas -
Attached is the output I believe you requested (standard boot - ommiting
the NOHPET directive)
Unless you want to try something else i will run in this configuration
today to try and verify that the problem is still with us.
Thanks for th good wishes - it is going to be a while - I
On Sat, 9 Feb 2008, Chris Holvenstot wrote:
Thomas -
Attached is the output I believe you requested (standard boot - ommiting
the NOHPET directive)
Unless you want to try something else i will run in this configuration
today to try and verify that the problem is still with us.
Thanks
On Fri, 8 Feb 2008, Jiri Kosina wrote:
> > > I hope that, from at least my perspective, your question is
> > > rhetorical.
> > Yeah. The non rhetorical one was directed to Jiri. :)
> Actually, I have no idea :) I am right now confused too, I am quite
> surprised that 'nohpet' fixes the problem
On Thu, 7 Feb 2008, Thomas Gleixner wrote:
> > I hope that, from at least my perspective, your question is rhetorical.
> Yeah. The non rhetorical one was directed to Jiri. :)
Actually, I have no idea :) I am right now confused too, I am quite
surprised that 'nohpet' fixes the problem for you,
On Fri, 8 Feb 2008, Jiri Kosina wrote:
I hope that, from at least my perspective, your question is
rhetorical.
Yeah. The non rhetorical one was directed to Jiri. :)
Actually, I have no idea :) I am right now confused too, I am quite
surprised that 'nohpet' fixes the problem for you,
On Thu, 7 Feb 2008, Thomas Gleixner wrote:
I hope that, from at least my perspective, your question is rhetorical.
Yeah. The non rhetorical one was directed to Jiri. :)
Actually, I have no idea :) I am right now confused too, I am quite
surprised that 'nohpet' fixes the problem for you,
Thomas -
I believe that the following is the output you are looking for - sorry
for the delay - between doctors and grandkids I was ready for a few pain
pills and a long nap.
I suspect you often feel the same way after dealing with some who post
here.
Thank you for your support
Chris
[
Chris,
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
> Thomas -
>
> I hope that, from at least my perspective, your question is rhetorical.
Yeah. The non rhetorical one was directed to Jiri. :)
> I am fully willing to publicly admit that I don't have a clue. About
> much of anything. I will
Thomas -
I hope that, from at least my perspective, your question is rhetorical.
I am fully willing to publicly admit that I don't have a clue. About
much of anything. I will even admit that until prompted by Jiri
yesterday I had never even heard of the nohpet directive for the boot
line.
I
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
> OK - I think that this is wat you are looking for. If there is
> anything else I can proivde or if I have mucked up this simple cut and
> paste just let me know.
>
> /proc/timer_list after a "standard" boot up:
> Tick Device: mode: 1
> Clock
On Thu, 7 Feb 2008, Jiri Kosina wrote:
> On Thu, 7 Feb 2008, Chris Holvenstot wrote:
>
> > I have been up and running now for about a half hour - since I did not
> > hear your preference I stayed with git15 instead of jumping up to git16
> > in an attempt to avoid introducing any unwanted
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
> I have been up and running now for about a half hour - since I did not
> hear your preference I stayed with git15 instead of jumping up to git16
> in an attempt to avoid introducing any unwanted changes.
>
> The only non-standard thing I did was to
Jiri -
I have been up and running now for about a half hour – since I did not
hear your preference I stayed with git15 instead of jumping up to git16
in an attempt to avoid introducing any unwanted changes.
The only non-standard thing I did was to use the nohpet directive at
boot time - I did
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
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
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
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
On Thu, 7 Feb 2008, Jiri Kosina wrote:
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
I have been up and running now for about a half hour - since I did not
hear your preference I stayed with git15 instead of jumping up to git16
in an attempt to avoid introducing any unwanted changes.
Chris,
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
Thomas -
I hope that, from at least my perspective, your question is rhetorical.
Yeah. The non rhetorical one was directed to Jiri. :)
I am fully willing to publicly admit that I don't have a clue. About
much of anything. I will even
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
OK - I think that this is wat you are looking for. If there is
anything else I can proivde or if I have mucked up this simple cut and
paste just let me know.
/proc/timer_list after a standard boot up:
Tick Device: mode: 1
Clock Event
Thomas -
I believe that the following is the output you are looking for - sorry
for the delay - between doctors and grandkids I was ready for a few pain
pills and a long nap.
I suspect you often feel the same way after dealing with some who post
here.
Thank you for your support
Chris
[
Jiri -
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.
Even though Mark Hounschell pointed me at this old Suse issue
(https://bugzilla.novell.com/show_bug.cgi?id=223561)
which has the same suggestion (taskset) as
On Wed, 6 Feb 2008 14:54:21 +0100 (CET)
Jiri Kosina <[EMAIL PROTECTED]> wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
>
> > On this system I am using a PS2 Keyboard - and let me stress that it is
> > only occasionaly that it happens - I have had 2.6.24-git15 up for about
> > 2 hours now
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
> On this system I am using a PS2 Keyboard - and let me stress that it is
> only occasionaly that it happens - I have had 2.6.24-git15 up for about
> 2 hours now and have only seen it about a dozen times. I also note one
> other thing - although my
Thank you for your response, Jiri -
On this system I am using a PS2 Keyboard - and let me stress that it is
only occasionaly that it happens - I have had 2.6.24-git15 up for about
2 hours now and have only seen it about a dozen times.
I also note one other thing - although my system is lightly
Chris Holvenstot wrote:
> I built 2.6.24-git15 this morning and seem to have picked up a little
> “funny” along the way – occasionally what should be a single key stroke
> ends up spraying multiple characters on to my screen.
>
>
> By this I mean I type “w” and get “w” or whatever.
>
>
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
> I built 2.6.24-git15 this morning and seem to have picked up a little
> "funny" along the way - occasionally what should be a single key stroke
> ends up spraying multiple characters on to my screen. By this I mean I
> type "w" and get "w"
I built 2.6.24-git15 this morning and seem to have picked up a little
“funny” along the way – occasionally what should be a single key stroke
ends up spraying multiple characters on to my screen.
By this I mean I type “w” and get “w” or whatever.
This has happened a number of times
I built 2.6.24-git15 this morning and seem to have picked up a little
“funny” along the way – occasionally what should be a single key stroke
ends up spraying multiple characters on to my screen.
By this I mean I type “w” and get “w” or whatever.
This has happened a number of times
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
I built 2.6.24-git15 this morning and seem to have picked up a little
funny along the way - occasionally what should be a single key stroke
ends up spraying multiple characters on to my screen. By this I mean I
type w and get w or
Chris Holvenstot wrote:
I built 2.6.24-git15 this morning and seem to have picked up a little
“funny” along the way – occasionally what should be a single key stroke
ends up spraying multiple characters on to my screen.
By this I mean I type “w” and get “w” or whatever.
This
Thank you for your response, Jiri -
On this system I am using a PS2 Keyboard - and let me stress that it is
only occasionaly that it happens - I have had 2.6.24-git15 up for about
2 hours now and have only seen it about a dozen times.
I also note one other thing - although my system is lightly
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
On this system I am using a PS2 Keyboard - and let me stress that it is
only occasionaly that it happens - I have had 2.6.24-git15 up for about
2 hours now and have only seen it about a dozen times. I also note one
other thing - although my
On Wed, 6 Feb 2008 14:54:21 +0100 (CET)
Jiri Kosina [EMAIL PROTECTED] wrote:
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
On this system I am using a PS2 Keyboard - and let me stress that it is
only occasionaly that it happens - I have had 2.6.24-git15 up for about
2 hours now and have
Jiri -
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.
Even though Mark Hounschell pointed me at this old Suse issue
(https://bugzilla.novell.com/show_bug.cgi?id=223561)
which has the same suggestion (taskset) as
39 matches
Mail list logo
