From: john stultz <johnstul@us.ibm.com>
To: Roland Lezuo <roland.lezuo@chello.at>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Re: 2.6.0-test8 mad clock rate drifts and sleeping function ...
Date: 24 Oct 2003 11:04:04 -0700 [thread overview]
Message-ID: <1067018643.1118.199.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <200310241306.57433.roland.lezuo@chello.at>
On Fri, 2003-10-24 at 04:06, Roland Lezuo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > So you're seeing time run twice as fast overall? Are you running with
> > NTP? Do you have any sort of hardware power management on the system?
> > Do you have any more details about the system?
>
> I used to run NTP but I thought I didn't do that when I epxerienced that clock
> drift. The Box (after a restart) is up for 1 day and 13 hours now, there is
> no clock drift any more...
> ...the xmms problem disappeared by recompileing the xmms-alsa plugin (which is
> strange for me), but it is gone...
>
>
> the only thing left:
>
> Debug: sleeping function called from invalid context at
> include/asm/uaccess.h:473
> in_atomic():0, irqs_disabled():1
> Call Trace:
> [<c0120150>] __might_sleep+0xa0/0xd0
> [<c010d40a>] save_v86_state+0x6a/0x200
> [<c010ca67>] do_IRQ+0x117/0x160
> [<c010a49e>] work_notifysig_v86+0x6/0x14
> [<c010a44b>] syscall_call+0x7/0xb
>
> ... there are more of this called from different source files...
Dunno about that one, but please let me know if you later find you can
reproduce the time drift issue.
thanks
-john
prev parent reply other threads:[~2003-10-24 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 8:44 Roland Lezuo
2003-10-23 19:51 ` john stultz
2003-10-24 11:06 ` Roland Lezuo
2003-10-24 18:04 ` john stultz [this message]
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=1067018643.1118.199.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland.lezuo@chello.at \
/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®