Public bug reported:

> ---Problem Description---
> Getting the following error during ziomon execution:
> 
> ziomon -i 2 -d 1 -l 1M -o ziomonlog  /dev/sdb /dev/sda 
> Check devices...done
> Estimated maximum disk space required for log data: approx. <1 MBytes
> Collecting configuration data...done
> Start data collection processes...done
> Collecting data...FAILED to start thread on CPU 6: 22/Invalid argument
> FAILED to start thread on CPU 7: 22/Invalid argument
> FAILED to start thread on CPU 8: 22/Invalid argument
> FAILED to start thread on CPU 9: 22/Invalid argument

Could you ensure that the cpuplugd is not running while using ziomon?

== >Yes, cpuplugd is not running during ziomon execution.

I have also called blktrace directly and got the same errors:

s35lp49:~ # blktrace -w 1 -d /dev/sda
FAILED to start thread on CPU 6: 22/Invalid argument
FAILED to start thread on CPU 7: 22/Invalid argument
FAILED to start thread on CPU 8: 22/Invalid argument
FAILED to start thread on CPU 9: 22/Invalid argument

I found an interesting thing.
I installed the blktrace source and I found several patches in there, one of 
them is exactly the opposite of what this patch proposes: use configured cpus 
instead of online cpus: 
blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch
Without applying the patches:

s35lp49:/usr/src/packages/SOURCES # ls -l b*patch
-rw-r--r-- 1 root root 3171 Dec 15  2008 
blkparse-track-smallest-sequence-read-per-device.patch
-rw-r--r-- 1 root root 3748 Aug 20  2015 
blktrace-blkreplay-convert-to-use-a-dynamic-cpu_set_t.patch
-rw-r--r-- 1 root root 1223 Aug 20  2015 
blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch
-rw-r--r-- 1 root root 1155 Aug 20  2015 
btreplay-fix-typo-in-scaling-up-the-dynamic-cpu-set-size.patch
-rw-r--r-- 1 root root 1593 Aug 20  2015 
btreplay-machines-are-now-large-enough-that-holes-need-to-be-dealt-with.patch
-rw-r--r-- 1 root root 1292 Aug 20  2015 
btreplay-use-sysconf-to-get-the-number-of-configured-cpus.patch

or if I apply the patch proposed in:

http://git.kernel.dk/?p=blktrace.git;a=commit;h=80c4041b2e7a7d5afb75df563bf51bb27773c095

after applying the patches mentioned above, blktrace works:

s35lp49:/usr/src/packages/SOURCES/blktrace-1.0.5 # ./blktrace -w 1 -d /dev/sda
=== sda ===
  CPU  0:                    0 events,        0 KiB data
  CPU  1:                    1 events,        1 KiB data
  CPU  2:                    0 events,        0 KiB data
  CPU  3:                    0 events,        0 KiB data
  CPU  4:                    0 events,        0 KiB data
  CPU  5:                    0 events,        0 KiB data
  Total:                     1 events (dropped 0),        1 KiB data

It seems to me that blktrace-use-number-of-configured-cpus-instead-of-
online-cpus.patch was the cause of this bug.

====> Common code specific !

** Affects: ubuntu-z-systems
     Importance: Undecided
         Status: New

** Affects: blktrace (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: New


** Tags: architecture-s39064 bugnameltc-152254 severity-medium 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-152254 severity-medium
targetmilestone-inin---

** Changed in: ubuntu
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (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/1692907

Title:
  blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument

Status in Ubuntu on IBM z Systems:
  New
Status in blktrace package in Ubuntu:
  New

Bug description:
  > ---Problem Description---
  > Getting the following error during ziomon execution:
  > 
  > ziomon -i 2 -d 1 -l 1M -o ziomonlog  /dev/sdb /dev/sda 
  > Check devices...done
  > Estimated maximum disk space required for log data: approx. <1 MBytes
  > Collecting configuration data...done
  > Start data collection processes...done
  > Collecting data...FAILED to start thread on CPU 6: 22/Invalid argument
  > FAILED to start thread on CPU 7: 22/Invalid argument
  > FAILED to start thread on CPU 8: 22/Invalid argument
  > FAILED to start thread on CPU 9: 22/Invalid argument

  Could you ensure that the cpuplugd is not running while using ziomon?

  == >Yes, cpuplugd is not running during ziomon execution.

  I have also called blktrace directly and got the same errors:

  s35lp49:~ # blktrace -w 1 -d /dev/sda
  FAILED to start thread on CPU 6: 22/Invalid argument
  FAILED to start thread on CPU 7: 22/Invalid argument
  FAILED to start thread on CPU 8: 22/Invalid argument
  FAILED to start thread on CPU 9: 22/Invalid argument

  I found an interesting thing.
  I installed the blktrace source and I found several patches in there, one of 
them is exactly the opposite of what this patch proposes: use configured cpus 
instead of online cpus: 
blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch
  Without applying the patches:

  s35lp49:/usr/src/packages/SOURCES # ls -l b*patch
  -rw-r--r-- 1 root root 3171 Dec 15  2008 
blkparse-track-smallest-sequence-read-per-device.patch
  -rw-r--r-- 1 root root 3748 Aug 20  2015 
blktrace-blkreplay-convert-to-use-a-dynamic-cpu_set_t.patch
  -rw-r--r-- 1 root root 1223 Aug 20  2015 
blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch
  -rw-r--r-- 1 root root 1155 Aug 20  2015 
btreplay-fix-typo-in-scaling-up-the-dynamic-cpu-set-size.patch
  -rw-r--r-- 1 root root 1593 Aug 20  2015 
btreplay-machines-are-now-large-enough-that-holes-need-to-be-dealt-with.patch
  -rw-r--r-- 1 root root 1292 Aug 20  2015 
btreplay-use-sysconf-to-get-the-number-of-configured-cpus.patch

  or if I apply the patch proposed in:

  
http://git.kernel.dk/?p=blktrace.git;a=commit;h=80c4041b2e7a7d5afb75df563bf51bb27773c095

  after applying the patches mentioned above, blktrace works:

  s35lp49:/usr/src/packages/SOURCES/blktrace-1.0.5 # ./blktrace -w 1 -d /dev/sda
  === sda ===
    CPU  0:                    0 events,        0 KiB data
    CPU  1:                    1 events,        1 KiB data
    CPU  2:                    0 events,        0 KiB data
    CPU  3:                    0 events,        0 KiB data
    CPU  4:                    0 events,        0 KiB data
    CPU  5:                    0 events,        0 KiB data
    Total:                     1 events (dropped 0),        1 KiB data

  It seems to me that blktrace-use-number-of-configured-cpus-instead-of-
  online-cpus.patch was the cause of this bug.

  ====> Common code specific !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1692907/+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

Reply via email to