[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
This kernel seems to be missing a change that is present in the upstream
version of the patch.
See:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/lib/feature-fixups.c?commit=a048a07d7f4535baa4cbad6bc024f175317ab938#n189
--- a/arch/powerpc/lib/feature-fixups.c 2018-05-24 23:31:52.497801437 +1000
+++ b/arch/powerpc/lib/feature-fixups.c 2018-05-24 23:29:18.141606123 +1000
@@ -185,12 +186,21 @@
i = 0;
if (types & STF_BARRIER_FALLBACK || types & STF_BARRIER_SYNC_ORI) {
- instrs[i++] = 0x7db243a6; /* mtsprg 2,r13 */
- instrs[i++] = 0x7db142a6; /* mfsprg r13,1 */
+ if (cpu_has_feature(CPU_FTR_HVMODE)) {
+ instrs[i++] = 0x7db14ba6; /* mtspr 0x131, r13 (HSPRG1)
*/
+ instrs[i++] = 0x7db04aa6; /* mfspr r13, 0x130 (HSPRG0)
*/
+ } else {
+ instrs[i++] = 0x7db243a6; /* mtsprg 2,r13 */
+ instrs[i++] = 0x7db142a6; /* mfsprg r13,1*/
+ }
instrs[i++] = 0x7c0004ac; /* hwsync */
instrs[i++] = 0xe9ad; /* ld r13,0(r13) */
instrs[i++] = 0x63ff; /* ori 31,31,0 speculation barrier */
- instrs[i++] = 0x7db242a6; /* mfsprg r13,2 */
+ if (cpu_has_feature(CPU_FTR_HVMODE)) {
+ instrs[i++] = 0x7db14aa6; /* mfspr r13, 0x131 (HSPRG1)
*/
+ } else {
+ instrs[i++] = 0x7db242a6; /* mfsprg r13,2 */
+ }
} else if (types & STF_BARRIER_EIEIO) {
instrs[i++] = 0x7e0006ac; /* eieio + bit 6 hint */
}
--
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/1773162
Title:
4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
supported)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot
with 4.15.0-22-generic and is in a reboot cycle.
```
Exiting petitboot. Type 'exit' to return.
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
[31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1
[32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2
[2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec
[2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1]
[2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV
[2.660462] Modules linked in:
[2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic
#24-Ubuntu
[2.660549] NIP: c000b9ec LR: CTR:
[2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted
(4.15.0-22-generic)
[2.660657] MSR: 90001031 CR: XER:
[2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000
SOFTE: -4611686018408771536
[2.660713] GPR00: 7fffcd511100
[2.660713] GPR04:
[2.660713] GPR08:
[2.660713] GPR12: 75501b231700 000200f0
[2.660713] GPR16:
[2.660713] GPR20:
[2.660713] GPR24:
[2.660713] GPR28:
[2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184
[2.661249] LR [] (null)
[2.661285] Call Trace:
[2.661303] Instruction dump:
[2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088
e8810090
[2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff
7db242a6 4810
[2.661445] ---[ end trace b607b09fe6490607 ]---
[…]
```
Please find the full log attached. Selecting Linux 4.4.0-124-generic
works.
```
$ uname -a
Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
$ dpkg -l linux-image-4.15.0-22-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-==-==-===
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Thanks. I see very little left between good and bad which could explain the bug going away. So I'm wondering if the bisect has gone off the rails. -- 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/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Can you post the latest bisect log? -- 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/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Can you please post the bisection log using upstream commit ids. -- 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/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
I'm seeing this on a fresh install of vivid (3.19.0-12-generic) on ppc64le: sudo update-grub [sudo] password for michael: Generating grub configuration file ... Found linux image: /boot/vmlinux-3.19.0-12-generic Found initrd image: /boot/initrd.img-3.19.0-12-generic [ 14.787303] EXT4-fs (sda1): VFS: Can't find ext4 filesystem [ 14.789751] EXT4-fs (sda1): VFS: Can't find ext4 filesystem [ 14.791951] EXT4-fs (sda1): VFS: Can't find ext4 filesystem [ 14.794039] FAT-fs (sda1): bogus number of reserved sectors [ 14.808160] FAT-fs (sda1): bogus number of reserved sectors [ 14.823019] qnx4: no qnx4 filesystem (no root dir). [ 14.825187] ufs: You didn't specify the type of your ufs filesystem [ 14.825187] [ 14.825187] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... [ 14.825187] [ 14.825187] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 14.826020] ufs: ufs_fill_super(): bad magic number -- 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/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to rea
[Kernel-packages] [Bug 1433809] Re: linux build failure seen building 32bit user space support on ppc64el
We'll aim to fix this in the kernel. It's a long-held assumption in the 64-bit code that 32-bit also exists, so teasing it all apart will take some work, all mechanical but time consuming. In the short term it might be best to just re-enable 32-bit in the toolchain. -- 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/1433809 Title: linux build failure seen building 32bit user space support on ppc64el Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: linux build failure seen building 32bit user space support on ppc64el, using the toolchain from ubuntu-toolchain-r/ppa on trusty. complete build log at https://launchpad.net/ubuntu/+archive/test-rebuild-20150317-security/+build/7070318 VDSO32A arch/powerpc/kernel/vdso32/gettimeofday.o /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S: Assembler messages: /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:42: Error: syntax error; found `@', expected `,' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:42: Error: junk at end of line: `@local' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:48: Error: syntax error; found `@', expected `,' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:48: Error: junk at end of line: `@local' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:83: Error: syntax error; found `@', expected `,' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:83: Error: junk at end of line: `@local' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:87: Error: syntax error; found `@', expected `,' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:87: Error: junk at end of line: `@local' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:195: Error: syntax error; found `@', expected `,' /build/buildd/linux-3.13.0/arch/powerpc/kernel/vdso32/gettimeofday.S:195: Error: junk at end of line: `@local' make[4]: *** [arch/powerpc/kernel/vdso32/gettimeofday.o] Error 1 make[3]: *** [arch/powerpc/kernel/vdso32] Error 2 make[3]: *** Waiting for unfinished jobs yeah, thanks for non-verbose build logs !!! doing it the hard way, you see that this file was (and wants to be) compiled with -m32, and I assume with gcc finally dropping the multilib configurations for ppc64el, the kernel configury decides that it can do without -m32. but why in the first place is this needed? there is no powerpcle user space. I assume this issue is latent in all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433809/+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
