** 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
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 Ubuntu
Bugs, which is subscribed t
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
** 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 Ubuntu
Bugs, which is subscribed to
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 different system of the same config, but *wit
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
Good, any other pending tests?
If not, i'll move forward and send a the above v2 arm64 kpti patchset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749040
Title:
KPTI support for arm64 systems
To
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 Ubuntu
Bugs, which is subscri
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
Is there a way for me to manually run disk/disk_stress_ng_dm-1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749040
Title:
KPTI support for arm64 systems
To manage notifications about this bug go
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 Ubuntu
Bugs, which is subscribed to Ubu
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
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
If the bug in #39 is not related to kpti, can you spawn it into a
separate LP bug and add a reproducer?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749040
Title:
KPTI support for arm64 s
Merlin system cert results.
** Attachment added: "results of cert on merlin"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066621/+files/submission_2018-03-02T03.59.13.971794.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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 Ubuntu
Bugs, which is subscribed
D05 & QDF2400 errors are all expected, thanks Manoj!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749040
Title:
KPTI support for arm64 systems
To manage notifications about this bug go to:
https:
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
cert testing on QDF2400
** Attachment added: "cert testing on QDF2400"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066200/+files/submission_2018-03-01T15.40.44.388832.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hisilicon D05-0 testing.
** Attachment added: "cert testing on Hisilicon"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066199/+files/submission_2018-03-01T15.37.19.324054.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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).
Let's see what the other boards report.
1:
https://launchpadlibrarian.net/359043692/submission_2018-03-01T05.58.16.640032.
Refreshed kernel now in ppa:dannf/kpti
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749040
Title:
KPTI support for arm64 systems
To manage notifications about this bug go to:
https://bugs.launchp
** 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 Ubuntu
Bugs, which i
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
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 addr_limit_user_check' fixes a
FTBFS for armhf
2) 'arm64: mm: fix thinko in non-global page ta
Yep, if it boots fine, i usually retry 2/3 times, and it has happened
that it failed only the second or the third time i tried.
Anyhow, now i'm down to this delta .config (the initial one had ~2k
entries), so the bug appears to be ACPI related:
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
No need to install 4.16-rc3 in both host & guest: i can reproduce it
on d05-6 using 4.13.0-36-generic #40~16.04.1 on host (no KPTI
patchset) and 4.16.0-rc3+ on guest.
Unfortunately defconfig boots fine, so there's something in that .config that
trips it.
If trying to reproduce it, remove the CONF
** Summary changed:
- KPTI-enabled kernel fails to boot on Cavium ThunderX CRB
+ KPTI support for arm64 systems
** Attachment added: "config used to build 4.16-rc3 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5064177/+files/.config
--
You received this bu
30 matches
Mail list logo