Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936136Ab3DIN4I (ORCPT ); Tue, 9 Apr 2013 09:56:08 -0400 Received: from hydra.sisk.pl ([212.160.235.94]:54773 "EHLO hydra.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764221Ab3DIN4F (ORCPT ); Tue, 9 Apr 2013 09:56:05 -0400 From: "Rafael J. Wysocki" To: sedat.dilek@gmail.com Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, Linux PM list , Viresh Kumar Subject: Re: linux-next: Tree for Apr 9 [cpufreq: NULL pointer deref] Date: Tue, 09 Apr 2013 16:03:50 +0200 Message-ID: <31778276.CDMUtaAAnc@vostro.rjw.lan> User-Agent: KMail/4.9.5 (Linux/3.9.0-rc4+; KDE/4.9.5; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1286 Lines: 40 On Tuesday, April 09, 2013 02:47:39 PM Sedat Dilek wrote: > On Tue, Apr 9, 2013 at 11:30 AM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20130408: > > > > The vfs tree still had its build failure so I used the version from > > next-20130405. > > > > The wireless-next tree lost its build failure. > > > > The mfd tree still had its build failure so I used the version from > > next-20130405. > > > > The ftrace tree gained a conflict against Linus' tree. > > > > The arm-soc tree gained conflicts against the omap_dss2 and gpio-lw trees. > > > > ---------------------------------------------------------------------------- > > > > On reboot I see hanging cpufreq with the help of kdb/kgdb? > See screenshot. > > I have also a screenshot with next-20130326, so this issue seems not to be new. This is during CPU offline. Does it only happen on reboot? What about trying to offline/online CPUs from sysfs? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/