Petr Tesarik

Failed to receive session end confirmation after successful BOOT upload

1

With heimdall v1.4.2, I'm getting this: ``` … BOOT upload successful Ending session... [ 7.187929] [000066fe] libusb: debug [libusb_submit_transfer] transfer 0x557eea28c420 [ 7.187937] [000066fe] libusb: debug [add_to_flying_list] arm timer for...

Even with commit 8adf11136838426bef34cf5734981e57129ff417, the OBS build contains `NET_USER=0`. Local build on an IBM POWER LPAR (jostaberry-4) produces a more credible number. I haven't tried with `osc build` yet for...

Rapidquilt attempted to rollback a patch and that failed.

4

The [attached series](https://github.com/openSUSE/rapidquilt/files/10143129/bug-rollback.tar.gz) triggers a bug. Output with `RUST_BACKTRACE=1 rapidquilt push -a --dry-run --threads=1` (just to make sure it's not a race condition, but it also fails multi-threaded): ``` Applying...

Missing support for RISC-V

2

It would be nice to be the first dump-related project that supports RISC-V. ;-)

This architecture is currently supported by makedumpfile, and we aim at feature parity so that libkdumpfile can become a backend for makedumpfile.

Files produced by the VMDUMP command under z/VM are not supported. The format is described here: https://github.com/ibm-s390-linux/s390-tools/blob/d5f853c460f04961fa9f7cb42c48c9f2f9341e5e/libvmdump/vm_dump.h

Attributes need reference counting

1

Attributes can be used after deallocation (see e.g. https://github.com/osandov/drgn/issues/280). That's because an explicit or implicit (like in the above case) reference may still exist after the attribute is cleared.

Many ppc64 paging forms are not recognized. Hardware page tables are not supported.

This architecture is currently supported by `makedumpfile`, and we aim at feature parity so that `libkdumpfile` can become a backend for `makedumpfile`.

This architecture is currently supported by `makedumpfile`, and we aim at feature parity so that `libkdumpfile` can become a backend for `makedumpfile`.