https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c1 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |nfbrown@suse.com InfoProvider| |pmlists@free.fr --- Comment #1 from Neil Brown 2014-07-02 04:50:24 UTC --- Your hardware description doesn't mention it, but presumably it is an 'rtc_cmos' clock - that is the interface all all x86 PCs use I think. You could confirm with ls -l /sys/class/rtc/rtc0/device/driver which should show a symlink to ../../../bus/pnp/drivers/rtc_cmos Please confirm. My notebook has an rtc_cmos clock and runs 13.1 (3.11.10-11-desktop) and your little script works perfectly, so it doesn't seem like it is a generic problem. The commit you looked to seems to address quite different symptoms. That has the machine rebooting after shutdown when it shouldn't. Your symptom could be caused by the rtc being out of sync with the system clock. Please run date +%s;cat /sys/class/rtc/rtc0/since_epoch and report the two numbers. If the difference is more than 10, that would explain the problem. If not I'll probably have to pass this to someone else. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c3 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jdelvare@suse.com InfoProvider| |bpetkov@suse.com --- Comment #3 from Neil Brown 2014-07-02 06:10:40 UTC --- Thanks Peter. Hi Borislav - I note you've fixed an rtc related problem recently - any idea whay might be causing this? Adding 'cc' to Jean as well as he apparently has some knowledge of RTC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c5 --- Comment #5 from Peter Münster 2014-07-03 08:50:12 UTC --- Thanks. It's a known upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=68331 Workaround: kernel parameter "hpet=disable" Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c6 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |pmlists@free.fr --- Comment #6 from Borislav Petkov 2014-07-03 10:04:00 UTC --- "Erratic behaviour of the HPET when Spread Spectrum is enabled (related to AMD Product Advisory PA_SB700AG2)" This reminds me, do you have an option in the BIOS which disables Spread Spectrum? If so, try disabling it and try your test again. Then, the wiki page reminded me of a6825f1c1fa8 ("x86: hpet: workaround SB700 BIOS") which is included in 13.1. Can you upload full dmesg please? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c8 Peter Münster changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|pmlists@free.fr | --- Comment #8 from Peter Münster 2014-07-03 22:07:56 UTC --- (In reply to comment #6)

This reminds me, do you have an option in the BIOS which disables Spread Spectrum?

No.

Then, the wiki page reminded me of a6825f1c1fa8 ("x86: hpet: workaround SB700 BIOS") which is included in 13.1. Can you upload full dmesg please?

Yes. Attached. Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c10 --- Comment #10 from Borislav Petkov 2014-07-07 14:31:05 UTC --- Hmm, so your second dmesg looks interesting: [ 583.298388] hpet_rtc_timer_reinit: 84 callbacks suppressed [ 583.298391] hpet1: lost 1099 rtc interrupts and since rtc is using hpet interrupts: [ 1.099227] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs ^^^^^^^^^ I can imagine us losing some of the hpet interrupts during suspend/resume could cause us to miss out on the wakeup alarm. And AFAIR, on those boxes/chipsets, HPET is emulated in the BIOS so it could be that the HPET might have problems if the machine is suspended. Now, I've checked whether upstream has gotten any new fixes to hpet.c or rtc-cmos.c since 13.1 but I don't see anything relevant. You said above:

Workaround: install kernel-desktop-3.7.10-1.32.1 from opensuse-12.3

which would mean that some commit after 3.7 introduced the regression. So the only thing I could think of right now is to bisect it. Basically grab an upstream kernel git tree and first build and test in a coarse-grained manner kernels 3.7, 3.8, ... 3.15. At the first major release number X which shows the regression, you do a normal bisect between kernels 3.X-1 and 3.X as we're assuming 3.X-1 was still ok. I know, it is time consuming so it is up to you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c12 --- Comment #12 from Peter Münster 2014-07-08 08:03:22 UTC --- Just tested, no bisect needed: Commit e005715efaf674660ae59af83b13822567e3a758 introduces the regression. Commit a5ef73f06cb648c3f41edfb5920cbc208368e5bd works. Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c14 --- Comment #14 from Peter Münster 2014-07-08 23:01:33 UTC --- (In reply to comment #13)

Would you be willing to debug this further if I sent you a debugging patch against the 13.1 kernel which you'd need to apply, catch the debugging output after programming the alarm and doing the suspend cycle, and upload it?

A patch against the Linux kernel source tree would be better (HEAD wherever you want) because it's already set up on my box. Peter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=884899 https://bugzilla.novell.com/show_bug.cgi?id=884899#c16 --- Comment #16 from Borislav Petkov 2014-07-08 23:35:54 UTC --- (In reply to comment #14)

A patch against the Linux kernel source tree would be better (HEAD wherever you want) because it's already set up on my box.

You mean against the upstream kernel? Sure, that shouldn't be different wrt this issue.

Don't you agree with Dainius Masiliūnas: "the *real* fix could in fact be to disable HPET"?

Why would you want that? Then you won't have any timer anymore... Or are you saying that booting with "hpet=disable" *actually* fixes the issue on your box and you're able to get the wake up alarm?

(Do I have the AMD-700 chipset? I don't know...)

Maybe, let me check that tomorrow - it is too late for that here. :-) Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=884899 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com Flags|needinfo?(pmlists@free.fr) | -- You are receiving this mail because: You are on the CC list for the bug.