On Fri, 25 Apr 2025 at 22:24:43 +0200, Mark Kettenis wrote:
> > Date: Fri, 25 Apr 2025 19:28:05 +
> > From: Miod Vallat
> >
> > > My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> > > attached, because the reg values in the DTB were 0x000-0x003 rather
> > > than 0xf00-0xf
> Date: Fri, 25 Apr 2025 19:28:05 +
> From: Miod Vallat
>
> > My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> > attached, because the reg values in the DTB were 0x000-0x003 rather
> > than 0xf00-0xf03. This caused a "Fatal kernel mode prefetch abort"
> > because it wa
> Date: Fri, 25 Apr 2025 14:25:40 -0500
> From: joshua stein
>
> My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> attached, because the reg values in the DTB were 0x000-0x003 rather
> than 0xf00-0xf03. This caused a "Fatal kernel mode prefetch abort"
> because it was tryin
> > Why not simply skip that call if ci_flush_bp is NULL?
>
> Because ci_flush_bp should probably be set to something so I figured
> the diagnostic is better than skipping it. In my case it was
> because mainbus_match_primary() was not matching to the cpu device
> when it should have, which pr
On Fri, 25 Apr 2025 at 19:28:05 +, Miod Vallat wrote:
> > My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> > attached, because the reg values in the DTB were 0x000-0x003 rather
> > than 0xf00-0xf03. This caused a "Fatal kernel mode prefetch abort"
> > because it was tryi
> My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> attached, because the reg values in the DTB were 0x000-0x003 rather
> than 0xf00-0xf03. This caused a "Fatal kernel mode prefetch abort"
> because it was trying to execute a null function pointer.
>
> It took me a while to
