Hello Kowshik Jois, thanks for raising our attention on this.

I apologize, but once a Launchpad ticket got closed (for example as Fix 
Released), like with LP#2055126, it is no longer actively monitored anymore (by 
our team), hence we missed your additional comments.
(I just found your comments, after I explicitly opened it again ...)

In addition I personally didn't recognized LP#2052767, since it wasn't
opened via the Bugzilla-to-Launchpad bridge, hence wasn't marked as
affecting the 'The Ubuntu-power-systems project', which is what we
actively monitor.

But anyway, each problem needs it's own Launchpad entry, so it was correct to 
open this one here.
(I'll just mark LP#2052767 as a duplicate of this one, LP#2059237).
___

So it looks like this happens with a kernel 6.6 (info taken from LP#2052767: 
linux-6.6.0 - is this an upstream kernel build that you did by yourself? Since 
- afair - we never had a kernel 6.6 in noble/24.04, just a 6.7.)
and with kernel 6.8.0-11 (from the bug description here) - that is the one we 
currently have in the daily IOSs.

There is already an updated kernel available from our "-proposed" pocket.
$ rmadison --arch=ppc64el --suite=noble,noble-proposed linux-generic
 linux-generic | 6.8.0-11.11+1 | noble          | ppc64el
 linux-generic | 6.8.0-20.20+1 | noble-proposed | ppc64el <==
Would you mind installing and trying the 6.8.0-20 from proposed, to see if that 
(very latest) kernel still shows this 'UBSAN: array-index-out-of-bounds' issue?

** Changed in: ubuntu-power-systems
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059237

Title:
  [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
  every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2059237/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to