[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1334677466.1435.0.camel@localhost.localdomain>
Date: Tue, 17 Apr 2012 17:44:26 +0200
From: Thomas Meyer <thomas@...3r.de>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
cbou@...l.ru, stern@...land.harvard.edu,
Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: 3.3.2 - Crash in kthread_data (power_supply_core/led?)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists