From: john stultz <johnstul@us.ibm.com>
To: Nathan Becker <nbecker@physics.ucsb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lost ticks and Hangcheck
Date: Fri, 19 Aug 2005 17:34:43 -0700 [thread overview]
Message-ID: <1124498084.2932.3.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508191714150.8252@claven.physics.ucsb.edu>
On Fri, 2005-08-19 at 17:22 -0700, Nathan Becker wrote:
> > I use the no_timer_check kernel parm and that keeps the clock from
> > running at double speed. I still see some other annoying boot-time
>
> As I mentioned, no_timer_check doesn't fix it for me. In fact it makes
> the problem significantly worse. I tried it again just to be sure. Also
> I tried noapic again and it doesn't help either.
>
> I found there was an upgrade to the NVIDIA graphics driver that addressed
> a clock issue (I don't know if it's related to my problem). I upgraded
> from version 7667 to 7676. That seemed to help a little bit, at least in
> prolonging the amount of time I could reasonably use the system. Someone
> in another thread mentioned that they thought this problem might be caused
> by something in x.org, which I am using.
Please make sure this issue is reproducible without any binary only
drivers.
> Any other ideas or patches would be much appreciated.
If it happens w/o binary only drivers, could you open a bug at
bugzilla.kernel.org and provide full dmesg output?
Also check bug #3341 to see if it is at all similar to what you are
seeing.
thanks
-john
next prev parent reply other threads:[~2005-08-20 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 7:41 Nathan Becker
2005-08-19 9:45 ` Kurt Wall
2005-08-20 0:22 ` Nathan Becker
2005-08-20 0:34 ` john stultz [this message]
2005-08-20 9:50 ` Nathan Becker
2005-08-30 13:47 ` Frank van Maarseveen
2005-09-04 11:39 ` 2.6.13 SMP on Athlon X2: nanosleep returning waay to soon, clock_gettime(CLOCK_REALTIME...) proceeding too fast Frank van Maarseveen
2005-09-04 14:27 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1124498084.2932.3.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbecker@physics.ucsb.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®