** Patch added: "0002-UBUNTU-fix-missing-modules.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+attachment/5276122/+files/0002-UBUNTU-fix-missing-modules.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Patch added: "0001-UBUNTU-Config-enable-ARCH_MESON.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+attachment/5276121/+files/0001-UBUNTU-Config-enable-ARCH_MESON.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Source package with fix in:
https://people.canonical.com/~ppisati/lp1837073/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837073
Title:
linux 5.2.0-8.9 disabled backlight on s390x.
S
** Attachment added: "dcci-driver-linux_0.3.2-2_0.3.2-2ubuntu1.diff.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837073/+attachment/5278043/+files/dcci-driver-linux_0.3.2-2_0.3.2-2ubuntu1.diff.gz
--
You received this bug notification because you are a member of Kernel
Packages, w
** Description changed:
+ Impact:
+
+ Enable ARCH_MESON for arm64 as we already do in armhf.
+
+ Fix:
+
+ Apply the attached patches.
+
+ How to test:
+
+ Boot the patched kernel on a support MESON board.
+
+ Regression potential:
+
+ Low - the patch is enabling an architecture alreay enabl
Last working image / kernel version? First broken image / kernel
version? So we can compare the two.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1837209
Title:
Splash screen fa
If you remove the dtoverlay line (just tested it) and it works fine
during boot (before root is mounted), it means initrd has all necessary
modules to make it work, so it's not like initrd is missing something.
--
You received this bug notification because you are a member of Kernel
Packages, whi
Test kernel snap available here:
https://people.canonical.com/~ppisati/lp1837209/pi-
kernel_4.15.0-1041.44_armhf.snap
and precooked image here:
https://people.canonical.com/~ppisati/lp1837209/ubuntu-
core-18-pi_lp1837209fix.img.xz
--
You received this bug notification because you are a member
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1841146 (bionic/linux-hwe-edge)
--
-workflow/prepare-package
Importance: Medium
Assignee: Paolo Pisati (p-pisati)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-meta
Importance: Medium
Assignee: Paolo Pisati (p-pisati)
Status: In Progress
** Affects: kernel-sru-workflow
*** This bug is a duplicate of bug 1841159 ***
https://bugs.launchpad.net/bugs/1841159
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
Public bug reported:
Impact:
Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot:
...
[1.856849] arm-smmu da.arm,smmu: probing hardware configuration...
[1.859296] arm-smmu da.arm,smmu: SMMUv2 with:
[1.865845] arm-smmu da.arm,smmu:stage 1 translation
[1.870658]
** Description changed:
Impact:
Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot:
...
[1.856849] arm-smmu da.arm,smmu: probing hardware configuration...
[1.859296] arm-smmu da.arm,smmu: SMMUv2 with:
[1.865845] arm-smmu da.arm,smmu:stage 1 transla
Public bug reported:
Impact:
Ubuntu-snapdragon-4.15.0-1061.68 stacktraces during boot around msm
init:
[8.113018] msm_dsi_manager_register: failed to register mipi dsi host for
DSI 0
[8.131081] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops
[msm]): -517
[8.138234] msm 1a
** Description changed:
Impact:
- Ubuntu-snapdragon-4.15.0-1061.68 stacktraces during boot around msm
- init:
+ Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot around msm init.
+ Sometimes we get the following stack trace, or the boot completes and the
board hangs during reboot:
+ ...
** Summary changed:
- Kernel crash during msm init (or during shutdown)
+ Kernel hangs during msm init
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1841911
Title:
Kernel ha
** Description changed:
+ Impact:
+
We recently adjusted CONFIG_NVM to fix a build failure. The change
causing this was actually a mis-merge and will be reverted. However the
question came up whether it makes sense at all to build any raspberry
kernel with NVME support at all. There curre
nel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
--
You recei
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisat
** Description changed:
+ Impact:
+
+ apt-get source suggets the wrong instructions when inquiring for linux-
+ meta-raspi2:
+
+ $ apt-get source linux-meta-raspi2
+ ...
+ NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version
control system at:
+ git://git.launchpad.net/~ubun
Armhf is already using zImage (and the kernel decompress itself once we
jump to it), so this is an arm64-only issue and no, there's no reason to
have vmlinuz uncompressed as long as the bootloader can handle it - i'll
send a fix to switch to Image.gz in Eoan.
--
You received this bug notification
I realize this is just a workaround (and the above 31M cma memory
fragmentation is ugly), but we should definitely bump CMA allocation
space: definitely 32M (since that's what upstream default to) but if 64M
solves a problem you have at the moment (until we sort out the driver
issue), i'm not oppos
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1808056
Title:
vmlinuz is very large
Yes, arm64 kernels don't have any decompressor build-in (and they'll
never get one) - i'm fine with your idea of compressing / decompressing
kernels upon installation (to avoid regression in corner cases) but i
would like (at some point in the future) to switch to compressed kernels
though (next LT
Yes, i have all the hardware to do some testing, prepare some kernels
and we can take it from there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors
** Changed in: linux-raspi2 (Ubuntu)
Assignee: Paolo Pisati (p-pisati) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1808056
Title:
vmlinuz is very large
Here are dmesg and meminfo for all 3 cases (generuic, cma3 and
cma3=64M):
https://people.canonical.com/~ppisati/lp1823753/
Other than the different memory alloaction, i didn't notice any evident
regression.
--
You received this bug notification because you are a member of Kernel
Packages, which
Can you add all the relevant information here?
How to reproduce the issue (kernel version pre & post regression),
hardware used (cpu board, io board), an accurate description of the
issue (what *exactly* was working before the regression, what didn't
work after the breakage, etc), any other releva
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Paolo Pisati (p-pisati)
Status: Confirmed
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which
** Description changed:
+ Impact:
+
+ The linux-raspi2 kernel doesn't have the necessary UEFI hooks to boot on
+ a UEFI enabled system.
+
+ Fix:
+
+ Enable the relevant UEFI options (see the attached patch).
+
+ How to test:
+
+ On a patched kernel, UEFI presence will be check during boot:
+
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1831219
BugLink: https://bugs.launchpad.net/bugs/1825235
Impact:
Since the release of Ubuntu Disco, the upstream RaspberryPI BSP has
received a lot of bug fixes and improvements over the release imported
in disco/raspi2.
Among the fi
On the kernel side, the switch to a compressed kernel is a trivial
change:
diff --git a/debian.raspi2/rules.d/arm64.mk b/debian.raspi2/rules.d/arm64.mk
index ada61b8..9f82433 100644
--- a/debian.raspi2/rules.d/arm64.mk
+++ b/debian.raspi2/rules.d/arm64.mk
@@ -3,7 +3,7 @@ build_arch = arm64
h
Public bug reported:
Impact:
The bionic/snapdragon kernel should work on qcom410 and qcom820
chipsets, but due to some bugs, it never booted on any qcom820 board
(e.g. Qualcomm DB820C APQ8096).
Fix:
Import all the necessary patches (see the pull request below).
How to test:
1) put the board i
** Summary changed:
- Enable the Qualcomm DB820C board
+ Initial support for Qualcomm Snapdragon 820 chipset
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1832012
Title:
Ini
** Description changed:
Impact:
- The bionic/snapdragon kernel should work on qcom410 and qcom820
- chipsets, but due to some bugs, it never booted on any qcom820 board
- (e.g. Qualcomm DB820C APQ8096).
+ Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm
landing
+ tree
** Description changed:
Impact:
- Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm
+ Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm
landing tree kernel[1], it didn't work on Snapdragon 820 based board
(e.g. Qualcomm DB820C APQ8096).
F
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1825235
Title:
Load average inexplicably high with 5.0 kernel o
I can reproduce the bug on a fresh installation of Disco/armhf rpi3.
Moreover, the bug appears to be kernel in-kernel - by installing the
Disco kernel on a Bionic image (that didn't show any abnormal load with
its Bionic/armhf kernel), the bug appears there too.
The bug is reproducible as early a
p;id=ce621b56138a15dd3c67d6b40429f5739a6b51ec
Once positively verified, add a step by step test procedure to this bug
so we can move forward with integrating the changes.
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1827750
Title:
Not boot with EFI
Status in linux-raspi2 packa
Copied out that package, try again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1827750
Title:
Not boot with EFI
Status in linux-raspi2 package in Ubuntu:
Incomplete
Bug de
23 (and pc-kernel #196), kernel snap's initrd went
missing all fb kmods - that was workarounded for pi-kernel last week
by manually adding the modules back in:
commit edd1f8914fded36d4739fd24cdbdd05c5cf37611
Author: Paolo Pisati
Date: Tue Jul 23 11:30:49 2019 +0200
Initrd modu
Public bug reported:
Impact:
Around pi-kernel #23 (and pc-kernel #196), kernel snap's initrd went
missing all fb kmods - that was workarounded for pi-kernel last week by
manually adding the modules back in:
commit edd1f8914fded36d4739fd24cdbdd05c5cf37611
Author: Paolo Pisati
Date: Tue J
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: New
** Affects: kernel-sru-workflow/prepare-package
Importance: Medium
Assignee: Paolo Pisati (p-pisati)
Status: In Progress
** Affects: kernel-sru-workflow/prepare-package-meta
Importance: Medium
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisa
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
variant: debs
** Affects: ke
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 186
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 186
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 186
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 186
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 186
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 186
FWIW, i'm having a similar problem on Focal 5.4:
https://paste.ubuntu.com/p/CdFBr9QmHp/
...
libbpf: Error loading .BTF into kernel: -22.
Failed to load SK_SKB verdict prog
but i have clang-10:
ii clang1:10.0-50~exp1 amd64
C, C++ and Obje
There were several nvme related commits in the last kernel upload
(Ubuntu-5.4.0-24.28), could you try it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1871611
Title:
multipath nvme, fa
I've posted some test kernel with the RT_GROUP_SCHED option turned off
here:
https://people.canonical.com/~ppisati/lp1873315/
can you test it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Description changed:
+ Impact:
+
+ Software that requires RT priority is not working anymore since we
+ turned on RT_GROUP_SCHED:
+
+ commit 9b039fc517876d312e7fa0955571101a299c91f5
+ Author: Seth Forshee
+ Date: Mon Apr 6 07:11:44 2020 -0500
+
+ UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y
+
** Description changed:
Impact:
Software that requires RT priority is not working anymore since we
turned on RT_GROUP_SCHED:
commit 9b039fc517876d312e7fa0955571101a299c91f5
Author: Seth Forshee
Date: Mon Apr 6 07:11:44 2020 -0500
UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y
Here is a test kernel, could you test it and tell us if it fixes your
problem?
https://people.canonical.com/~ppisati/lp1871182/
linux-image-unsigned-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb
linux-modules-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb
linux-modules-extra-5.4.0-25-generic
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
- This is another case of linux-kvm having unexplained differences
- compared to linux-generic in areas that aren't related to hardware
- drivers (see other bug we filed for missing nft).
+ [Description]
+
+ Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
*
You are running an old Eoan kernel:
...
Package: linux-image-generic 5.3.0.29.33
...
can you update to the latest Eoan kernel and report if such a bug still
exist?
linux-image-generic | 5.3.0.40.34| eoan-updates | amd64, arm64, armhf,
ppc64el, s390x
--
You received this bug notificat
*** This bug is a duplicate of bug 1850439 ***
https://bugs.launchpad.net/bugs/1850439
** This bug has been marked a duplicate of bug 1850439
No sound on ASUS UX534FT
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863627
Title:
Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem
Looks like a grub config syntax error, definitely not a kernel issue:
...
Found Debian GNU/Linux 10 (buster) on /dev/sdc2
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 178
Syntax errors are detected in generated GRUB config file.
Ensure that there are no
Which kernel version are you using?
Please run "apport-collect 1863761" on your laptop.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863761
Title:
CONFIG_HID_SENSOR_HUB=m makes keybo
Michael, could you check if this kernel fixes your issue?
https://people.canonical.com/~ppisati/lp1863810/
linux-buildinfo-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb
linux-cloud-tools-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb
linux-headers-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64
Could you test if latest Focal kernel and firmware fix this issue?
linux-image-generic | 5.4.0.14.17
linux-firmware | 1.186
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1861237
Disconnect the laptop from the docking station, boot into the
problematic kernel, and run `apport-collect 1863864` again.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
--
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
*
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
--
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
*
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
--
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
*
Public bug reported:
[Impact]
Upstream has good support for qcom410 and 820 chipsets, so enable the
Dragonboard410c and db820c out of generic
[Fix]
Apply the packaging and config changes in the below pull request
[How to test]
Boot the resulting kernel on the db410c / db820c boards
[Regressi
** Description changed:
[Impact]
- Upstream has good support for qcom410 and 820 chipsets, so enable the
- Dragonboard410c and db820c out of generic
+ Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820
+ SOCs, so enable the Dragonboard410c and Dragonboard820c out of it,
+ i
** Summary changed:
- Enable the Dragonboards out of eoan/generic
+ Enable the Dragonboards out of Eoan/generic arm64 kernel
** Summary changed:
- Enable the Dragonboards out of Eoan/generic arm64 kernel
+ Enable the Dragonboards out of Eoan/master arm64 kernel
** Description changed:
[Impac
** Description changed:
[Impact]
- Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820
- SOCs, so enable the Dragonboard410c and Dragonboard820c out of it,
- isolating all the changes in a 'snapdragon' flavour.
+ Upstream has good support for Qcom Snapdragon SOCs, so enable
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisa
eam (canonical-kernel-team) => Paolo Pisati
(p-pisati)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati
(p-pisati)
*
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Hui Wang (hui.wang)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1847596
Title:
rpi3b+: corrupted screen on h
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
1 - 100 of 718 matches
Mail list logo
