[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2019-10-03 Thread Po-Hsu Lin
** 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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-36.40

---
linux (4.13.0-36.40) artful; urgency=medium

  * linux: 4.13.0-36.40 -proposed tracker (LP: #1750010)

  * Rebuild without "CVE-2017-5754 ARM64 KPTI fixes" patch set

linux (4.13.0-35.39) artful; urgency=medium

  * linux: 4.13.0-35.39 -proposed tracker (LP: #1748743)

  * CVE-2017-5715 (Spectre v2 Intel)
- Revert "UBUNTU: SAUCE: turn off IBPB when full retpoline is present"
- SAUCE: turn off IBRS when full retpoline is present
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

linux (4.13.0-34.37) artful; urgency=medium

  * linux: 4.13.0-34.37 -proposed tracker (LP: #1748475)

  * libata: apply MAX_SEC_1024 to all LITEON EP1 series devices (LP: #1743053)
- libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

  * KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)
(LP: #1747090)
- KVM: s390: wire up bpb feature

  * artful 4.13 i386 kernels crash after memory hotplug remove (LP: #1747069)
- Revert "mm, memory_hotplug: do not associate hotadded memory to zones 
until
  online"

  * CVE-2017-5715 (Spectre v2 Intel)
- x86/feature: Enable the x86 feature to control Speculation
- x86/feature: Report presence of IBPB and IBRS control
- x86/enter: MACROS to set/clear IBRS and set IBPB
- x86/enter: Use IBRS on syscall and interrupts
- x86/idle: Disable IBRS entering idle and enable it on wakeup
- x86/idle: Disable IBRS when offlining cpu and re-enable on wakeup
- x86/mm: Set IBPB upon context switch
- x86/mm: Only set IBPB when the new thread cannot ptrace current thread
- x86/entry: Stuff RSB for entry to kernel for non-SMEP platform
- x86/kvm: add MSR_IA32_SPEC_CTRL and MSR_IA32_PRED_CMD to kvm
- x86/kvm: Set IBPB when switching VM
- x86/kvm: Toggle IBRS on VM entry and exit
- x86/spec_ctrl: Add sysctl knobs to enable/disable SPEC_CTRL feature
- x86/spec_ctrl: Add lock to serialize changes to ibrs and ibpb control
- x86/cpu/AMD: Add speculative control support for AMD
- x86/microcode: Extend post microcode reload to support IBPB feature
- KVM: SVM: Do not intercept new speculative control MSRs
- x86/svm: Set IBRS value on VM entry and exit
- x86/svm: Set IBPB when running a different VCPU
- KVM: x86: Add speculative control CPUID support for guests
- SAUCE: turn off IBPB when full retpoline is present

  * Artful 4.13 fixes for tun (LP: #1748846)
- tun: call dev_get_valid_name() before register_netdevice()
- tun: allow positive return values on dev_get_valid_name() call
- tun/tap: sanitize TUNSETSNDBUF input

  * boot failure on AMD Raven + WestonXT (LP: #1742759)
- SAUCE: drm/amdgpu: add atpx quirk handling (v2)

linux (4.13.0-33.36) artful; urgency=low

  * linux: 4.13.0-33.36 -proposed tracker (LP: #1746903)

  [ Stefan Bader ]
  * starting VMs causing retpoline4 to reboot (LP: #1747507) // CVE-2017-5715
(Spectre v2 retpoline)
- x86/retpoline: Fill RSB on context switch for affected CPUs
- x86/retpoline: Add LFENCE to the retpoline/RSB filling RSB macros
- x86/retpoline: Optimize inline assembler for vmexit_fill_RSB
- x86/retpoline: Remove the esp/rsp thunk
- x86/retpoline: Simplify vmexit_fill_RSB()

  * Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC
(LP: #1743638)
- [d-i] Add qede to nic-modules udeb

  * hisi_sas: driver robustness fixes (LP: #1739807)
- scsi: hisi_sas: fix reset and port ID refresh issues
- scsi: hisi_sas: avoid potential v2 hw interrupt issue
- scsi: hisi_sas: fix v2 hw underflow residual value
- scsi: hisi_sas: add v2 hw DFX feature
- scsi: hisi_sas: add irq and tasklet cleanup in v2 hw
- scsi: hisi_sas: service interrupt ITCT_CLR interrupt in v2 hw
- scsi: hisi_sas: fix internal abort slot timeout bug
- scsi: hisi_sas: us start_phy in PHY_FUNC_LINK_RESET
- scsi: hisi_sas: fix NULL check in SMP abort task path
- scsi: hisi_sas: fix the risk of freeing slot twice
- scsi: hisi_sas: kill tasklet when destroying irq in v3 hw
- scsi: hisi_sas: complete all tasklets prior to host reset

  * [Artful/Zesty] ACPI APEI error handling bug fixes (LP: #1732990)
- ACPI: APEI: fix the wrong iteration of generic error status block
- ACPI / APEI: clear error status before acknowledging the error

  * [Zesty/Artful] On ARM64 PCIE physical function passthrough guest fails to
boot (LP: #1732804)
- vfio/pci: Virtualize Maximum Payload Size
- vfio/pci: Virtualize Maximum Read Request Size

  * hisi_sas: Add ATA command support for SMR disks (LP: #1739891)
- scsi: hisi_sas: support zone management commands

  * thunderx2: i2c driver PEC and ACPI clock fixes (LP: #1738073)
- ACPI / APD: Add clock frequency for ThunderX2 I2C controller
- i2c: xlp9xx: Get clock frequency with clk API
- i2c: xlp9xx: Handle 

[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-02-20 Thread dann frazier
Verified:

ubuntu@dawes:~$ dmesg | grep Machine
[0.00] Machine model: Cavium ThunderX CN88XX board
ubuntu@dawes:~$ cat /proc/version
Linux version 4.13.0-36-generic (buildd@bos02-arm64-021) (gcc version 5.4.0 
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #40~16.04.1-Ubuntu SMP Fri Feb 
16 23:26:28 UTC 2018
ubuntu@dawes:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=9c5dc96d-4531-4b51-aa28-cc97a30b1274 ro acpi=on


** Tags removed: verification-failed-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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-02-20 Thread Kleber Sacilotto de Souza
Hi,

We have reverted some arm64 patches that were causing boot issues so the
system should be able to boot now. Could you please verify the fix for
this bug again with the latest Artful kernel on -proposed?

Thank you.

-- 
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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-02-14 Thread dann frazier
Marking failed due to LP: #1749040

** Tags removed: verification-needed-artful
** Tags added: verification-failed-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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-02-14 Thread Kleber Sacilotto de Souza
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-02-06 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Artful)
   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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2018-01-24 Thread Stefan Bader
** Changed in: linux (Ubuntu Zesty)
   Status: New => 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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2017-12-13 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

2017-12-06 Thread dann frazier
** Description changed:

  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1
  
  In some configurations, this causes the SATA controller to fail to
- initialize, making the system unbootable.
+ initialize, making the system unbootable. (Note to self: this occurs on
+ our internal system known as "alekhin").
  
  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.
  
  [Regression Risk]
+ The fixes are restricted to quirks for Cavium ThunderX hardware

** Description changed:

  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1
  
  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs on
  our internal system known as "alekhin").
  
  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.
  
  [Regression Risk]
- The fixes are restricted to quirks for Cavium ThunderX hardware
+ The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

-- 
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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp