Bug 870766 - [abrt]: WARNING: at kernel/watchdog.c:242 watchdog_overflow_callback+0xac/0xd0()
Summary: [abrt]: WARNING: at kernel/watchdog.c:242 watchdog_overflow_callback+0xac/0xd0()
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2e40b91821274c1f0a259c1575a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-28 15:51 UTC by Fernando Cordeiro
Modified: 2013-03-28 14:22 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-28 14:22:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fernando Cordeiro 2012-10-28 15:51:51 UTC
Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
cmdline:        BOOT_IMAGE=/boot/vmlinuz-3.6.2-4.fc17.i686 root=UUID=4b8daf82-65d0-45dc-a105-66dc529c2ce9 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=pt-latin1 rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
kernel:         3.6.2-4.fc17.i686

backtrace:
:WARNING: at kernel/watchdog.c:242 watchdog_overflow_callback+0xac/0xd0()
:Hardware name: HP G42 Notebook PC              
:Watchdog detected hard LOCKUP on cpu 0
:Modules linked in:
:Pid: 1, comm: swapper/0 Not tainted 3.6.2-4.fc17.i686 #1
:Call Trace:
: [<c043c562>] warn_slowpath_common+0x72/0xa0
: [<c04ba65c>] ? watchdog_overflow_callback+0xac/0xd0
: [<c04ba65c>] ? watchdog_overflow_callback+0xac/0xd0
: [<c04ba5b0>] ? touch_nmi_watchdog+0x70/0x70
: [<c043c633>] warn_slowpath_fmt+0x33/0x40
: [<c04ba65c>] watchdog_overflow_callback+0xac/0xd0
: [<c04ecc96>] __perf_event_overflow+0xa6/0x270
: [<c04ed7b5>] perf_event_overflow+0x15/0x20
: [<c0415c04>] intel_pmu_handle_irq+0x154/0x2c0
: [<c0955bfb>] perf_event_nmi_handler+0x1b/0x20
: [<c09553d9>] nmi_handle.isra.0+0x39/0x60
: [<c09554e8>] do_nmi+0xe8/0x3f0
: [<c0444d67>] ? irq_exit+0x67/0xb0
: [<c04248ae>] ? smp_apic_timer_interrupt+0x5e/0x90
: [<c0954b40>] nmi_stack_correct+0x2f/0x34
: [<c0671bf2>] ? delay_tsc+0x32/0x60
: [<c0671b5e>] __const_udelay+0x1e/0x20
: [<c0945bd1>] native_cpu_up+0x3b8/0x827
: [<c0461dbe>] ? __raw_notifier_call_chain+0x1e/0x30
: [<c0946e52>] _cpu_up+0x99/0xf9
: [<c0946efc>] cpu_up+0x4a/0x59
: [<c09520f8>] ? mutex_lock+0x18/0x40
: [<c0c1299a>] smp_init+0x3e/0x85
: [<c0934f23>] ? register_cpu_notifier+0x23/0x30
: [<c0bfca67>] kernel_init+0xa3/0x1ae
: [<c0bfc9c4>] ? start_kernel+0x365/0x365
: [<c095b3be>] kernel_thread_helper+0x6/0x10

Comment 1 Josh Boyer 2013-03-12 19:05:20 UTC
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing?

Comment 2 Josh Boyer 2013-03-28 14:22:20 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.