After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login

2021-10-11 Thread Mark Millard via freebsd-arm
I did not even get a chance to finish typing a command after
login for the fist boot after updating:

Fatal kernel mode data abort: 'Translation Fault (L2)' on read
trapframe: 0xe18d6998
FSR=0007, FAR=fff4, spsr=a013
r0 =0001, r1 =, r2 =, r3 =
r4 =d8ce7100, r5 =07d0, r6 =90001010, r7 =
r8 =c08dfc10, r9 =0001, r10=c08dfc1c, r11=e18d6aa8
r12=e18d69e0, ssp=e18d6a28, slr=e18d6a28, pc =e18d6a4c

panic: Fatal abort
cpuid = 0
time = 1633999791
KDB: stack backtrace:
db_trace_self() at db_trace_self
 pc = 0xc062ef7c  lr = 0xc007eb58 (db_trace_self_wrapper+0x30)
 sp = 0xe18d6770  fp = 0xe18d6888
db_trace_self_wrapper() at db_trace_self_wrapper+0x30
 pc = 0xc007eb58  lr = 0xc030ee04 (vpanic+0x17c)
 sp = 0xe18d6890  fp = 0xe18d68b0
 r4 = 0x0100  r5 = 0x
 r6 = 0xc07cac38  r7 = 0xc0941d68
vpanic() at vpanic+0x17c
 pc = 0xc030ee04  lr = 0xc030ec88 (vpanic)
 sp = 0xe18d68b8  fp = 0xe18d68bc
 r4 = 0xe18d6998  r5 = 0x0013
 r6 = 0xfff4  r7 = 0x0007
 r8 = 0x0007  r9 = 0xda5e9000
r10 = 0xfff4
vpanic() at vpanic
 pc = 0xc030ec88  lr = 0xc0652f68 (abort_align)
 sp = 0xe18d68c4  fp = 0xe18d68f0
 r4 = 0x0007  r5 = 0x0007
 r6 = 0xda5e9000  r7 = 0xfff4
 r8 = 0xe18d68bc  r9 = 0xc030ec88
r10 = 0xe18d68c4
abort_align() at abort_align
 pc = 0xc0652f68  lr = 0xc0652a90 (abort_handler+0x2a8)
 sp = 0xe18d68f8  fp = 0xe18d6990
 r4 = 0x0013  r5 = 0xfff4
abort_handler() at abort_handler+0x2a8
 pc = 0xc0652a90  lr = 0xc063191c (exception_exit)
 sp = 0xe18d6998  fp = 0xe18d6aa8
 r4 = 0xd8ce7100  r5 = 0x07d0
 r6 = 0x90001010  r7 = 0x
 r8 = 0xc08dfc10  r9 = 0x0001
r10 = 0xc08dfc1c
exception_exit() at exception_exit
 pc = 0xc063191c  lr = 0xe18d6a28 (0xe18d6a28)
 sp = 0xe18d6a28  fp = 0xe18d6aa8
 r0 = 0x0001  r1 = 0x
 r2 = 0x  r3 = 0x
 r4 = 0xd8ce7100  r5 = 0x07d0
 r6 = 0x90001010  r7 = 0x
 r8 = 0xc08dfc10  r9 = 0x0001
r10 = 0xc08dfc1c r12 = 0xe18d69e0
ucom_cons_softc() at 0xe18d6a4c
 pc = 0xe18d6a4c  lr = 0xe18d6a28 (0xe18d6a28)
 sp = 0xe18d6a28  fp = 0xe18d6aa8
KDB: enter: panic
[ thread pid 894 tid 100135 ]
Stopped at  kdb_enter+0x58: ldrbr15, [r15, r15, ror r15]!
db>

It is not reliably repeatable. Unsure if I can get a repeat at
all.

There is this "mixer" oddity for each boot:

Feeding entropy: .
mixer: 75:75: no such device
mixer: 75:75: no such device
mixer: 75:75: no such device
mixer: 25:25: no such device
mixer: 75:75: no such device
mixer: 75:75: no such device
mixer: =rec: no such device
lo0: link state changed to UP

(in case that matters for some reason).

For reference:

