From: Kasper Sandberg <lkml@metanurb.dk>
To: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: 2.6.18 BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
Date: Mon, 29 Dec 2008 22:50:38 +0100 [thread overview]
Message-ID: <1230587438.23771.9.camel@localhost> (raw)
Hello.
I just noticed, on a debian etch(stable) system, using kernel 2.6.18
some messages.
I have not experienced any real problems from it, and well.. i just
wanted to post in case someone can get some stuff out of it..
it has happened a few times.
Every night an usb disk is mounted for backup purposes, and you can with
that, estimate how often it happens.
Dont know if this happens on newer kernels.
Also, should i be worried about this? or just not care?
anyway, without further delay, the log:
BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
[<c0132ab4>] unlock_cpu_hotplug+0x2c/0x54
[<f894a25a>] do_dbs_timer+0x125/0x168 [cpufreq_ondemand]
[<c012ac08>] run_workqueue+0x78/0xb5
[<f894a135>] do_dbs_timer+0x0/0x168 [cpufreq_ondemand]
[<c012b4f2>] worker_thread+0xd9/0x10b
[<c0117778>] default_wake_function+0x0/0xc
[<c012b419>] worker_thread+0x0/0x10b
[<c012d86b>] kthread+0xc2/0xef
[<c012d7a9>] kthread+0x0/0xef
[<c0101005>] kernel_thread_helper+0x5/0xb
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
[<c0132ab4>] unlock_cpu_hotplug+0x2c/0x54
[<f894a25a>] do_dbs_timer+0x125/0x168 [cpufreq_ondemand]
[<c012ac08>] run_workqueue+0x78/0xb5
[<f894a135>] do_dbs_timer+0x0/0x168 [cpufreq_ondemand]
[<c012b4f2>] worker_thread+0xd9/0x10b
[<c0117778>] default_wake_function+0x0/0xc
[<c012b419>] worker_thread+0x0/0x10b
[<c012d86b>] kthread+0xc2/0xef
[<c012d7a9>] kthread+0x0/0xef
[<c0101005>] kernel_thread_helper+0x5/0xb
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
[<c0132ab4>] unlock_cpu_hotplug+0x2c/0x54
[<f894a25a>] do_dbs_timer+0x125/0x168 [cpufreq_ondemand]
[<c012ac08>] run_workqueue+0x78/0xb5
[<f894a135>] do_dbs_timer+0x0/0x168 [cpufreq_ondemand]
[<c012b4f2>] worker_thread+0xd9/0x10b
[<c0117778>] default_wake_function+0x0/0xc
[<c012b419>] worker_thread+0x0/0x10b
[<c012d86b>] kthread+0xc2/0xef
[<c012d7a9>] kthread+0x0/0xef
[<c0101005>] kernel_thread_helper+0x5/0xb
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Regards,
Kasper Sandberg
reply other threads:[~2008-12-29 21:50 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=1230587438.23771.9.camel@localhost \
--to=lkml@metanurb.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.