Bug 784414
Summary: | [abrt] kernel: BUG: scheduling while atomic: colord/1456/0x10000101 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | collura |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | collura, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:0d27c08901cacbbee24f52ae96ff3e44a1b5858a | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-01-26 10:10:43 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: | |||
Attachments: |
Description
collura
2012-01-24 20:16:37 UTC
Can you install kernel-debug and see if something else is produced before this? Created attachment 557396 [details]
var log messages with various programs giving sched atomic error for kernel 3.2.1-3.fc16
line 0001 was from kernel-3.1.9-1.fc16.x86_64 no kernel-debug
line 1330 was from kernel-3.2.1-3.fc16.x86_64 no kernel-debug
line 2648 was from kernel-3.2.0-2.fc17.x86_64 with kernel-debug
Created attachment 557398 [details]
var log messages for only kernel-3.2.1-3 with kernel-debug installed ; various programs give schedule atomic error
didnt see much about the colord reference but various other programs (firefox, swapper, colord, ..) gave similar 'scheduling while atomic' messages so probably this and other bugs that can be condensed from the duplicate cloud? Would you be willing to try installing a few more kernels? If we can narrow down the range the "scheduling while atomic" issue shows up in, we might get a better handle on which commit in 3.2 caused it. Assuming the 3.1.x kernels work fine, let's start with 3.2-rc1: http://koji.fedoraproject.org/koji/buildinfo?buildID=272907 If that works, then rc2: http://koji.fedoraproject.org/koji/buildinfo?buildID=274346 We'll go from there. One of the other bugs stumbled upon a possible fix. Can you try this kernel: http://koji.fedoraproject.org/koji/taskinfo?taskID=3732597 Created attachment 557615 [details]
dmesg for kernel-3.1.9-1.fc16.x86_64
Created attachment 557616 [details]
dmesg for kernel-3.2.0-0.rc1.git0.1.fc17.x86_64
Created attachment 557617 [details]
dmesg for kernel-3.2.0-0.rc2.git1.1.fc17.x86_64
Created attachment 557618 [details]
dmesg for kernel-3.2.1-3.fc16.x86_64
Created attachment 557619 [details]
dmesg for kernel-3.2.1-4.1.fc16.x86_64
yes the kernel-3.2.1-4.1.fc16.x86_64 helped with me as well (though didnt fix the disappearing brightness slider lol) notifications and log files are much quieter. scheduling while atomic: kernel-3.2.0-0.rc1.git0.1.fc17.x86_64 kernel-3.2.0-0.rc2.git1.1.fc17.x86_64 kernel-3.2.0-2.fc17.x86_64 kernel-3.2.1-3.fc16.x86_64 notably improved particle integrity: kernel-3.1.9-1.fc16.x86_64 kernel-3.2.1-4.1.fc16.x86_64 closing for now. will reopen if reoccurs. thanks for the fix :') |