linux-kernel - Re: [PATCH 0/9] clocksource/drivers/clksrc-of: Improve error handling

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:	Thu, 9 Jun 2016 09:49:31 +0200
From:	Daniel Lezcano <daniel.lezcano@...aro.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH 0/9] clocksource/drivers/clksrc-of: Improve error handling

On 06/09/2016 09:46 AM, Geert Uytterhoeven wrote:
> Hi Daniel,
>
> On Wed, Jun 8, 2016 at 4:10 PM, Daniel Lezcano
> <daniel.lezcano@...aro.org> wrote:
>> On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
>>
>> [ ... ]
>>
>>> in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
>>> (arm32) and r8a7795/salvator-x (arm64).
>>>
>>> Using "earlycon keep_bootcon" on koelsch (this doesn't help on arm64)
>>> reveals it's stuck at:
>>>
>>>       clocksource_probe: no matching clocksources found
>>>       sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every
>>> 21474836475000000ns
>>>       Calibrating delay loop...
>>>
>>> With the above commit reverted, it works again:
>>>
>>>       Architected cp15 timer(s) running at 10.00MHz (virt).
>>>       clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
>>> 0x24e6a1710, max_idle_ns: 440795202120 ns
>>>       sched_clock: 56 bits at 10MHz, resolution 100ns, wraps every
>>> 4398046511100ns
>>>       Switching to timer-based delay loop, resolution 100ns
>>>       Calibrating delay loop (skipped), value calculated using timer
>>> frequency.. 20.00 BogoMIPS (lpj=100000)
>>
>> I think it is fixed now and pushed on my tree. Is it possible to confirm
>> your boards are working correctly again after the linux-next is updated with
>> my latest changes ?
>
> I can confirm the issue is fixed in today's clockevents/next
> (52be039599e1339e).

Great ! Thanks for testing.

   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog