Control: found -1 78.11.0esr-1

Hi Hideki and Jochen,

Thank you for both of your responses.

On Thu, Jul 01, 2021 at 08:08:44AM +0200, Jochen Sprickerhof wrote:
> * Hideki Yamane <henr...@iijmio-mail.jp> [2021-06-28 22:35]:

> > Can you reproduce it on freshly installed bullseye sytem?

After apt upgrade (firefox now at 78.11.0esr-1), the issue is still there. The 
offending instruction is the same and the backtrace looks very similar. Given 
that the cause seems well understood (use of NEON instructions on a non-NEON 
system), I don't think a fresh install would give us any new information.

> I only found this reference for NEON on armhf:
> 
> "NEON and VFP/VFP2/VFP3 remain an optional part of the architecture."
> 
> https://wiki.debian.org/ArmHardFloatPort#VFP

In addition:

"VFPv3-D16 is the common denominator of the processors to support here 
(therefore the recommended build option is -mfpu=vfpv3-d16)"

https://wiki.debian.org/ArmHardFloatPort/VfpComparison#FPU

I couldn't find a more authoritative definition of the supported architecture 
subset for the armhf port.

> If this is still reproducible, I see two options:
> - Disable NEON code.
> - Depend on the neon-support dummy package.

Agreed.

> > > Kernel: Linux 3.5.7-14-ARCH (PREEMPT)
> > It seems that is not the kernel bullseye provides.

Correct. The default Debian armhf kernel doesn't give me video, and I forgot 
whether it even boots.

> > And it maybe help to provide its hardware information, too.
> The bug author wrote:
> 
> > > This is on a Marvell Dove system, with VFPv3-D16. From /proc/cpuinfo:
> > > Features  : swp half thumb fastmult vfp edsp iwmmxt thumbee vfpv3 
> > > vfpv3d16 tls

More specifically, this is on a SolidRun CuBox (first generation, so not the 
CuBox-i or CuBox-M).

I noticed that some time ago, the severity of this bug was raised from normal 
to serious. While it is serious on my system, I had set it to normal because it 
likely affects only a relatively small number of systems. And while I would 
appreciate this bug getting resolved, making it release critical seems 
unnecessary.

Regards,
Vincent.

Reply via email to