Skip to contentSkip to conversation

:WARNING: at arch/x86/kernel/rtc.c:122 in 2.6.26-rc1

BUG Mirco Tischler 3 participants 9 messages May 7, 2008 – May 8, 2008

lore
Share & tools
lore
#0 lore raw

Hello
I've triggered this warning in 2.6.26-rc1-git from 6th of may:
...

[11677.490019] CPU1 is down
[11677.490149] Extended CMOS year: 2000
[11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[11677.490747] Back to C!
[11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date
= 03132007 
[11677.491065] ------------[ cut here ]------------
[11677.491065] WARNING: at arch/x86/kernel/rtc.c:122 mach_get_cmos_time
+0x9e/0x14e()
[11677.491065] Modules linked in: i915 microcode cpufreq_userspace

cpufreq_conservative cpufreq_powersave sbs sbshc wmi aes_x86_64 dm_crypt rtc_cmos rtc_core rtc_lib kvm_intel kvm coretemp hwmon sbp2 snd_hda_intel snd_pcm snd_page_alloc snd_hwdep pata_acpi snd_seq firewire_ohci firewire_core tifm_7xx1 crc_itu_t snd_timer snd_seq_device tpm_infineon tpm tpm_bios psmouse tifm_core ide_pci_generic snd soundcore intel_agp ohci1394 ieee1394 ata_generic ehci_hcd uhci_hcd fan fuse usbcore [last unloaded: iwl4965]

[11677.491065] Pid: 30643, comm: pm-suspend Not tainted
2.6.26-rc1-experimental #72
[11677.491065] 
[11677.491065] Call Trace:
[11677.491065]  [<ffffffff80235361>] warn_on_slowpath+0x51/0x8c
[11677.491065]  [<ffffffff8022bb5b>] try_to_wake_up+0x1d8/0x1e9
[11677.491065]  [<ffffffff8021560b>] do_machine_check+0xa4/0x3d3
[11677.491065]  [<ffffffff8022c076>] __wake_up+0x38/0x4e
[11677.491065]  [<ffffffff80211cdb>] mach_get_cmos_time+0x9e/0x14e
[11677.491065]  [<ffffffff80211da6>] read_persistent_clock+0x1b/0x35
[11677.491065]  [<ffffffff8024c101>] timekeeping_resume+0xb/0x120
[11677.491065]  [<ffffffff803be5a6>] __sysdev_resume+0x16/0x43
[11677.491065]  [<ffffffff803be5f9>] sysdev_resume+0x26/0x61
[11677.491065]  [<ffffffff803c296a>] device_power_up+0x9/0xf
[11677.491065]  [<ffffffff80257e76>] suspend_devices_and_enter
+0xbc/0x105
[11677.491065]  [<ffffffff80257fef>] enter_state+0xe3/0x131
[11677.491065]  [<ffffffff802580f1>] state_store+0xb4/0xd5
[11677.491065]  [<ffffffff802e8b11>] sysfs_write_file+0xd0/0x107
[11677.491065]  [<ffffffff802a2524>] vfs_write+0xad/0x136
[11677.491065]  [<ffffffff802a2669>] sys_write+0x45/0x6e
[11677.491065]  [<ffffffff8020bedb>] system_call_after_swapgs+0x7b/0x80
[11677.491065] 
[11677.491065] ---[ end trace cce3eb8653db51b7 ]---
[11677.491065] Extended CMOS year: 2000
[11677.491232] Enabling non-boot CPUs ...

...

I wasn't able to reproduce the warning yet, but because the commit message introducing the WARN_ON says:

Quoted 3 lines

[ [email protected]: changed to WARN_ON - we want to know that!
If no one reports it we can remove the complete if (RTC_ALWAYS_BCD) magic, which has RTC_ALWAYS_BCD defined to 1 since Linux 1.0 ... ]

I'm reporting it anyway now.

Thanks

Mirco

#1 lore raw
Quoted 51 lines · Mirco Tischler

Hello
I've triggered this warning in 2.6.26-rc1-git from 6th of may:
...

[11677.490019] CPU1 is down
[11677.490149] Extended CMOS year: 2000
[11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[11677.490747] Back to C!
[11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date
= 03132007 
[11677.491065] ------------[ cut here ]------------
[11677.491065] WARNING: at arch/x86/kernel/rtc.c:122 mach_get_cmos_time
+0x9e/0x14e()
[11677.491065] Modules linked in: i915 microcode cpufreq_userspace

cpufreq_conservative cpufreq_powersave sbs sbshc wmi aes_x86_64 dm_crypt rtc_cmos rtc_core rtc_lib kvm_intel kvm coretemp hwmon sbp2 snd_hda_intel snd_pcm snd_page_alloc snd_hwdep pata_acpi snd_seq firewire_ohci firewire_core tifm_7xx1 crc_itu_t snd_timer snd_seq_device tpm_infineon tpm tpm_bios psmouse tifm_core ide_pci_generic snd soundcore intel_agp ohci1394 ieee1394 ata_generic ehci_hcd uhci_hcd fan fuse usbcore [last unloaded: iwl4965]

[11677.491065] Pid: 30643, comm: pm-suspend Not tainted
2.6.26-rc1-experimental #72
[11677.491065] 
[11677.491065] Call Trace:
[11677.491065]  [<ffffffff80235361>] warn_on_slowpath+0x51/0x8c
[11677.491065]  [<ffffffff8022bb5b>] try_to_wake_up+0x1d8/0x1e9
[11677.491065]  [<ffffffff8021560b>] do_machine_check+0xa4/0x3d3
[11677.491065]  [<ffffffff8022c076>] __wake_up+0x38/0x4e
[11677.491065]  [<ffffffff80211cdb>] mach_get_cmos_time+0x9e/0x14e
[11677.491065]  [<ffffffff80211da6>] read_persistent_clock+0x1b/0x35
[11677.491065]  [<ffffffff8024c101>] timekeeping_resume+0xb/0x120
[11677.491065]  [<ffffffff803be5a6>] __sysdev_resume+0x16/0x43
[11677.491065]  [<ffffffff803be5f9>] sysdev_resume+0x26/0x61
[11677.491065]  [<ffffffff803c296a>] device_power_up+0x9/0xf
[11677.491065]  [<ffffffff80257e76>] suspend_devices_and_enter
+0xbc/0x105
[11677.491065]  [<ffffffff80257fef>] enter_state+0xe3/0x131
[11677.491065]  [<ffffffff802580f1>] state_store+0xb4/0xd5
[11677.491065]  [<ffffffff802e8b11>] sysfs_write_file+0xd0/0x107
[11677.491065]  [<ffffffff802a2524>] vfs_write+0xad/0x136
[11677.491065]  [<ffffffff802a2669>] sys_write+0x45/0x6e
[11677.491065]  [<ffffffff8020bedb>] system_call_after_swapgs+0x7b/0x80
[11677.491065] 
[11677.491065] ---[ end trace cce3eb8653db51b7 ]---
[11677.491065] Extended CMOS year: 2000
[11677.491232] Enabling non-boot CPUs ...

...

I wasn't able to reproduce the warning yet, but because the commit message introducing the WARN_ON says:

Quoted 8 lines
Quoted 3 lines

[ [email protected]: changed to WARN_ON - we want to know that!
If no one reports it we can remove the complete if (RTC_ALWAYS_BCD) magic, which has RTC_ALWAYS_BCD defined to 1 since Linux 1.0 ... ]

I'm reporting it anyway now.

Thanks

Mirco

Resend cause Andi's email has changed

#2 lore raw
In reply to Mirco Tischler
Quoted 12 lines · Mirco Tischler

Hello
I've triggered this warning in 2.6.26-rc1-git from 6th of may:
...

[11677.490019] CPU1 is down
[11677.490149] Extended CMOS year: 2000
[11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[11677.490747] Back to C!
[11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date
= 03132007 
[11677.491065] ------------[ cut here ]------------
[11677.491065] WARNING: at arch/x86/kernel/rtc.c:122 mach_get_cmos_time
Quoted 5 lines

+0x9e/0x14e()

[11677.491065]  [<ffffffff80211cdb>] mach_get_cmos_time+0x9e/0x14e
[11677.491065]  [<ffffffff80211da6>] read_persistent_clock+0x1b/0x35
[11677.491065]  [<ffffffff8024c101>] timekeeping_resume+0xb/0x120

Interesting. That's in the resume path.

Quoted 2 lines

I wasn't able to reproduce the warning yet, but because the commit message introducing the WARN_ON says:

This is a WARN_ON_ONCE so you only see it once per boot. Resume does not count :) You might change that WARN_ON_ONCE to WARN_ON to check whether it happens more than once.

Quoted 4 lines
Quoted 3 lines

[ [email protected]: changed to WARN_ON - we want to know that!
If no one reports it we can remove the complete if (RTC_ALWAYS_BCD) magic, which has RTC_ALWAYS_BCD defined to 1 since Linux 1.0 ... ]

I'm reporting it anyway now.

Thanks. That's why I put the WARN_ON there. The backtrace attracts attention and it's also an interesting info that this did not happen on boot, where we read out the RTC as well.

Can you please provide some details about the system ?

Thanks,
tglx

#3 lore raw
Quoted 15 lines · Thomas Gleixner
Quoted 9 lines
[11677.490019] CPU1 is down
[11677.490149] Extended CMOS year: 2000
[11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[11677.490747] Back to C!
[11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date
= 03132007 
[11677.491065] ------------[ cut here ]------------
[11677.491065] WARNING: at arch/x86/kernel/rtc.c:122 mach_get_cmos_time
Quoted 5 lines

+0x9e/0x14e()

[11677.491065]  [<ffffffff80211cdb>] mach_get_cmos_time+0x9e/0x14e
[11677.491065]  [<ffffffff80211da6>] read_persistent_clock+0x1b/0x35
[11677.491065]  [<ffffffff8024c101>] timekeeping_resume+0xb/0x120
Quoted 8 lines

Interesting. That's in the resume path.

Quoted 2 lines

I wasn't able to reproduce the warning yet, but because the commit message introducing the WARN_ON says:

This is a WARN_ON_ONCE so you only see it once per boot. Resume does not count :) You might change that WARN_ON_ONCE to WARN_ON to check whether it happens more than once.

The problem is that I am currently not able to reproduce it. I've tried ~10 suspends & resumes till now. With a reboot in between. Will try some more testing with WARN_ON though.

Quoted 1 line

Can you please provide some details about the system ?

This is a Zepto notebook with Intel chipset (santa rosa generation) and core2duo cpu. I'm running Ubuntu 8.04 x86_64. I attach a lspci output. Just ask if you need more specific information.

Quoted 2 lines

Thanks,
tglx

Thanks
Mirco

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02) 04:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) 06:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
06:06.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller 06:06.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) 06:06.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller

#4 lore raw
Quoted 8 lines · Mirco Tischler
Quoted 7 lines · Thomas Gleixner
Quoted 7 lines
[11677.490019] CPU1 is down
[11677.490149] Extended CMOS year: 2000
[11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[11677.490747] Back to C!
[11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date

= 03132007

That's an odd one: updated from revision 0x92 to 0x92

It's right before the warning triggers. Is this microcode message in all your boot/resume logs ?

Quoted 1 line

Just ask if you need more specific information.

See above ::

Thanks,
tglx

#5 lore raw
Quoted 11 lines · Thomas Gleixner
Quoted 8 lines · Mirco Tischler
Quoted 7 lines · Thomas Gleixner
Quoted 7 lines
[11677.490019] CPU1 is down
[11677.490149] Extended CMOS year: 2000
[11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[11677.490747] Back to C!
[11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date

= 03132007

Quoted 4 lines

That's an odd one: updated from revision 0x92 to 0x92

It's right before the warning triggers. Is this microcode message in all your boot/resume logs ?

Yes, wondered about that too. It's defintely not on all resumes. But it is on more than that single one triggering the warning:

May  7 19:53:21 kernel: [4307505.090195] Extended CMOS year: 2000
May  7 19:53:21 kernel: [4307505.090195] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 19:53:21 kernel: [4307505.090195] Back to C!
May  7 19:53:21 kernel: [4307505.090195] microcode: CPU0 updated from revision 0x92 to 0x92, date = 03132007 
May  7 19:53:21 kernel: [4307505.090195] Extended CMOS year: 2000
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000
May  7 21:52:04 kernel: [4294896.091827] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 21:52:04 kernel: [4294896.091827] Back to C!
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000

Thanks
Mirco

#6 lore raw
Quoted 5 lines
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000
May  7 21:52:04 kernel: [4294896.091827] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 21:52:04 kernel: [4294896.091827] Back to C!
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000

If the data is read correctly (and it looks like it) then just the bit is wrong and we should ignore it I guess. So just remove the WARN_ON_ONCE()?

-Andi

#7 lore raw
Quoted 9 lines · Andi Kleen
Quoted 5 lines
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000
May  7 21:52:04 kernel: [4294896.091827] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 21:52:04 kernel: [4294896.091827] Back to C!
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000

If the data is read correctly (and it looks like it) then just the bit is wrong and we should ignore it I guess. So just remove the WARN_ON_ONCE()?

You put a printk there in the first place :) I changed it to WARN_ON_ONCE as one line printks are more likely to be ignored.

I'm all for it to remove the while BCD check, which is hardcoded to ALWAYS_BCD = 1 since linux 1.0.

This oddball case is interesting as it just triggered once and it looks more like a hardware glitch than something we need to worry about.

Thanks,
tglx

#8 lore raw
Quoted 11 lines · Thomas Gleixner
Quoted 7 lines · Andi Kleen
Quoted 4 lines
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000
May  7 21:52:04 kernel: [4294896.091827] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 21:52:04 kernel: [4294896.091827] Back to C!
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000

If the data is read correctly (and it looks like it) then just the bit is wrong and we should ignore it I guess. So just remove the WARN_ON_ONCE()?

You put a printk there in the first place :) I changed it to WARN_ON_ONCE as one line printks are more likely to be ignored.

Ignoring would have been fine here, but point taken.

Quoted 2 lines

I'm all for it to remove the while BCD check, which is hardcoded to ALWAYS_BCD = 1 since linux 1.0.

Fine for me.

-Andi