** Changed in: kunpeng920/upstream-kernel
Status: Triaged => Fix Committed
--
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/1853999
Title:
[sas-1126]scsi: hisi_sas: use wait_for_com
** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.5
--
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/1854550
Title:
[scsi-1130]scsi: scsi_transport_sas: Fix memory
ntu-19.10
Milestone: None => ubuntu-19.10-sru-5
** Changed in: kunpeng920/ubuntu-19.10
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: kunpeng920/ubuntu-20.04
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920/ubuntu-20.04
Status: Tria
** Changed in: kunpeng920/ubuntu-19.04
Status: New => Triaged
** Changed in: kunpeng920/ubuntu-19.10
Status: New => Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: kunpeng920/ubuntu-19.04
Milestone: ubuntu-19.04-sru-11 => ubuntu-19.04-sru-12
--
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/1853997
Title:
[sas-1126]scsi: hisi_sas: F
There is no plan to reapply the kernel side of these fixes ahead of
18.04.4. Introducing the mdadm side of that in 18.04.4 therefore would
cause a regression in functionality:
ubuntu@ip-172-30-0-208:~$ sudo mdadm --create /dev/md0 --run
--metadata=default --level=0 --raid-devices=2 /dev/xvdb /dev/
Adding the block-proposed-* tags as per comment #11.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-eoan
** Tags added: block-proposed-bionic block-proposed-disco block-proposed-eoan
verification-done verification-done-bionic verific
** Changed in: kunpeng920
Status: In Progress => Triaged
--
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/1854549
Title:
[acc-1130]sync mainline kernel 5.5rc1 acc patchset into ubu
** Changed in: kunpeng920
Status: In Progress => Triaged
--
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/1850117
Title:
[hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ub
@Ike: fyi, I have already prepared a backport for focal here:
https://code.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux/+ref/lp1850117-f
I just didn't have a way to test it. Feel free to start with that (or not) :)
--
You received this bug notification because you are a member of Kerne
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
--
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/1852723
Title:
[Regression] Bionic kernel 4.15.0-71.80 can not bo
With earlycon on, I am able to get more output. This looks like a
smoking gun:
[0.460249] CPU features: CPU1: Detected conflict for capability 11
(Virtualization Host Extensions), System: 0, CPU: 1
git blame for this error message points at:
e988af0188e30 arm64: capabilities: Unify the verifi
My bisect landed on:
628859e8621cb arm64: capabilities: Change scope of VHE to Boot CPU feature
I'm doing a build w/ that patch reverted to verify.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Yes, reverting just that change seems to fix it for me on a Sabre board.
--
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/1852723
Title:
[Regression] Bionic kernel 4.15.0-71.80 can not boo
How frequently does this occur? Are the backtraces always the same?
--
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/1853485
Title:
Bionic kernel panic on Cavium ThunderX CN88XX
Status in
** Tags added: dgx2-performance-regression
--
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/1853927
Title:
Stream Scale Time is 12% higher in 4.15.0-70.77 than 4.15.0-68.75
Status in linu
** Tags added: dgx2-performance-regression
--
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/1853930
Title:
io RAID Read 100% Rand 128K 4 jobs depth 8 test for Config 1 shows
-11.23 % dro
** Tags added: dgx2-performance-regression
--
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/1853928
Title:
Stream Scale Rate Test shows -11.99% lower for Config 1 in
4.15.0-70.77 than 4.
Tracking the reapplication of the reverted patches in bug 1854207.
--
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/1853326
Title:
[Regression] Bionic kernel 4.15.0-71.80 can not boot on T
Public bug reported:
We reverted a couple changes in 4.15.0-72.81 because they were causing a
regression (bug 1853326) that was not understood at press time:
b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"
5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not a
** Changed in: kunpeng920/upstream-kernel
Status: Triaged => Fix Committed
** Changed in: kunpeng920/ubuntu-20.04
Status: Triaged => In Progress
** Changed in: kunpeng920/ubuntu-20.04
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubu
Public bug reported:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
[Test Case]
dmesg | grep "Cannot enable"
[Fix]
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
git bisect reports:
0b6a70743beacb15516ef9572b40c93b8b3892d3 is the first bad commit
commit 0b6a70743beacb15516ef9572b40c93b8b3892d3
Author: Jan-Marek Glogowski
Date: Fri Feb 1 13:52:31 2019 +0100
usb: handle warm-reset port requests on hub resume
--
You received this bug notification because
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Description changed:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
+
+ Kernel emits messages like:
+ usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[Test Case]
dme
Running upstream 5.5-rc2 mainline build:
$ dmesg | grep -e usb -e xhci -e hub
[ 13.482690] usbcore: registered new interface driver usbfs
[ 13.486685] usbcore: registered new interface driver hub
[ 13.490894] usbcore: registered new device driver usb
[ 20.767117] xhci_hcd :00:14.0: xHC
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1854207
Title:
Unrevert "arm64: Use firmware to detect CPUs that are not
I can reproduce on 4.15.0-107.73, the current -updates kernel:
ubuntu@dragon410c:~$ ls /sys/devices/system/cpu/cpufreq/
ubuntu@dragon410c:~$
So this is not a regression with current -proposed.
With 4.15.0-45.48 (the one from the ppisati image):
ubuntu@dragon410c:~$ ls /sys/devices/system/cpu/cpufr
Correction: that should be 4.15.0-1070.73.
4.15.0-1053.57, which appears to be the oldest one in the archive,
*does* have those files.
--
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/
1057.62 has them, 1058.64 does not.
I noticed that 1057.62 has only the performance governor built-in, and
1058.64 only has the on-demand governor built-in.
ubuntu@dragon410c:~$ grep CPU_FREQ_DEFAULT_GOV
/boot/config-4.15.0-1057-snapdragon /boot/config-4.15.0-1058-snapdragon
/boot/config-4.15.0
@djgalloway: If you haven't removed your previously working older
kernel, you should be able to boot into it from the GRUB menu. Another
suggestion would be to boot into rescue mode from an Ubuntu 18.04.3 ISO.
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1854000
Title:
[sas-1126]scsi: hisi_sas: Replace in_
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1850117
Title:
[hpre-1017]sync mainline kernel 5.4rc
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1853999
Title:
[sas-1126]scsi: hisi_sas: use wait_fo
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1854549
Title:
[acc-1130]sync mainline kernel 5.5rc1
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1854550
Title:
[scsi-1130]scsi: scsi_transport_sas:
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1855952
Title:
scsi: hisi_sas: Check sas_port before
** Changed in: kunpeng920/upstream-kernel
Status: Fix Committed => Fix Released
--
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/1855958
Title:
scsi: hisi_sas: Return directly if in
We carry this patch in focal - do we just need to backport it to bionic?
http://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
I uploaded a test fix to ppa:dannf/test. Could someone w/ hw access
verify that?
--
You received this bug notification b
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: dmidecode (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: dmidecode (Ubuntu Eoan)
Status: New => In Progress
** Changed in: dmidecode (Ubuntu Bionic)
Status: New => I
Actually, I realized I can reproduce this on a dragonboard I have here.
I've verified the PPA fix myself, so I'll go ahead and SRU.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/185861
** Description changed:
- Device: Inforce 6640
-
https://www.inforcecomputing.com/products/single-board-computers-sbc/qualcomm-snapdragon-820-inforce-6640-sbc
- SoC: Snapdragon 820
+ [Impact]
+ Running 'sudo dmidecode' on non-UEFI ARM systems can cause them to
crash/reboot. cloud-init apparently
** Also affects: dmidecode (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: dmidecode (Ubuntu Xenial)
Status: New => In Progress
** Changed in: dmidecode (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notifi
Another instance:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/s/systemd/20200127_181441_fb524@/log.gz
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubunt
Notice in the log in comment #6 that the unexpected error we are seeing
for "unhappy-2" is the expected error for "unhappy-1".
I wonder if there's a race here:
# tests for error conditions
for f in unhappy-*.input; do
echo "*** Running test $f"
rm -
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Expired
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Expired
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
ystemd (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: systemd (Ubuntu Eoan)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notific
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1776654
Title:
systemd upstream sysusers tests fails
Sta
My $0.02 is that we should mark this Invalid. We appear to have
intentionally changed the governor, and that new governor does not
expose the attributes that the old one did. @Gavin: is this causing any
issue for you, or is it just something your testing noticed?
** Changed in: linux-snapdragon (U
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
--
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/1
I attempted to bisect this, using the following process:
- Run the kernel-build-reboot-loop test on 3 machines in parallel
I used 2 CRB1S systems (anuchin, bestovius) and 1 R120-T33 (seidel)
- If any machine crashes w/ the parity error message, consider it failed
- If all machines survive
Looking at the git log - I wonder if this could be related?
commit 94bb804e1e6f0a9a77acf20d7c70ea141c6c821e
Author: Pavel Tatashin
Date: Tue Nov 19 17:10:06 2019 -0500
arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess
fault
It's interesting because ThunderX is somewhat un
The patch I highlighted in Comment #9 appears to be unrelated -
4.15.0-76 still fails even though it has the patch. A test build of
4.15.0-76 w/ the patch reverted also fails.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Changed in: linux (Ubuntu Disco)
Status: Triaged => Won't Fix
--
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/1860013
Title:
[thunderx] Synchronous External Abort: synchronous p
e/b/x all verified on a dragonboard 410c
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
Both crmsh autopkgtest failures could be explained by a flaky network
connection. The eoan one is certainly that - it's unable to connect to
the archive. The error from the bionic case is masked - but the test is
trying to apt install vim. That could obviously also be an archive
connectivity issue.
** Changed in: kunpeng920/ubuntu-19.04
Status: Fix Committed => Fix Released
--
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/1845355
Title:
Support Hi1620 zip hw accelerator
Statu
)
Importance: Critical
Assignee: dann frazier (dannf)
Status: Confirmed
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Focal)
Importance
OK - this is a messy one. It is due to the backport of this:
https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9
Reverting that is probably not the right answer because the point of it
is to avoid corruption. But this is a pretty serious usability issue. It
is not at
** Description changed:
- [Impact]
- After installing the 4.15.0-67.76 kernel from bionic-proposed, our Nvidia
DGX2 system is no longer bootable.
+ Users of RAID0 arrays are susceptible to a corruption issue if:
+ - The members of the RAID array are not all the same size[*]
+ - Data has been wr
** Description changed:
Users of RAID0 arrays are susceptible to a corruption issue if:
- - The members of the RAID array are not all the same size[*]
- - Data has been written to the array while running kernels < 3.14 and >=
3.14.
+ - The members of the RAID array are not all the same size[
** Description changed:
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are not all the same size[*]
- Data has been written to the array while running kernels < 3.14 *and* >=
3.14.
- Upstream is dealing with this by adding a versioned la
I've proposed changing the error message to point to a webpage w/ a better
explanation:
https://marc.info/?l=linux-raid&m=157196348406853&w=2
--
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
This appears to be a new driver, so backporting it should not be a
significant regression risk.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Im
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920/upstream-kernel
Status: New => Triaged
** Also affects: kunpeng920/ubu
** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.5
--
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/1850117
Title:
[hpre-1017]sync mainline kernel 5.4rc3 hpre patc
** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04-ga
--
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/1850117
Title:
[hpre-1017]sync mainline kernel 5.4rc3 hpre pa
Public bug reported:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug tracks the re-application of that fix once we have a full
solution.
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are not all the same size[*
** Description changed:
+ This bug tracks the temporary revert of the upstream fix for a
+ corruption issue. Bug 1850540 tracks the re-application of that fix once
+ we have a full solution.
+
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are
I've nominated mdadm for this issue as well because it currently does not:
1) Let you create a new raid0 array w/o first setting a default_layout, which
will regress behavior in installers, etc.
2) save the layout version in the raid config, so you need to set
default_layout - or set individu
** Description changed:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug tracks the re-application of that fix once we have a full
solution.
Users of RAID0 arrays are susceptible to a corruption issue if:
- The members of the RAID array are not all
** Description changed:
Bug 1849682 tracks the temporarily revert of the fix for this issue,
while this bug tracks the re-application of that fix once we have a full
solution.
+
+ Fix checklist:
+ [ ] Restore c84a1372df929 md/raid0: avoid RAID0 data corruption due to layout
confusion.
+ [
Our testing found the same issue on 2 other CN88XX systems (seidel &
anuchin), I'll attach the logs here. Interestingly, while both systems
hit the oops when booting the bionic 4.15.0-74.84, neither system had a
problem with the xenial hwe 4.15.0-74.84.
--
You received this bug notification becau
** Attachment added: "anuchin-4.15.0-74.84-xenial-no-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317961/+files/anuchin-4.15.0-74.84-xenial-no-oops.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Attachment added: "seidel-4.15.0-74.84-xenial-no-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317963/+files/seidel-4.15.0-74.84-xenial-no-oops.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** Attachment added: "anuchin-4.15.0-74.84-bionic-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317960/+files/anuchin-4.15.0-74.84-bionic-oops.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Attachment added: "seidel-4.15.0-74.84-bionic-oops.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5317962/+files/seidel-4.15.0-74.84-bionic-oops.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
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/1857074
Title:
Cavium ThunderX CN88XX Panic : Unknown reason
Status i
Tagging verification-failed due to bug 1857074.
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
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/1853485
Marking verification failed, as that is blocked by bug 1857074.
** Description changed:
We reverted a couple changes in 4.15.0-72.81 because they were causing a
regression (bug 1853326) that was not understood at press time:
b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hv
@kaihengfeng - sorry for the delay over the US holidays. I don't have
physical access to the system myself, but I've made the request to a
user who does.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Attachment added: "'dmesg | grep -e usb -e xhci -e hub' w/ usbcore.dyndbg=+p"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+attachment/5318666/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
*** This bug is a duplicate of bug 1857074 ***
https://bugs.launchpad.net/bugs/1857074
** This bug has been marked a duplicate of bug 1857074
Cavium ThunderX CN88XX Panic : Unknown reason
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
crash autopkgtests have began to fail on arm64, as seen here:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/arm64/c/crash/20191223_190616_50c73@/log.gz
The significant difference between this test and the l
18892/+files/recht-console.log
** Changed in: linux (Ubuntu Focal)
Assignee: dann frazier (dannf) => (unassigned)
--
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/1856608
Title:
[Regressi
** Also affects: crash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1859226
Title:
crash reports Illegal instruction w/ newer binut
This appears to fix it for me:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;a=commitdiff;h=8cd0e5e93145699736a370b271ff03f3f41670b0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/b
in: binutils (Ubuntu)
Status: New => Fix Committed
** Changed in: binutils (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: crash (Ubuntu)
Status: New => In Progress
** Changed in: crash (Ubuntu)
Assignee: (unassigned) => dann frazier (dan
fyi, I was able to reproduce this w/ upstream 4.14.164, built w/ an
Ubuntu-based config.
** Attachment added: "4.14.164.dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5319909/+files/4.14.164.dmesg
--
You received this bug notification because you are a member
** Attachment added: "4.14.164.config"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/+attachment/5319910/+files/4.14.164.config
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
v4.14.151 upstream fails as well - but with a different symptom (see
below). v4.14.150 seems fine, so I'll try and bisect between the two. Of
course, that's really just a shot in the dark, as we know this issue is
finicky..
[ 34.896151] Unable to handle kernel paging request at virtual address
On Tue, Jan 14, 2020 at 8:35 AM Juerg Haefliger
<1857...@bugs.launchpad.net> wrote:
>
> We certainly want this:
>
> commit 71c751f2a43fa03fae3cf5f0067ed3001a397013
> Author: Mark Rutland
> Date: Mon Apr 23 11:41:33 2018 +0100
>
> arm64: add sentinel to kpti_safe_list
Agreed, nice catch. Unf
Public bug reported:
This bug tracks the reapplication of "usb: handle warm-reset port
requests on hub resume".
We reverted "usb: handle warm-reset port requests on hub resume" from
the Ubuntu kernels due to a regression it introduced (bug 1856608).
However, that patch did fix an issue for a user
We reverted the offending patch while we continue to work towards root
causing the failure. The revert will cause this bug to be resolved, so
I've opened bug 1859873 to track fixing and reapplying the patch (+ any
fixes). I suggest we move further technical discussion there.
** Description changed
I built a kernel with the proposed patches[*] and ran a reboot/kernel
compile test on 4 systems. The tests survived 46 total iterations
(~12/system) before I interrupted. Two systems failed with "Synchronous
External Abort: synchronous parity or ECC error" errors.
I've reverted the systems back to
I've now seen an occurrence of the the SEA/ECC issue on a system w/ the
4.15.0-70 kernel, so I think we can safely assume this is not a
regression related to this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
The description shows 2 Oops messages - one in IPMI, and one in ext4. I
had marked this as a duplicate of bug 1857074 because the ext4 symptom
is in both. But, per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857074/comments/18
, the IPMI issue exists even with the fix for LP: #1857074. So
Public bug reported:
[Impact]
Under load, ThunderX systems eventually fail with:
[ 282.360376] Synchronous External Abort: synchronous parity or ECC error
(0x9618) at 0xa6eb7000
[ 282.372351] Internal error: : 9618 [#1] SMP
[ 282.379152] Modules linked in: nls_iso8859_1 thunde
On Wed, Jan 15, 2020 at 11:28 PM Juerg Haefliger
wrote:
>
> On Thu, 16 Jan 2020 02:14:16 -0000
> dann frazier wrote:
>
> > I built a kernel with the proposed patches[*] and ran a reboot/kernel
> > compile test on 4 systems. The tests survived 46 total iterations
&
201 - 300 of 1628 matches
Mail list logo
