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
___
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 .tex
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@f
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
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