# uname -apKU
FreeBSD OPiP2E_RPi2v11 14.0-CURRENT FreeBSD 14.0-CURRENT #10 
main-n249978-032448cd2c52-dirty: Sat Oct  9 02:11:35 PDT 2021 
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA7-nodbg-clang/usr/main-src/arm.armv7/sys/GENERIC-NODBG-CA7
  arm armv7 1400036 1400036





===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Re: drm-devel-kmod build failures

2021-10-11 Thread Michael Butler via freebsd-current

Thanks - that works :-)

On 10/11/21 13:31, Mateusz Guzik wrote:

This should do it (untested):

diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
index 37b268afa..f05de73fa 100644
--- a/drivers/dma-buf/dma-buf.c
+++ b/drivers/dma-buf/dma-buf.c
@@ -117,9 +117,15 @@ dma_buf_close(struct file *fp, struct thread *td)
 return (0);
  }

+#if __FreeBSD_version >= 1400037
+static int
+dma_buf_stat(struct file *fp, struct stat *sb,
+struct ucred *active_cred __unused)
+#else
  static int
  dma_buf_stat(struct file *fp, struct stat *sb,
  struct ucred *active_cred __unused, struct thread *td __unused)
+#endif
  {

 /* XXX need to define flags for st_mode */


On 10/11/21, Michael Butler via freebsd-current
 wrote:

After the latest freebsd version bump in param.h, I tried to rebuild the
DRM modules. It failed with ..

--- dma-buf.o ---
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:121:1:

error: conflicting types for 'dma_buf_stat'
dma_buf_stat(struct file *fp, struct stat *sb,
^
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:70:18:

note: previous declaration is here
static fo_stat_t dma_buf_stat;
   ^
1 error generated.
*** [dma-buf.o] Error code 1

make[3]: stopped in
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/linuxkpi
1 error

make[3]: stopped in
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/linuxkpi

I get a similar error with drm-current-kmod. What changed?

imb










Re: drm-devel-kmod build failures

2021-10-11 Thread Mateusz Guzik
This should do it (untested):

diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
index 37b268afa..f05de73fa 100644
--- a/drivers/dma-buf/dma-buf.c
+++ b/drivers/dma-buf/dma-buf.c
@@ -117,9 +117,15 @@ dma_buf_close(struct file *fp, struct thread *td)
return (0);
 }

+#if __FreeBSD_version >= 1400037
+static int
+dma_buf_stat(struct file *fp, struct stat *sb,
+struct ucred *active_cred __unused)
+#else
 static int
 dma_buf_stat(struct file *fp, struct stat *sb,
 struct ucred *active_cred __unused, struct thread *td __unused)
+#endif
 {

/* XXX need to define flags for st_mode */


On 10/11/21, Michael Butler via freebsd-current
 wrote:
> After the latest freebsd version bump in param.h, I tried to rebuild the
> DRM modules. It failed with ..
>
> --- dma-buf.o ---
> /usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:121:1:
>
> error: conflicting types for 'dma_buf_stat'
> dma_buf_stat(struct file *fp, struct stat *sb,
> ^
> /usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:70:18:
>
> note: previous declaration is here
> static fo_stat_t dma_buf_stat;
>   ^
> 1 error generated.
> *** [dma-buf.o] Error code 1
>
> make[3]: stopped in
> /usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/linuxkpi
> 1 error
>
> make[3]: stopped in
> /usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/linuxkpi
>
> I get a similar error with drm-current-kmod. What changed?
>
>   imb
>
>


-- 
Mateusz Guzik 



drm-devel-kmod build failures

2021-10-11 Thread Michael Butler via freebsd-current
After the latest freebsd version bump in param.h, I tried to rebuild the 
DRM modules. It failed with ..


--- dma-buf.o ---
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:121:1: 
error: conflicting types for 'dma_buf_stat'

dma_buf_stat(struct file *fp, struct stat *sb,
^
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:70:18: 
note: previous declaration is here

static fo_stat_t dma_buf_stat;
 ^
1 error generated.
*** [dma-buf.o] Error code 1

make[3]: stopped in 
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/linuxkpi

1 error

make[3]: stopped in 
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/linuxkpi


I get a similar error with drm-current-kmod. What changed?

imb