from:"Kalpana S Shetty"

[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-06-03 Thread Kalpana S Shetty

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.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage
root@ltc-wcwsp3:~# uname -a
Linux ltc-wcwsp3 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:55:18 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
root@ltc-wcwsp3:~# tail /proc/cpuinfo 
cpu : POWER9, altivec supported
clock   : 3800.00MHz
revision: 2.3 (pvr 004e 1203)

timebase: 51200
platform: PowerNV
model   : 8335-GTW
machine : PowerNV 8335-GTW
firmware: OPAL
MMU : Radix

root@ltc-wcwsp3:~# grep -H . /sys/devices/system/cpu/vulnerabilities/spectre_v2
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software count 
cache flush (hardware accelerated)

root@ltc-wcwsp3:~# dmesg | grep count-cache-flush
[0.00] count-cache-flush: hardware assisted flush sequence enabled

root@ltc-wcwsp3:~# echo x > /proc/sysrq-trigger
[  337.227090] sysrq: SysRq : Entering xmon
cpu 0x50: Vector: 0  at [c000201bebeefae0]
pc: c00e59f8: sysrq_handle_xmon+0xc8/0xd0
lr: c00e59f8: sysrq_handle_xmon+0xc8/0xd0
sp: c000201bebeefc40
   msr: 90009033
  current = 0xc000201bebe67600
  paca= 0xcfab7000   softe: 0irq_happened: 0x01
pid   = 5129, comm = bash
Linux version 4.15.0-50-generic (buildd@bos02-ppc64el-006) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #54-Ubuntu SMP Mon May 6 18:55:18 UTC 2019 (Ubuntu 
4.15.0-50.54-generic 4.15.18)
enter ? for help
[c000201bebeefc70] c07fbe28 __handle_sysrq+0xf8/0x2c0
[c000201bebeefd10] c07fc638 write_sysrq_trigger+0x68/0x90
[c000201bebeefd40] c0487bc8 proc_reg_write+0x88/0xd0
[c000201bebeefd70] c03da9fc __vfs_write+0x3c/0x70
[c000201bebeefd90] c03dac58 vfs_write+0xd8/0x220
[c000201bebeefde0] c03daf78 SyS_write+0x68/0x110
[c000201bebeefe30] c000b288 system_call+0x5c/0x70
--- Exception: c01 (System Call) at 70566a24e420
SP (76712c70) is in userspace
50:mon> 
50:mon> di $_switch 20
c000db00  7c0802a6  mflrr0
c000db04  f8010010  std r0,16(r1)
c000db08  f821fe31  stdur1,-464(r1)
c000db0c  f9c100e0  std r14,224(r1)
c000db10  f9e100e8  std r15,232(r1)
c000db14  fa0100f0  std r16,240(r1)
c000db18  fa2100f8  std r17,248(r1)
c000db1c  fa410100  std r18,256(r1)
c000db20  fa610108  std r19,264(r1)
c000db24  fa810110  std r20,272(r1)
c000db28  faa10118  std r21,280(r1)
c000db2c  fac10120  std r22,288(r1)
c000db30  fae10128  std r23,296(r1)
c000db34  fb010130  std r24,304(r1)
c000db38  fb210138  std r25,312(r1)
c000db3c  fb410140  std r26,320(r1)
c000db40  fb610148  std r27,328(r1)
c000db44  fb810150  std r28,336(r1)
c000db48  fba10158  std r29,344(r1)
c000db4c  fbc10160  std r30,352(r1)
c000db50  fbe10168  std r31,360(r1)
c000db54  f8010170  std r0,368(r1)
c000db58  7ee00026  mfcrr23
c000db5c  fae101a0  std r23,416(r1)
c000db60  f823  std r1,0(r3)
c000db64  4bffdb1d  bl  c000b680# 
flush_count_cache+0x0/0x2480
c000db68  3cc06000  lis r6,24576
c000db6c  7d40322c  dcbt0,r6,10
c000db70  38c4f4d0  addir6,r4,-2864
c000db74  f8cd0260  std r6,608(r13)
c000db78  e904  ld  r8,0(r4)
c000db7c  4864  b   c000dbe0# 
_switch+0xe0/0x180
50:mon> di $flush_count_cache 4d
c000b680  7d2802a6  mflrr9
c000b684  4805  bl  c000b688# 
flush_count_cache+0x8/0x2480
 ...
c000b784  481c  b   c000b7a0# 
flush_count_cache+0x120/0x2480
c000b788  6000  nop
 ...
c000b7a0  7d2803a6  mtlrr9
c000b7a4  39207fff  li  r9,32767
c000b7a8  7d2903a6  mtctr   r9
c000b7ac  4c400420  bcctr-  2,lt
c000b7b0  4e800020  blr
50:mon> 

Summary:
Mitigation fix validation passed.

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

2018-07-04 Thread Kalpana S Shetty

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 right path to pick the fixed kernel.

-- 
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 The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

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
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'i

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

2018-05-31 Thread Kalpana S Shetty

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?
> 
> Could you also see if this bug happens with the Bionic -proposed or mainline
> kernel:
> 
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed.
> 
> Mainline can be downloaded from:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/

Tested with given kernels below is the summary.

4.15.0-20-generic -> System boots
4.15.0-22-generic -> System fails to boots with oops
4.15.0-23-generic -> System fails to boots with oops
4.15.0-23-generic #26~lp1773162 -> System boots

Thanks,
Pavithra

-- 
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 The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

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
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw

[Kernel-packages] [Bug 1742772] Re: powerpc: flush L1D on return to use

2018-01-21 Thread Kalpana S Shetty

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 in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  powerpc: flush L1D on return to use

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742772/+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 1743412] Re: linux: 4.13.0-30.33 -proposed tracker

2018-01-21 Thread Kalpana S Shetty

*** 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.
https://bugs.launchpad.net/bugs/1743412

Title:
  linux: 4.13.0-30.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1743413,1743414,1743415,1743416,1743417,1743418
  derivatives: 1743419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1743412/+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 1743362] Re: linux: 4.4.0-111.134 -proposed tracker

2018-01-21 Thread Kalpana S Shetty

*** 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.
https://bugs.launchpad.net/bugs/1743362

Title:
  linux: 4.4.0-111.134 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1743363,1743364
  derivatives: 1743365,1743367,1743368,1743369,1743370,1743371
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1743362/+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 Power architecture for 16.04

2016-08-31 Thread Kalpana S Shetty

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.launchpad.net/bugs/1573062

Title:
  memory_stress_ng failing for Power architecture for 16.04

Status in linux package in Ubuntu:
  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

2016-08-17 Thread Kalpana S Shetty

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
Variable run time is 2860 seconds per stressor
Estimated total run time is 396 minutes

Is there any way I can run the test for less memory config, the system I
have got is 256Gig mem.

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

2016-08-17 Thread Kalpana S Shetty

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 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 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 1318809] Re: crash tool support for the ppc64el arch

2014-05-29 Thread Kalpana S Shetty

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 for crash tool
root@ubuk60:~# apt-cache policy crash
crash:
  Installed: (none)
  Candidate: 7.0.3-3ubuntu3
  Version table:
 7.0.3-3ubuntu3 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el 
Packages
root@ubuk60:~# 

4)  apt-get install crash

5)  crash /usr/lib/debug/boot/vmlinux-3.13.0-27-generic
/root/kal_ubu_stress.dump

I could able to invoke crash with debug linux and able to see the bt
etc


We can push this package to 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 Released
Status in “crash” source package in Trusty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: crash doesn't work on ppc64el architectures
  Test Case: run crash on a ppc64el crash dump
  Regression Potential: This only affects ppc64el architectures, and is 
currently in utopic.

  --

  Hi,

  Is it possible to (discuss how to) enable the crash package to on the
  ppc64el arch?

  Recently the kernel received the config changes
  (CONFIG_CRASH_DUMP=y, CONFIG_RELOCATABLE=y, currently in the -proposed pocket 
[1])

  Is it hard to move to GDB 7.7? (ppc64el GDB package starts on that
  version).

  Thanks!

  [1] https://launchpad.net/ubuntu/trusty/+source/linux/3.13.0-26.48

  For testing the trusty SRU:

   - the package builds on ppc64el
   - follow test procedure from comment #6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1318809/+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 1318809] Re: crash tool support for the ppc64el arch

2014-05-28 Thread Kalpana S Shetty

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 Released
Status in “crash” source package in Trusty:
  In Progress

Bug description:
  Hi,

  Is it possible to (discuss how to) enable the crash package to on the
  ppc64el arch?

  Recently the kernel received the config changes
  (CONFIG_CRASH_DUMP=y, CONFIG_RELOCATABLE=y, currently in the -proposed pocket 
[1])

  Is it hard to move to GDB 7.7? (ppc64el GDB package starts on that
  version).

  Thanks!

  [1] https://launchpad.net/ubuntu/trusty/+source/linux/3.13.0-26.48

  
  For testing the trusty SRU:

   - the package builds on ppc64el
   - follow test procedure from comment #6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1318809/+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 1318809] Re: crash tool support for the ppc64el arch

2014-05-19 Thread Kalpana S Shetty

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 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:
  In Progress

Bug description:
  Hi,

  Is it possible to (discuss how to) enable the crash package to on the
  ppc64el arch?

  Recently the kernel received the config changes 
  (CONFIG_CRASH_DUMP=y, CONFIG_RELOCATABLE=y, currently in the -proposed pocket 
[1])

  Is it hard to move to GDB 7.7? (ppc64el GDB package starts on that
  version).

  Thanks!

  [1] https://launchpad.net/ubuntu/trusty/+source/linux/3.13.0-26.48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1318809/+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 1318809] Re: Support for the ppc64el arch

2014-05-19 Thread Kalpana S Shetty

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_ubu_at
dump_file: kal_ubu_at.dump

2)  scp "kal_ubu_at.dump"  to Ubuntu VM

3) Install crash tool from development
  
(http://poc1.ltc.br.ibm.com/~mauricfo/for_kalpana/lp1318809/crash_7.0.3-3ubuntu2.1+lp1318809.c3_ppc64el.deb)

4) Run crash => PASS

5)  Open dump file using crash (for analysis purpose)
crash /usr/lib/debug/boot/vmlinux-3.13.0-24-generic  
/root/kal_ubu_at.dump

Could able to open the dump file ===> PASS

crash 7.0.3
Copyright (C) 2002-2013  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.
 
GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-24-generic
DUMPFILE: /root/kal_ubu_at.dump
CPUS: 1
DATE: Mon May 19 11:58:51 2014
  UPTIME: 2 days, 13:26:42
LOAD AVERAGE: 0.00, 0.03, 0.05
   TASKS: 139
NODENAME: ubuk61
 RELEASE: 3.13.0-24-generic
 VERSION: #47-Ubuntu SMP Fri May 2 23:29:18 UTC 2014
 MACHINE: ppc64le  (3026 Mhz)
  MEMORY: 2 GB
   PANIC: ""
 PID: 0
 COMMAND: "swapper/0"
TASK: c0ea59f0  [THREAD_INFO: c0fc8000]
 CPU: 0
   STATE: TASK_RUNNING (PANIC)

crash>


few of crash commands tried:

crash> bt
PID: 0  TASK: c0ea59f0  CPU: 0   COMMAND: "swapper/0"

 R0:  22002084R1:  c0fcba70R2:  c0fccf88   
 R3:  R4:  c0e24e80R5:     


crash> ipcs
SHMID_KERNEL KEY  SHMID  UID   PERMS BYTES  NATTCH STATUS
c00075b2c380  0  0 644   80 2   
c00075b2d280  32769  0 644   16384  2   
c00075b22d80  65538  0 644   2802   
c000778ba980  98307  0 644   64 2  dest 
c000778bd280  131076 0 644   16384  2  dest 
c000778b9f80  163845 0 644   2802  dest 

SEM_ARRAYKEY  SEMID  UID   PERMS NSEMS 
c00077b34a80 00a7 0  0 600   1 
c00077b39880 610f20f1 32769  0 666   1 

MSG_QUEUEKEY  MSQID  UID   PERMS USED-BYTES   MESSAGES
(none allocated)

crash> help

*  files  mach   repeat timer  
alias  foreachmodrunq   tree   
ascii  fuser  mount  search union  
bt gdbnetsetvm 
btop   help   p  sigvtop   
devipcs   ps struct waitq  
disirqpteswap   whatis 
eval   kmem   ptob   symwr 
exit   list   ptov   sysq  
extend logrd task   

crash version: 7.0.3gdb version: 7.6
For help on any command above, enter "help ".
For help on input options, enter "help input".
For help on output options, enter "help output".

-- 
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:
  Support for the ppc64el arch

Status in “crash” package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Is it possible to (discuss how to) enable the crash package to on the
  ppc64el arch?

  Recently the kernel received the config changes 
  (CONFIG_CRASH_DUMP=y, CONFIG_RELOCATABLE=y, currently in the -proposed pocket 
[1])

  Is it hard to move to GDB 7.7? (ppc64el GDB package starts on

[Kernel-packages] [Bug 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

2014-04-14 Thread Kalpana S Shetty

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/powerpc64le-linux-gnu/asm/signal.h"I  see
MINSIGSTKSZ  > 2048

It would be good if you can give suggestion/input on which header file
to include in appln. code for signal.h

-- 
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 missmatches
  kernel (was: sigaltstack system call unable to send proper return code
  (error12))

Status in “eglibc” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is  /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8
  The issue:
  ==
  sigaltstack system call unable send proper return value.

  
  How to run :
  
  -->cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack

  --> ./sigaltstack02  ==> Getting the below error

  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12 
=>> FAIL

  <<>>
  tag=sigaltstack02 stime=1386653793
  cmdline="sigaltstack02"
  contacts=""
  analysis=exit
  <<>>
  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  sigaltstack() should fail and set errno to ENOMEM when the size of alternate 
stack area is less than MINSIGSTKSZ.
  But here its sigaltstack() is returning 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1267062/+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 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

2014-04-11 Thread Kalpana S Shetty

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 to right signal.h when
an appln includes signal.h, I'm not sure which signal.h to use if we
include explicitely from #include "/usr/include/asm-powerpc/signal.h"
Test case works fine.

Conclusion: It does not seems to be a test case issue.

root@ubuntuk60:~# cat s1.c
/*
 * TC1:
 * sigaltstack() should fails and sets errno to ENOMEM when the size of 
alternate
 * stack area is less than MINSIGSTKSZ.
*/
#include 
//#include 
#include "/usr/include/asm-powerpc/signal.h"
#include 

int main()
{
 stack_t sigstk; /* signal stack storing struct. */
 int rc;

 sigstk.ss_size = MINSIGSTKSZ - 1;
 sigstk.ss_flags = 0;

 printf ("MINSTKSZ = %d\n", MINSIGSTKSZ);
 /* Verify sigaltstack() fails and sets errno */
 rc = sigaltstack(&sigstk, (stack_t *) 0);
 if (rc < 0)
 {
  // TC pass if rc < 0
  printf ("FAILED: rc = %d, errono = %d\n", rc, errno);
 }
 else {
  printf ("PASS: rc = %d, errono = %d\n", rc, errno);
 }
}

output TC PASS: used with #include "/usr/include/asm-powerpc/signal.h"
root@ubuntuk60:~# ./a.out
MINSTKSZ = 2048
FAILED: rc = -1, errono = 12 

output TC FAILED: used with #include 
root@ubuntuk60:~# ./a.out
MINSTKSZ = 4096
PASS: rc = 0, errono = 0


The same behavior on LE Ubuntu as well.

-- 
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 missmatches
  kernel (was: sigaltstack system call unable to send proper return code
  (error12))

Status in “eglibc” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is  /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8
  The issue:
  ==
  sigaltstack system call unable send proper return value.

  
  How to run :
  
  -->cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack

  --> ./sigaltstack02  ==> Getting the below error

  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12 
=>> FAIL

  <<>>
  tag=sigaltstack02 stime=1386653793
  cmdline="sigaltstack02"
  contacts=""
  analysis=exit
  <<>>
  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  sigaltstack() should fail and set errno to ENOMEM when the size of alternate 
stack area is less than MINSIGSTKSZ.
  But here its sigaltstack() is returning 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1267062/+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 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

2014-04-11 Thread Kalpana S Shetty

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
an appln includes signal.h, in this case when appln include "signal.h"
it should be taken from --> "/usr/include/powerpc64le-linux-
gnu/asm/signal.h"  NOT from "/usr/include/signal.h".

Conclusion: I do not see this is a test case issue.

root@ubuntuk60:~# cat s1.c
/*
 * TC1:
 * sigaltstack() should fails and sets errno to ENOMEM when the size of 
alternate
 *  stack area is less than MINSIGSTKSZ.
*/
#include 
//#include 
#include "/usr/include/powerpc64le-linux-gnu/asm/signal.h"
#include 

int main()
{
stack_t sigstk; /* signal stack storing struct. */
int rc;

sigstk.ss_size = MINSIGSTKSZ - 1;
sigstk.ss_flags = 0;

printf ("MINSTKSZ = %d\n", MINSIGSTKSZ);
/* Verify sigaltstack() fails and sets errno */
rc = sigaltstack(&sigstk, (stack_t *) 0);
if (rc < 0)
{
// TC pass if rc < 0
printf ("FAILED: rc = %d, errono = %d\n", rc, errno);
}
else {
printf ("PASS: rc = %d, errono = %d\n", rc, errno);
}
}

output TC PASS:   used with "#include 
"/usr/include/powerpc64le-linux-gnu/asm/signal.h"
root@ubuntuk60:~# ./a.out 
MINSTKSZ = 2048
FAILED: rc = -1, errono = 12

output TC FAILED:   used with #include 
root@ubuntuk60:~# ./a.out 
MINSTKSZ = 4096
PASS: rc = 0, errono = 0

-- 
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 missmatches
  kernel (was: sigaltstack system call unable to send proper return code
  (error12))

Status in “eglibc” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is  /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8
  The issue:
  ==
  sigaltstack system call unable send proper return value.

  
  How to run :
  
  -->cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack

  --> ./sigaltstack02  ==> Getting the below error

  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12 
=>> FAIL

  <<>>
  tag=sigaltstack02 stime=1386653793
  cmdline="sigaltstack02"
  contacts=""
  analysis=exit
  <<>>
  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  sigaltstack() should fail and set errno to ENOMEM when the size of alternate 
stack area is less than MINSIGSTKSZ.
  But here its sigaltstack() is returning 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1267062/+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 1267910] Re: ping -R does not work to and from a ubuntu VM image

2014-04-01 Thread Kalpana S Shetty

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 does not work to and from a ubuntu VM image

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Description:
  ===

  The ping command with the -R option does not work to and from a Ubuntu guest.
   The command hangs and does not return.
  The following is the snapshot.

  [root@localhost test]# ping -R 192.168.122.182
  PING 192.168.122.182 (192.168.122.182) 56(124) bytes of data.
  ^C
  --- 192.168.122.182 ping statistics ---
  17 packets transmitted, 0 received, 100% packet loss, time 16006ms

  [root@localhost test]#

  root@ubuntu:/usr/lib/mysql-testsuite# ping -R 9.3.189.114
  PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data.
  ^C
  --- 9.3.189.114 ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2003ms

  root@ubuntu:/usr/lib/mysql-testsuite#

  In the above snapshot 192.168.122.82 is the IP of the guest which is
  running with the ubuntu image.

  
  PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data.
  ^C
  --- 9.3.189.114 ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2003ms

  
  Environment:
  ===

  Guest running ubuntu on a Power8 host.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267910/+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 1267914] Re: Unable to login to ubuntu guest , returns Incorrect Login

2014-04-01 Thread Kalpana S Shetty

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 ubuntu guest , returns Incorrect Login

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Description:
  =

  The LTP test suite was being run. After a while, the guest running ubuntu 
image hung .
  On a re-login returned an Incorrect login message.
  Was reported by all the members using the qemu command to open the ubuntu 
image on the same host.

  The Login credentials provided were ubuntu/passw0rd

  Machine Details:
  
  Host: 9.3.189.114(root/.pasroot)
  Loc: /var/lib/libvirt/images/anasuya/new_ubuntu_alpha1
  Command to open the guest:
  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic 
