** Description changed:
[Impact]
The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe
errors to the AER (Advanced Error Reporting) driver, which surfaces them to
userspace. However, we're currently only reporting "recoverable" errors and not
errors of other types (e
hould be an entry for the injected error, as shown below:
No Memory errors.
PCIe AER events:
1 2018-05-07 17:55:46 + Fatal error: Receiver Error
No Extlog errors.
No MCE errors.
[Regression Risk]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because
river, and the HisSilicon D05 and
D06 are the only two boards Ubuntu supports that use this driver. Explicit
testing on these two boards should mitigate the regression risk.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Af
signed) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
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/1768971
Title:
Warnings
this writing, there are no changesets in linux-next
marked as Fixing this commit, implying that upstream has not yet found/fixed
any bugs related to it.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (U
Public bug reported:
[Impact]
Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer
dereference, leading to a crash:
[ 2366.923208] Unable to handle kernel NULL pointer dereference
at virtual address 07b8
...
[ 2368.766334] Call trace:
[ 2368.781712] [] sas_find_dev_by_rph
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug
linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ker
such system in the field - most SDEI-based systems will likely
be ACPI based.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (
** Description changed:
[Impact]
In bug 1756096, we backported SDEI (Software Delegated Exception Interface)
support for arm64. However, this backport missed 2 changes that make the SDEI
entry point a trampoline which make sure the kernel is mapped before
processing. (The kernel may not be
SDEI.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu B
ubuntu@d05-1:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
ubuntu@d05-1:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
enahisic2i0-tx0
enahisic2i0-tx1
enahisic2
ubuntu@hotdog:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
ubuntu@hotdog:~$ sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support : MD5
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
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/1767490
Title
ubuntu@hotdog:~$ sudo perf list | grep thunderx2
thunderx2 imp def:
ubuntu@hotdog:~$ cat /proc/version
Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0
(Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018
** Tags removed: verification-needed-ar
ubuntu@hotdog:~$ dmesg | grep W+X
[ 35.653992] arm64/mm: Found insecure W+X mapping at address
00ac9000/0x00ac9000
[ 36.046414] Checked W+X mappings: FAILED, 12 W+X pages found, 0 non-UXN
pages found
Yep, that's in the userspace mapping.
** Tags removed: verification-needed-
Regression Risk]
Including a new driver is a common practice that should have minimal regression
risk.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Kerne
For xenial and artful, I have verified by:
1) Deploying an arm64 system (Cavium ThunderX CRB1S), enabling proposed,
installing kdump-tools, rebooting, then triggering a dump.
2) Regression/upgrade tested on x86 by launching a guest, installing
kdump-tools, rebooting, then trigger a dump. Next, e
ic2i0-tx11
enahisic2i0-tx12
enahisic2i0-tx13
enahisic2i0-tx14
enahisic2i0-tx15
[Regression Risk]
Upstream patch, restricted to a single driver for a system we can directly test.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: I
(Ubuntu Artful)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Art
There's no evidence that this is a kernel issue - this works fine when
executing qemu directly:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/comments/13
I'm not a regularly user of uvt - but it looks like the guest is booting
up and you're able to talk to it over the network, but
This works fine for me now, see attached. bug 1765668 is a different
issue, unrelated to the kernel.
** Attachment added: "xenial-guest-in-bionic.log"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5123982/+files/xenial-guest-in-bionic.log
--
You received this bug no
I've tried a couple memory testers:
- Userspace 'memtester', which passed overnight
- Kernel's 'memtest' cmdline arg, which also passed earlyboot. Running
stress-ng afterwards still reported errors.
Attached is the console log from the kernel 'memtest' run. Note that I
saw 3 ECCs here, the last
** Description changed:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
-
** Description changed:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
+
ew => Fix Released
** Changed in: kexec-tools (Ubuntu)
Status: New => Fix Released
** Changed in: kexec-tools (Ubuntu Xenial)
Status: New => In Progress
** Changed in: kexec-tools (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: makedu
Public bug reported:
[Impact]
Crash dump support doesn't work by default on any known arm64 platform. Users
have to figure out working incantations for the crashkernel= parameter and the
parameters passed to the crash-dump kernel themselves and manual edit 2
different config files.
[Test Case]
** Changed in: makedumpfile (Ubuntu Artful)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1694859
Title:
arm64 kernel crashdump support
** Description changed:
We're carrying a couple SAUCE patches for the hisi_sas driver to enable
- hip08 SoC support. Alternative patches have since landed upstream, which
- are more complete, and will be a better basis for backporting future
- patches to this driver.
+ hip08 SoC support. One of
The problem appears to be that acpi=force is being specified on the
command line. Not all arm64 servers support ACPI and, even for the ones
that do, there isn't sufficient support in the 4.4 kernel to support
them.
--
You received this bug notification because you are a member of Kernel
Packages,
buntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
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/1762824
Title:
hisi_sas: Revert and replace SAUCE pa
** Description changed:
[Impact]
There are several stability issues with the i2c-xlp9xxx that cause
communication issues between the host and the BMC, leading to unpredictable
results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0).
[Test Case]
Reboot the system s
we have no port).
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubu
ubuntu@alekhin:~$ cat /proc/version
Linux version 4.13.0-39-generic (buildd@bos02-arm64-024) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #44~16.04.1-Ubuntu SMP Thu Apr
5 16:44:45 UTC 2018
ubuntu@alekhin:~$ dmesg | grep "failed to claim resource for efifb"
** Tags removed:
10:18 2018 +0100
RDMA/hns: ensure for-loop actually iterates and free's buffers
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
e upstream patches.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
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/1762
Public bug reported:
HiSilicon hip08 systems support a cq/rq record feature for RDMA that is
currently not supported by the kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification
cided
Assignee: dann frazier (dannf)
Status: In Progress
** Summary changed:
- hns3 support
+ Hisilicon Network Subsystem Support HNS3
** Summary changed:
- Hisilicon Network Subsystem Support HNS3
+ Hisilicon network subsystem 3 support
** Changed in: linux (Ubuntu)
Status
Since this appears to be a hardware issue, I'll mark Invalid. fyi, we're
working with the vendor to figure out next steps for lundmark.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is s
]
This teaches existing code about a new SoC, which should mitigate regressions
for all other platforms.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee
Ignore comment #4 - was meant for a different bug.
--
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/1747523
Title:
support thunderx2 vendor pmu events
Status in linux package in Ubuntu:
public bug 1760712
--
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/1747523
Title:
support thunderx2 vendor pmu events
Status in linux package in Ubuntu:
Fix Released
Status in linux so
I believe this occurred while running disk/disk_stress_ng_dm-1 from the
certification test suite on the system in our lab called "seuss", which
had been installed manually w/ d-i, using LVM w/ crypted home. (I dug
that info out of LP: #1749040, from whence this bug was spawned).
Since this crash o
** Summary changed:
- arm64 - stress_ng triggers panic on crypted lvm
+ kernel BUG at
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
These observations were on a system in our lab called "seuss". My
suggestions for next steps would be:
1) Determine how reliable this failure is.
a) Deploy xenial/hwe on seuss, and downgrade the kernel to the version in the
crash log (4.13.0-36-generic #40~16.04.1-Ubuntu).
b) Run the com.canoni
** Description changed:
Seen on a Cavium CRB1S a couple of times while running the
- com.canonical.certification::disk/disk_stress_ng_sda kernel from the
+ com.canonical.certification::disk/disk_stress_ng_sda testcase from the
canonical-certification-server test suite:
[ 1823.116031] Unab
Closing as Invalid, as I believe the problem is in firmware. Will reopen
if that proves false.
** Changed in: linux (Ubuntu Artful)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Invalid
--
You received this bug notification because you are a me
** Description changed:
[Impact]
The following error is reported on boot:
[6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
efifb!
This results in the efifb not being activated at boot. On this platform,
the same device will be initialized by the astdrmfb driv
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
** Description changed:
[Impact]
The following error is reported on boot:
[6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
efifb!
This results in the efifb not being activated at boot. On this platform,
the same device will be initialized by the astdrmfb driv
ance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New
** Changed in: linux (Ubuntu)
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/1623627
Title:
thunder: faulty TSO padding
Status in linux pack
** Changed in: linux (Ubuntu)
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/1624569
Title:
thunder: chip errata w/ multiple CQEs for a TSO p
What should be happening here is that:
1) The efifb driver initializes, detects a device.
2) The console driver makes the efifb an active console, and output appears
3) Later, the astdrmfb initializes, detects a device
4) The kernel checks for an overlap in the framebuffers used by efifb &
Verified by a Huawei engineer.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1752695
Title:
hisi_sas
Ran ethtool -p enahisic2i2 (the 10G onboard NIC), and an amber light
marked L/A flashed.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1745246
Title:
perf stat segfaults on uncore events w/o
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1747523
Title:
support thunderx2 vendor pmu events
Sta
artful verification:
dannf@alekhin:~$ cat /proc/version
Linux version 4.13.0-38-generic (buildd@bos02-arm64-005) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #43~16.04.1-Ubuntu SMP Wed Mar
14 17:49:43 UTC 2018
dannf@alekhin:~$ dmesg | grep i2c
[7.330023] i2c /dev entri
Verified:
ubuntu@starbuck:~$ cat /proc/version
Linux version 4.13.0-38-generic (buildd@bos02-arm64-005) (gcc version 5.4.0
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #43~16.04.1-Ubuntu SMP Wed Mar
14 17:49:43 UTC 2018
ubuntu@starbuck:~$ lsmod | grep cppc
cppc_cpufreq 16384 0
*
** Attachment added: "dmesg-bionic-host.txt"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084479/+files/dmesg-bionic-host.txt
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are
After updating to the proposed kernel, I was able to boot a xenial cloud
image with qemu-efi from both xenial (DTB mode) and bionic (ACPI mode).
** Attachment added: "dmesg-xenial-host.txt"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084478/+files/dmesg-xenial-host
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Public bug reported:
[Impact]
Using the SBSA watchdog will crash the OS on ThunderX2 systems. This is not an
issue in current firmware because the SBSA watchdog is not exposed - but it is
likely to be introduced in a future update.
[Test Case]
$ sudo bash
# cat < /dev/watchdog
[Regression Risk
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => 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/1755304
Title:
Regression: vga term no longer active on Cavium Th
Public bug reported:
Cavium ThunderX-based systems, such as the Cavium CRBs and Gigabyte
implementations, have an ASPEED VGA controller that can be viewed
remotely using a JAVA application exposed by the BMC. The kernel will
use serial as the default console on this platform but, with the xenial
G
This fix landed upstream in v4.11, so marking Fix Released.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1590168
T
My backport for option #3 has been merged, so no need for a change in
the cloud images or edk2.
** Changed in: cloud-images
Status: New => Invalid
** Changed in: edk2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Pac
)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Chang
Public bug reported:
[Impact]
A misleading error is occasionally emitted by the kernel.
[Test Case]
Boot a ThunderX system and watch for the error:
i2c-thunderx :01:09.4: unhandled state: 0
[Regression Risk]
Driver is specific to a platform, and the only functional change is skipping
the e
Public bug reported:
Seen on a Cavium CRB1S a couple of times while running the
com.canonical.certification::disk/disk_stress_ng_sda kernel from the
canonical-certification-server test suite:
[ 1823.116031] Unable to handle kernel read from unreadable memory at virtual
address 0038
[ 1823.12
I've reproduced the CRB1S panic with the current (non-kpti) kernel and
without crypt lvm (standard MAAS install) and reported bug 1754053 to
track it. We can rule that out as being caused by kpti.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
** Attachment added: "combined kern.log/serial log of lundmark SEA crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5071412/+files/lundmark-cert-failure-sea.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
I rebooted the machine (lundmark) and restarted the test mentioned in
the previous comment, this time the system crashed w/ a Synchronous
External Abort:
[23243.094384] Synchronous External Abort: synchronous parity or ECC
error (0x8618) at 0xb0f74f68
This suggests a non-software issu
On Mon, Mar 5, 2018 at 9:06 AM, dann frazier wrote:
> On Mon, Mar 5, 2018 at 7:47 AM, Paolo Pisati <1749...@bugs.launchpad.net>
> wrote:
>> Good, any other pending tests?
>
> Yes, just one more. I'm going to run the same test on the kpti kernel
> on a differen
On Mon, Mar 5, 2018 at 7:47 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> Good, any other pending tests?
Yes, just one more. I'm going to run the same test on the kpti kernel
on a different system of the same config, but *without* lvm crypt.
Starting that now.
--
You received this bug n
** Attachment added: "console.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753489/+attachment/5069934/+files/console.log
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Als
I was able to reproduce a crash on a crypted LVM system w/ the pre-KPTI
kernel. LP: #1753489.
The backtrace isn't identical, but it does show that crypted LVM was
fragile even before the KPTI patches.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Public bug reported:
[ 1678.415861] kernel BUG at
/build/linux-hwe-Fuabdm/linux-hwe-4.13.0/fs/jbd2/transaction.c:1868!
[ 1678.425019] Internal error: Oops - BUG: 0 [#1] SMP
[ 1678.430358] Modules linked in: nls_iso8859_1 i2c_thunderx i2c_smbus
cavium_rng_vf thunderx_edac thunderx_zip shpchp ipmi
On Mon, Mar 5, 2018 at 2:34 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> Is there a way for me to manually run disk/disk_stress_ng_dm-1?
I've just started a run on the server/config that failed the test, but
with a pre-kpti kernel, to see if it follows kpti or the
system/config. The comm
All failures expected.
** Attachment added: "Gigabyte R120 (ACPI mode ThunderX) results"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5067656/+files/r120.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
crb1s results - all expected failures except disk/disk_stress_ng_dm-1
which is what was running when the panic mentioned in comment #39
occurred.
** Attachment added: "results from thunderx crb1s"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5067655/+files/crb1s.htm
** Description changed:
[Impact]
The disk LED is not supported on HiSilicon D05 systems
[Test Case]
- View LED. (Not sure if this is a "online" LED or an "activity" LED yet)
+ Plug in disk, view LED.
[Regression Risk]
Code only touches the hisi_sas driver, so risk is limited to pla
On Fri, Mar 2, 2018 at 4:48 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> If the bug in #39 is not related to kpti, can you spawn it into a
> separate LP bug and add a reproducer?
If it is shown to not be related to KPTI after I run those further
tests, that is the plan.
-dann
--
You
I've seen a couple crashes on a ThunderX CRB1S system - though at this
point I don't have reason to believe it is related to KPTI. This system
happened to be installed with LVM + crypted home, and we haven't ran the
cert tests on such a config before. After the remaining tests complete,
I plan to r
** Attachment added: "sabre test results - all errors expected"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066572/+files/submission_2018-03-01T15.11.01.312793.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
)
Status: New => Fix Released
** Changed in: makedumpfile (Ubuntu Artful)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kexec-tools (Ubuntu Artful)
Status: New => Fix Relea
** Also affects: kexec-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: kexec-tools (Ubuntu
** Description changed:
[Impact]
The disk LED is not supported on HiSilicon D05 systems
[Test Case]
+ View LED. (Not sure if this is a "online" LED or an "activity" LED yet)
[Regression Risk]
Code only touches the hisi_sas driver, so risk is limited to platforms that
use it (i.e.
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Bionic)
Public bug reported:
[Impact]
The disk LED is not supported on HiSilicon D05 systems
[Test Case]
[Regression Risk]
Code only touches the hisi_sas driver, so risk is limited to platforms that use
it (i.e. the D05)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
D05 & QDF2400 errors are all expected, thanks Manoj!
--
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/1749040
Title:
KPTI support for arm64 systems
Status in linux package in Ubuntu:
In
On Thu, Mar 1, 2018 at 8:50 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> I see 5 failures marked as blocker there: 4 couldn't complete due to the
> test environment, and 1[*], apparently, is a CONFIG issue (so something
> that predates this patchset).
Sorry - I didn't have time to analyz
** Attachment added: "Updated test results from an HP m400 (X-Gene) system"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5065762/+files/submission_2018-03-01T05.58.16.640032.html
--
You received this bug notification because you are a member of Kernel
Packages, whi
Refreshed kernel now in ppa:dannf/kpti
--
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/1749040
Title:
KPTI support for arm64 systems
Status in linux package in Ubuntu:
Incomplete
Statu
On Wed, Feb 28, 2018 at 10:12 AM, Paolo Pisati
<1749...@bugs.launchpad.net> wrote:
> Found && fixed.
>
> https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/log/?h=artful-
> master-next-arm64-kpti-414-backport
>
> I pushed two fixes on top of it:
>
> 1) 'syscalls: Use CHECK_DATA_CORRUPTION for
tu)
Importance: Medium
Assignee: dann frazier (dannf)
Status: In Progress
--
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/1752146
Title:
errors with sas hotplug
Status
Right - I should've mentioned that - the issue follows the guest kernel
for me as well. I tested w/ latest upstream for both just in case the
guest failure is a somehow a side-effect of a host kernel bug.
Also, I should have mentioned that this is an intermittent failure for
me. I sometimes have t
901 - 1000 of 1626 matches
Mail list logo
