From: Thomas Meyer <thomas@m3y3r.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
cbou@mail.ru, stern@rowland.harvard.edu,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: 3.3.2 - Crash in kthread_data (power_supply_core/led?)
Date: Tue, 17 Apr 2012 17:44:26 +0200 [thread overview]
Message-ID: <1334677466.1435.0.camel@localhost.localdomain> (raw)
In-Reply-To: <201204152036.41938.rjw@sisk.pl>
Am Sonntag, den 15.04.2012, 20:36 +0200 schrieb Rafael J. Wysocki:
> On Sunday, April 15, 2012, Thomas Meyer wrote:
> > Hi,
> >
> > I resumed my computer from RAM today and found this crash on the text
> > console -> see attachment. One LED was blinking, (PS2 attached) keyboard
> > didn't react anymore and I had to reboot my machine.
> >
> > I couldn't capture the whole dump, the crash didn't made it to the log
> > on disk, so I only have this screenshot. It's the first time I see this
> > crash with any kernel. I did update to 3.3.2 yesterday, but maybe this
> > is unrelated.
> >
> > The crash looks like the power_supply_core/led wants to send some event
> > and then things goes awry.
>
> This looks like a delayed work item triggering at a wrong time.
>
> I guess that the leds' suspend forgets to cancel its delayed work itmes which
> then may be started during system resume.
just resumed my machine again and same crash. again I needed to reboot
my machine. I never had these problems with 3.2.x kernels.
>
> Thanks,
> Rafael
prev parent reply other threads:[~2012-04-17 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 9:24 3.3.2 - Crash in kthread_data (power_supply_core/led?) Thomas Meyer
2012-04-15 18:36 ` Rafael J. Wysocki
2012-04-17 15:44 ` Thomas Meyer [this message]
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=1334677466.1435.0.camel@localhost.localdomain \
--to=thomas@m3y3r.de \
--cc=cbou@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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