Hello Manuel, thanks for documenting your findings. On Wed, Apr 27, 2016 at 08:55:13PM +0200, Manuel Roeder wrote: > - if you see > [ 2.261416] rtc rtc0: invalid alarm value: 1900-1-29 1193038:40:16 > when checking the kernel-log > > - unbind the rtc-driver > echo 0-0030 > /sys/bus/i2c/devices/0-0030/driver/unbind > > - The following command ist needed for sure !!! other ways it wont work > > i2cget 0 0x30 1 To finally understand the problem can somebody with the problem please issue to following commands on his/her machine: dmesg -c > /dev/null echo 0-0030 > /sys/bus/i2c/devices/0-0030/driver/unbind echo 1 > /sys/kernel/debug/tracing/events/i2c/enable echo 0-0030 > /sys/bus/i2c/drivers/rtc-s35390a/bind echo 0-0030 > /sys/bus/i2c/devices/0-0030/driver/unbind i2cget 0 0x30 1 echo 0-0030 > /sys/bus/i2c/drivers/rtc-s35390a/bind dmesg cat /sys/kernel/debug/tracing/trace and then please provide the output generated by the commands above. Thanks Uwe
Attachment:
signature.asc
Description: PGP signature