[Kernel-packages] [Bug 1857073] Re: Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI related)

2020-01-16 Thread dann frazier
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 let's
keep this bug to track the IPMI issue.

** This bug is no longer 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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857073

Title:
  Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI
  related)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Series: Bionic 
  Kernel: 4.15.0-74.84  linux-generic

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle. 
  This kernel was built to include fixes for the following bugs:

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
correct place
  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.

  system hostname: wright

  Possible Cause: wright's crash possibly is caused by faulty error
  handling in the ipmi driver (notice this in its dmesg: [ 52.150201]
  ipmi_ssif 0-0012: Unable to get the device id: -5)

  [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  [  OK  ] FounBYZ-011FA0 efi.
   Mounting /boot/[  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting Set console font and keymap...
   Starting Create Volatile Files and Directories...
   Starting ebtables ruleset management...
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  nsole font and keymap.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [  OK  ] Started Create Volatile Files and Directories.
   Starting Network Time Synchronization...
   Starting Update UTMP about Syst
  [  OK  ] Started Update UTMP utdown.
  [  OK  ] Started ebtables ruleset management.
  [  OK  ] Starnization.
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Started AppArmor initialization.
  [   50.689136] cloud-init[1246]: Cloud-init v. 
19.3-41-gc4735dd3-0ubuntu1~18.04.1 running 'init-local' at Thu, 19 Dec 20 50.28 
seconds.
  [   50.712486] cloud-init[1246]: 2019-12-19 22:40:37,893 - 
handlers.py[WARNING]: failed posting event: start: init-local/check-cache: 
attempting to read from cache [trust]
  [   50.736307] cloud-init[1246]: 2019-12-19 22:40:37,941 - 
handlers.py[WARNING]: failed posting event: finish: init-local/check-cache: 
SUCCESS: restored from cache: DataSourceMAAS 
[http://10.229.32.21:5248/MAAS/metadata/]
  [   51.244224] cloud-init[1246]: 2019-12-19 22:40:38,450 - 
handlers.py[WARNING]: failed posting event: finish: init-local: SUCCESS: 
searching for local datasources
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Wait for Network to be Configured...
   Starting Network Name Resolution...
  [   52.150201] ipmi_ssif 0-0012: Unable to get the device id: -5
  [   52.300309] Unable to handle kernel read fromvirtual address 0018
  [   52.311284] Mem abort info:
  [   52.316895]  604
  [   52.322622]   Exception class = DABT (current EL), IL = 32 bits
  [   52.331061]   SET = 0, FnV = 0
  [   52.336639]   EA = 0, S1PTW = 0
  [   52.342311] Data abort info:
  [   52.347731]   ISV = 0, ISS = 0x0004
  [   52.354131]   CM = 0, WnR = 0
  [   52.359739] user pgtable: 4k pages, 48-bit VAs, pgd = 44052f71
  [   52.368909] [0018] *pgd=
  [   52.376522] Internal error: Oops: 9604 [#1] SMP
  [   52.384039] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif(+) 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit aes_ce_blk ttm aes_ce_cipher crc32_ce drm_kms_helper 
crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect sysimgblt 

[Kernel-packages] [Bug 1857073] Re: Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI related)

2020-01-08 Thread dann frazier
*** 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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857073

Title:
  Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI
  related)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Series: Bionic 
  Kernel: 4.15.0-74.84  linux-generic

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle. 
  This kernel was built to include fixes for the following bugs:

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
correct place
  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.

  system hostname: wright

  Possible Cause: wright's crash possibly is caused by faulty error
  handling in the ipmi driver (notice this in its dmesg: [ 52.150201]
  ipmi_ssif 0-0012: Unable to get the device id: -5)

  [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  [  OK  ] FounBYZ-011FA0 efi.
   Mounting /boot/[  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting Set console font and keymap...
   Starting Create Volatile Files and Directories...
   Starting ebtables ruleset management...
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  nsole font and keymap.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [  OK  ] Started Create Volatile Files and Directories.
   Starting Network Time Synchronization...
   Starting Update UTMP about Syst
  [  OK  ] Started Update UTMP utdown.
  [  OK  ] Started ebtables ruleset management.
  [  OK  ] Starnization.
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Started AppArmor initialization.
  [   50.689136] cloud-init[1246]: Cloud-init v. 
19.3-41-gc4735dd3-0ubuntu1~18.04.1 running 'init-local' at Thu, 19 Dec 20 50.28 
seconds.
  [   50.712486] cloud-init[1246]: 2019-12-19 22:40:37,893 - 
handlers.py[WARNING]: failed posting event: start: init-local/check-cache: 
attempting to read from cache [trust]
  [   50.736307] cloud-init[1246]: 2019-12-19 22:40:37,941 - 
handlers.py[WARNING]: failed posting event: finish: init-local/check-cache: 
SUCCESS: restored from cache: DataSourceMAAS 
[http://10.229.32.21:5248/MAAS/metadata/]
  [   51.244224] cloud-init[1246]: 2019-12-19 22:40:38,450 - 
handlers.py[WARNING]: failed posting event: finish: init-local: SUCCESS: 
searching for local datasources
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Wait for Network to be Configured...
   Starting Network Name Resolution...
  [   52.150201] ipmi_ssif 0-0012: Unable to get the device id: -5
  [   52.300309] Unable to handle kernel read fromvirtual address 0018
  [   52.311284] Mem abort info:
  [   52.316895]  604
  [   52.322622]   Exception class = DABT (current EL), IL = 32 bits
  [   52.331061]   SET = 0, FnV = 0
  [   52.336639]   EA = 0, S1PTW = 0
  [   52.342311] Data abort info:
  [   52.347731]   ISV = 0, ISS = 0x0004
  [   52.354131]   CM = 0, WnR = 0
  [   52.359739] user pgtable: 4k pages, 48-bit VAs, pgd = 44052f71
  [   52.368909] [0018] *pgd=
  [   52.376522] Internal error: Oops: 9604 [#1] SMP
  [   52.384039] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif(+) 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit aes_ce_blk ttm aes_ce_cipher crc32_ce drm_kms_helper 
crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect sysimgblt sha256_arm64 
fb_sys_fops thunder_bgx sha1_ce drm ahci libahci thunder_xcv i2c_thunderx 
mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd 
cryptd aes_arm64
  [   52.473094] Process kworker/87:1 (pid: 674, stack limit = 

[Kernel-packages] [Bug 1857073] Re: Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI related)

2019-12-19 Thread Sean Feole
2nd record crash by wright

** Attachment added: "wright2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857073/+attachment/5314165/+files/wright2.txt

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

Title:
  Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI
  related)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Series: Bionic 
  Kernel: 4.15.0-74.84  linux-generic

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle. 
  This kernel was built to include fixes for the following bugs:

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
correct place
  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.

  system hostname: wright

  Possible Cause: wright's crash possibly is caused by faulty error
  handling in the ipmi driver (notice this in its dmesg: [ 52.150201]
  ipmi_ssif 0-0012: Unable to get the device id: -5)

  [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  [  OK  ] FounBYZ-011FA0 efi.
   Mounting /boot/[  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting Set console font and keymap...
   Starting Create Volatile Files and Directories...
   Starting ebtables ruleset management...
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  nsole font and keymap.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [  OK  ] Started Create Volatile Files and Directories.
   Starting Network Time Synchronization...
   Starting Update UTMP about Syst
  [  OK  ] Started Update UTMP utdown.
  [  OK  ] Started ebtables ruleset management.
  [  OK  ] Starnization.
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Started AppArmor initialization.
  [   50.689136] cloud-init[1246]: Cloud-init v. 
19.3-41-gc4735dd3-0ubuntu1~18.04.1 running 'init-local' at Thu, 19 Dec 20 50.28 
seconds.
  [   50.712486] cloud-init[1246]: 2019-12-19 22:40:37,893 - 
handlers.py[WARNING]: failed posting event: start: init-local/check-cache: 
attempting to read from cache [trust]
  [   50.736307] cloud-init[1246]: 2019-12-19 22:40:37,941 - 
handlers.py[WARNING]: failed posting event: finish: init-local/check-cache: 
SUCCESS: restored from cache: DataSourceMAAS 
[http://10.229.32.21:5248/MAAS/metadata/]
  [   51.244224] cloud-init[1246]: 2019-12-19 22:40:38,450 - 
handlers.py[WARNING]: failed posting event: finish: init-local: SUCCESS: 
searching for local datasources
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Wait for Network to be Configured...
   Starting Network Name Resolution...
  [   52.150201] ipmi_ssif 0-0012: Unable to get the device id: -5
  [   52.300309] Unable to handle kernel read fromvirtual address 0018
  [   52.311284] Mem abort info:
  [   52.316895]  604
  [   52.322622]   Exception class = DABT (current EL), IL = 32 bits
  [   52.331061]   SET = 0, FnV = 0
  [   52.336639]   EA = 0, S1PTW = 0
  [   52.342311] Data abort info:
  [   52.347731]   ISV = 0, ISS = 0x0004
  [   52.354131]   CM = 0, WnR = 0
  [   52.359739] user pgtable: 4k pages, 48-bit VAs, pgd = 44052f71
  [   52.368909] [0018] *pgd=
  [   52.376522] Internal error: Oops: 9604 [#1] SMP
  [   52.384039] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif(+) 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit aes_ce_blk ttm aes_ce_cipher crc32_ce drm_kms_helper 
crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect sysimgblt sha256_arm64 
fb_sys_fops thunder_bgx sha1_ce drm ahci libahci thunder_xcv i2c_thunderx 
mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd 
cryptd aes_arm64
  [   52.473094] Process kworker/87:1 (pid: 674, stack limit = 
0x4907a88f)
  [   

[Kernel-packages] [Bug 1857073] Re: Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI related)

2019-12-19 Thread Sean Feole
Fill console output for wright

** Attachment added: "wright.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857073/+attachment/5314164/+files/wright.txt

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

Title:
  Cavium ThunderX CN88XX Crashes : Internal error Ooops(Possibly IPMI
  related)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Series: Bionic 
  Kernel: 4.15.0-74.84  linux-generic

  The following crash was observed while testing the proposed kernel for the 
2019.12.02 SRU Cycle. 
  This kernel was built to include fixes for the following bugs:

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
  (LP: #1853326)
  - Revert "arm64: Use firmware to detect CPUs that are not affected by
Spectre-v2"
  - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

* [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
  Kunpeng920 (LP: #1852723)
  - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
correct place
  The following crash appears to be a NEW bug. not related to the prior bugs 
listed above.

  system hostname: wright

  Possible Cause: wright's crash possibly is caused by faulty error
  handling in the ipmi driver (notice this in its dmesg: [ 52.150201]
  ipmi_ssif 0-0012: Unable to get the device id: -5)

  [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
  [  OK  ] FounBYZ-011FA0 efi.
   Mounting /boot/[  OK  ] Mounted /boot/efi.
  [  OK  ] Reached target Local File Systems.
   Starting Set console font and keymap...
   Starting Create Volatile Files and Directories...
   Starting ebtables ruleset management...
   Starting AppArmor initialization...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  nsole font and keymap.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [  OK  ] Started Create Volatile Files and Directories.
   Starting Network Time Synchronization...
   Starting Update UTMP about Syst
  [  OK  ] Started Update UTMP utdown.
  [  OK  ] Started ebtables ruleset management.
  [  OK  ] Starnization.
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Started AppArmor initialization.
  [   50.689136] cloud-init[1246]: Cloud-init v. 
19.3-41-gc4735dd3-0ubuntu1~18.04.1 running 'init-local' at Thu, 19 Dec 20 50.28 
seconds.
  [   50.712486] cloud-init[1246]: 2019-12-19 22:40:37,893 - 
handlers.py[WARNING]: failed posting event: start: init-local/check-cache: 
attempting to read from cache [trust]
  [   50.736307] cloud-init[1246]: 2019-12-19 22:40:37,941 - 
handlers.py[WARNING]: failed posting event: finish: init-local/check-cache: 
SUCCESS: restored from cache: DataSourceMAAS 
[http://10.229.32.21:5248/MAAS/metadata/]
  [   51.244224] cloud-init[1246]: 2019-12-19 22:40:38,450 - 
handlers.py[WARNING]: failed posting event: finish: init-local: SUCCESS: 
searching for local datasources
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Wait for Network to be Configured...
   Starting Network Name Resolution...
  [   52.150201] ipmi_ssif 0-0012: Unable to get the device id: -5
  [   52.300309] Unable to handle kernel read fromvirtual address 0018
  [   52.311284] Mem abort info:
  [   52.316895]  604
  [   52.322622]   Exception class = DABT (current EL), IL = 32 bits
  [   52.331061]   SET = 0, FnV = 0
  [   52.336639]   EA = 0, S1PTW = 0
  [   52.342311] Data abort info:
  [   52.347731]   ISV = 0, ISS = 0x0004
  [   52.354131]   CM = 0, WnR = 0
  [   52.359739] user pgtable: 4k pages, 48-bit VAs, pgd = 44052f71
  [   52.368909] [0018] *pgd=
  [   52.376522] Internal error: Oops: 9604 [#1] SMP
  [   52.384039] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip 
cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq uio ipmi_ssif(+) 
ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf 
nicpf ast i2c_algo_bit aes_ce_blk ttm aes_ce_cipher crc32_ce drm_kms_helper 
crct10dif_ce ghash_ce syscopyarea sha2_ce sysfillrect sysimgblt sha256_arm64 
fb_sys_fops thunder_bgx sha1_ce drm ahci libahci thunder_xcv i2c_thunderx 
mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd 
cryptd aes_arm64
  [   52.473094] Process kworker/87:1 (pid: 674, stack limit = 
0x4907a88f)
  [