On February 12th, 2015, the DMTF released version 3.0.0 of the System Management BIOS Reference Specification. This update isn't just adding enumerated values to existing structures, as previous updates did. It is also introducing a new entry point format which allows for larger tables and structures. Support for this needs to be added to dmidecode.

Additionally, reading the entry point and the table from /dev/mem is no longer possible on all systems, so some work is in progress to offer an alternative interface through sysfs. It would be great to finalize this and release a new version of dmidecode that would support both SMBIOS version 3.0 and this new kernel interface.

Looking for hackers with the skills:

smbios dmi kernel c

This project is part of:

Hack Week 12

Activity

  • about 6 years ago: dawei_pang liked this project.
  • about 10 years ago: royfranz joined this project.
  • over 10 years ago: joeyli liked this project.
  • over 10 years ago: jdelvare added keyword "c" to this project.
  • over 10 years ago: jdelvare added keyword "smbios" to this project.
  • over 10 years ago: jdelvare added keyword "dmi" to this project.
  • over 10 years ago: jdelvare added keyword "kernel" to this project.
  • over 10 years ago: jdelvare started this project.
  • over 10 years ago: jdelvare originated this project.

  • Comments

    • jdelvare
      about 10 years ago by jdelvare | Reply

      Roy Franz's patches have been reviewed, tested and committed. This lets dmidecode make use of the upcoming sysfs interface to DMI tables.

    • jdelvare
      about 10 years ago by jdelvare | Reply

      I have just committed the dmidecode patches that implement support for the SMBIOS 3.0.0 specification. So the user-space side of the project is mostly completed, although a few cleanups and improvements are still possible.

    • jdelvare
      about 10 years ago by jdelvare | Reply

      I committed a few more patches yesterday and this morning. There's one issue left that I'm aware of (reading SMBIOS 3.0 64-table from a dump file), I'll look into it.

    • jdelvare
      about 10 years ago by jdelvare | Reply

      A kernel fix was merged upstream:
      http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5c1ac56b51b9d222ab202dec1ac2f4215346129d

      The remaining 8 kernel patches are queued for kernel v4.2:
      http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/

    Similar Projects

    early stage kdump support by mbrugger

    Project Description

    When we experience a early boot crash, we are not able to analyze the kernel dump, as user-space wasn't able to load the crash system. The idea is to make the crash system compiled into the host kernel (think of initramfs) so that we can create a kernel dump really early in the boot process.

    Goal for the Hackweeks

    1. Investigate if this is possible and the implications it would have (done in HW21)
    2. Hack up a PoC (done in HW22 and HW23)
    3. Prepare RFC series (giving it's only one week, we are entering wishful thinking territory here).

    update HW23

    • I was able to include the crash kernel into the kernel Image.
    • I'll need to find a way to load that from init/main.c:start_kernel() probably after kcsan_init()
    • I workaround for a smoke test was to hack kexec_file_load() systemcall which has two problems:
      1. My initramfs in the porduction kernel does not have a new enough kexec version, that's not a blocker but where the week ended
      2. As the crash kernel is part of init.data it will be already stale once I can call kexec_file_load() from user-space.

    The solution is probably to rewrite the POC so that the invocation can be done from init.text (that's my theory) but I'm not sure if I can reuse the kexec infrastructure in the kernel from there, which I rely on heavily.

    update HW24

    • Day1
      • rebased on v6.12 with no problems others then me breaking the config
      • setting up a new compilation and qemu/virtme env
      • getting desperate as nothing works that used to work
    • Day 2
      • getting to call the invocation of loading the early kernel from __init after kcsan_init()
    • Day 3

      • fix problem of memdup not being able to alloc so much memory... use 64K page sizes for now
      • code refactoring
      • I'm now able to load the crash kernel
      • When using virtme I can boot into the crash kernel, also it doesn't boot completely (major milestone!), crash in elfcorehdr_read_notes()
    • Day 4

      • crash systems crashes (no pun intended) in copy_old_mempage() link; will need to understand elfcorehdr...
      • call path vmcore_init() -> parse_crash_elf_headers() -> elfcorehdr_read() -> read_from_oldmem() -> copy_oldmem_page() -> copy_to_iter()
    • Day 5

      • hacking arch/arm64/kernel/crash_dump.c:copy_old_mempage() to see if crash system really starts. It does.
      • fun fact: retested with more reserved memory and with UEFI FW, host kernel crashes in init but directly starts the crash kernel, so it works (somehow) \o/
    • TODOs

      • fix elfcorehdr so that we actually can make use of all this...
      • test where in the boot __init() chain we can/should call kexec_early_dump()