From: Paolo Ornati <ornati@fastwebnet.it>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: BUG: scheduling while atomic: events/0/0x00000001/4, etc..
Date: Thu, 2 Nov 2006 19:25:01 +0100 [thread overview]
Message-ID: <20061102192501.40e6322a@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
kernel: 2.6.19-rc4-g4b1c46a3
Today I've got these 2 type of messages in kernel log:
1)
BUG: scheduling while atomic: events/0/0x00000001/4
Call Trace:
[<ffffffff8049fafb>] __sched_text_start+0x5b/0x4cc
[<ffffffff802f34b6>] list_add+0xc/0xe
[<ffffffff80236519>] worker_thread+0x0/0x11b
[<ffffffff802365ce>] worker_thread+0xb5/0x11b
[<ffffffff802233e2>] default_wake_function+0x0/0xf
[<ffffffff80236519>] worker_thread+0x0/0x11b
[<ffffffff80239269>] kthread+0xce/0x101
[<ffffffff802234b1>] schedule_tail+0x30/0xa2
[<ffffffff8020a238>] child_rip+0xa/0x12
[<ffffffff8023919b>] kthread+0x0/0x101
[<ffffffff8020a22e>] child_rip+0x0/0x12
2)
BUG: sleeping function called from invalid context at include/asm/semaphore.h:105
in_atomic():1, irqs_disabled():0
Call Trace:
[<ffffffff8049ff6c>] thread_return+0x0/0xf9
[<ffffffff802226ae>] __might_sleep+0xb2/0xb4
[<ffffffff8022749a>] acquire_console_sem+0x66/0x90
[<ffffffff80358086>] console_callback+0xe/0xde
[<ffffffff80235fce>] run_workqueue+0xb6/0x126
[<ffffffff80236519>] worker_thread+0x0/0x11b
[<ffffffff802365ff>] worker_thread+0xe6/0x11b
[<ffffffff802233e2>] default_wake_function+0x0/0xf
[<ffffffff80236519>] worker_thread+0x0/0x11b
[<ffffffff80239269>] kthread+0xce/0x101
[<ffffffff802234b1>] schedule_tail+0x30/0xa2
[<ffffffff8020a238>] child_rip+0xa/0x12
[<ffffffff8023919b>] kthread+0x0/0x101
[<ffffffff8020a22e>] child_rip+0x0/0x12
---------------------------------------
They repeated themself every few senconds and when I noticed I was
unable to get the full log because of log rotation...
Attached:
config
normal dmesg
first 1000 lines of log
--
Paolo Ornati
Linux 2.6.19-rc4-g4b1c46a3 on x86_64
[-- Attachment #2: config.txt.gz --]
[-- Type: application/x-gzip, Size: 9067 bytes --]
[-- Attachment #3: dmesg.txt.gz --]
[-- Type: application/x-gzip, Size: 6570 bytes --]
[-- Attachment #4: log.txt.gz --]
[-- Type: application/x-gzip, Size: 5347 bytes --]
reply other threads:[~2006-11-02 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061102192501.40e6322a@localhost \
--to=ornati@fastwebnet.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox