Ubuntu16.04.3 Installation fails for JFS file system

Bug #1708096 reported by bugproxy on 2017-08-02
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
High
Canonical Kernel Team
linux (Ubuntu)
High
Canonical Kernel

Bug Description

---Problem Description---

Ubuntu16.04.3 installation fails for JFS file system.

---Environment---
Garrison Power8

---Steps to reproduce---
 Install Ubuntu 16.04.3 with
 - prepboot
- /root [JFS filesystem]
- swap space

---Fails in below step---

             ?? [!!] Install the GRUB boot loader on a hard disk ??
  ???????????? ? ?????????
  ? ? Unable to install GRUB in /dev/sdi1 ? ?
  ? ? Executing 'grub-install /dev/sdi1' failed. ? ?
  ? ? ? ?
  ? Running "? This is a fatal error. ? ?
  ? ? ? ?
  ???????????? <Go Back> <Continue> ? ?????????
             ? ?
             ??????????????????????????????????????????????????????

<Tab> moves; <Space> selects; <Enter> activates buttons

     ????????? [!!] Install the GRUB boot loader on a hard disk ??????????
     ? ?
     ? Installation step failed ?
     ? An installation step failed. You can try to run the failing item ?
     ? again from the menu, or skip it and choose something else. The ?
     ? failing step is: Install the GRUB boot loader on a hard disk ?
     ? ?
     ? <Continue> ?
     ? ?
     ?????????????????????????????????????????????????????????????????????

<Tab> moves; <Space> selects; <Enter> activates buttons

Comment 3 2017-07-20 04:31:05 CDT

Based on your error, may be you deleted partition 1 (8MB the PReP boot partition) which is required for installing the boot loader in IBM power systems. Or maybe you changed the use type to JFS from PReP boot.

Partition 1 (PReP boot) does NOT contain a filesystem and is not mounted.Grub is written to it raw and the firmware loads the contents of the partition into ram and executes it raw.

Can you try one more time,
Pick the default guided partitioning, then change the root partition(partition 2) from ext4(or <xyz> filesystem) to JFS.Do not delete and create any partitions from the default guided setup. Paste the results.

Comment 4 2017-07-20 09:22:22 CDT

(In reply to comment #3)
> Based on your error, may be you deleted partition 1 (8MB the PReP boot
> partition) which is required for installing the boot loader in IBM power
> systems. Or maybe you changed the use type to JFS from PReP boot.
>
> Partition 1 (PReP boot) does NOT contain a filesystem and is not
> mounted.Grub is written to it raw and the firmware loads the contents of the
> partition into ram and executes it raw.
>
> Can you try one more time,
> Pick the default guided partitioning, then change the root
> partition(partition 2) from ext4(or <xyz> filesystem) to JFS.Do not delete
> and create any partitions from the default guided setup. Paste the results.

No, I have not deleted partition and I have not changed the use type to JFS from PReP boot.

Any ways I tried again and it still fails.

?????????????????????????? [!!] Partition disks ???????????????????????????
  ? ?
  ? This is an overview of your currently configured partitions and mount ?
  ? points. Select a partition to modify its settings (file system, mount ?
  ? point, etc.), a free space to create partitions, or a device to ?
  ? initialize its partition table. ?
  ? ?
  ? SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313 ?
  ? > 1.0 MB FREE SPACE ? ?
  ? > #1 7.3 MB K ? ?
  ? > #2 959.7 GB F ext4 / ? ?
  ? > #3 40.5 GB f swap swap ?
  ? > 728.6 kB FREE SPACE ? ?
  ? SCSI5 (0,0,0) (sdj) - 1.0 TB ATA ST1000NX0313 ? ?
  ? > #1 primary 4.2 MB B ? ?
  ? > #2 primary 1.1 GB xfs ? ?
  ? > #3 primary 214.7 GB xfs ?
  ? ?
  ? <Go Back> ?
  ? ?
  ???????????????????????????????????????????????????????????????????????????

<F1> for help; <Tab> moves; <Space> selects; <Enter> activates buttons

  ?????????????????????????? [!!] Partition disks ???????????????????????????
  ? ?
  ? You are editing partition #1 of SCSI4 (0,0,0) (sdi). No existing file ?
  ? system was detected in this partition. ?
  ? ?
  ? Partition settings: ?
  ? ?
  ? Name: ?
  ? Use as: PowerPC PReP boot partition ?
  ? ?
  ? Bootable flag: off ?
  ? ?
  ? Erase data on this partition ?
  ? Delete the partition ?
  ? Done setting up the partition ?
  ? ?
  ? <Go Back> ?
  ? ?
  ???????????????????????????????????????????????????????????????????????????

<F1> for help; <Tab> moves; <Space> selects; <Enter> activates buttons

  ?????????????????????????? [!!] Partition disks ???????????????????????????
  ? ?
  ? This is an overview of your currently configured partitions and mount ?
  ? points. Select a partition to modify its settings (file system, mount ?
  ? point, etc.), a free space to create partitions, or a device to ?
  ? initialize its partition table. ?
  ? ?
  ? > #1 51.6 GB xfs ?
  ? LVM VG rhelp_ltc-garri3, LV swap - 4.3 GB Linux device-mapper (li ? ?
  ? > #1 4.3 GB swap ? ?
  ? SCSI4 (0,0,0) (sdi) - 1.0 TB ATA ST1000NX0313 ? ?
  ? > 1.0 MB FREE SPACE ? ?
  ? > #1 7.3 MB K ?
  ? > #2 959.7 GB F jfs / ? ?
  ? > #3 40.5 GB f swap swap ? ?
  ? > 728.6 kB FREE SPACE ? ?
  ? SCSI5 (0,0,0) (sdj) - 1.0 TB ATA ST1000NX0313 ?
  ? ?
  ? <Go Back> ?
  ? ?
  ???????????????????????????????????????????????????????????????????????????

<F1> for help; <Tab> moves; <Space> selects; <Enter> activates buttons

             ?? [!!] Install the GRUB boot loader on a hard disk ??
  ???????????? ? ?????????
  ? ? Unable to install GRUB in /dev/sdi1 ? ?
  ? ? Executing 'grub-install /dev/sdi1' failed. ? ?
  ? ? ? ?
  ? Running "? This is a fatal error. ? ?
  ? ? ? ?
  ???????????? <Go Back> <Continue> ? ?????????
             ? ?
             ??????????????????????????????????????????????????????

<Tab> moves; <Space> selects; <Enter> activates buttons

Thanks,
Pooja

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-156861 severity-high targetmilestone-inin16043
Changed in ubuntu:
assignee: nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
affects: ubuntu → debian-installer (Ubuntu)
Changed in ubuntu-power-systems:
assignee: nobody → Canonical Foundations Team (canonical-foundations)
importance: Undecided → High
Adam Conrad (adconrad) wrote :

Is this a regression from 16.04.2?

Adam Conrad (adconrad) wrote :

Also, my attempts to reproduce this with the current (20170801) 16.04.3 release candidate haven't panned out. I can install to JFS root just fine on ppc64el.

On Wed, Aug 02, 2017 at 11:28:42AM -0000, Adam Conrad wrote:
> Also, my attempts to reproduce this with the current (20170801) 16.04.3
> release candidate haven't panned out. I can install to JFS root just
> fine on ppc64el.

Does there need to be a separate non-JFS /boot partition? I don't recall if
GRUB supports JFS.

------- Comment From <email address hidden> 2017-08-03 12:23 EDT-------
I tried installing ubuntu 16.04 from below link, and see the same issue.

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

?? [!!] Install the GRUB boot loader on a hard disk ??
???????????? ? ?????????
? ? Unable to install GRUB in /dev/sdc1 ? ?
? ? Executing 'grub-install /dev/sdc1' failed. ? ?
? ? ? ?
? Running "? This is a fatal error. ? ?
? ? ? ?
???????????? <Go Back> <Continue> ? ?????????
? ?
??????????????????????????????????????????????????????

<Tab> moves; <Space> selects; <Enter> activates buttons

Thanks,
Pooja

bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2017-08-03 15:10 EDT-------
Tried with latest net-boot.

http://cdimages.ubuntu.com/netboot/xenial/
(Ubuntu 16.04 LTS (Xenial Xerus) Netboot with HWE kernel)

http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-ppc64el/current/images/hwe-netboot/ubuntu-installer/ppc64el/

The installation completes with no error, but after installation completes and reboots there is no disk listed in Petitboot menu.

Thanks,
Pooja

Steve Langasek (vorlon) wrote :

> The installation completes with no error, but after installation completes
> and reboots there is no disk listed in Petitboot menu.

Did grub install to a separate non-JFS /boot partition, or is it installed to JFS? Does Petitboot support reading from JFS disks?

Manoj Iyer (manjo) on 2017-08-14
Changed in debian-installer (Ubuntu):
importance: Undecided → High
tags: added: triage-g
Download full text (6.2 KiB)

Grub supports JFS to some degree; systems boot on JFS over multipath with relative ease (see below). Using JFS without multipath, it seems to fairly reliably fail to complete the install (so of course you wouldn't manage to boot). In this case it looks as though detection of jfs fails in grub-install.

I did run into a kernel crash though, while booting JFS-over-multipath. Furthermore, JFS in general seems to have issues with filesystem corruption here. From one boot to the next, the system may drop to the initramfs failing to mount the root partition (with an "Invalid argument" error; running fsck.jfs seems to fix the issue). Kernel oops for the crash I got follows:

[ 6.626202] Unable to handle kernel paging request for data at address 0x00000000
[ 6.626322] Faulting instruction address: 0xd000000003f3e1cc
[ 6.626366] Oops: Kernel access of bad area, sig: 11 [#1]
[ 6.626492] SMP NR_CPUS=2048 NUMA pSeries
[ 6.626536] Modules linked in: autofs4 jfs dm_round_robin ibmvscsi ibmveth scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
[ 6.626685] CPU: 4 PID: 2176 Comm: systemd-udevd Not tainted 4.4.0-92-generic #115-Ubuntu
[ 6.626771] task: c000000004e82a20 ti: c000000004f08000 task.ti: c000000004f08000
[ 6.626823] NIP: d000000003f3e1cc LR: d000000003f3e168 CTR: c0000000001195c0
[ 6.626873] REGS: c000000004f0b470 TRAP: 0300 Not tainted (4.4.0-92-generic)
[ 6.626921] MSR: 8000000100009033 <SF,EE,ME,IR,DR,RI,LE> CR: 44048824 XER: 00000000
[ 6.627110] CFAR: c0000000000108e8 DAR: 0000000000000000 DSISR: 40000000 SOFTE: 1
GPR00: d000000003f3e168 c000000004f0b6f0 d000000003f590d0 c000000770e1b440
GPR04: d000000003f4fba0 d000000003f52e58 00000000000007e1 0000000000000001
GPR08: 0000000000000000 0000000000000000 0000000000250003 d000000003f4aad8
GPR12: c0000000001195c0 c00000000fb42600 fffffffffffffffb 000001003b9b18d0
GPR16: c00000077ba92d60 c00000077ba92c48 000001003b9b0080 c00000077ba92e88
GPR20: c000000004f0b9e0 c0000000030789fe c000000778fda000 c000000004f0b900
GPR24: 0000000000250003 0000000000001000 0000000000000000 d000000003f52e38
GPR28: 0000000000250003 f000000001dcb200 c0000007752a7b00 c000000770e1b400
[ 6.628023] NIP [d000000003f3e1cc] __get_metapage+0x1dc/0x650 [jfs]
[ 6.628065] LR [d000000003f3e168] __get_metapage+0x178/0x650 [jfs]
[ 6.628108] Call Trace:
[ 6.628127] [c000000004f0b6f0] [d000000003f3e168] __get_metapage+0x178/0x650 [jfs] (unreliable)
[ 6.628193] [c000000004f0b7d0] [d000000003f394e0] dtSearch+0x4c0/0xa20 [jfs]
[ 6.628247] [c000000004f0b8e0] [d000000003f23b68] jfs_lookup+0x88/0x100 [jfs]
[ 6.628314] [c000000004f0ba10] [c0000000002f3864] lookup_real+0x64/0xe0
[ 6.628408] [c000000004f0ba50] [c0000000002fa324] do_last+0x9f4/0xff0
[ 6.628455] Unable to handle kernel paging request for data at address 0x00000000
[ 6.628458] Faulting instruction address: 0xd000000003f3e1cc
[ 6.628641] [c000000004f0bb10] [c0000000002fab3c] path_openat+0xcc/0x3c0
[ 6.628707] [c000000004f0bb90] [c0000000002fca5c] do_filp_open+0xfc/0x170
[ 6.628771] [c000000004f0bcb0] [c0000000002ed82c] do_open_execat+0x9c/0x2c0
[ 6.628833] [c000000004f0bd20] [c0000000002f0148] do_ex...

Read more...

Testing the same scenarios (X-on-multipath and just-X) where X is ext4 works correctly in all cases. This really looks to be specific to the JFS support somewhere. I'm not sure it's a kernel issue, but it looks like it might be.

I'm doing more testing on a Firestone now, should be sufficiently similar hardware to show the same failure to boot (but successful install) reported earlier.

Download full text (4.2 KiB)

Turns out this looks to be the same issue, due to filesystem corruption the disk is unavailable in that Linux image that runs petitboot; so it can't be scanned to find something to boot.

Furthermore, it seems like the issues are reliably fixed by running fsck.jfs on the filesystem (even mounted), but there is no fsck.jfs available in the petitboot environment for me to test this with.

For good measure, even when I do manage to boot to disk in the absence of multipath, but using JFS as a root filesystem, I still get crashes (this one comes from 16.04):

[ 71.761950] BUG: Bad page state in process jfsCommit pfn:77280
[ 71.762035] page:f000000001dca000 count:0 mapcount:0 mapping: (null) index:0x15008
[ 71.762115] flags: 0x3ffff80000080d(locked|referenced|uptodate|private)
[ 71.762225] page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set
[ 71.762293] bad because of flags:
[ 71.762334] flags: 0x801(locked|private)
[ 71.762402] Modules linked in: vmx_crypto rtc_generic autofs4 jfs ibmveth ibmvscsi
[ 71.762415] CPU: 5 PID: 1723 Comm: jfsCommit Not tainted 4.4.0-92-generic #115-Ubuntu
[ 71.762418] Call Trace:
[ 71.762431] [c0000007704b3a40] [c000000000b18f28] dump_stack+0xb0/0xf0 (unreliable)
[ 71.762437] [c0000007704b3a80] [c000000000234d34] bad_page.part.10+0x114/0x170
[ 71.762440] [c0000007704b3b10] [c0000000002355b4] free_pages_prepare+0x424/0x4a0
[ 71.762443] [c0000007704b3b90] [c000000000238980] free_hot_cold_page+0x60/0x210
[ 71.762447] [c0000007704b3be0] [c000000000245058] put_page+0x78/0xb0
[ 71.762455] [c0000007704b3c10] [d000000003b02668] txUnlock+0x278/0x330 [jfs]
[ 71.762461] [c0000007704b3cd0] [d000000003b06208] jfs_lazycommit+0x1e8/0x3b0 [jfs]
[ 71.762466] [c0000007704b3d80] [c0000000000e7354] kthread+0x124/0x150
[ 71.762471] [c0000007704b3e30] [c000000000009538] ret_from_kernel_thread+0x5c/0xa4
[ 71.762474] Disabling lock debugging due to kernel taint
[ 71.762477] BUG: Bad page state in process jfsCommit pfn:77280
[ 71.762541] page:f000000001dca000 count:0 mapcount:0 mapping: (null) index:0x15008
[ 71.762623] flags: 0x3ffff80000081c(referenced|uptodate|dirty|private)
[ 71.762737] page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set
[ 71.762806] bad because of flags:
[ 71.762853] flags: 0x800(private)
[ 71.762910] Modules linked in: vmx_crypto rtc_generic autofs4 jfs ibmveth ibmvscsi
[ 71.762918] CPU: 5 PID: 1723 Comm: jfsCommit Tainted: G B 4.4.0-92-generic #115-Ubuntu
[ 71.762919] Call Trace:
[ 71.762923] [c0000007704b3940] [c000000000b18f28] dump_stack+0xb0/0xf0 (unreliable)
[ 71.762927] [c0000007704b3980] [c000000000234d34] bad_page.part.10+0x114/0x170
[ 71.762930] [c0000007704b3a10] [c0000000002355b4] free_pages_prepare+0x424/0x4a0
[ 71.762933] [c0000007704b3a90] [c000000000238980] free_hot_cold_page+0x60/0x210
[ 71.762936] [c0000007704b3ae0] [c000000000245058] put_page+0x78/0xb0
[ 71.762942] [c0000007704b3b10] [d000000003afde2c] release_metapage+0xfc/0x2c0 [jfs]
[ 71.762948] [c0000007704b3b90] [d000000003afe6f8] put_metapage+0xb8/0x250 [jfs]
[ 71.762954] [c0000007704b3c10] [d000000003b0253c] txUnlock+0x14c/0x330 [j...

Read more...

affects: debian-installer (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Canonical Kernel (canonical-kernel)
Changed in ubuntu-power-systems:
assignee: Canonical Foundations Team (canonical-foundations) → nobody
tags: added: kernel-da-key
Manoj Iyer (manjo) on 2017-08-23
Changed in ubuntu-power-systems:
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
tags: added: kernel-key
bugproxy (bugproxy) on 2017-08-24
tags: removed: bugnameltc-156861 kernel-da-key kernel-key severity-high triage-g
Manoj Iyer (manjo) on 2017-09-11
tags: added: triage-r
bugproxy (bugproxy) on 2017-09-14
tags: added: bugnameltc-156861 severity-high
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Juerg Haefliger (juergh) wrote :

I'm able to reproduce the OOPS by booting a Xenial VM with root on JFS:

[ 42.018954] Unable to handle kernel paging request for data at address 0x00000000
[ 42.019098] Faulting instruction address: 0xd00000000108e1cc
[ 42.019501] Oops: Kernel access of bad area, sig: 11 [#1]
[ 42.019611] SMP NR_CPUS=2048 NUMA pSeries
[ 42.020320] Modules linked in: iscsi_tcp(+) libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 jfs btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi
[ 42.021106] CPU: 0 PID: 1067 Comm: ureadahead Not tainted 4.4.0-96-generic #119-Ubuntu
[ 42.021285] task: c00000000474e7b0 ti: c000000004c4c000 task.ti: c000000004c4c000
[ 42.021361] NIP: d00000000108e1cc LR: d00000000108e168 CTR: c0000000001196c0
[ 42.021425] REGS: c000000004c4f570 TRAP: 0300 Not tainted (4.4.0-96-generic)
[ 42.021475] MSR: 8000000000009033 <SF,EE,ME,IR,DR,RI,LE> CR: 48048844 XER: 00000000
[ 42.021738] CFAR: c000000000008468 DAR: 0000000000000000 DSISR: 40000000 SOFTE: 1
GPR00: d00000000108e168 c000000004c4f7f0 d0000000010a90d0 c00000003ec8f658
GPR04: d00000000109fba0 d0000000010a2e58 0000000000005aca 0000000000000001
GPR08: 0000000000000000 0000000000000000 0000000000168660 d00000000109aad8
GPR12: c0000000001196c0 c00000000fb40000 0000000000000009 0000000000000000
GPR16: c00000003793ac20 c00000003793ab08 0000000000000000 c00000003793ad48
GPR20: c000000004c4fae0 c00000003a8059fe c000000004d06800 c000000004c4fa00
GPR24: 0000000000168660 0000000000001000 0000000000000000 d0000000010a2e38
GPR28: 0000000000168660 f00000000000d840 c000000004428e80 c00000003ec8f618
[ 42.023072] NIP [d00000000108e1cc] __get_metapage+0x1dc/0x650 [jfs]
[ 42.023171] LR [d00000000108e168] __get_metapage+0x178/0x650 [jfs]
[ 42.023283] Call Trace:
[ 42.023435] [c000000004c4f7f0] [d00000000108e168] __get_metapage+0x178/0x650 [jfs] (unreliable)
[ 42.023630] [c000000004c4f8d0] [d0000000010894e0] dtSearch+0x4c0/0xa20 [jfs]
[ 42.023737] [c000000004c4f9e0] [d000000001073b68] jfs_lookup+0x88/0x100 [jfs]
[ 42.024132] [c000000004c4fb10] [c0000000002f4924] lookup_real+0x64/0xe0
[ 42.024216] [c000000004c4fb50] [c0000000002fb3e4] do_last+0x9f4/0xff0
[ 42.024289] [c000000004c4fc10] [c0000000002fbbfc] path_openat+0xcc/0x3c0
[ 42.024361] [c000000004c4fc90] [c0000000002fdb1c] do_filp_open+0xfc/0x170
[ 42.024433] [c000000004c4fdb0] [c0000000002e4310] do_sys_open+0x1c0/0x3b0
[ 42.024569] [c000000004c4fe30] [c000000000009204] system_call+0x38/0xb4
[ 42.024685] Instruction dump:
[ 42.024947] f91f0020 f93f0028 fbdf0030 fb9f0038 e93d0000 7927afe3 418203fc ebdd0030
[ 42.025154] 41920034 e93d0008 e95f0038 811e0000 <e9290000> 39080001 81290090 911e0000
[ 42.025744] ---[ end trace 054e73e40709cbff ]---

Juerg Haefliger (juergh) wrote :

Same issue with upstream 4.14.0-rc2:

[ 12.034089] Unable to handle kernel paging request for data at address 0x00000000
[ 12.034374] Faulting instruction address: 0xc0000000005230b8
[ 12.034819] Oops: Kernel access of bad area, sig: 11 [#1]
[ 12.034889] LE SMP NR_CPUS=2048 NUMA pSeries
[ 12.035371] Modules linked in:
[ 12.035817] CPU: 0 PID: 167 Comm: (solvconf) Not tainted 4.14.0-rc2 #1
[ 12.036080] task: c000000039a58a00 task.stack: c000000039a70000
[ 12.036180] NIP: c0000000005230b8 LR: c000000000523040 CTR: c000000000296950
[ 12.036262] REGS: c000000039a73530 TRAP: 0300 Not tainted (4.14.0-rc2)
[ 12.036321] MSR: 800000000280b033 <SF,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 44248882 XER: 00000000
[ 12.036721] CFAR: c000000000008708 DAR: 0000000000000000 DSISR: 40000000 SOFTE: 1
[ 12.036721] GPR00: c000000000523040 c000000039a737b0 c00000000172a100 c00000003a5ef3c0
[ 12.036721] GPR04: c000000000ff0e58 c000000001a3ddc0 000000000000483b 0000000000000000
[ 12.036721] GPR08: 0000000000000000 001ffffc0000102d 00000000002103b2 c00000000fdc0008
[ 12.036721] GPR12: 0000000000002000 c00000000fdc0000 c0000000377c8100 0000000000000000
[ 12.036721] GPR16: 0000000000000000 c000000037b1bb80 c0000000377ecaa0 c000000039e22f10
[ 12.036721] GPR20: c000000039a73bd0 0000000000000041 0000000080000000 0000000080000000
[ 12.036721] GPR24: 0000000000000001 00000000002103b2 0000000000000000 c0000000377e93a0
[ 12.036721] GPR28: 0000000000001000 f0000000000e6480 c00000003949f300 c00000003a5ef380
[ 12.038096] NIP [c0000000005230b8] __get_metapage+0x218/0x6d0
[ 12.038270] LR [c000000000523040] __get_metapage+0x1a0/0x6d0
[ 12.038375] Call Trace:
[ 12.038499] [c000000039a737b0] [c000000000522ff4] __get_metapage+0x154/0x6d0 (unreliable)
[ 12.038653] [c000000039a73890] [c0000000005115a0] diRead+0x130/0x250
[ 12.038745] [c000000039a73940] [c000000000507904] jfs_iget+0x64/0x1d0
[ 12.038804] [c000000039a73970] [c000000000508e7c] jfs_lookup+0xdc/0xf0
[ 12.038872] [c000000039a73aa0] [c00000000038af80] path_openat+0x1280/0x1460
[ 12.038938] [c000000039a73ba0] [c00000000038ca5c] do_filp_open+0xec/0x160
[ 12.038998] [c000000039a73cd0] [c00000000037d1e4] do_open_execat+0x84/0x210
[ 12.039067] [c000000039a73d30] [c00000000037feb4] do_execveat_common.isra.13+0x234/0x840
[ 12.039252] [c000000039a73e00] [c0000000003807a4] SyS_execve+0x54/0x70
[ 12.039336] [c000000039a73e30] [c00000000000b104] system_call+0x58/0x6c
[ 12.039470] Instruction dump:
[ 12.039682] 7fc9f214 39200001 fbdf0030 f93f0028 e93d0000 71281000 41820428 ebdd0030
[ 12.039818] 41920034 e8fd0008 811e0000 e95f0038 <e8c70000> 38e80001 81060090 90fe0000
[ 12.040789] ---[ end trace e842adbc1d2236a6 ]---

Juerg Haefliger (juergh) wrote :

Just to be clear: The above tests were done using ppc64el user-space emulation on x86_64.

Andrew Cloke (andrew-cloke) wrote :

As this is an issue with the upstream kernel, we need assistance from upstream to address this issue. Marking as "incomplete".

Changed in ubuntu-power-systems:
status: New → Incomplete
tags: added: triage-g
removed: triage-r
Manoj Iyer (manjo) on 2017-11-28
Changed in ubuntu-power-systems:
status: Incomplete → Opinion
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments