linux-kernel - Re: 3.3.2 - Crash in kthread_data (power_supply

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Apr 2012 20:36:41 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Meyer <thomas@...3r.de>
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?)

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.

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/