-nodefaults -monitor stdio -serial pty -append "root=/dev/sda" -kernel 
vmlinux-3.13.0-0-generic -device spapr-vscsi -device 
spapr-vlan,netdev=net0,mac=6c:ae:8b:69:16:68 -netdev bridge,br=virbr0,id=net0 
-drive file=trusty-server-cloudimg-ppc64el.img.qcow2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267914/+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 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

2014-04-01 Thread Kalpana S Shetty

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 missmatches
  kernel (was: sigaltstack system call unable to send proper return code
  (error12))

Status in “eglibc” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is  /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8
  The issue:
  ==
  sigaltstack system call unable send proper return value.

  
  How to run :
  
  -->cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack

  --> ./sigaltstack02  ==> Getting the below error

  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12 
=>> FAIL

  <<>>
  tag=sigaltstack02 stime=1386653793
  cmdline="sigaltstack02"
  contacts=""
  analysis=exit
  <<>>
  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  sigaltstack() should fail and set errno to ENOMEM when the size of alternate 
stack area is less than MINSIGSTKSZ.
  But here its sigaltstack() is returning 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1267062/+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 1267910] Re: ping -R does not work to and from a ubuntu VM image

2014-03-31 Thread Kalpana S Shetty

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 is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1267910

Title:
  ping -R does not work to and from a ubuntu VM image

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Description:
  ===

  The ping command with the -R option does not work to and from a Ubuntu guest.
   The command hangs and does not return.
  The following is the snapshot.

  [root@localhost test]# ping -R 192.168.122.182
  PING 192.168.122.182 (192.168.122.182) 56(124) bytes of data.
  ^C
  --- 192.168.122.182 ping statistics ---
  17 packets transmitted, 0 received, 100% packet loss, time 16006ms

  [root@localhost test]#

  root@ubuntu:/usr/lib/mysql-testsuite# ping -R 9.3.189.114
  PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data.
  ^C
  --- 9.3.189.114 ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2003ms

  root@ubuntu:/usr/lib/mysql-testsuite#

  In the above snapshot 192.168.122.82 is the IP of the guest which is
  running with the ubuntu image.

  
  PING 9.3.189.114 (9.3.189.114) 56(124) bytes of data.
  ^C
  --- 9.3.189.114 ping statistics ---
  3 packets transmitted, 0 received, 100% packet loss, time 2003ms

  
  Environment:
  ===

  Guest running ubuntu on a Power8 host.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267910/+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 1267914] Re: Unable to login to ubuntu guest , returns Incorrect Login

2014-03-31 Thread Kalpana S Shetty

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://bugs.launchpad.net/bugs/1267914

Title:
  Unable to login to ubuntu guest , returns Incorrect Login

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  =

  The LTP test suite was being run. After a while, the guest running ubuntu 
image hung .
  On a re-login returned an Incorrect login message.
  Was reported by all the members using the qemu command to open the ubuntu 
image on the same host.

  The Login credentials provided were ubuntu/passw0rd

  Machine Details:
  
  Host: 9.3.189.114(root/.pasroot)
  Loc: /var/lib/libvirt/images/anasuya/new_ubuntu_alpha1
  Command to open the guest:
  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic 
-nodefaults -monitor stdio -serial pty -append "root=/dev/sda" -kernel 
vmlinux-3.13.0-0-generic -device spapr-vscsi -device 
spapr-vlan,netdev=net0,mac=6c:ae:8b:69:16:68 -netdev bridge,br=virbr0,id=net0 
-drive file=trusty-server-cloudimg-ppc64el.img.qcow2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267914/+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 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

2014-03-31 Thread Kalpana S Shetty

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.
https://bugs.launchpad.net/bugs/1267062

Title:
  LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches
  kernel (was: sigaltstack system call unable to send proper return code
  (error12))

Status in “eglibc” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is  /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8
  The issue:
  ==
  sigaltstack system call unable send proper return value.

  
  How to run :
  
  -->cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack

  --> ./sigaltstack02  ==> Getting the below error

  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12 
=>> FAIL

  <<>>
  tag=sigaltstack02 stime=1386653793
  cmdline="sigaltstack02"
  contacts=""
  analysis=exit
  <<>>
  sigaltstack021  TPASS  :  stgaltstack() fails, Invalid Flag value, 
errno:22
  sigaltstack022  TFAIL  :  sigaltstack() returned 0, expected -1, errno:12
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  sigaltstack() should fail and set errno to ENOMEM when the size of alternate 
stack area is less than MINSIGSTKSZ.
  But here its sigaltstack() is returning 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1267062/+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 1266737] Re: error sda: WRITE SAME failed when installing package

2014-03-17 Thread Kalpana S Shetty

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 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.

** Attachment added: "dmesg_write_same.log"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266737/+attachment/4028748/+files/dmesg_write_same.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/1266737

Title:
error sda: WRITE SAME failed when installing package

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Description:
==
Was installing perl packages using apt-get install command. I saw WRITE SAME
failed displayed during the process.

Command used : apt-get install perl*
on my Ubuntu guest to install all perl packages.

I saw the message as below
.
.
.
.
Setting up perlindex (1.606-1) ...
Generating index (this may take a while)...sda: WRITE SAME failed. Manually
zeroing.
done.

it took few seconds to complete and later on the process continued.

Environment:

Host: Power8
Guest : ubuntu hosted on Power8

used below qemu command :

[root@localhost ubuntu_alpha1]# cat kvmg.p8.h
KERNEL=trusty-server-cloudimg-ppc64el-vmlinuz-generic
#FSIMAGE=trusty-server-cloudimg-ppc64el.img
FSIMAGE=trusty-server-cloudimg-ppc64el.img.qcow2
MEM=8G
qemu-system-ppc64 \
-enable-kvm -M pseries -cpu POWER8 -smp cores=4,threads=1 -m $MEM \
-net nic -net user \
-device spapr-vscsi -drive file=$FSIMAGE \
-kernel $KERNEL \
-append "earlyprintk root=/dev/sda console=hvc0 --no-sessions" \
-nographic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266737/+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 1267712] Re: ubuntu guest's file system becoming read only

2014-03-12 Thread Kalpana S Shetty

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 becoming read only

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  9.3.189.114 (root/.pasroot) (Host Machine)
  Run the follwoing command to go to the guest victim machine from 
(/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

  qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G
  -nographic -nodefaults -monitor stdio -serial pty -append
  "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic
  -device spapr-vscsi -device spapr-
  vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev
  bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-
  ppc64el.img.qcow2

  after this command you will get the screen number.
  example:

  QEMU 1.6.0 monitor - type 'help' for more information
  (qemu) char device redirected to /dev/pts/16 (label serial0)

  Then open another host session and execute the below command

  # screen /dev/pts/16
  (qemu)

  Here the screen number is /dev/pts/16

  -->>Then you will get a blank screen so press ENTER key.

  The guest machine login: ubuntu/passw0rd

  Then do --->sudo -i

  Environment:
  ===
  Host: Power8
  Guest : ubuntu hosted on Power8

  The issue:
  ==
  After logging into the guest some times it becomes read - only file system.

  Description:
  ===

  Here i am not able to create directory or a file.

  root@ubuntu:/opt/ltp# cat /etc/issue
  Ubuntu Trusty Tahr (development branch) \n \l=>>ubuntu 
guest

  root@ubuntu:~# ifconfig
  eth0  Link encap:Ethernet  HWaddr 6c:ae:8b:69:16:15
inet addr:192.168.122.131  Bcast:192.168.122.255  Mask:255.255.255.0
inet6 addr: fe80::6eae:8bff:fe69:1615/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:72 errors:0 dropped:4 overruns:0 frame:0
TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6764 (6.7 KB)  TX bytes:3914 (3.9 KB)
Interrupt:22

  loLink encap:Local Loopback
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  
  root@ubuntu:/opt/ltp# ./runltp -f timers -p -l timers.log -o timers.out
  cat: /opt/ltp/Version: No such file or directory
  INFO: creating /opt/ltp/results directory
  mktemp: failed to create directory via template â/tmp/ltp-XXâ: 
Read-only file system==>>error
  FATAL: Unable to make temporary directory:

  root@ubuntu:/opt/ltp# df -k
  Filesystem 1K-blocksUsed Available Use% Mounted on
  /dev/sda51573372 1303052  47632556   3% /
  none   4   0 4   0% /sys/fs/cgroup
  devtmpfs 5161908 296   5161612   1% /dev
  none 1032440 184   1032256   1% /run
  none5120   0  5120   0% /run/lock
  none 5162192   0   5162192   0% /run/shm
  none  102400   0102400   0% /run/user

  root@ubuntu:/opt/ltp# mkdir -m 777 jagan
  mkdir: cannot create directory âjaganâ: Read-only file system>>error

  root@ubuntu:/opt/ltp# touch jagan
  touch: cannot touch âjaganâ: Read-only file system>>error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267712/+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 1266737] Re: error sda: WRITE SAME failed when installing package

2014-03-12 Thread Kalpana S Shetty

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

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Description:
  ==
  Was installing perl packages using apt-get install command. I saw WRITE SAME 
failed displayed during the process.

  Command used : apt-get install perl* 
  on my Ubuntu guest to install all perl packages.

  I saw the message as below
  .
  .
  .
  .
  Setting up perlindex (1.606-1) ...
  Generating index (this may take a while)...sda: WRITE SAME failed. Manually 
zeroing.
   done.

  it took few seconds to complete  and later on the process continued.

  
  Environment:
  

  Host: Power8
  Guest : ubuntu hosted on Power8

  used below qemu command :

  [root@localhost ubuntu_alpha1]# cat kvmg.p8.h
  KERNEL=trusty-server-cloudimg-ppc64el-vmlinuz-generic
  #FSIMAGE=trusty-server-cloudimg-ppc64el.img
  FSIMAGE=trusty-server-cloudimg-ppc64el.img.qcow2
  MEM=8G
  qemu-system-ppc64 \
  -enable-kvm -M pseries -cpu POWER8 -smp cores=4,threads=1 -m $MEM \
  -net nic -net user \
  -device spapr-vscsi -drive file=$FSIMAGE \
  -kernel $KERNEL \
  -append "earlyprintk root=/dev/sda console=hvc0 --no-sessions" \
  -nographic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266737/+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 1274479] Re: Call Traces found while executing fsracer tests

