Re: r330538 broken CURRENT on MacBookPro

2018-03-15 Thread Warner Losh 
On Thu, Mar 15, 2018 at 7:55 PM, huanghwh  wrote:

> Hi,
> I got this panic:
> http://sw.gddsn.org.cn/freebsd/panic.jpg
>
>
> r330538 broken CURRENT found by svn bisect
>
>
> any idea?
>

'trace' at the db> prompt would let us know better what's going on.

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

amd64: panic on -CURRENT @r330539 for certain UEFI hosts

2018-03-15 Thread Peter Lei 
Some recent UEFI implementations have begun to leave the CPU with page
write protection enabled in CR0.

With r330539 which enables kernel page protections, interesting things
happen during boot (aka panic) when protection is already enabled,
including a write protection fault from an explicit .text fixup write
from xsave->xsaveopt by fpuinit().

I see this so far booting -CURRENT under virtual environments:

- QEMU with recent OVMF EDK2 builds: this is certainly due to UEFI
enabling paging and page protections.

- VMWare Fusion 10.1.x on Mac: no specific insight on what's going
inside the implementation, but CR0_WP is definitely left enabled before
the kernel is booted.

I have patched my kernel build to explicitly clear CR0_WP (e.g. in
initializecpu) prior to creating the page tables to get around this, but
someone might have a cleaner/better solution...

--peter



smime.p7s
Description: S/MIME Cryptographic Signature

Re:r330539 broken CURRENT on MacBookPro

2018-03-15 Thread huanghwh 

Sorry,  It is r330539, not r330538.



At 2018-03-16 09:55:02, "huanghwh"  wrote:
>Hi,
>I got this panic:
>http://sw.gddsn.org.cn/freebsd/panic.jpg
>
>
>r330538 broken CURRENT found by svn bisect
>
>
>any idea?
>
>
>Huang Wen Hui 
>___
>freebsd-current@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

r330538 broken CURRENT on MacBookPro

2018-03-15 Thread huanghwh 
Hi,
I got this panic:
http://sw.gddsn.org.cn/freebsd/panic.jpg


r330538 broken CURRENT found by svn bisect


any idea?


Huang Wen Hui 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Clang-6 and GNUisms.

2018-03-15 Thread Ian FREISLICH 
On 03/12/18 13:54, Dimitry Andric wrote:
> On 12 Mar 2018, at 16:03, Dimitry Andric  wrote:
>> On 12 Mar 2018, at 00:56, Ian FREISLICH  
>> wrote:
> ...
>>> I haven't got avr-gcc to compile yet.
>> No idea about this, is it very different from regular gcc's?  As those
>> all compile fine now.
> For avr-gcc, which is an older version of gcc with some customizations,
> a fix similar to https://svnweb.freebsd.org/changeset/ports/458581 is
> needed, such as the attached patch

This works,  thanks.  Can you commit to the port, the maintainer hasn't
responded to me.

Ian

-- 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"