From: Andi Kleen <andi@firstfloor.org>
To: Johannes Stezenbach <js@sig21.net>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
robert.richter@amd.com
Subject: Re: 2.6.31-rc5 regression: x86 MCE malfunction on Thinkpad T42p
Date: Mon, 10 Aug 2009 21:44:13 +0200 [thread overview]
Message-ID: <20090810194413.GE6838@basil.fritz.box> (raw)
In-Reply-To: <20090810192658.GA15513@sig21.net>
> But in demsg I got this:
AFAIK that's already fixed. cc Robert to confirm. Not sure if the fix made it into 2.6.31 though?
-Andi
>
> Delta way too big! 18446744022868427516 ts=18446744022868427516 write stamp = 0
> ------------[ cut here ]------------
> WARNING: at kernel/trace/ring_buffer.c:1392 rb_reserve_next_event+0x150/0x309()
> Hardware name: 2373Y4M
> Modules linked in: ath5k mac80211 ath cfg80211 oprofile bnep sco rfcomm l2cap bluetooth ehci_hcd uhci_hc
> Pid: 13478, comm: opcontrol Not tainted 2.6.31-rc5 #5
> Call Trace:
> [<c10248dd>] warn_slowpath_common+0x60/0x90
> [<c102491a>] warn_slowpath_null+0xd/0x10
> [<c1054129>] rb_reserve_next_event+0x150/0x309
> [<c1068c06>] ? get_page_from_freelist+0x86/0x35a
> [<c10544f7>] ring_buffer_lock_reserve+0xe7/0x135
> [<f88622c0>] op_cpu_buffer_write_reserve+0x1a/0x4b [oprofile]
> [<f886239d>] op_add_code+0x57/0x98 [oprofile]
> [<c1068c06>] ? get_page_from_freelist+0x86/0x35a
> [<c1367c08>] ? page_fault+0x0/0x8
> [<f8862409>] log_sample+0x2b/0x6c [oprofile]
> [<c1064c76>] ? filemap_fault+0x74/0x32b
> [<f886249c>] oprofile_add_sample+0x3b/0x6b [oprofile]
> [<f88641d8>] ppro_check_ctrs+0x66/0xdb [oprofile]
> [<c1074bde>] ? __do_fault+0x303/0x32f
> [<f8863907>] profile_exceptions_notify+0x1f/0x26 [oprofile]
> [<c103953b>] notifier_call_chain+0x2b/0x55
> [<c10398e3>] __atomic_notifier_call_chain+0x1a/0x3a
> [<c103990f>] atomic_notifier_call_chain+0xc/0xe
> [<c103993e>] notify_die+0x2d/0x2f
> [<c1003c54>] do_nmi+0x63/0x222
> [<c1367d1d>] nmi_stack_correct+0x28/0x2d
> [<c1367c08>] ? page_fault+0x0/0x8
> ---[ end trace d174f39c63495e01 ]---
>
>
> Thanks
> Johannes
>
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-08-10 19:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 17:09 2.6.31-rc5 regression: x86 MCE malfunction on Thinkpad T42p Johannes Stezenbach
2009-08-09 10:03 ` Johannes Stezenbach
2009-08-09 10:34 ` Bartlomiej Zolnierkiewicz
2009-08-09 16:47 ` Johannes Stezenbach
2009-08-10 10:31 ` Andi Kleen
2009-08-10 12:27 ` Johannes Stezenbach
2009-08-10 12:32 ` Andi Kleen
2009-08-10 12:56 ` Johannes Stezenbach
2009-08-10 13:29 ` Ingo Molnar
2009-08-10 19:26 ` Johannes Stezenbach
2009-08-10 19:44 ` Andi Kleen [this message]
2009-08-10 20:05 ` Robert Richter
2009-08-10 20:14 ` Ingo Molnar
2009-08-10 20:37 ` Johannes Stezenbach
2009-08-10 21:31 ` Ingo Molnar
2009-08-10 22:13 ` Johannes Stezenbach
2009-08-11 9:34 ` [patch] cache-miss and cache-refs events on P6-mobile CPUs Ingo Molnar
2009-08-11 9:39 ` Peter Zijlstra
2009-08-11 11:06 ` Ingo Molnar
2009-08-11 11:21 ` Peter Zijlstra
2009-08-11 15:50 ` Johannes Stezenbach
2009-08-11 16:56 ` Ingo Molnar
2009-08-11 15:40 ` 2.6.31-rc5 regression: x86 MCE malfunction on Thinkpad T42p Johannes Stezenbach
2009-08-17 14:49 ` Steven Rostedt
2009-08-12 11:59 ` *PING* [PATCH]: x86: mce: fix mce warning with disabled lapic Ingo Molnar
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=20090810194413.GE6838@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=js@sig21.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=robert.richter@amd.com \
--cc=x86@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