Date: Mon, 04 Feb 2013 23:00:11 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Adrian Chadd <adrian@FreeBSD.org> Cc: freebsd-hackers <freebsd-hackers@FreeBSD.org> Subject: Re: [clang] NMI while trying to read acpi timer register Message-ID: <5110215B.5000405@FreeBSD.org> In-Reply-To: <CAJ-VmokD-iiSwb8eqxFq97HQ6Y2Ed__7gHqFyLus=KGGrC9ntA@mail.gmail.com> References: <51068B74.2070808@FreeBSD.org> <51098A9E.1080100@FreeBSD.org> <CAJ-VmokD-iiSwb8eqxFq97HQ6Y2Ed__7gHqFyLus=KGGrC9ntA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 04/02/2013 21:11 Adrian Chadd said the following: > On 30 January 2013 13:03, Andriy Gapon <avg@freebsd.org> wrote: >> 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. > > Do you have stack traces showing where it's happening? > > Posting that and the disassembly from those areas may shed a clue. The information should be available from a user who got this issue. Are you willing to take a look? I'll connect you. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5110215B.5000405>