** Description changed:
+ [ Impact ]
+
+ Boot failures are being observed with the current Bionic image in some
+ (but not all) Pi 4 2GB rev 1.4 boards (identified by revision code
+ b03114 in /proc/cpuinfo). The back-port is intended to rectify booting
+ on these machines. It is expected that
Okay, I think I see that the missing breaks in flash-kernel might be
planned (per debian/changelog).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940400
Title:
Pi 4B 2GB boot failure
To manage
Yes, sure, but SRU procedures require defining at least some base test
criteria. So I'd like us to include info about which exact Pi device is
affected and needs to be tested + maybe a requirement to test it on a
few other Pi's as well, just to be sure we did not regress. We need to
look at the
The 'fix' is to backport the Pi fw from focal. The testcase is booting a
Pi :-)
The current bionic 5.4 raspi kernel is also a backport from focal so
that new combo for bionic is what we're currently running in focal. If
that's problematic we should have received focal bug reports by now.
--
You
I'm generally +1 on getting this accepted, and I know that writing SRU
information for such cases is not really easy (since it is not a
targeted fix just a new release version). But could we at least get a
formalized test case people might run? + any other nice-to-run tests to
make sure that we
** Tags removed: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940400
Title:
Pi 4B 2GB boot failure
To manage notifications about this bug go to:
I've installed the edge kernel on my Pi 4 Rev 1.4 2GB board and haven't
been able to recreate the issue:
jawn-smith@localhost:~$ snap info pi-kernel | egrep "installed|18-pi/edge"
tracking: 18-pi/edge
18-pi/edge: 5.4.0-1043.47~18.04.1 2021-08-25 (343) 193MB -
installed:
Discussed jawn-smith's failure to reproduce with juergh; it appears the
issue only affects certain Pi 4 2GB rev 1.4's but not others. The test
package prepared in
https://launchpad.net/~waveform/+archive/ubuntu/firmware appears to fix
the issue over several devices juergh has tested so I've pushed
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940400
Title:
Pi 4B 2GB boot failure
To manage notifications about this bug go to:
** Tags added: fr-1669
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940400
Title:
Pi 4B 2GB boot failure
To manage notifications about this bug go to:
** Changed in: linux-firmware-raspi2 (Ubuntu Bionic)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: linux-firmware-raspi2 (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
11 matches
Mail list logo
