Hello Manuel, On Mon, May 02, 2016 at 12:00:13AM +0200, Manuel Roeder wrote: > Tested again, here is the output. Machine will not poweroff, it hangs again. > > root@ts219p:~# dmesg | grep rtc > [ 1.241631] rtc rtc0: invalid alarm value: 1900-1-3 1193044:18:16 > [ 1.247944] rtc-s35390a 0-0030: rtc core: registered rtc-s35390a as rtc0 > [ 1.276697] rtc-s35390a 0-0030: setting system clock to 2016-05-01 > 21:50:18 UTC (1462139418) > root@ts219p:~# echo 1 > /sys/kernel/debug/tracing/events/i2c/enable > root@ts219p:~# cat /sys/class/rtc/rtc0/wakealarm > root@ts219p:~# echo 0 > /sys/class/rtc/rtc0/wakealarm > root@ts219p:~# cat /sys/class/rtc/rtc0/wakealarm > root@ts219p:~# cat /sys/kernel/debug/tracing/trace > # tracer: nop > # > # entries-in-buffer/entries-written: 3/3 #P:1 > # > # _-----=> irqs-off > # / _----=> need-resched > # | / _---=> hardirq/softirq > # || / _--=> preempt-depth > # ||| / delay > # TASK-PID CPU# |||| TIMESTAMP FUNCTION > # | | | |||| | | > bash-708 [000] .... 117.749305: i2c_read: i2c-0 #0 a=032 f=0001 l=7 > bash-708 [000] .... 117.749552: i2c_reply: i2c-0 #0 a=032 f=0001 l=7 [68-a0-80-00-86-4a-28] > bash-708 [000] .... 117.749556: i2c_result: i2c-0 n=1 ret=1 Hmm, this is less than I expected but I think I understand the reason. Here is another try: - Please pass trace_event=i2c on the command line for a boot that triggers that "invalid alarm value". (This is the equivalent of echo 1 > /sys/kernel/debug/tracing/events/i2c/enable but happens early enough to trace the probing of the rtc driver.) - Then send the output of the following commands: echo +10000 > /sys/class/rtc/rtc0/wakealarm echo 0 > /sys/class/rtc/rtc0/wakealarm cat /sys/kernel/debug/tracing/trace - Can you shut down after this sequence? Best regards Uwe
Attachment:
signature.asc
Description: PGP signature