From: Sedat Dilek <sedat.dilek@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org, Linux PM list <linux-pm@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: linux-next: Tree for Apr 9 [cpufreq: NULL pointer deref]
Date: Tue, 9 Apr 2013 16:04:53 +0200 [thread overview]
Message-ID: <CA+icZUXXHb9vmcNuFmYha34SV7xch2S8OcgZ+cLVVnNebs5pNQ@mail.gmail.com> (raw)
In-Reply-To: <31778276.CDMUtaAAnc@vostro.rjw.lan>
On Tue, Apr 9, 2013 at 4:03 PM, Rafael J. Wysocki <rjw@sisk.pl> 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@canb.auug.org.au> 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.
next prev parent reply other threads:[~2013-04-09 14:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUU_K9PiFMqMsOEk1+c2DX8LrUojZptPiRVarv4dcB2qFA@mail.gmail.com>
2013-04-09 14:03 ` linux-next: Tree for Apr 9 [cpufreq: NULL pointer deref] Rafael J. Wysocki
2013-04-09 14:04 ` Sedat Dilek [this message]
2013-04-09 14:56 ` Viresh Kumar
2013-04-09 14:59 ` Sedat Dilek
2013-04-09 16:08 ` Sedat Dilek
2013-04-09 16:51 ` Viresh Kumar
2013-04-09 16:57 ` Sedat Dilek
2013-04-09 18:26 ` Sedat Dilek
2013-04-09 18:29 ` Sedat Dilek
2013-04-09 18:39 ` Sedat Dilek
2013-04-09 20:26 ` Sedat Dilek
2013-04-10 5:41 ` Sedat Dilek
2013-04-10 5:53 ` Sedat Dilek
2013-04-10 6:14 ` Sedat Dilek
2013-04-12 8:23 ` Viresh Kumar
2013-04-12 14:24 ` Sedat Dilek
2013-04-12 15:45 ` Sedat Dilek
2013-04-12 16:27 ` Sedat Dilek
2013-04-12 21:08 ` Sedat Dilek
2013-04-12 22:51 ` Rafael J. Wysocki
2013-04-13 9:55 ` Sedat Dilek
2013-04-15 16:07 ` Dirk Brandewie
2013-04-15 16:13 ` Sedat Dilek
2013-04-15 17:22 ` Viresh Kumar
2013-04-15 17:51 ` Sedat Dilek
2013-04-15 17:57 ` Sedat Dilek
2013-04-15 18:07 ` Sedat Dilek
2013-04-15 18:01 ` Dirk Brandewie
2013-04-17 14:04 ` Sedat Dilek
2013-04-17 16:14 ` Rafael J. Wysocki
2013-04-21 23:30 ` Rafael J. Wysocki
2013-04-22 3:14 ` Viresh Kumar
2013-04-22 12:00 ` Rafael J. Wysocki
2013-04-15 17:27 ` Nathan Zimmer
2013-04-15 17:42 ` Dirk Brandewie
2013-04-15 18:05 ` Nathan Zimmer
2013-04-09 14:59 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+icZUXXHb9vmcNuFmYha34SV7xch2S8OcgZ+cLVVnNebs5pNQ@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).