crash version 4.0-4.8 is available

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




- Implemented support for kernels configured with CONFIG_SLUB, which
  completely replaces the venerable "kernel/slab.c" with the new
  "kernel/slub.c" kmalloc() slab subsystem.  Accordingly, the
  "kmem -s [address]", "kmem -S [address]", and "kmem <address>"
  commands will display slab-related information in a similar manner
  to what they currently do, with additional per-node information.
  It should be noted that, due to slub.c's design, the verbose
  "kmem -S" output will be pared down slightly to not display the
  list of all "full" slabs unless the proper kernel slub debugging
  has been turned on.  However, given a address of an object from a
  full slab page, or of the full slab page itself, that address
  will then be traced back to its original slab cache and its data
  displayed.  (anderson@xxxxxxxxxx)

- Change for support of LKCD dumpfile version 8 and later to determine
  the backtrace starting registers from the dumpfile header.  Increase
  (maximum) NR_CPUS for ia64 to 4096.  (bwalle@xxxxxxx)

- The SIAL interpreter extension module has been updated to support
  the ia64, ppc64, s390 and s390x architectures.  Several fixes have
  been applied, and three new debug commands, sdebug, sclass and sname
  have been added.  (lucchouina@xxxxxxxxx)

- Fixed a bug in the CONFIG_SPARSEMEM patch (contributed in 4.0-3.22)
  in which a static pointer variable was initializing itself with a
  buffer that was returned from a command-time-only GETBUF() call,
  instead of using malloc().  It would then continue to use the buffer,
  trampling on the buffer contents set up by whatever command that
  subsequently allocated the buffer.  I only caught this during the
  CONFIG_SLUB development, so I have no examples (if any) of how this
  would have ever manifested itself in a crash command error.
  (anderson@xxxxxxxxxx)

- Fixed the "mach" command in CONFIG_SLUB kernels which would abort
  with the error message: "mach: cannot resolve cache_cache" when
  trying to determine the value for the L1 CACHE SIZE display.  Since
  the generic manner of determining the cache size no longer worked
  correctly anyway, the L1 CACHE SIZE display has been removed.
  (anderson@xxxxxxxxxx)

- Fix for missing NODE header in NUMA "kmem -f" output.
  (anderson@xxxxxxxxxx)

- Fix for the chronology of the contents of the kernel message buffer
  output by the "log" command.  (atyson@xxxxxx)

- Display a WARNING message if a PT_LOAD segment in an ELF-style
  dumpfile advertises a memory segment that would go beyond the end
  of the dumpfile.  (bwalle@xxxxxxx, anderson@xxxxxxxxxx)

Download from: http://people.redhat.com/anderson


--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility

[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux