sorry s/Juery/Juerg/!
--
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 parity or ECC error
Status in linux package in
@Juery: I have no reason to believe this is related to the boot
regression we fixed (bug 1857074). I haven't re-tested lately, but as of
4.15.0-76 it was still reproducible.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is this related to the boot regression that we fixed or a different
problem? I.e., can you still reproduce this with latest 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/1860013
** 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
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
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
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
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321216/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "dmidecode_-t_bios.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321214/+files/dmidecode_-t_bios.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "dmidecode_-t_memory.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321215/+files/dmidecode_-t_memory.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "dmidecode_-t_processor.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321213/+files/dmidecode_-t_processor.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "Full console log of host seidel oops w/ error 5.0.0-37.40"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860013/+attachment/5321212/+files/seidel.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
All 3 of my machines survived overnight testing on the 5.5-rc6 mainline
build[*].
Next step is to try 5.3. 5.3 mainline doesn't boot on these systems, so I'll
use Ubuntu's 5.3.0-24.
[*] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc6/
--
You received this bug notification because you
Also reproducible w/ the 5.0.0-37.40 kernel. I'll try a mainline 5.5-rc6
build next.
[ 602.796765] Internal error: synchronous parity or ECC error: 9618 [#1]
SMP
[ 602.803994] Modules linked in: nls_iso8859_1 cavium_rng_vf ipmi_ssif
ipmi_devintf input_leds joydev ipmi_msghandler
14 matches
Mail list logo