2014-03-12 Thread Kalpana S Shetty

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” package in Ubuntu:
  Confirmed

Bug description:

  Host machine : 9.3.189.114(roo/.pasroot)

  run "virsh console harini"   to get the console access

  Description:
  -

  fs racer test from ltp test suite was being run on ubuntu alpha 1
  guest.  After couple of hours of testing got some errors on the
  command prompt along with call trace in dmesg.

  Location for fsracer test : /root/ltp-
  full-20140115/testcases/kernel/fs/racer/

  Ran :

   nohup /root/ltp-full-20140115/testcases/kernel/fs/racer/fs_racer.sh
  -t 1000  &

  
=
  On command prompt:
  -
  root@ubuntu:~# [88680.412397] INFO: task ln:16792 blocked for more than 120 
seconds.
  [88680.412527]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.412595] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.412992] INFO: task mkdir:16801 blocked for more than 120 seconds.
  [88680.413079]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.413145] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.413290] INFO: task dd:17882 blocked for more than 120 seconds.
  [88680.413401]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.413468] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.413625] INFO: task fs_racer_file_c:29630 blocked for more than 120 
seconds.
  [88680.413726]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.413793] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.414025] INFO: task fs_racer_file_c:29631 blocked for more than 120 
seconds.
  [88680.414127]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.414196] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.414341] INFO: task ln:29635 blocked for more than 120 seconds.
  [88680.414425]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.414491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.414632] INFO: task ln:29637 blocked for more than 120 seconds.
  [88680.414715]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.414782] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.415139] INFO: task fs_racer_file_c:29641 blocked for more than 120 
seconds.
  [88680.415243]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.415311] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.415456] INFO: task mkdir:29646 blocked for more than 120 seconds.
  [88680.415539]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.415605] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.415748] INFO: task mkdir:29647 blocked for more than 120 seconds.
  [88680.415835]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.415983] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  ==

  Call trace:
  -

  [88680.412397] INFO: task ln:16792 blocked for more than 120 seconds.
  [88680.412527]   Not tainted 3.13.0-5-generic #20-Ubuntu
  [88680.412595] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [88680.412696] ln  D 3fff9b89ea68 0 16792  25258 
0x0004
  [88680.412703] Call Trace:
  [88680.412732] [c00c76ad74b0] [c00c765eeae0] 0xc00c765eeae0 
(unreliable)
  [88680.412852] [c00c76ad7680] [c00154c0] .__switch_to+0x1d0/0x340
  [88680.412917] [c00c76ad7730] [c0abd968] .__schedule+0x368/0x8c0
  [88680.412922] [c00c76ad79b0] [c0abe498] 
.schedule_preempt_disabled+0x18/0x30
  [88680.412926] [c00c76ad7a20] [c0ac078c] 
.__mutex_lock_slowpath+0x18c/0x2c0
  [88680.412930] [c00c76ad7af0] [c0ac0924] .mutex_lock+0x64/0x68
  [88680.412975] [c00c76ad7b70] [c02303e0] 
.kern_path_create+0xb0/0x1e0
  [88680.412979] [c00c76ad7cd0] [c0232a48] 
.user_path_create+0x68/0xa0
  [88680.412983] [c00c76ad7d60] [c0233c88] .SyS_symlinkat+0x78/0x140
  [88680.412989] [c00c76ad7e30] [c0009e58] syscall_exit+0x0/0x98

  
===

  File system status at that moment
  --
  root@ubuntu:~# df -h
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sda 50G   18G   29G  39% /
  none4.0K 0  4.0K   0% /sys/fs/cgroup
  devtmpfs 25G  8.0K   25G

[Kernel-packages] [Bug 1288564] Re: [beta1] tool fdisk do not support disks with more than 65535 cylinders

2014-03-06 Thread Kalpana S Shetty

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 Ubuntu:
  Incomplete

Bug description:
  Description:
  ==
  Installed Ubuntu beta1 build ISO on a Power 8 machine as a KVM guest

  Trying to create partition on a 1 tera byte scsi disk using fdisk, but
  could not create as the cylinders are not shown if it is more than
  65535.

  also,

  uname -a
  
  Linux ubuntu 3.13.0-14-generic #34-Ubuntu SMP Thu Feb 27 22:35:16 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

  Detail logs
  

  user@ubuntu:~$ lsblk
  NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sda  8:00 1T  0 disk  
  vda253:0080G  0 disk 
  ├─vda1 253:10 7M  0 part 
  ├─vda2 253:20  76.7G  0 part /
  └─vda3 253:30   3.3G  0 part 

  > create parition on sda using fdisk

  root@ubuntu:~# fdisk /dev/sda
  The number of cylinders for this disk is set to 65535.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 7300 of partition table 4 will be corrected by w(rite)

  Command (m for help): p

  Disk /dev/sda: 255 heads, 63 sectors, 65535 cylinders
  Units = cylinders of 16065 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System

  Command (m for help): n
  Command action
 e   extended
 p   primary partition (1-4)
  p
  Partition number (1-4): 1
  First cylinder (1-65535): 1
  Last cylinder or +size or +sizeM or +sizeK ([1]-65535): 65535   
=>  cannot select more than 65535 as I want to create more partition using 
all cylinders of the disk

  Command (m for help): p

  Disk /dev/sda: 255 heads, 63 sectors, 65535 cylinders
  Units = cylinders of 16065 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  /dev/sda11165535526409856   83  Linux native

  Command (m for help): w
  The partition table has been altered!

  Calling ioctl() to re-read partition table.
  (Reboot to ensure the partition table has been updated.)
  Syncing disks.

  WARNING: If you have created or modified any DOS 6.x
  partitions, please see the fdisk manual page for additional
  information.

  ===>  check if the parition is created
  root@ubuntu:~# lsblk
  NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sda  8:00 1T  0 disk 
  ├─sda1   8:10   502G  0 part 
  ├─sda2   8:20   208G  0 part 
  ├─sda3   8:30   176G  0 part 
  └─sda4   8:40   144G  0 part 

  > dmesg logs:
  [  104.576752] type=1006 audit(1394083820.277:27): pid=844 uid=0 old 
auid=4294967295 new auid=1000 old ses=4294967295 new ses=1 res=1
  [  246.220015]  sda: sda1 sda2 sda3 sda4
  [  246.220772] sda: p2 size 1811966464 extends beyond EOD, enabling native 
capacity
  [  246.222415]  sda: sda1 sda2 sda3 sda4
  [  246.222541] sda: p2 size 1811966464 extends beyond EOD, truncated
  [  246.222619] sda: p3 size 1879076352 extends beyond EOD, truncated
  [  246.222673] sda: p4 size 1946186240 extends beyond EOD, truncated
  [  248.252926]  sda: sda1 sda2 sda3 sda4
  [  248.253858] sda: p2 size 1811966464 extends beyond EOD, truncated
  [  248.253930] sda: p3 size 1879076352 extends beyond EOD, truncated
  [  248.253995] sda: p4 size 1946186240 extends beyond EOD, truncated
  [  456.215618] type=1006 audit(1394084171.917:28): pid=914 uid=0 old 
auid=4294967295 new auid=1000 old ses=4294967295 new ses=2 res=1
  [  560.438928] kjournald starting.  Commit interval 5 seconds

  
  > Problem : I did not create the last 3 partition and they are not in 
size as I need, so fdisk tool needs support for the large disk

  > my guest xml

  
spartan_b1_disktest
4b1d8ea3-5674-c98c-dd21-a42172b46070
2097152
2097152
1

  /machine


  hvm
  


  
  
  


destroy
restart
restart

  /usr/bin/qemu-kvm
  





  
  





  
  


  
  

  
  


  
  






  
  




  
  




  


  system_u:system_r:svirt_t:s0:c51,c857
  system_u:object_r:svirt_image_t:s0:c51,c857

  

  Please let me know if you need more information

  Thanks
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory

[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Kernel-packages] [Bug 1742772] Re: powerpc: flush L1D on return to use

[Kernel-packages] [Bug 1743412] Re: linux: 4.13.0-30.33 -proposed tracker

[Kernel-packages] [Bug 1743362] Re: linux: 4.4.0-111.134 -proposed tracker

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Kernel-packages] [Bug 1318809] Re: crash tool support for the ppc64el arch

[Kernel-packages] [Bug 1318809] Re: crash tool support for the ppc64el arch

[Kernel-packages] [Bug 1318809] Re: crash tool support for the ppc64el arch

[Kernel-packages] [Bug 1318809] Re: Support for the ppc64el arch

[Kernel-packages] [Bug 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

[Kernel-packages] [Bug 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

[Kernel-packages] [Bug 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

[Kernel-packages] [Bug 1267910] Re: ping -R does not work to and from a ubuntu VM image

[Kernel-packages] [Bug 1267914] Re: Unable to login to ubuntu guest , returns Incorrect Login

[Kernel-packages] [Bug 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

[Kernel-packages] [Bug 1267910] Re: ping -R does not work to and from a ubuntu VM image

[Kernel-packages] [Bug 1267914] Re: Unable to login to ubuntu guest , returns Incorrect Login

[Kernel-packages] [Bug 1267062] Re: LTP sigaltstack02 test failure -- MINSIGSTKSZ in userspace missmatches kernel (was: sigaltstack system call unable to send proper return code (error12))

[Kernel-packages] [Bug 1266737] Re: error sda: WRITE SAME failed when installing package

[Kernel-packages] [Bug 1267712] Re: ubuntu guest's file system becoming read only

[Kernel-packages] [Bug 1266737] Re: error sda: WRITE SAME failed when installing package

[Kernel-packages] [Bug 1274479] Re: Call Traces found while executing fsracer tests

[Kernel-packages] [Bug 1288564] Re: [beta1] tool fdisk do not support disks with more than 65535 cylinders

27 matches

Site Navigation

Mail list logo

Footer information