Bug 1916990 - updating fedora kernel error message
Summary: updating fedora kernel error message
Keywords:
Status: CLOSED DUPLICATE of bug 1911038
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-16 08:15 UTC by jpbn
Modified: 2021-01-17 10:28 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-17 07:10:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg.txt (101.88 KB, text/plain)
2021-01-16 08:15 UTC, jpbn
no flags Details

Description jpbn 2021-01-16 08:15:18 UTC
Created attachment 1748063 [details]
dmesg.txt

1. Please describe the problem:
update gives error:
 Running scriptlet: kernel-core-5.10.7-200.fc33.x86_64                   96/96 
^Csort: fflush failed: 'standard output': Broken pipe
sort: write error

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
sort: write failed: 'standard output': Broken pipe
sort: write error



2. What is the Version-Release number of the kernel:

 kernel-core-5.10.7-200.fc33.x86_64   

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Alessio 2021-01-17 07:10:09 UTC

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


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