Bug 26862 - Oops: Attempted to kill the idle task
Summary: Oops: Attempted to kill the idle task
Status: RESOLVED UNREPRODUCIBLE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-16 20:30 UTC by Ozan Caglayan
Modified: 2011-01-26 20:22 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.37
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (76.49 KB, text/plain)
2011-01-16 20:31 UTC, Ozan Caglayan 		Details
Screenshot of oops (442.32 KB, image/jpeg)
2011-01-16 20:32 UTC, Ozan Caglayan 		Details
/proc/cpuinfo (1.44 KB, text/plain)
2011-01-16 20:32 UTC, Ozan Caglayan 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Ozan Caglayan 2011-01-16 20:30:40 UTC 
This happens on 2.6.37 on an AMD Athlon(tm) 64 X2 Dual Core Processor 6000+.

cpuinfo, dmesg and the screenshot is attached.
Comment 1 Ozan Caglayan 2011-01-16 20:31:25 UTC 
Created attachment 43722 [details]
dmesg
Comment 2 Ozan Caglayan 2011-01-16 20:32:03 UTC 
Created attachment 43732 [details]
Screenshot of oops
Comment 3 Ozan Caglayan 2011-01-16 20:32:23 UTC 
Created attachment 43742 [details]
/proc/cpuinfo
Comment 4 Ozan Caglayan 2011-01-16 20:32:59 UTC 
BTW, this happens when the user is trying to logoff from KDE/shutdown/reboot.
Comment 5 Rafael J. Wysocki 2011-01-16 21:49:22 UTC 
The crash is in get_next_timer_interrupt(), so it probably isn't a cpuidle
problem.  Reassigning to platform/x86_64.

BTW, it would be nice to figure out what code get_next_timer_interrupt+0x148
corresponds to (using gdb).
Comment 6 Thomas Renninger 2011-01-18 08:32:34 UTC 
The kernel is tainted, because you are using a driver from drivers/staging:
rt2870sta
This one is even throwing a warning, do things work better if you avoid loading this one (/etc/modprobe.conf.d -> blacklist rt2870sta)?
Comment 7 Ozan Caglayan 2011-01-20 09:01:28 UTC 
He reports that the problem is solved. Now I'm trying to figure out what update has fixed his problem.
Comment 8 Ozan Caglayan 2011-01-26 20:22:45 UTC 
// Mark this as UNREPRODUCIBLE as the reporter can't reproduce anymore.
Note You need to log in before you can comment on or make changes to this bug.