linux-kernel - Re: 2.6.33-rc1: hrtimers and tickless broken on m68knommu.

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]

Date:	Fri, 18 Dec 2009 19:20:12 -0800
From:	Steven King <sfking@...dc.com>
To:	linux-kernel@...r.kernel.org
Cc:	john stultz <johnstul@...ibm.com>
Subject: Re: 2.6.33-rc1: hrtimers and tickless broken on m68knommu.

On Friday 18 December 2009 06:44:44 john stultz wrote:
> On Fri, Dec 18, 2009 at 6:13 PM, Steven King <sfking@...dc.com> wrote:
> > Attach is the .config; it works on v2.6.32 but fails to boot on .33-rc1;
> > but if I deselect hrtimers && tickless then it works.
>
> Sorry for the dup, forgot to cc lkml on my reply.
>
> Fails to boot all together? Or does it hang at some point in the dmesg
> that you can point out?

fails to boot all together; nothing on the serial console.
>
> Could you run the following so we can narrow down which clocksource your
> using? cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> cat /sys/devices/system/clocksource/clocksource0/available_clocksource
>
> Then with the kernel that doesn't boot, go through the clocksources
> listed in available_clocksources and try booting w/
> "clocksource=<clock name>" and see if the behavior changes.

on the working .32 kernel:

# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
pit
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
pit

just to be sure, I tried clocksource=pit on the .33-rc1 kernel.  It didnt make 
any difference.

-- 
Steven King -- sfking at fdwdc dot com
--
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/