Bug 2261852 - uname --processor is broken from Fedora38 and above!
Summary: uname --processor is broken from Fedora38 and above!
Keywords:
Status: CLOSED DUPLICATE of bug 2126206
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: 38
Hardware: ppc64le
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Lukáš Zaoral
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-30 05:40 UTC by IBM Bug Proxy
Modified: 2024-01-30 09:36 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-01-30 09:36:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 205001 0 None None None 2024-01-30 05:40:40 UTC

Description IBM Bug Proxy 2024-01-30 05:40:17 UTC

Comment 1 IBM Bug Proxy 2024-01-30 05:40:29 UTC
== Comment: #0 - Anushree Mathur <Anushree.Mathur2> - 2024-01-29 03:06:30 ==
ENV:
HOST OS : Fedora38
Architecture : ppc64-LE
kernel : i) 6.8.0-rc2 (Upstream kernel)
         ii) 6.6.13-200.fc39.ppc64le (Latest fedora kernel)

uname --processor command is not giving the expected output! I have tried with upstream kernel and fedora kernel both. It is broken from Fedora38 and above!

Steps to reproduce:
1) uname --processor

Expected output:
ppc64le

Actual output:
unknown

It is working fine with coreutils-9.1-7.fc37.ppc64le but broken from coreutils-9.1-12.fc38.ppc64le and above.

Comment 2 Kamil Dudka 2024-01-30 07:18:08 UTC
This seems to be yet another duplicate of bug #2126206.  Please use `uname -m` to print hardware class.

Comment 3 IBM Bug Proxy 2024-01-30 08:30:24 UTC
------- Comment From Anushree.Mathur2 2024-01-30 03:21 EDT-------
With uname -m i am getting the output:

root# uname -m

Comment 4 Lukáš Zaoral 2024-01-30 09:36:29 UTC
Is this the whole output you got from `uname -m`?  It seems to be cut-off.

Anyway, `uname -p` and `uname -i` are purely informative and should not be used for any serious decision making.  Please reopen the bug if `uname -m` does not work for you.

*** This bug has been marked as a duplicate of bug 2126206 ***


Note You need to log in before you can comment on or make changes to this bug.