lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 7 May 2008 21:06:57 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: Mirco Tischler <mt-ml@....de> cc: Andi Kleen <ak@...e.de>, Ingo Molnar <mingo@...hat.com>, lkml <linux-kernel@...r.kernel.org> Subject: Re: [BUG]:WARNING: at arch/x86/kernel/rtc.c:122 in 2.6.26-rc1 On Wed, 7 May 2008, Mirco Tischler wrote: > 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] [<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. > 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. > > [ tglx@...utronix.de: 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists