Test Environment:
- Witherspoon DD2.3
- Ubu 18.04.2
Test Result:
Ubuntu 18.04.2 LTS ltc-wcwsp3 hvc0
ltc-wcwsp3 login:
Ubuntu 18.04.2 LTS ltc-wcwsp3 hvc0
ltc-wcwsp3 login: root
Password:
Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-50-generic ppc64le)
* Documentation: https://help.ubuntu.
I'm pasting Pavithra comments on testing with fixed kernel:
> Pavithra's update:
(In reply to comment #8)
> --- Comment From jsalisbury 2018-05-30 01:19:05 UTC---
> Did this issue start with the 4.15.0-22 kernel? Was there a prior 4.15
> based kernel that did not exhibit this bug?
>
We have used below bionic "-proposed" path to get install it freshly,
still it fails to boot.
Issue is still observed after installing from http://ports.ubuntu.com
/ubuntu-ports/dists/bionic-proposed/main/installer-
ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
Please advice with the r
*** This bug is a duplicate of bug 1744294 ***
https://bugs.launchpad.net/bugs/1744294
IBM test done regression testing on this "-proposed" builds and found no
issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
*** This bug is a duplicate of bug 1744244 ***
https://bugs.launchpad.net/bugs/1744244
IBM test done regression testing on this "-proposed" builds and found no
issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
IBM test done regression testing on this "-proposed" builds and found no
issues.
--
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/1742772
Title:
powerpc: flush L1D on return to use
Status
Don't we get this as part of 14.04 SRU ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1318809
Title:
crash tool support for the ppc64el arch
Status in “crash” package in Ubuntu:
Fix
I tested with "trusty-proposed" packages and crash tool is working
fine.
Steps to install trusty-proposed crash tool:
1) Added below entry in /etc/apt/source.list
deb http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed restricted main
multiverse universe
2) Did apt-get update
3) Check
I have tested the ported "crash" tool from development team(Mauricio and
Bharata). It is working fine. Here are the steps I followed to do basic
testing.
1) dump Ubuntu 14.04 LE VM dump using virsh dump command
Ex: virsh dump --memory-onlykal_ubu_at kal_ubu_at.dump--verbose
VM: kal_
We need to make sure ported crash packages should be part of upcoming
SRU cycle. I'm not sure when would be the next SRU patches coming in.
Need help from Ubuntu/Canonical.
** Summary changed:
- Support for the ppc64el arch
+ crash tool support for the ppc64el arch
--
You received this bug noti
Please lower the severity to lower say medium not high.
--
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/1267062
Title:
LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatch
As per the #9 comment moving this to invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1267910
Title:
ping -R do
Based on #5 moving this to invalid.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1267914
Title:
Unable to login to ub
Here is my analysis with a small code:
Summary:
If we include signal.h from usr/include: MINSIGSTKSZ -> 4096 ###TC case
FAIL
If we explicitly include signal.h from ppc64le : MINSIGSTKSZ -> 4096 ###TC
case PASS
In my opinion glibc should be taken care to point to right signal.h when
a
Here is my analysis with a small code:
Summary:
If we include signal.h from usr/include: MINSIGSTKSZ -> 4096 ###TC FAIL
If we explicitly include signal.h from"/usr/include/asm-powerpc/signal.h" :
MINSIGSTKSZ -> 2048 ###TC case PASS
In my opinion glibc should be taken care to point t
My question is which header file to include in application code for
"signal.h"?
Since each of these header file include in the application code seems
different definiation.
With the sample code I include in #10 if we includeI see
MINSIGSTKSZ > 4096
and
If #include "/usr/include/powerpc
We can close this bug; not seen with latest build.
--
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/1274479
Title:
Call Traces found while executing fsracer tests
Status in “linux” packag
Looks like Diane is unable to change this to "critical". This needs to
be tracked manually.
--
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/1267712
Title:
ubuntu guest's file system becom
This issue no more seen on daily builds. Please close this issue.
--
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/1266737
Title:
error sda: WRITE SAME failed when installing package
Stat
Today's build (mar 17) I installed on a NFS shared location and after
the installation while bringing up the VM I see message "sda2: WRITE
SAME failed. Manually zeroing." console and even dmesg has this message
logged.
Attached the dmesg.?field.comment=Today's build (mar 17) I installed on
a NFS s
Anasuya, can you please check what is the #define for "MINSIGSTKSZ" and
take appropriate correction in the test suites. Hopefully it should
match all distros not just Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Anasuya, It is been a month now so can you please recreate on latest
build and update the defect. If you are unable to recreate on latest
build please close this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Anasuya, can you please check on the debian defect on this, I remember
debian has the analysis and marked as not a bug. Please do check on
debian. If you think it is similar issue as debian please close this.
--
You received this bug notification because you are a member of Kernel
Packages, which
Please mark this High.
--
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/1288564
Title:
[beta1] tool fdisk do not support disks with more than 65535 cylinders
Status in “linux” package in
I have had 5 successful runs so far with below kernel. however I keep
see OOM call traces.
root@ltc-haba1:~/log# uname -a
Linux ltc-haba1 4.4.0-34-generic #53~lp1573062PATCHED SMP Wed Aug 10 23:59:53
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
--
You received this bug notification because you ar
I have been trying to recreate this issue on my Haba-LC system and not able to
do so.
The difference I see in total memory installed on my system against your system
i.e 32Gig.
Total memory is 256 GiB -> my Haba-LC.
Constant run time is 300 seconds per stressor
Variab
Joseph: Is it possible for you to post test kernel with Balbir's patches ?
and place them at earlier location -
http://kernel.ubuntu.com/~jsalisbury/lp1573062/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
27 matches
Mail list logo
