From owner-freebsd-bugs@FreeBSD.ORG Thu May 7 20:34:54 2015 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C630F21 for ; Thu, 7 May 2015 20:34:54 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1C731ABA for ; Thu, 7 May 2015 20:34:53 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t47KYrPH001121 for ; Thu, 7 May 2015 20:34:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198149] [hwpmc] pmcstat -P -t (top mode, process sampling) stops after a while Date: Thu, 07 May 2015 20:34:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 20:34:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198149 --- Comment #12 from John Baldwin --- Finally snagged the hang with the first hack in place. By the end of the trace all the PMCs have super high thresholds again, but here is where it went wrong: 211497 1 305651558868602 MDP:WRI:1: iaf-write cpu=1 ri=2 msr=0x40000002 v=ffffffdaa2a0 iafctrl=0 pmc=ffffffdaa2a0 211490 1 305651558791430 MDP:REA:1: iaf-read cpu=1 ri=2 msr=0x40000002 -> v=25ec32 211481 1 305651558772962 MDP:WRI:1: iaf-write cpu=1 ri=2 msr=0x40000002 v=ffffffd9db37 iafctrl=0 pmc=ffffffd9db37 211474 1 305651558684430 MDP:REA:1: iaf-read cpu=1 ri=2 msr=0x40000002 -> v=ffffffffffd8db37 211465 1 305651556116174 MDP:WRI:1: iaf-write cpu=1 ri=2 msr=0x40000002 v=1000000000000 iafctrl=0 pmc=0 211458 1 305651555926610 MDP:REA:1: iaf-read cpu=1 ri=2 msr=0x40000002 -> v=c220 211449 1 305651555915314 MDP:WRI:1: iaf-write cpu=1 ri=2 msr=0x40000002 v=ffffffff1ef0 iafctrl=0 pmc=ffffffff1ef0 211442 1 305651555647630 MDP:REA:1: iaf-read cpu=1 ri=2 msr=0x40000002 -> v=97d8 211433 1 305651555563074 MDP:WRI:1: iaf-write cpu=1 ri=2 msr=0x40000002 v=ffffffff438c iafctrl=0 pmc=ffffffff438c In particular, after writing 0 to the pmc in 211465, things went downhill. I'm still looking in the debug logs, but one thing is that we definitely can't put a value of 0 into a PMC. We should possibly force it to -1 in this case so that the interrupt triggers on the next event in that case? -- You are receiving this mail because: You are the assignee for the bug.