Bug 782266

Summary:	Freezing on poweroff (kworker, swapper)
Product:	[Fedora] Fedora	Reporter:	Konstantin Svist <fry.kun>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-13 15:04:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Konstantin Svist 2012-01-17 01:25:30 UTC

Description of problem:
During normal shutdown process, my laptop sometimes locks up and just sits there as if waiting for some process to finish. If left alone for a minute or two, it shuts down on its own. If I press SysRq+E, it shuts down right away.

This has been a problem for a while, I've been hoping it would go away with more recent updates.


SysRq backtrace:
Process swapper (pid:0, ti=f3c20000 task=c0b57fa0 task.ti=c0b16000)
Stack:
Call Trace:
 <IRQ>
Code: 26 00 64 8b 15 1c ae c5 c0 69 d2 fa 00 00 00 8d 04 80 c1 e0 02 f7 e2 8d 42 01 ff 15 90 ea b8 c0 5d c3 90 8d b4 26 00 00 00 00 55 <89> e5 57 56 53 83 ec 04 3e 8d 74 26 00 64 8b 35 ac 60 c5 c0 89
Process kworker/0:0 (pid:0, ti=f3cac000 task=f3cb0c90 task.ti=f3cac000)
Stack:
Call Trace:
Code: 0c 04 5d c3 55 89 e5 3e 8d 74 26 00 8a 50 08 80 fa 01 75 07 e8 f5 9c d6 ff eb 17 80 fa 02 75 07 e8 a6 ff ff ff eb 0b 8b 50 04 ec <8b> 15 3c 24 d3 c0 ed 5d c3 55 89 e5 53 83 ec 10 3e 8d 74 26 00


I've noticed that kworker code doesn't change from run to run, but swapper code is different. Will check if it seems to change during same run.

In case it's relevant, I don't use swap file/partition - it's not defined in /etc/fstab and I disabled fedora-autoswap.service by symlinking it to /dev/null in /etc/systemd/system

Comment 1 Konstantin Svist 2012-01-17 01:38:33 UTC

More info: trace is from 3.1.7-1.fc16.i686
Just now updated to 3.1.9-1.fc16.i686 and have not seen the problem yet today (but that means nothing since it's intermittent)

Comment 2 Konstantin Svist 2012-01-19 00:15:33 UTC

Confirmed that swapper code changes during same run but keeps coming back to same piece of code pretty often. Issue still present

Comment 3 Konstantin Svist 2012-01-24 20:42:57 UTC

Is this bug even in the right category? I'm not sure it's kernel, but no idea where it should be assigned to.

Comment 4 Dave Jones 2012-03-22 16:37:30 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 5 Dave Jones 2012-03-22 16:42:37 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 6 Dave Jones 2012-03-22 16:50:55 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 7 Konstantin Svist 2012-03-24 02:47:50 UTC

Actually bug was gone in 3.2 versions, but present in 3.3.0-4

Comment 8 Konstantin Svist 2012-03-30 05:02:39 UTC

*ping* anyone looking at this??

Comment 9 Josh Boyer 2012-09-05 14:16:37 UTC

There isn't much info to go on here.  Are you still seeing this with the 3.4.X kernels in F16?

Comment 10 Dave Jones 2012-10-23 15:25:07 UTC

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 11 Justin M. Forbes 2012-11-13 15:04:07 UTC

With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.