Bug 458484
Summary: | crash version update in Fedora 9 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas Meyer <thomas.mey> |
Component: | crash | Assignee: | Dave Anderson <anderson> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | nate |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-06-10 12:20:53 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: |
Description
Thomas Meyer
2008-08-08 19:38:02 UTC
It's not worth the effort due to the constantly-shifting sands of the kernel. Every so often the rawhide version will get updated. http://koji.fedoraproject.org/koji/buildinfo?buildID=47600 Hi. Thanks for the quick response. I can live with that solution, just installed the rpm from the given adress and now i can use this great tool to do post mortem analysis. One more question: doing "kmem -S" on kernel next-20080808 gives me the following error: crash> kmem -S kmem: invalid structure member offset: kmem_cache_objects FILE: memory.c LINE: 13500 FUNCTION: dump_kmem_cache_slub() [/usr/bin/crash] error trace: 8085195 => 809f946 => 80c0d82 => 813b9a0 CACHE NAME OBJSIZE ALLOCATED TOTAL SLABS SSIZE 813b9a0: OFFSET_verify+118 80c0d82: dump_kmem_cache_slub+1033 809f946: cmd_kmem+3196 8085195: exec_command+265 kmem: invalid structure member offset: kmem_cache_objects FILE: memory.c LINE: 13500 FUNCTION: dump_kmem_cache_slub() Are you interested in this kind of kernel "progress" or is linux-next too volatile for you to look at? Yeah, this is exactly the type of issue... I don't work with upstream kernels much, and it looks like the venerable old "kmem_cache.objects" structure member no longer exists, and has been replaced somehow by two order-type members?: /* Allocation and freeing of slabs */ struct kmem_cache_order_objects max; struct kmem_cache_order_objects min; It's the first time I've seen this. And it doesn't appear to be a straight-forward fix for the crash utility. Anyway, I'll get around to it eventually, typically when somebody forwards me a sample vmlinux/vmcore pair to work with. Dave Fixed in upstream version 4.0-7.2: http://people.redhat.com/anderson/crash.changelog.html#4_0_7_2 4.0-7.2 - Fix for initialization-time failure when running against 2.6.27 x86_64 kernels, which indicate "crash: cannot resolve: end_pfn". The patch sets the new 2.6.27 x86_64 PAGE_OFFSET value, handles the change in the x86_64 "_cpu_pda" variable declaration, and distinguishes paravirtual "pv_ops" kernels from traditional xen kernels. (oomichi.nec.co.jp, anderson) - When an improper structure member offset or structure size is attempted, a partial crash backtrace is displayed in the ensuing error message. However, if the crash binary was stripped, it would show "/usr/bin/nm: /tmp/crash: no symbols" instead of the address and name of the symbol. This has been fixed to work with stripped binaries if the crash symbol can be found in the crash binary; if the crash symbol cannot be found, such as for static text symbols, it will just display its address and "(undetermined)". (bwalle) - crash.spec file addition: Requires: binutils (anderson) - Fix for LKCD kerntypes debuginfo files to use "node_states" when "node_online_map" is not in use. (cpw) - Implement support for s390/s390x CONFIG_SPARSEMEM kernels. Without the patch, crash sessions would fail during initialization with the error message: "crash: CONFIG_SPARSEMEM kernels not supported for this architecture". (holzheu.ibm.com) - Fix for "kmem -[sS]" when running against 2.6.27 CONFIG_SLUB kernels, in which the kmem_cache.objects and .order members were replaced by a kmem_cache_order_objects structure. Without the patch, the command would fail with the error message: "kmem: "invalid structure member offset: kmem_cache_objects". The fix also recognizes and supports potentially variable slab sizes as introduced by the kernel patch. (anderson) - Increased the maximum number of SIAL commands from 100 to 200. (cpw) - 4.0-7.1 to 4.0-7.2 incremental patch (9/15/08) Information for build crash-4.0-8.7.2.fc11 http://koji.fedoraproject.org/koji/buildinfo?buildID=84905 This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |