linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: 2.6.0-t1: i2c+sensors still whacky (hi Greg :)
Date: Tue, 15 Jul 2003 19:07:27 +1000	[thread overview]
Message-ID: <20030715090726.GJ363@zip.com.au> (raw)

Ok. For a while i2c+sensors for me would freeze my box. Lately though
it has been slowing it down to a crawl. And by slow I mean I can see
the framebuffer console scroll block by block and be able to see 
individual lines half-scrolled and suchlike things. All is fine with 
the kernel until it hits the i2c and sensors code. Then it slows to
a crawl. By the look at the HD usage indicator it seems that it pauses
a second at a time (ie approx seconds pause, burst of activity, seconds
pause etc). This also happened before AS was merged into the kernel.

-- 
"How can I not love the Americans? They helped me with a flat tire the
other day," he said.
	- http://www.toledoblade.com/apps/pbcs.dll/artikkel?SearchID=73139162287496&Avis=TO&Dato=20030624&Kategori=NEWS28&Lopenr=106240111&Ref=AR

             reply	other threads:[~2003-07-15  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  9:07 CaT [this message]
2003-07-15 16:11 ` 2.6.0-t1: i2c+sensors still whacky (hi Greg :) Greg KH
2003-07-16  6:04   ` CaT
2003-07-16  6:10     ` Greg KH
2003-07-16  6:29       ` CaT
2003-07-16  7:31         ` Greg KH
2003-07-16 22:47           ` CaT
2003-07-16 22:54             ` Greg KH
2003-07-17 15:33               ` 2.6.0-t1: i2c+sensors still whacky CaT
2003-07-18  2:33                 ` Greg KH
2003-07-21  7:37                   ` CaT
2003-07-21  7:58                     ` CaT

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=20030715090726.GJ363@zip.com.au \
    --to=cat@zip.com.au \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).