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

On Tue, Jul 15, 2003 at 07:07:27PM +1000, CaT wrote:
> 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.

So, if you don't have any i2c code loaded, everything works?  How about
just loading the i2c driver and not the sensor driver?

Oh, how about enabiling debugging in the i2c driver that you are using?
Any interesting info in the kernel log would be appreciated.

thanks,

greg k-h

  reply	other threads:[~2003-07-15 16:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  9:07 CaT
2003-07-15 16:11 ` Greg KH [this message]
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=20030715161127.GA2925@kroah.com \
    --to=greg@kroah.com \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.0-t1: i2c+sensors still whacky (hi Greg :)' \
    /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

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).