ions. There was one in
> the linuxkpi sources that I corrected in the same commit as the change in
> api. I don't see any users of these in drm-current-kmod. It is possible
> that I have somehow missed it. I did just commit a fix to cpuset that may
>
n-current/sys/kern/kern_shutdown.c:479
> > #3 0x80690ec6 in vpanic (fmt=, ap=)
> > at /opt/src/svn-current/sys/kern/kern_shutdown.c:908
> > #4 0x80690ce3 in panic (fmt=)
> > at /opt/src/svn-current/sys/kern/kern_shutdown.c:835
> > #5 0x
n-current/sys/kern/kern_shutdown.c:479
> > #3 0x80690ec6 in vpanic (fmt=, ap=)
> > at /opt/src/svn-current/sys/kern/kern_shutdown.c:908
> > #4 0x80690ce3 in panic (fmt=)
> > at /opt/src/svn-current/sys/kern/kern_shutdown.c:835
> > #5 0x
b)
I also tried drm-legacy-kmod this morning before heading off to work. It
wouldn't panic but a hard hang. At least drm-current-kmod panics. I suspect
some of
It's interesting to note that though the first occurrence of this panic
occurred on Dec 9, it is more frequent now.
-rw--- 1
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
l (frame=0xfe007c98bc00, eva=2928416)
at /opt/src/svn-current/sys/amd64/amd64/trap.c:926
#6 0x80a31c5f in trap_pfault (frame=0xfe007c98bc00,
usermode=, signo=, ucode=)
at /opt/src/svn-current/sys/amd64/amd64/trap.c:743
#7 0x80a3144b in trap (frame=0xfe007c98
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 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 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
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
10 matches
Mail list logo
