linux-kernel - Re: 2.6.25-rc5-mm1 - x86_64 boot problem with git-sched.patch

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: <1205432409.19403.24.camel@dyn9047017100.beaverton.ibm.com>
Date:	Thu, 13 Mar 2008 10:20:09 -0800
From:	Badari Pulavarty <pbadari@...ibm.com>
To:	Guillaume Chazarain <guichaz@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, a.p.zijlstra@...llo.nl,
	mingo@...e.hu, vatsa@...ux.vnet.ibm.com,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.25-rc5-mm1 - x86_64 boot problem with git-sched.patch

On Thu, 2008-03-13 at 18:55 +0100, Guillaume Chazarain wrote:
> On Thu, Mar 13, 2008 at 6:40 PM, Badari Pulavarty <pbadari@...ibm.com> wrote:
> >  commit 60befbc1c0b6d141c9c26e61ddd303aedd1e7396
> >  Author: Guillaume Chazarain <guichaz@...oo.fr>
> >  Date:   Mon Mar 10 08:16:41 2008 +0100
> >
> >     sched: make sure jiffies is up to date before calling
> >  __update_rq_clock()
> 
> I didn't know this patch could prevent booting, but anyway it should
> have been removed a long time ago:
> http://lkml.org/lkml/2008/1/25/408
> 

I don't know whats happening either, but my debug shows that 
tick_nohz_update_jiffies() always returns due to following
check without calling touch_softlockup_watchdog().

        if (!ts->tick_stopped)
                return;

BTW, I have CONFIG_DETECT_SOFTLOCKUP=y in my config.


Thanks,
Badari        

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