From: markus reichelt <mr@lists.notified.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 "clock preempt"?
Date: Tue, 27 Jan 2004 22:30:26 +0100 [thread overview]
Message-ID: <20040127213026.GA1315@lists.notified.de> (raw)
In-Reply-To: <20040123203835.GA518@h00a0cca1a6cf.ne.client2.attbi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
timothy parkinson <t@timothyparkinson.com> wrote:
> * Running with SpeedStep (this is a cpu thing i assume?) could cause this.
> * Not having DMA enabled on your hard disk(s) could cause this. See the hdparm
> utility to enable it.
> * Incorrect TSC synchronization on SMP systems could cause this.
> * Anything else?
Yepp:
Jan 27 20:12:12 tatooine kernel: Losing too many ticks!
I had to set "CONFIG_IDE_TASK_IOCTL=y" in my .config in order to get
it working.
- --
Bastard Administrator in $hell
GPG-Key at http://lists.notified.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAFthyLMyTO8Kj/uQRAojoAJ9ZIdhKEij8DW/QdkO1ZG9ksi1hqwCeMGQA
jjROcxpIDSJgirm931LKl0c=
=v37i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-01-27 21:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:36 2.6.1 "clock preempt"? Steinar Hauan
2004-01-20 21:26 ` john stultz
2004-01-21 15:06 ` Steinar Hauan
2004-01-21 18:19 ` john stultz
2004-01-22 19:37 ` timothy parkinson
2004-01-22 19:42 ` john stultz
2004-01-22 19:50 ` timothy parkinson
2004-01-22 19:54 ` john stultz
2004-01-22 20:00 ` timothy parkinson
2004-01-22 21:21 ` john stultz
2004-01-23 19:02 ` timothy parkinson
2004-01-23 19:17 ` john stultz
2004-01-23 19:36 ` timothy parkinson
2004-01-23 20:06 ` john stultz
2004-01-23 20:38 ` timothy parkinson
2004-01-23 21:04 ` john stultz
2004-01-27 21:30 ` markus reichelt [this message]
2004-01-30 23:32 ` Bartlomiej Zolnierkiewicz
2004-01-31 0:24 ` timothy parkinson
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=20040127213026.GA1315@lists.notified.de \
--to=mr@lists.notified.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.