Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2245707
| Summary: | [abrt] udisks2: __ioctl(): udisksd killed by SIGABRT | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Camiropan <camiropan> | ||||||||||||||||||||||||||
| Component: | udisks2 | Assignee: | Tomáš Bžatek <tbzatek> | ||||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 39 | CC: | awilliam, camiropan, gnome-sig, kparal, tbzatek, vtrefny | ||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/57b93d3d09bd1dfce7760e736bb1eecc9f7eb51 | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:ca80b7352eeb9b35db2dcb31357b02f202b6a8f9;VARIANT_ID=workstation; AcceptedFreezeException | ||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||
| Last Closed: | 2023-10-26 23:38:41 UTC | Type: | --- | ||||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||||||||||
| Bug Blocks: | 2143447 | ||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||
|
Description
Camiropan
2023-10-23 17:45:10 UTC
Created attachment 1995213 [details]
File: proc_pid_status
Created attachment 1995214 [details]
File: maps
Created attachment 1995215 [details]
File: limits
Created attachment 1995216 [details]
File: environ
Created attachment 1995217 [details]
File: open_fds
Created attachment 1995218 [details]
File: mountinfo
Created attachment 1995219 [details]
File: os_info
Created attachment 1995220 [details]
File: cpuinfo
Created attachment 1995221 [details]
File: core_backtrace
Created attachment 1995222 [details]
File: dso_list
Created attachment 1995223 [details]
File: var_log_messages
Created attachment 1995224 [details]
File: backtrace
FEDORA-2023-0f7d8165cb has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0f7d8165cb This is caused by a NVMe device not conforming to the official NVM Express specification. Contact your hardware vendor for firmware update. *** Bug 2245285 has been marked as a duplicate of this bug. *** Tomáš, will the new libblockdev work around the firmware bug? If this is the case, let's propose this as a freeze exception, so that people can install F39 on these disks (you can read more details in bug 2245285 ). Unfortunately, there are no firmware updates for the SK hynix PC611 NVMe. Neither Dell nor SK hynix offer any kind of firmware updates. I have installed Windows 10, dell update commander, and SK hynix Center, but as I said, there are no updates available. (In reply to Kamil Páral from comment #16) > Tomáš, will the new libblockdev work around the firmware bug? Only partially. We've received number of similar reports upstream and worked with the NVMe community on a temporary solution. Still it's just a workaround for userspace until the kernel host nvme driver gets fixed (not much progress as of now). Also needed are some libnvme patches (that I got upstreamed but haven't had time to make a Fedora backport). Will do that tomorrow. > If this is the case, let's propose this as a freeze exception, so that > people can install F39 on these disks (you can read more details in bug > 2245285 ). Sure. The libblockdev update can go in independently from libnvme, no direct ABI dependencies. So I have built libnvme-1.6-2.fc39 and libnvme-1.6-2.fc40 Please test both https://bodhi.fedoraproject.org/updates/FEDORA-2023-0f7d8165cb and https://bodhi.fedoraproject.org/updates/FEDORA-2023-b4ed0a0db1 together. (In reply to Tomáš Bžatek from comment #19) > https://bodhi.fedoraproject.org/updates/FEDORA-2023-b4ed0a0db1 together. Can you please mark the libnvme update as also fixing this bug? We need it for freeze exception tracking process. Thanks! @camiropan Can you please quickly test whether this F39 Workstation Live image works for you? It includes both the updates mentioned above: https://fedorapeople.org/groups/qa/bugs/rhbz2245707.iso FEDORA-2023-b4ed0a0db1 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b4ed0a0db1 I tested the Live image https://fedorapeople.org/groups/qa/bugs/rhbz2245707.iso and installed fedora 39 with it and everything works fine. A small issue i noticed is that in the information tab in Gnome settings the capacity of the nvme is "unknown". Besides that, everything works as expected. So this patches of libblockdev and libnvme are a workaround in userspace for a problem in the kernel, which exists because of the SK hyndix firmware bug, right? Thanks for testing, Camiropan. Please give +1 karma to both Bodhi updates from comment 19. Thanks! (In reply to Camiropan from comment #23) > So this patches of libblockdev and libnvme are a workaround in userspace for > a problem in the kernel, which exists because of the SK hyndix firmware bug, > right? Correct. This is not limited to SK Hynix, it's just one of the reputable manufacturers that often came up. We found evidence of some Phison-based drives as well (that got fixed by firmware update), though most issues were reported with random Chinese-made NVMe controllers. > A small issue i noticed is that in the information tab in Gnome settings the > capacity of the nvme is "unknown". That's https://github.com/storaged-project/udisks/issues/1194, not all controllers apparently report Total NVM Capacity data, would need to find an algorithm to guess goood-enough size in the meantime. the libnvme patches are claimed to be "backports", but what are they backports *of*? I can find no trace that they've been submitted to or discussed at http://lists.infradead.org/pipermail/linux-nvme/ , which AFAICT is where they're supposed to go. The spec file does not provide any comment explaining their provenance (as it's supposed to). We're trying to do a candidate compose and I'm really on the fence about whether it's a good idea to pull this stuff in. oh, wait - I see the libnvme repo at least has pull requests enabled. These appear to be: * https://github.com/linux-nvme/libnvme/pull/727 * https://github.com/linux-nvme/libnvme/pull/731 The note that the second "received only minimal testing" seems a bit concerning. Both seem to have been merged with fairly cursory review. +4 in https://pagure.io/fedora-qa/blocker-review/issue/1420 , marking accepted. I am a bit worried this is quite a lot of change to land in a fairly critical component at this point, though. It does seem like Arch has had the changes landed for a week or two and no new bugs seem to have been reported. FEDORA-2023-0f7d8165cb has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-b4ed0a0db1 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. |