Re: [clang] NMI while trying to read acpi timer register
On 30 January 2013 13:03, Andriy Gapon a...@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. Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [clang] NMI while trying to read acpi timer register
on 04/02/2013 21:11 Adrian Chadd said the following: On 30 January 2013 13:03, Andriy Gapon a...@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 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [clang] NMI while trying to read acpi timer register
I'm not the right person for it, but I think it's worth wrapping up all my requested details in a PR so Those Who Know can take a peek. Especially if it boils down to the choice of compiler. Who knows what other weird corner issues people will see with clang compiling their drivers? Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [clang] NMI while trying to read acpi timer register
on 04/02/2013 23:06 Adrian Chadd said the following: I'm not the right person for it, but I think it's worth wrapping up all my requested details in a PR so Those Who Know can take a peek. Especially if it boils down to the choice of compiler. Who knows what other weird corner issues people will see with clang compiling their drivers? OK, I'll ask the user to open a PR. I'll just note that the problem seems to be too strange... There is a huge distance from compiler to nmi. -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [clang] NMI while trying to read acpi timer register
... again, that's why I'm suggesting they post some further details, such as the disassembly in question. The contents of /etc/src.cnof and /etc/make.conf would be useful too, as well as a verbose dmesg just to make sure devices and CPU flags are all there. Who knows, it could be some corner case of optimisation that's screwing him, or a bad choice of instruction for his given platform, etc, etc. Adrian On 4 February 2013 13:09, Andriy Gapon a...@freebsd.org wrote: on 04/02/2013 23:06 Adrian Chadd said the following: I'm not the right person for it, but I think it's worth wrapping up all my requested details in a PR so Those Who Know can take a peek. Especially if it boils down to the choice of compiler. Who knows what other weird corner issues people will see with clang compiling their drivers? OK, I'll ask the user to open a PR. I'll just note that the problem seems to be too strange... There is a huge distance from compiler to nmi. -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
[clang] NMI while trying to read acpi timer register
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 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
