public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	Jiri Slaby <jslaby@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: BUG: using smp_processor_id() in preemptible code: s2disk
Date: Sun, 13 Jun 2010 23:33:52 +0300	[thread overview]
Message-ID: <20100613203352.GA3577@swordfish> (raw)

[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]

Hello,

.35-rc3, x86

Hit the following error today:

kernel: [   94.817525] CPU1: Thermal monitoring handled by SMI
kernel: [   94.951454] BUG: using smp_processor_id() in preemptible [00000000] code: s2disk/3392
kernel: [   94.951462] caller is nr_iowait_cpu+0xe/0x1e
kernel: [   94.951466] Pid: 3392, comm: s2disk Not tainted 2.6.35-rc3-dbg-00106-ga75e02b #2
kernel: [   94.951469] Call Trace:
kernel: [   94.951478]  [<c1184c55>] debug_smp_processor_id+0xa5/0xbc
kernel: [   94.951484]  [<c10282a5>] nr_iowait_cpu+0xe/0x1e
kernel: [   94.951489]  [<c104ab7c>] update_ts_time_stats+0x32/0x6c
kernel: [   94.951494]  [<c104ac73>] get_cpu_idle_time_us+0x36/0x58
kernel: [   94.951500]  [<c124229b>] get_cpu_idle_time+0x12/0x74
kernel: [   94.951505]  [<c1242963>] cpufreq_governor_dbs+0xc3/0x2dc
kernel: [   94.951511]  [<c1240437>] __cpufreq_governor+0x51/0x85
kernel: [   94.951515]  [<c1241190>] __cpufreq_set_policy+0x10c/0x13d
kernel: [   94.951520]  [<c12413d3>] cpufreq_add_dev_interface+0x212/0x233
kernel: [   94.951526]  [<c1241b1e>] ? handle_update+0x0/0xd
kernel: [   94.951533]  [<c1241a18>] cpufreq_add_dev+0x34b/0x35a
kernel: [   94.951538]  [<c103c973>] ? schedule_delayed_work_on+0x11/0x13
kernel: [   94.951544]  [<c12c14db>] cpufreq_cpu_callback+0x59/0x63
kernel: [   94.951550]  [<c1042f39>] notifier_call_chain+0x26/0x48
kernel: [   94.951555]  [<c1042f7d>] __raw_notifier_call_chain+0xe/0x10
kernel: [   94.951560]  [<c102efb9>] __cpu_notify+0x15/0x29
kernel: [   94.951564]  [<c102efda>] cpu_notify+0xd/0xf
kernel: [   94.951568]  [<c12bfb30>] _cpu_up+0xaf/0xd2
kernel: [   94.951574]  [<c12b3ad4>] enable_nonboot_cpus+0x3d/0x94
kernel: [   94.951580]  [<c1055eef>] hibernation_snapshot+0x104/0x1a2
kernel: [   94.951585]  [<c1058b49>] snapshot_ioctl+0x24b/0x53e
kernel: [   94.951589]  [<c1028ad1>] ? sub_preempt_count+0x7c/0x89
kernel: [   94.951595]  [<c10ab91d>] vfs_ioctl+0x2e/0x8c
kernel: [   94.951599]  [<c10588fe>] ? snapshot_ioctl+0x0/0x53e
kernel: [   94.951604]  [<c10ac2c7>] do_vfs_ioctl+0x42f/0x45a
kernel: [   94.951609]  [<c10a0ba5>] ? fsnotify_modify+0x4f/0x5a
kernel: [   94.951615]  [<c11e9dc3>] ? tty_write+0x0/0x1d0
kernel: [   94.951619]  [<c10a12d6>] ? vfs_write+0xa2/0xda
kernel: [   94.951623]  [<c10ac333>] sys_ioctl+0x41/0x62
kernel: [   94.951629]  [<c10027d3>] sysenter_do_call+0x12/0x2d
kernel: [   94.954195] CPU1 is up
kernel: [   94.954862] ACPI: Waking up from system sleep state S4


	Sergey

[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]

             reply	other threads:[~2010-06-13 20:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 20:33 Sergey Senozhatsky [this message]
2010-06-13 20:33 ` BUG: using smp_processor_id() in preemptible code: s2disk Maxim Levitsky
2010-06-13 23:36   ` Rafael J. Wysocki
2010-06-14 14:09     ` Sergey Senozhatsky
2010-06-14 14:23       ` Rafael J. Wysocki
2010-06-14 14:38       ` Arjan van de Ven
2010-06-14 14:54         ` Sergey Senozhatsky
2010-06-14 15:01           ` Arjan van de Ven
2010-06-14 15:17             ` Sergey Senozhatsky
2010-06-15  3:40               ` Arjan van de Ven
2010-06-15  6:19                 ` [PATCH] avoid using smp_processor_id() in preemptible code (nr_iowait_cpu) Sergey Senozhatsky
2010-06-15 14:24                   ` Arjan van de Ven
2010-06-15 14:50                     ` Sergey Senozhatsky
2010-06-15 15:08                       ` Arjan van de Ven
2010-06-15 15:23                         ` Sergey Senozhatsky
2010-06-15 15:31                           ` Sergey Senozhatsky
2010-06-15 16:13                         ` Sergey Senozhatsky
2010-06-16  6:05                           ` Arjan van de Ven
2010-06-16  9:34                             ` Sergey Senozhatsky
2010-06-17  6:29                         ` [PATCH] cpuidle: avoid using smp_processor_id() in preemptible code (nr_iowait_cpu) v4 Sergey Senozhatsky
2010-06-17  6:43                           ` Arjan van de Ven
2010-06-17  6:59                           ` Andrew Morton
2010-06-17  7:04                             ` Andrew Morton
2010-06-17  7:34                             ` Sergey Senozhatsky
2010-06-25 14:39                           ` Peter Zijlstra
2010-06-30 19:58                             ` Andrew Morton
2010-07-01  6:17                               ` Sergey Senozhatsky
2010-07-01  7:07                               ` [PATCH] sched: Cure nr_iowait_cpu() users Peter Zijlstra
2010-07-01  8:18                                 ` Sergey Senozhatsky
2010-07-01  8:45                                 ` [tip:sched/urgent] " tip-bot for Peter Zijlstra

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=20100613203352.GA3577@swordfish \
    --to=sergey.senozhatsky@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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