| 2019-08-20 21:24:21 |
Rafael David Tinoco |
bug |
|
|
added bug |
| 2019-08-20 21:24:53 |
Rafael David Tinoco |
bug task added |
|
linux (Ubuntu) |
|
| 2019-08-20 21:26:38 |
Rafael David Tinoco |
bug |
|
|
added subscriber Canonical Server Team |
| 2019-08-20 21:29:01 |
Rafael David Tinoco |
description |
From bug:
https://bugs.launchpad.net/bugs/1840511
clockhouse test started failing because of the presence of stderr whenever using the function:
cpuinfo_linux_get_max_processors_count(void)
From cpuid library.
This happens because:
----
#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
/*
* Android NDK headers before platform 21 do not define CPU_SETSIZE,
* so we hard-code its value, as defined in platform 21 headers
*/
#if defined(__LP64__)
static const uint32_t default_max_processors_count = 1024;
#else
static const uint32_t default_max_processors_count = 32;
#endif
#else
static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif
----
#if !defined(__ANDROID__)
/*
* sched.h is only used for CPU_SETSIZE constant.
* Android NDK headers before platform 21 do have this constant in sched.h
*/
#include <sched.h>
#endif
----
and resolving includes:
x86_64-linux-gnu/bits/cpu-set.h:
/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024
----
And the warning:
Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023
Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed).
Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? |
From bug:
https://bugs.launchpad.net/bugs/1840511
clockhouse builds test started failing because of the presence of stderr whenever using the function:
cpuinfo_linux_get_max_processors_count(void)
From cpuid library.
This happens because:
----
#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
/*
* Android NDK headers before platform 21 do not define CPU_SETSIZE,
* so we hard-code its value, as defined in platform 21 headers
*/
#if defined(__LP64__)
static const uint32_t default_max_processors_count = 1024;
#else
static const uint32_t default_max_processors_count = 32;
#endif
#else
static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif
----
#if !defined(__ANDROID__)
/*
* sched.h is only used for CPU_SETSIZE constant.
* Android NDK headers before platform 21 do have this constant in sched.h
*/
#include <sched.h>
#endif
----
and resolving includes:
x86_64-linux-gnu/bits/cpu-set.h:
/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024
----
And the warning:
Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023
Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed).
Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? |
|
| 2019-08-20 21:30:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-08-21 02:06:47 |
Rafael David Tinoco |
cpuinfo (Ubuntu): status |
New |
In Progress |
|
| 2019-08-21 02:06:50 |
Rafael David Tinoco |
cpuinfo (Ubuntu): importance |
Undecided |
Medium |
|
| 2019-08-21 02:06:52 |
Rafael David Tinoco |
cpuinfo (Ubuntu): assignee |
|
Rafael David Tinoco (rafaeldtinoco) |
|
| 2019-08-21 02:21:10 |
Rafael David Tinoco |
attachment added |
|
cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840847/+attachment/5283577/+files/cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff |
|
| 2019-08-21 02:22:06 |
Rafael David Tinoco |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2019-08-21 02:22:10 |
Rafael David Tinoco |
linux (Ubuntu): importance |
Undecided |
Low |
|
| 2019-08-21 02:22:31 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Kernel Team |
| 2019-08-21 02:23:10 |
Rafael David Tinoco |
description |
From bug:
https://bugs.launchpad.net/bugs/1840511
clockhouse builds test started failing because of the presence of stderr whenever using the function:
cpuinfo_linux_get_max_processors_count(void)
From cpuid library.
This happens because:
----
#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
/*
* Android NDK headers before platform 21 do not define CPU_SETSIZE,
* so we hard-code its value, as defined in platform 21 headers
*/
#if defined(__LP64__)
static const uint32_t default_max_processors_count = 1024;
#else
static const uint32_t default_max_processors_count = 32;
#endif
#else
static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif
----
#if !defined(__ANDROID__)
/*
* sched.h is only used for CPU_SETSIZE constant.
* Android NDK headers before platform 21 do have this constant in sched.h
*/
#include <sched.h>
#endif
----
and resolving includes:
x86_64-linux-gnu/bits/cpu-set.h:
/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024
----
And the warning:
Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023
Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed).
Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? |
From bug:
https://bugs.launchpad.net/bugs/1840511
clockhouse builds test started failing because of the presence of stderr whenever using the function:
cpuinfo_linux_get_max_processors_count(void)
From cpuid library.
This happens because:
----
#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
/*
* Android NDK headers before platform 21 do not define CPU_SETSIZE,
* so we hard-code its value, as defined in platform 21 headers
*/
#if defined(__LP64__)
static const uint32_t default_max_processors_count = 1024;
#else
static const uint32_t default_max_processors_count = 32;
#endif
#else
static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif
----
#if !defined(__ANDROID__)
/*
* sched.h is only used for CPU_SETSIZE constant.
* Android NDK headers before platform 21 do have this constant in sched.h
*/
#include <sched.h>
#endif
----
and resolving includes:
x86_64-linux-gnu/bits/cpu-set.h:
/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024
----
And the warning:
Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023
Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed).
FOR THE KERNEL TEAM:
Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? |
|
| 2019-08-21 03:50:30 |
Rafael David Tinoco |
bug |
|
|
added subscriber Robie Basak |
| 2019-08-21 04:25:11 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2019-08-21 04:25:23 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2019-08-21 04:58:58 |
Rafael David Tinoco |
description |
From bug:
https://bugs.launchpad.net/bugs/1840511
clockhouse builds test started failing because of the presence of stderr whenever using the function:
cpuinfo_linux_get_max_processors_count(void)
From cpuid library.
This happens because:
----
#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
/*
* Android NDK headers before platform 21 do not define CPU_SETSIZE,
* so we hard-code its value, as defined in platform 21 headers
*/
#if defined(__LP64__)
static const uint32_t default_max_processors_count = 1024;
#else
static const uint32_t default_max_processors_count = 32;
#endif
#else
static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif
----
#if !defined(__ANDROID__)
/*
* sched.h is only used for CPU_SETSIZE constant.
* Android NDK headers before platform 21 do have this constant in sched.h
*/
#include <sched.h>
#endif
----
and resolving includes:
x86_64-linux-gnu/bits/cpu-set.h:
/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024
----
And the warning:
Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023
Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed).
FOR THE KERNEL TEAM:
Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? |
From bug:
https://bugs.launchpad.net/bugs/1840511
clickhouse builds test started failing because of the presence of stderr whenever using the function:
cpuinfo_linux_get_max_processors_count(void)
From cpuid library.
This happens because:
----
#if defined(__ANDROID__) && !defined(CPU_SETSIZE)
/*
* Android NDK headers before platform 21 do not define CPU_SETSIZE,
* so we hard-code its value, as defined in platform 21 headers
*/
#if defined(__LP64__)
static const uint32_t default_max_processors_count = 1024;
#else
static const uint32_t default_max_processors_count = 32;
#endif
#else
static const uint32_t default_max_processors_count = CPU_SETSIZE;
#endif
----
#if !defined(__ANDROID__)
/*
* sched.h is only used for CPU_SETSIZE constant.
* Android NDK headers before platform 21 do have this constant in sched.h
*/
#include <sched.h>
#endif
----
and resolving includes:
x86_64-linux-gnu/bits/cpu-set.h:
/* Size definition for CPU sets. */
#define __CPU_SETSIZE 1024
----
And the warning:
Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023
Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed).
FOR THE KERNEL TEAM:
Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? |
|
| 2019-08-21 14:11:19 |
Launchpad Janitor |
cpuinfo (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-09-08 05:57:53 |
Mathew Hodson |
bug task deleted |
linux (Ubuntu) |
|
|
