On Tue, Apr 9, 2013 at 4:03 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > On Tuesday, April 09, 2013 02:47:39 PM Sedat Dilek wrote: >> On Tue, Apr 9, 2013 at 11:30 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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? > I have seen it on reboots. How to online/offline from sysfs? - Sedat - > Rafael > > > -- > I speak only for myself. > Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
