| 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: Mon, 17 Mar 2008 16:46:39 +0100 From: Pavel Machek <pavel@....cz> To: "Joel K. Greene" <joel.greene@...apult.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Timer interrupt stops, causes soft lockup Hi! > Of course when time stops progessing forward at a steady pace all > sorts of Bad Things happen. > > The clock loop is caused by jiffies not incrementing. It seems that wall > time updates itself and then resync's with jiffies every ~4s. > > We verified that all spinlocks ( xtime_lock in particular ) were not > being held, and that the kernel had no reason not to update jiffies. > Other interrupts continue to fire, so we're not stuck in the timer > handler. > > So, we went on to look at the PIC. We threw together a little kernel > module to get some debug info. Nice debugging. > We have over 10 systems demonstrating the problem, many in customer > sites. Does nosmp help? Does noapic/nolapic help? You may want to try testing with HZ=4000... to show the problem faster. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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