linux-kernel - Re: [patch] fix the softlockup watchdog to actually work

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070725085204.GA22067@elte.hu>
Date:	Wed, 25 Jul 2007 10:52:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	stable@...nel.org, Greg KH <greg@...ah.com>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [patch] fix the softlockup watchdog to actually work


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> > apparently the functionality of the soft lockup watchdog was never 
> > actually tested with that patch applied ...
> > 
> > [this is -stable material too.]
> 
> Still isn't working.  I'm getting random meaningless softlockup 
> trippings coming out for no apparent reason.

hm, you still havent applied the other 4 patches i sent:

 softlockup-fix.patch

 softlockup-add-irq-regs-h.patch
 softlockup-better-printout.patch
 softlockup-cleanups.patch
 softlockup-use-cpu-clock.patch

they are all necessary.

softlockup-use-cpu-clock.patch could easily solve the present problem 
you have: as i pointed it out it is _wrong_ to use sched_clock(), 
because sched_clock() is not a reliable clocksource. Especially on your 
VAIO.

	Ingo
-
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/