From: Jean Delvare <khali@linux-fr.org>
To: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
Cc: Robert Norris <robn@opera.com>,
Daniel Kurtz <djkurtz@chromium.org>,
linux-kernel@vger.kernel.org,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550)
Date: Fri, 17 May 2013 11:47:04 +0200 [thread overview]
Message-ID: <20130517114704.442f1368@endymion.delvare> (raw)
In-Reply-To: <5195F6C9.5050200@fold.natur.cuni.cz>
On Fri, 17 May 2013 11:22:17 +0200, Martin Mokrejs wrote:
> Hi,
> while you are chasing some problem with i2c_801 I would like to mention
> that I never got an answer on the thread https://lkml.org/lkml/2013/1/23/405
> about a kmemleak reported by kernel . Maybe this could give you a hint?
> If these do not overlap I would be anyways glad to receive an answer via
> the original thread I have started.
> Thank you,
> Martin
I have no clue what the problem is nor how to investigate it, and in
fact I strongly suspect that this is either a false positive or a
problem in lower layers - driver core, sysfs etc. so nothing I can help
with.
So until someone comes with an evidence that there is an actual memory
leak in the i2c-i801 driver itself I'm not going to pay any attention
to your report, sorry.
--
Jean Delvare
next prev parent reply other threads:[~2013-05-17 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 1:22 PROBLEM: modprobe hang at startup (3.8.x, 3.9.x, IBM x3550) Robert Norris
2013-05-14 23:16 ` Robert Norris
2013-05-15 9:20 ` Jean Delvare
2013-05-15 11:27 ` Robert Norris
2013-05-15 19:49 ` Jean Delvare
2013-05-16 3:44 ` Robert Norris
2013-05-17 8:36 ` Jean Delvare
2013-05-17 9:22 ` Martin Mokrejs
2013-05-17 9:47 ` Jean Delvare [this message]
2013-05-17 9:54 ` Daniel Kurtz
2013-05-17 10:26 ` Robert Norris
2013-05-17 10:24 ` Robert Norris
2013-05-17 12:18 ` Robert Norris
2013-05-17 8:49 ` Jean Delvare
2013-05-17 10:27 ` Robert Norris
2013-05-17 10:56 ` Jean Delvare
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=20130517114704.442f1368@endymion.delvare \
--to=khali@linux-fr.org \
--cc=djkurtz@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmokrejs@fold.natur.cuni.cz \
--cc=robn@opera.com \
/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