From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752690AbcBOXUE (ORCPT ); Mon, 15 Feb 2016 18:20:04 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:45836 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751987AbcBOXUC (ORCPT ); Mon, 15 Feb 2016 18:20:02 -0500 Subject: Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...' To: Peter Maydell References: <20160215170527.GA24453@roeck-us.net> Cc: "Rafael J. Wysocki" , linux-next@vger.kernel.org, lkml - Kernel Mailing List , arm-mail-list , linux-pm@vger.kernel.org From: Guenter Roeck Message-ID: <56C25D1D.5080409@roeck-us.net> Date: Mon, 15 Feb 2016 15:19:57 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Authenticated-Sender: bh-25.webhostbox.net: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/15/2016 02:29 PM, Peter Maydell wrote: > On 15 February 2016 at 17:05, Guenter Roeck wrote: >> I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace >> timers with utilization update callbacks' with next-20160215. An example >> crash log and bisect results are attached below. >> >> Please let me know if there is anything I can do to help tracking down >> the problem. >> >> Thanks, >> Guenter >> >> --- >> >> Building arm:beagle:multi_v7_defconfig:omap3-beagle ... running ..... failed (crashed) >> ------------ >> qemu log: > > You're using the QEMU beagle board emulation? Can I ask which > QEMU you're using (qemu-linaro?). If the OMAP3 emulation is still > actively useful to people I might have another stab at getting > it into upstream QEMU some day... > Yes, I use qemu-linaro for those tests. Is it useful ? Obviously for me, yes. It lets me test images in qemu, and I don't need real hardware to run those tests. That means that I don't depend on the hardware really working, and I am not hosed if the hardware breaks down and I don't have a replacement. Plus, of course, I don't need a lab with 90+ pieces of hardware. Guenter From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@roeck-us.net (Guenter Roeck) Date: Mon, 15 Feb 2016 15:19:57 -0800 Subject: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...' In-Reply-To: References: <20160215170527.GA24453@roeck-us.net> Message-ID: <56C25D1D.5080409@roeck-us.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 02/15/2016 02:29 PM, Peter Maydell wrote: > On 15 February 2016 at 17:05, Guenter Roeck wrote: >> I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace >> timers with utilization update callbacks' with next-20160215. An example >> crash log and bisect results are attached below. >> >> Please let me know if there is anything I can do to help tracking down >> the problem. >> >> Thanks, >> Guenter >> >> --- >> >> Building arm:beagle:multi_v7_defconfig:omap3-beagle ... running ..... failed (crashed) >> ------------ >> qemu log: > > You're using the QEMU beagle board emulation? Can I ask which > QEMU you're using (qemu-linaro?). If the OMAP3 emulation is still > actively useful to people I might have another stab at getting > it into upstream QEMU some day... > Yes, I use qemu-linaro for those tests. Is it useful ? Obviously for me, yes. It lets me test images in qemu, and I don't need real hardware to run those tests. That means that I don't depend on the hardware really working, and I am not hosed if the hardware breaks down and I don't have a replacement. Plus, of course, I don't need a lab with 90+ pieces of hardware. Guenter