From: Arjan van de Ven <arjan@linux.intel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: kernel/panic.c warn_slowpath_common printk timestamp weirdness
Date: Wed, 21 Jul 2010 06:36:41 -0700 [thread overview]
Message-ID: <4C46F7E9.3070200@linux.intel.com> (raw)
In-Reply-To: <62021.1279716868@localhost>
On 7/21/2010 5:54 AM, Valdis.Kletnieks@vt.edu wrote:
> Seeing this on my Dell Latitude. The timestamps from the 'cut here' and
> WARNING lines are different even though they're issued by sequential lines in
> panic.c - but then the printk timestamps remain identical even through an
> *entire second* WARN call. Is somebody blocking clock interrupts and failing
> to re-enable them, or is something different going on here?
>
> [42875.543219] ------------[ cut here ]------------
> [42875.544006] WARNING: at lib/plist.c:57 plist_check_head+0x47/0x114()
>
> [42875.544006] WARNING: at lib/plist.c:57 plist_check_head+0x47/0x114()
> [42875.544006] Hardware name: Latitude E6500
>
> [42882.428016] ------------[ cut here ]------------
> [42882.428016] WARNING: at lib/plist.c:57 plist_check_head+0x47/0x114()
>
Maybe I have not have had coffee yet.. but I don't see the one second
jump in the three cases you mailed...
next prev parent reply other threads:[~2010-07-21 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 12:54 kernel/panic.c warn_slowpath_common printk timestamp weirdness Valdis.Kletnieks
2010-07-21 13:36 ` Arjan van de Ven [this message]
2010-07-21 17:35 ` Valdis.Kletnieks
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=4C46F7E9.3070200@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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