Has anyone else had these since Dec 9?
<4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->
lock))
panic: page fault
cpuid = 1
time = 1576772837
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe007c98b930
vpanic() at vpanic+0x17e/frame 0
On 2019-12-19 17:50, Cy Schubert wrote:
Has anyone else had these since Dec 9?
<4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->
lock))
panic: page fault
cpuid = 1
time = 1576772837
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe00
In message , Hans Petter
Sela
sky writes:
> On 2019-12-19 17:50, Cy Schubert wrote:
> > Has anyone else had these since Dec 9?
> >
> > <4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->
> > lock))
> > panic: page fault
> > cpuid = 1
> > time = 1576772837
> > KDB: stack backtr
On 12/18/19 4:16 PM, Mark Millard wrote:
>
>
> On 2019-Dec-18, at 13:48, John Baldwin wrote:
>
>> In the interest of supporting newer versions of GCC for a base system
>> toolchain, I've renamed the external GCC packages from -gcc
>> to -gcc6. These are built as flavors of a new devel/freebsd-
On 2019-12-19 19:40, Cy Schubert wrote:
In message , Hans Petter
Sela
sky writes:
On 2019-12-19 17:50, Cy Schubert wrote:
Has anyone else had these since Dec 9?
<4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->
lock))
panic: page fault
cpuid = 1
time = 1576772837
KDB: sta
In message , Hans Petter
Sela
sky writes:
> On 2019-12-19 19:40, Cy Schubert wrote:
> > In message , Hans Petter
> > Sela
> > sky writes:
> >> On 2019-12-19 17:50, Cy Schubert wrote:
> >>> Has anyone else had these since Dec 9?
> >>>
> >>> <4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_
On Thu, 19 Dec 2019, Hans Petter Selasky wrote:
On 2019-12-19 19:40, Cy Schubert wrote:
In message , Hans Petter
Sela
sky writes:
On 2019-12-19 17:50, Cy Schubert wrote:
Has anyone else had these since Dec 9?
<4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!mutex_is_locked(&fbc->
lock))
pani
On 2019-12-19 20:12, Cy Schubert wrote:
In message , Hans Petter
Sela
sky writes:
On 2019-12-19 19:40, Cy Schubert wrote:
In message , Hans Petter
Sela
sky writes:
On 2019-12-19 17:50, Cy Schubert wrote:
Has anyone else had these since Dec 9?
<4>WARN_ON(!mutex_is_locked(&fbc->lock))WARN_ON(!
In message <6f60d4b5-8abe-573c-7140-9b449f3dd...@selasky.org>, Hans Petter
Sela
sky writes:
> On 2019-12-19 20:12, Cy Schubert wrote:
> > In message , Hans Petter
> > Sela
> > sky writes:
> >> On 2019-12-19 19:40, Cy Schubert wrote:
> >>> In message , Hans Pette
> r
> >>> Sela
> >>> sky writes:
>
On Wed, Dec 18, 2019 at 1:49 PM John Baldwin wrote:
>
> In the interest of supporting newer versions of GCC for a base system
> toolchain, I've renamed the external GCC packages from -gcc
> to -gcc6. These are built as flavors of a new devel/freebsd-gcc6
> port. The xtoolchain package is not use
In message <6f60d4b5-8abe-573c-7140-9b449f3dd...@selasky.org>, Hans Petter
Sela
sky writes:
> On 2019-12-19 20:12, Cy Schubert wrote:
> > In message , Hans Petter
> > Sela
> > sky writes:
> >> On 2019-12-19 19:40, Cy Schubert wrote:
> >>> In message , Hans Pette
> r
> >>> Sela
> >>> sky writes:
>
I was a bit worried with all the talk in drm changes, but just fine here.
AMD Ryzen 7 3700x/MSI 570 chipset Motherboard & Video card
I did notice the drm-current-kmod had a date of 12/17/2019: Works fine.
dmesg:
nvd0: 976762MB (2000409264 512 byte sectors)
hdacc0: at cad 0 on hdac0
hdaa0: at ni
12 matches
Mail list logo
