[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#684978: marked as done (linux-image-3.2.0-3-orion5x has i2c lock error in dmesg)

Your message dated Sat, 24 Apr 2021 16:00:57 +0200
with message-id <YIQkmZPWmhkXGB6D@eldamar.lan>
and subject line Re: Bug#684978: same as 622325
has caused the Debian Bug report #684978,
regarding linux-image-3.2.0-3-orion5x has i2c lock error in dmesg
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
684978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684978
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.2.0-3-orion5x     
Version: 3.2.21-3

I have installed debian wheezy on my NAS D-link DNS-323.
After successful installation, I have set the fancontrol package with pwmconfig, and it's well functioned.
However, once it is rebooted, following message shows dmesg :

[   17.977840] i2c /dev entries driver
[   17.982967] rtc-m41t80 0-0068: chip found, driver version 0.05
[   19.981100] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   19.987621] rtc-m41t80 0-0068: read error
[   19.992140] rtc-m41t80 0-0068: rtc core: registered m41t80 as rtc0
[   21.991005] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   21.997528] rtc-m41t80 0-0068: Can't clear HT bit
[   22.002634] rtc-m41t80: probe of 0-0068 failed with error -5
[   22.033412] /build/buildd-linux_3.2.21-3-armel-hXriS9/linux-3.2.21/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   33.601130] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   33.607689] lm75: probe of 0-0048 failed with error -110
[   35.611147] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   37.611163] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   39.611150] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   41.611147] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   43.611162] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   45.611171] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   47.611147] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   65.411105] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   67.411452] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[   69.411149] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0

and when I run the pwmconfig again, I got the message:

# pwmconfig revision 5857 (2010-08-22)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0/device is g760a

Found the following PWM controls:
   hwmon0/device/pwm1

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon0/device/fan1_input     current speed: 0 ... skipping!

There are no working fan sensors, all readings are 0.
Make sure you have a 3-wire fan connected.
You may also need to increase the fan divisors.
See doc/fan-divisors for more information.

this is the 'tree' output on /sys/devices/platform/mv64xxx_i2c.0/i2c-0
.
├── 0-003e
│   ├── driver -> ../../../../../bus/i2c/drivers/g760a
│   ├── fan1_alarm
│   ├── fan1_input
│   ├── hwmon
│   │   └── hwmon0
│   │       ├── device -> ../../../0-003e
│   │       ├── power
│   │       │   ├── autosuspend_delay_ms
│   │       │   ├── control
│   │       │   ├── runtime_active_kids
│   │       │   ├── runtime_active_time
│   │       │   ├── runtime_enabled
│   │       │   ├── runtime_status
│   │       │   ├── runtime_suspended_time
│   │       │   └── runtime_usage
│   │       ├── subsystem -> ../../../../../../../class/hwmon
│   │       └── uevent
│   ├── modalias
│   ├── name
│   ├── power
│   │   ├── autosuspend_delay_ms
│   │   ├── control
│   │   ├── runtime_active_kids
│   │   ├── runtime_active_time
│   │   ├── runtime_enabled
│   │   ├── runtime_status
│   │   ├── runtime_suspended_time
│   │   └── runtime_usage
│   ├── pwm1
│   ├── subsystem -> ../../../../../bus/i2c
│   └── uevent
├── 0-0048
│   ├── modalias
│   ├── name
│   ├── power
│   │   ├── autosuspend_delay_ms
│   │   ├── control
│   │   ├── runtime_active_kids
│   │   ├── runtime_active_time
│   │   ├── runtime_enabled
│   │   ├── runtime_status
│   │   ├── runtime_suspended_time
│   │   └── runtime_usage
│   ├── subsystem -> ../../../../../bus/i2c
│   └── uevent
├── 0-0068
│   ├── modalias
│   ├── name
│   ├── power
│   │   ├── autosuspend_delay_ms
│   │   ├── control
│   │   ├── runtime_active_kids
│   │   ├── runtime_active_time
│   │   ├── runtime_enabled
│   │   ├── runtime_status
│   │   ├── runtime_suspended_time
│   │   └── runtime_usage
│   ├── subsystem -> ../../../../../bus/i2c
│   └── uevent
├── delete_device
├── device -> ../../mv64xxx_i2c.0
├── i2c-dev
│   └── i2c-0
│       ├── dev
│       ├── device -> ../../../i2c-0
│       ├── name
│       ├── power
│       │   ├── autosuspend_delay_ms
│       │   ├── control
│       │   ├── runtime_active_kids
│       │   ├── runtime_active_time
│       │   ├── runtime_enabled
│       │   ├── runtime_status
│       │   ├── runtime_suspended_time
│       │   └── runtime_usage
│       ├── subsystem -> ../../../../../../class/i2c-dev
│       └── uevent
├── name
├── new_device
├── power
│   ├── autosuspend_delay_ms
│   ├── control
│   ├── runtime_active_kids
│   ├── runtime_active_time
│   ├── runtime_enabled
│   ├── runtime_status
│   ├── runtime_suspended_time
│   └── runtime_usage
├── subsystem -> ../../../../bus/i2c
└── uevent

23 directories, 68 files

--- End Message ---
--- Begin Message --- 
Hi,

On Tue, Sep 10, 2013 at 11:58:49AM +0100, Martin Michlmayr wrote:
> This is the same issue as #622325

And closing, as #622325 was resolved.

Regards,
Salvatore

--- End Message ---
Reply to: