From: manuel_roeder@gmx.de (Manuel Roeder)
To: linux-arm-kernel@lists.infradead.org
Subject: D-Link DNS323 Rev. B1 Problem with Kernel 2.6.38.1 (2.6.38, too) - I2C-Bus mv64xxx / RTC ST M41T80 / LM75 Sensor
Date: Tue, 29 Mar 2011 06:52:19 -0000 [thread overview]
Message-ID: <4D91803E.60601@gmx.de> (raw)
The formerly found bug seems to be introduced with the RTC-rework starting with kernel 2.6.38.
It seems to be NOT a bug of I2C- or LM75-driver!
The bug starts with kernel 2.6.38 and is still there in 2.6.38.2.
Kernel 2.6.37.6 runs fine!!!! No RTC-bug here!!!
[ 18.270364] i2c /dev entries driver
[ 18.274728] rtc-m41t80 0-0068: chip found, driver version 0.05
[ 18.280955] m41t80: dev (254:0)
[ 18.281012] rtc-m41t80 0-0068: rtc core: registered m41t80 as rtc0
[ 20.280626] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 20.287144] rtc-m41t80 0-0068: Can't clear HT bit
[ 20.292139] rtc-m41t80: probe of 0-0068 failed with error -5
[ 22.290615] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 22.297153] lm75: probe of 0-0048 failed with error -110
[ 24.300623] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 26.300925] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 28.300905] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 30.300636] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 32.300906] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 34.300844] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 36.300648] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
regards Manuel Roeder - manuel.roeder(at)web.de
next reply other threads:[~2011-03-29 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 6:52 Manuel Roeder [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-26 8:19 D-Link DNS323 Rev. B1 Problem with Kernel 2.6.38.1 (2.6.38, too) - I2C-Bus mv64xxx / RTC ST M41T80 / LM75 Sensor Manuel Roeder
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=4D91803E.60601@gmx.de \
--to=manuel_roeder@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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.