mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <srostedt@redhat.com>,
	dsaxena@plexity.net, linux-kernel@vger.kernel.org,
	Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: Re: TSC not updating after resume: Bug or Feature?
Date: Sun, 21 Dec 2008 21:54:21 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0812212140020.3739@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0812211639210.3376@localhost.localdomain>

On Sun, 21 Dec 2008, Thomas Gleixner wrote:
> On Thu, 18 Dec 2008, Rafael J. Wysocki wrote:
> Also we need to investigate whether sched_clock is referencing gtod
> values _before_ timekeeping is resume.

It does. I added a check into __update_sched_clock() and it triggers
on every resume:

WARNING: at /home/tglx/work/kernel/git/linux-2.6/kernel/sched_clock.c:117 __update_sched_clock+0x31/0xad()
Modules linked in: fuse i915 drm bridge stp bnep sco l2cap bluetooth coretemp sunrpc ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 cpufreq_ondemand acpi_cpufreq freq_table dm_mirror dm_region_hash dm_log dm_multipath uinput joydev thinkpad_acpi hwmon snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device pcspkr i2c_i801 snd_pcm_oss firewire_ohci i2c_core firewire_core yenta_socket iwlagn iTCO_wdt snd_mixer_oss rsrc_nonstatic crc_itu_t iTCO_vendor_support snd_pcm iwlcore snd_timer snd_page_alloc snd_hwdep rfkill snd soundcore e1000e wmi video output battery ac [last unloaded: microcode]
Pid: 3212, comm: pm-hibernate Not tainted 2.6.28-rc9 #80
Call Trace:
 [<ffffffff8103ef04>] warn_on_slowpath+0x5d/0x82
 [<ffffffff8117becf>] ? vsnprintf+0x669/0x6ba
 [<ffffffff81099c38>] ? __mod_zone_page_state+0x9/0x5a
 [<ffffffff810900b7>] ? __rmqueue+0x24/0x1fa
 [<ffffffff81057689>] __update_sched_clock+0x31/0xad
 [<ffffffff81090004>] ? __rmqueue_smallest+0xb7/0x146
 [<ffffffff81057809>] sched_clock_cpu+0x104/0x120
 [<ffffffff811b5030>] ? acpi_ns_search_one_scope+0xc/0x4b
 [<ffffffff81367d14>] ? _spin_lock+0xe/0x11
 [<ffffffff81038e17>] try_to_wake_up+0xff/0x1b1
 [<ffffffff8128e4ca>] ? cpufreq_debug_printk+0x17/0x124
 [<ffffffff81038ed6>] default_wake_function+0xd/0xf
 [<ffffffff81052d94>] autoremove_wake_function+0x16/0x3d
 [<ffffffff8103262f>] __wake_up_common+0x46/0x75
 [<ffffffff81032c7c>] __wake_up+0x38/0x50
 [<ffffffff8104f378>] insert_work+0x68/0x70
 [<ffffffff8104fb94>] __queue_work+0x2f/0x42
 [<ffffffff8104fc2f>] queue_work_on+0x47/0x50
 [<ffffffff8104fdc1>] queue_work+0x1f/0x21
 [<ffffffff8104fdde>] schedule_work+0x1b/0x1d
 [<ffffffff8128f0c8>] cpufreq_resume+0x157/0x16c
 [<ffffffff811fe436>] __sysdev_resume+0x3d/0x55
 [<ffffffff811fe484>] sysdev_resume+0x36/0x77
 [<ffffffff81203e28>] device_power_up+0x15/0x20
 [<ffffffff810670c9>] hibernation_snapshot+0x181/0x210
 [<ffffffff81067220>] hibernate+0xc8/0x1a6
 [<ffffffff81065f75>] state_store+0x5e/0xdd
 [<ffffffff81176f83>] kobj_attr_store+0x17/0x19
 [<ffffffff811106db>] sysfs_write_file+0xe4/0x119
 [<ffffffff810c1856>] vfs_write+0xb0/0x10a
 [<ffffffff810c197e>] sys_write+0x4c/0x74
 [<ffffffff8100c1fa>] system_call_fastpath+0x16/0x1b


  parent reply	other threads:[~2008-12-21 20:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 17:27 Deepak Saxena
2008-12-17 17:50 ` Steven Rostedt
2008-12-18  9:24   ` Peter Zijlstra
2008-12-18 12:39     ` Ingo Molnar
2008-12-18 22:19       ` Rafael J. Wysocki
2008-12-18 22:25         ` Dave Kleikamp
2008-12-18 23:39           ` Rafael J. Wysocki
2008-12-21 16:26         ` Thomas Gleixner
2008-12-21 19:43           ` Thomas Gleixner
2008-12-21 22:43             ` Fabio Comolli
2008-12-22 14:48               ` Thomas Gleixner
2008-12-22 15:00                 ` Ingo Molnar
2008-12-22 18:47                   ` Thomas Gleixner
2008-12-22 20:36                     ` Thomas Gleixner
2008-12-22 20:39                       ` Fabio Comolli
2008-12-22 21:13                         ` Thomas Gleixner
2008-12-22 21:35                           ` Fabio Comolli
2008-12-22 22:05                             ` Thomas Gleixner
2008-12-22 22:12                               ` Fabio Comolli
2008-12-22 22:16                                 ` Thomas Gleixner
2008-12-22 22:29                                   ` Fabio Comolli
2008-12-22 22:33                                     ` Thomas Gleixner
2008-12-23  0:28                                       ` Rafael J. Wysocki
2008-12-23 19:42                                       ` Fabio Comolli
2008-12-24 14:09                               ` Pavel Machek
2008-12-26  8:47                                 ` Peter Zijlstra
2008-12-22 20:19                 ` Fabio Comolli
2008-12-21 20:54           ` Thomas Gleixner [this message]
2008-12-23  0:47           ` Rafael J. Wysocki
2008-12-23  7:03             ` Thomas Gleixner
2008-12-23 14:15               ` Rafael J. Wysocki
2008-12-21 21:19 ` Thomas Gleixner
2008-12-23 22:03   ` Deepak Saxena

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=alpine.LFD.2.00.0812212140020.3739@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=dsaxena@plexity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rjw@sisk.pl \
    --cc=shaggy@linux.vnet.ibm.com \
    --cc=srostedt@redhat.com \
    /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

all inboxes | Powered by JetHome®