Bug 862831
Summary: | [abrt]: WARNING: at kernel/watchdog.c:242 watchdog_overflow_callback+0x9a/0xc0(): TAINTED G W | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | NewSea <newsea5> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-03-28 14:08:38 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
NewSea
2012-10-03 17:16:11 UTC
remove bogus abrt hash. Created attachment 622763 [details]
sos reports
sos report attached.
This issue chase me from the fedora 16 x64 (currently fedora 17 x64).
PC randomly hanged at early boot for around 30 secods with following message:
[ 0.301775] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.301882] Booting Node 0, Processors #1
[ 41.330960] ------------[ cut here ]------------
[ 41.330968] WARNING: at kernel/watchdog.c:242 watchdog_overflow_callback+0x9a/0xc0()
[ 41.330969] Hardware name: 20042
[ 41.330970] Watchdog detected hard LOCKUP on cpu 0
[ 41.330971] Modules linked in:
[ 41.330974] Pid: 1, comm: swapper/0 Not tainted 3.5.4-2.fc17.x86_64 #1
[ 41.330975] Call Trace:
[ 41.330976] <NMI> [<ffffffff8105864f>] warn_slowpath_common+0x7f/0xc0
[ 41.330986] [<ffffffff81058746>] warn_slowpath_fmt+0x46/0x50
[ 41.330988] [<ffffffff810e2bf0>] ? touch_nmi_watchdog+0x80/0x80
[ 41.330991] [<ffffffff810e2c8a>] watchdog_overflow_callback+0x9a/0xc0
[ 41.330995] [<ffffffff8111c72d>] __perf_event_overflow+0x9d/0x230
[ 41.331001] [<ffffffff81024187>] ? x86_perf_event_set_period+0xd7/0x160
[ 41.331003] [<ffffffff8111d234>] perf_event_overflow+0x14/0x20
[ 41.331006] [<ffffffff810294c3>] intel_pmu_handle_irq+0x193/0x310
[ 41.331012] [<ffffffff8160e9dd>] perf_event_nmi_handler+0x1d/0x20
[ 41.331014] [<ffffffff8160e191>] nmi_handle.isra.0+0x51/0x80
[ 41.331017] [<ffffffff8160e2a0>] do_nmi+0xe0/0x350
[ 41.331019] [<ffffffff8160d7bc>] end_repeat_nmi+0x1a/0x1e
[ 41.331022] [<ffffffff8101b0b6>] ? native_read_tsc+0x6/0x20
[ 41.331024] [<ffffffff8101b0b6>] ? native_read_tsc+0x6/0x20
[ 41.331026] [<ffffffff8101b0b6>] ? native_read_tsc+0x6/0x20
[ 41.331027] <<EOE>> [<ffffffff812da5da>] delay_tsc+0x4a/0x80
[ 41.331035] [<ffffffff812da528>] __const_udelay+0x28/0x30
[ 41.331040] [<ffffffff815fbb44>] native_cpu_up+0x453/0x8e7
[ 41.331042] [<ffffffff815fd51c>] _cpu_up+0xad/0x11e
[ 41.331045] [<ffffffff815fd5d6>] cpu_up+0x49/0x59
[ 41.331049] [<ffffffff81d10d29>] smp_init+0x7a/0xa6
[ 41.331053] [<ffffffff81cf6d08>] kernel_init+0xd1/0x1d4
[ 41.331057] [<ffffffff816161e4>] kernel_thread_helper+0x4/0x10
[ 41.331060] [<ffffffff81cf6c37>] ? start_kernel+0x3c4/0x3c4
[ 41.331062] [<ffffffff816161e0>] ? gs_change+0x13/0x13
[ 41.331068] ---[ end trace 8b827b31921406fa ]---
[ 41.539646] #2 #3
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing? This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |