From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 30 21:03:29 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7096DFE7 for ; Wed, 30 Jan 2013 21:03:29 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B41C66DC for ; Wed, 30 Jan 2013 21:03:28 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA29821 for ; Wed, 30 Jan 2013 23:03:27 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U0eoY-000OPW-To for freebsd-hackers@freebsd.org; Wed, 30 Jan 2013 23:03:27 +0200 Message-ID: <51098A9E.1080100@FreeBSD.org> Date: Wed, 30 Jan 2013 23:03:26 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-hackers Subject: [clang] NMI while trying to read acpi timer register References: <51068B74.2070808@FreeBSD.org> In-Reply-To: <51068B74.2070808@FreeBSD.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 21:03:29 -0000 on 28/01/2013 16:30 Andriy Gapon said the following: > is there any reasonable explanation for getting an NMI while trying to read acpi > timer register? > Note: this happens only after ACPI suspend/resume. An update. This happens only with clang compiled kernel, gcc compiled kernel is OK. Also, this happens only in the depth of fwohci driver (where it calls DELAY). If firewire is not loaded, then there is no problem. I suspect that perhaps there is some miscompilation that results in some incorrect I/O access that later leads to NMI. Too many unknowns and guesses here, obviously. -- Andriy Gapon