Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #53805 > unrolled thread
| Started by | Manuel Roeder <manuel_roeder@gmx.de> |
|---|---|
| First post | 2016-04-27 21:00 +0200 |
| Last post | 2016-05-01 16:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#794266: New Workaround Manuel Roeder <manuel_roeder@gmx.de> - 2016-04-27 21:00 +0200
Bug#794266: New Workaround Uwe Kleine-König <ukleinek@debian.org> - 2016-05-01 16:00 +0200
| From | Manuel Roeder <manuel_roeder@gmx.de> |
|---|---|
| Date | 2016-04-27 21:00 +0200 |
| Subject | Bug#794266: New Workaround |
| Message-ID | <rsCQP-66m-29@gated-at.bofh.it> |
- 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 - issue a reboot reboot - after reboot check again for [ 2.261416] rtc rtc0: invalid alarm value: 1900-1-29 1193038:40:16 ... it should be gone!!! ... if not start from the beginning ! - if the error message is gone you should be able to power the machine down now poweroff - powerdown will work normal again until the alarm is set wrong again Manuel
[toc] | [next] | [standalone]
| From | Uwe Kleine-König <ukleinek@debian.org> |
|---|---|
| Date | 2016-05-01 16:00 +0200 |
| Message-ID | <ru04F-1WN-3@gated-at.bofh.it> |
| In reply to | #53805 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web