Bug#1031765: pgrep: signal handler matching breaks argument parsing
Upstream has merged https://github.com/ganeti/ganeti/pull/1692, commit
9cd67e6a81c6 ("uidpool_unittest: avoid using negative UIDs") to solve
the issue.
Additionally the following patch is needed to fix a separate problem
with testing:
a40748ab26fc ("py-tests: make tests compatible with roman 3.2+")
Best regards
Heinrich
Bug#1031765: pgrep: signal handler matching breaks argument parsing
Upstream bug report created: https://github.com/ganeti/ganeti/issues/1691 Ubuntu bug LP #2009498
Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2
Hello Vagrant, copying initrd to high memory overwrites internal EFI structures. setenv initrd_high 0x setenv fdt_high 0x solves the problem on the Odroid C2. Best regards Heinrich
Bug#1019391: #1020099 is duplicate to #1019391
Bug report #1020099 is duplicate to #1019391 The issue is fixed by upstream patches available at https://github.com/lovasoa/marshmallow_dataclass/commits/master In Ubuntu we use LP #1991064 for tracking. Best regards Heinrich
Bug#995402: libclass-dbi-sweet-perl: FTBFS: test failure
Related Ubuntu bug https://bugs.launchpad.net/debiantesting/+bug/1961751 Suggested solution: drop package as upstream is not maintained anymore
Bug#988217: bootefi causes boot failure with boot.scr
The original problem report showed the following situation was hit:
common/malloc_simple.c:29:
log_err("alloc space exhausted\n");
You cannot expect normal system behavior when reaching this situation.
The available space for simple malloc is defined by:
CONFIG_SPL_SYS_MALLOC_F_LEN=0x2000
CONFIG_SYS_MALLOC_F_LEN=0x2000
I assume that the problem arises in main U-Boot not in SPL. Please,
increase CONFIG_SYS_MALLOC_F_LEN and check if this error message goes away.
Best regards
Heinrich
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
On 19.02.21 19:40, Dennis Filder wrote: > Control: tag -1 + moreinfo bullseye sid > > If you cannot switch to console with Ctrl-Alt-F2 then this is a strong > indicator that the bug is in the kernel, probably nouveau. > > If you can reproduce this reliably it would help a lot if you could > provide the output of these commands after the bug has happened: > > dmesg > strace -f -p $(pidof ksplashqml) 2>&1 | dd bs=1k count=20 > journalctl -ab > > You may have to run some of them as root. > dmesg shows a crash in the nouveau driver: [ 441.529012] [ cut here ] [ 441.529076] WARNING: CPU: 1 PID: 1964 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x84/0x9c [nouveau] [ 441.529078] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc rfkill overlay nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi aes_ce_blk crypto_simd snd_hda_intel cryptd snd_intel_dspcfg aes_ce_cipher snd_hda_codec ghash_ce gf128mul libaes sha2_ce snd_hda_core snd_hwdep snd_pcm sha256_arm64 sha1_ce snd_timer evdev snd soundcore sg efi_pstore omap_rng rng_core sbsa_gwdt armada_thermal fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod hid_generic usbhid hid sd_mod t10_pi crc_t10dif crct10dif_generic nouveau i2c_mux_pca954x i2c_mux ahci_platform libahci_platform libahci marvell10g libata crct10dif_ce [ 441.529194] crct10dif_common scsi_mod i2c_algo_bit ttm xhci_plat_hcd drm_kms_helper marvell xhci_hcd drm mvpp2 usbcore i2c_mv64xxx mvmdio mdio_devres sfp mdio_i2c phylink of_mdio phy_generic fixed_phy libphy sdhci_xenon_driver sdhci_pltfm usb_common phy_mvebu_cp110_comphy fixed sdhci [ 441.529236] CPU: 1 PID: 1964 Comm: kworker/1:0 Not tainted 5.10.0-3-arm64 #1 Debian 5.10.13-1 [ 441.529238] Hardware name: SolidRun Armada 8040 MacchiatoBin/Armada 8040 MacchiatoBin, BIOS EDK II Mar 26 2020 [ 441.529284] Workqueue: events nouveau_cli_work [nouveau] [ 441.529289] pstate: 6005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 441.529332] pc : nvif_vmm_put+0x84/0x9c [nouveau] [ 441.529375] lr : nvif_vmm_put+0x78/0x9c [nouveau] [ 441.529376] sp : 8000119cbc80 [ 441.529378] x29: 8000119cbc80 x28: · [ 441.529383] x27: 386ac5329f28 x26: 0001· [ 441.529387] x25: dead0100 x24: dead0122· [ 441.529391] x23: 386ac5329f18 x22: 386ac5077300· [ 441.529395] x21: 386ac5329f08 x20: 386ac2b00080· [ 441.529398] x19: 8000119cbce8 x18: · [ 441.529402] x17: x16: bbff1d518580· [ 441.529406] x15: x14: · [ 441.529410] x13: x12: 0040· [ 441.529414] x11: bbff1dcf5ec0 x10: 0ad0· [ 441.529417] x9 : bbfea5a3d3f0 x8 : fefefefefefefeff· [ 441.529421] x7 : 8888 x6 : 8000119cbcb8· [ 441.529425] x5 : x4 : 0008· [ 441.529429] x3 : 048a x2 : · [ 441.529433] x1 : x0 : fffe· [ 441.529437] Call trace: [ 441.529480] nvif_vmm_put+0x84/0x9c [nouveau] [ 441.529523] nouveau_vma_del+0x9c/0xe0 [nouveau] [ 441.529565] nouveau_gem_object_delete_work+0x48/0x80 [nouveau] [ 441.529607] nouveau_cli_work+0xe8/0x180 [nouveau] [ 441.529616] process_one_work+0x1d4/0x490 [ 441.529619] worker_thread+0x188/0x504 [ 441.529622] kthread+0x130/0x134 [ 441.529625] ret_from_fork+0x10/0x38 [ 441.529628] ---[ end trace 28675099a596659e ]--- :set nonumber Best regards Heinrich
Bug#983034: plasma-workspace-wayland: hanging in ksplashqml
Package: plasma-workspace-wayland Version: 4:5.20.5-3 Severity: grave Dear Maintainer, from SDDM I try to start a Wayland KDE session. The whole GUI freezes. CTRL-ALT-FN2 cannot be used to open a terminal session. SSH login is still possible. Top reports 100 % CPU load for ksplashqml. Mainboard is MacchiatoBIN with 16 GiB RAM. Video card is GeForce GT 710 with nouveau driver. Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-3-arm64 root=UUID= ro quiet The problem only occurs in Wayland sessions. X11 KDE is working fine. Best regards Heinrich Schuchardt -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-3-arm64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace-wayland depends on: ii kwayland-integration 5.20.5-1 ii kwin-wayland 4:5.20.5-1 ii libc6 2.31-9 ii libkf5configcore5 5.78.0-4 ii libkf5coreaddons5 5.78.0-2 ii libkworkspace5-5 4:5.20.5-3 ii libqt5core5a 5.15.2+dfsg-4 ii libqt5dbus5 5.15.2+dfsg-4 ii libstdc++610.2.1-6 ii plasma-workspace 4:5.20.5-3 ii qtwayland55.15.2-2 plasma-workspace-wayland recommends no packages. plasma-workspace-wayland suggests no packages. -- no debconf information
Bug#980085: open-iscsi: initiator does not connect
On 2/7/21 8:36 PM, Chris Hofstaedtler wrote: Hello Heinrich, I'm going to upload upstream's fix. Maybe you can give it a try. Best, Chris Debian release 2.1.3-2 added +upstream/0001-iscsiadm-Fix-memory-leak-in-iscsiadm.patch +upstream/0002-Fix-iscsiadm-segfault-when-exiting.patch +upstream/0003-Fix-iscsistart-login-issue-when-target-is-delayed.patch I have built the package from https://salsa.debian.org/linux-blocks-team/open-iscsi commit 7334ed475e26b8 This works for me but still shows the warning iscsistart: initiator reported error (15 - session exists) Tested-by: Heinrich Schuchardt
Bug#975705: marked as pending in cura
https://salsa.debian.org/3dprinting-team/cura/-/commit/871fcb258aa11077c3a6e16651fbcb44953e932e did not build cf. https://salsa.debian.org/3dprinting-team/cura/-/pipelines/205268 Best regards Heinrich
Bug#958497: geoclue-2.0 violates GDPR
Package: geoclue-2.0 Version: 2.5.6-1 Severity: serious The geoclue package collects SSIDs in the neighborhood and sends them to Mozilla location services. The SSID of an adhoc network (which for instance is set up for tethering via a mobile phone) is personally identifiable information. Sending this information about a third person without his or her explicit consent to another party especially one outside of the European Union is in breach of the German law Datenschutz-Grundverordnung which is the German implementation of the European General Data Protection Regulation (GDPR). The easiest remedy would be to remove the package from the repository until it is fixed upstream to be compliant. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924516 src/gclue-config.c:219: #define DEFAULT_WIFI_URL "https://location.services.mozilla.com/v1/geolocate?key=; MOZILLA_API_KEY #define DEFAULT_WIFI_SUBMIT_URL "https://location.services.mozilla.com/v1/submit?key=; MOZILLA_API_KEY Best regards Heinrich Schuchardt
Bug#949834: firefox-esr: illegal instruction in /usr/lib/firefox-esr/libxul.so
Package: firefox-esr Version: 68.4.1esr-1 Severity: critical Dear maintainer: Firefox cannot be started due to an illegal instruction: $ firefox-esr -safe-mode illegal instruction valgrind /usr/bin/firefox-essr -safe-mode ... ==2805== ==2805== Invalid free() / delete / delete[] / realloc() ==2805==at 0x4849FE0: free (vg_replace_malloc.c:540) ==2805==by 0x7E0D9F7: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x7627F37: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x76281DB: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA567F0F: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA569227: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA6FD98B: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA6FDF6F: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xA6FE477: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x10E957: ??? (in /usr/lib/firefox-esr/firefox-esr) ==2805==by 0x10E09B: ??? (in /usr/lib/firefox-esr/firefox-esr) ==2805==by 0x4AE72EB: (below main) (libc-start.c:308) ==2805== Address 0x1ba65820 is in a rw- anonymous segment ==2805== disInstr(arm64): unhandled instruction 0x disInstr(arm64): ' ' ' ' ==2805== valgrind: Unrecognised instruction at address 0xa5681f0. ==2805==at 0xA5681F0: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805== Your program just tried to execute an instruction that Valgrind ==2805== did not recognise. There are two possible reasons for this. ==2805== 1. Your program has a bug and erroneously jumped to a non-code ==2805==location. If you are running Memcheck and you just saw a ==2805==warning about a bad jump, it's probably your program's fault. ==2805== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2805==i.e. it's Valgrind's fault. If you think this is the case or ==2805==you are not sure, please let us know and we'll try to fix it. ==2805== Either way, Valgrind will now raise a SIGILL signal which will ==2805== probably kill your program. ==2805== ==2805== Process terminating with default action of signal 4 (SIGILL) ==2805==at 0x48934AC: raise (raise.c:46) ==2805==by 0xA6ED42B: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0xAEBD00F: ??? (in /usr/lib/firefox-esr/libxul.so) ==2805==by 0x580CAC8F: ??? (in /usr/lib/aarch64-linux-gnu/valgrind/memcheck-arm64-linux) ==2805== ==2805== HEAP SUMMARY: ==2805== in use at exit: 13,138,636 bytes in 66,191 blocks ==2805== total heap usage: 329,160 allocs, 285,076 frees, 48,657,728 bytes allocated ==2805== ==2805== LEAK SUMMARY: ==2805==definitely lost: 6,015 bytes in 94 blocks ==2805==indirectly lost: 36,096 bytes in 1,025 blocks ==2805== possibly lost: 1,570,965 bytes in 14,699 blocks ==2805==still reachable: 11,374,992 bytes in 49,176 blocks ==2805== of which reachable via heuristic: ==2805== length64 : 7,048 bytes in 106 blocks ==2805== newarray : 48,856 bytes in 816 blocks ==2805== multipleinheritance: 3,560 bytes in 8 blocks ==2805== suppressed: 0 bytes in 0 blocks ==2805== Rerun with --leak-check=full to see details of leaked memory ==2805== ==2805== For lists of detected and suppressed errors, rerun with: -s ==2805== ERROR SUMMARY: 22326 errors from 305 contexts (suppressed: 0 from 0) Illegal instruction -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.4.0-3-arm64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox-esr depends on: ii debianutils 4.9.1 ii fontconfig2.13.1-2+b1 ii libasound21.2.1.2-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-9 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-2 0.110-5 ii libevent-2.1-72.1.11-stable-1 ii libffi6 3.2.1-9 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc1 1:9.2.1-22 ii libgdk-pixbuf2.0-02.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1 ii libgtk-3-03.24.13-1 ii libjsoncpp1 1.7.4-3+b1 ii libnspr4 2:4.24-1 ii libnss3 2:3.45-1 ii libpango-1.0-01.42.4-7 ii libsqlite3-0 3.30.1+fossil191229-1 ii libstartup-notification0 0.12-6 ii libstdc++69.2.1-22 ii libx11-6 2:1.6.8-1 ii libx11-xcb1 2:1.6.8-1 ii
Bug#945001: grub-efi-amd64: GRUB-EFI messes up boot variables
Package: grub-efi-amd64
Version: 2.04-4
Severity: critical
Dear Maintainer,
I have multiple disk with different operating systems each with its own
bootloader.
Updating GRUB delete all existing UEFI variables BOOT and put in
some values that do not make any sense for my system. I had a lot of
trouble to get my system running again.
As this "makes unrelated software on the system (or the whole system)
break" I mark this error as critical.
One of the deleted entries was my second instance of Debian Buster
installed on device /dev/sda. GRUB did neither create a BOOT
variable for it nor did it add an entry to grub.conf.
I do not expect GRUB to ever touch my UEFI variables without my explicit
consent. Please, provide a dialogue.
Bug report 913916 seems to be related but I am not sure if it is
reporting the same issue.
Best regards
Heinrich Schuchardt
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/LVM1-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot ext2 rw,relatime 0 0
/dev/mapper/LVM1-home /home ext4 rw,relatime 0 0
/dev/nvme0n1p1 /boot/efi vfat
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod lvm
insmod ext2
set
root='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
b7e77dc3-85a0-4768-b18f-2774d561e90b
else
search --no-floppy --fs-uuid --set=root
b7e77dc3-85a0-4768-b18f-2774d561e90b
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod lvm
insmod ext2
set
root='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/z7Vz2e-hUSn-2wTk-3QEB-n2Eu-642O-EFG8XU/GuEKrb-SY50-1B2I-zLFX-pZef-iGBh-joFZ5o'
b7e77dc3-85a0-4768-b18f-2774d561e90b
else
search --no-floppy --fs-uuid --set=root
b7e77dc3-85a0-4768-b18f-2774d561e90b
fi
insmod png
if background_image
/usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-simple-b7e77dc3-85a0-4768-b18f-2774d561e90b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
1a42361e-b451-4f35-8bcc-4af14900c379
else
search --no-floppy --fs-uuid --set=root
1a42361e-b451-4f35-8bcc-4a
Bug#941231: u-boot-imx: mx6cuboxi fails to boot
The discussion lead to the following merged upstream patches: [1] - https://patchwork.ozlabs.org/patch/1173314/ [2] - https://patchwork.ozlabs.org/patch/1173316/ Best regards Heinrich
Bug#919029: grub-pc forgets installation device
> On Sat, Jan 12, 2019 at 02:11:25PM +0100, Vincent Lefevre wrote: > I'm not at all sure that I agree. The configuration in question exists > in order to tell the postinst which devices it should run grub-install > on. If the device does not exist, it obviously isn't possible to run > grub-install on it. Just to be very specific. The dialogue is shown without any change to installed drives or partitions. The problem is that grub-pc simply forgets where it is installed. Best regards Heinrich
Bug#908557: [RESOLVED] Error while setting the maximum protocol version
The issue was resolved with libqt5network5_5.11.1+dfsg-8_amd64.deb
Bug#888403: U-Boot: efi_loader: fix building crt0 on arm
U-Boot v2018.03-rc2 contains the following correction: efi_loader: fix building crt0 on arm http://git.denx.de/?p=u-boot.git;a=commit;h=268ec6e00e57497b96ebd4a5a5dc60b821e13fb0
Bug#888403: Fwd: [PATCH 1/1] efi_loader: fix building crt0 on arm
Forwarded Message
Subject: [PATCH 1/1] efi_loader: fix building crt0 on arm
Date: Wed, 31 Jan 2018 18:45:35 +
From: Heinrich Schuchardt <xypron.g...@gmx.de>
To: Alexander Graf <ag...@suse.de>
Before the patch an undefined constant EFI_SUBSYSTEM was used in the
crt0 code. The current version of binutils does not swallow the error.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888403
The necessary constant IMAGE_SUBSYSTEM_EFI_APPLICATION is already
defined in pe.h. So let's factor out asm-generic/pe.h for the
image subsystem constants and use it in our assembler code.
IMAGE_SUBSYSTEM_SAL_RUNTIME_DRIVER does not exist in the specification
let's use IMAGE_SUBSYSTEM_EFI_ROM instead.
The include pe.h is only used in code maintained by Alex so let him be the
maintainer here too.
Reported-by: Andre Przywara <andre.przyw...@arm.com>
Cc: Alexander Graf <ag...@suse.de>
Signed-off-by: Heinrich Schuchardt <xypron.g...@gmx.de>
---
MAINTAINERS | 2 ++
arch/arm/lib/crt0_aarch64_efi.S | 4 +++-
arch/arm/lib/crt0_arm_efi.S | 4 +++-
include/asm-generic/pe.h | 21 +
include/pe.h | 8 ++--
lib/efi_loader/efi_image_loader.c | 2 +-
6 files changed, 32 insertions(+), 9 deletions(-)
create mode 100644 include/asm-generic/pe.h
diff --git a/MAINTAINERS b/MAINTAINERS
index 0aecc18a6c..879b41c97e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -291,6 +291,8 @@ S: Maintained
T: git git://github.com/agraf/u-boot.git
F: doc/README.iscsi
F: include/efi*
+F: include/pe.h
+F: include/asm-generic/pe.h
F: lib/efi*/
F: test/py/tests/test_efi*
F: cmd/bootefi.c
diff --git a/arch/arm/lib/crt0_aarch64_efi.S
b/arch/arm/lib/crt0_aarch64_efi.S
index 52056469be..9b0e894f8a 100644
--- a/arch/arm/lib/crt0_aarch64_efi.S
+++ b/arch/arm/lib/crt0_aarch64_efi.S
@@ -8,6 +8,8 @@
* This file is taken and modified from the gnu-efi project.
*/
+#include
+
.section.text.head
/*
@@ -62,7 +64,7 @@ extra_header_fields:
*/
.long _start - ImageBase /* SizeOfHeaders */
.long 0 /* CheckSum */
- .short EFI_SUBSYSTEM /* Subsystem */
+ .short IMAGE_SUBSYSTEM_EFI_APPLICATION /* Subsystem */
.short 0 /* DllCharacteristics */
.quad 0 /* SizeOfStackReserve */
.quad 0 /* SizeOfStackCommit */
diff --git a/arch/arm/lib/crt0_arm_efi.S b/arch/arm/lib/crt0_arm_efi.S
index 967c885982..af55bba4ba 100644
--- a/arch/arm/lib/crt0_arm_efi.S
+++ b/arch/arm/lib/crt0_arm_efi.S
@@ -8,6 +8,8 @@
* This file is taken and modified from the gnu-efi project.
*/
+#include
+
.section.text.head
/*
@@ -64,7 +66,7 @@ extra_header_fields:
*/
.long _start - image_base /* SizeOfHeaders */
.long 0 /* CheckSum */
- .short EFI_SUBSYSTEM /* Subsystem */
+ .short IMAGE_SUBSYSTEM_EFI_APPLICATION /* Subsystem */
.short 0 /* DllCharacteristics */
.long 0 /* SizeOfStackReserve */
.long 0 /* SizeOfStackCommit */
diff --git a/include/asm-generic/pe.h b/include/asm-generic/pe.h
new file mode 100644
index 00..d1683f238a
--- /dev/null
+++ b/include/asm-generic/pe.h
@@ -0,0 +1,21 @@
+/*
+ * Portable Executable and Common Object Constants
+ *
+ * Copyright (c) 2018 Heinrich Schuchardt
+ *
+ * based on the "Microsoft Portable Executable and Common Object File
Format
+ * Specification", revision 11, 2017-01-23
+ *
+ * SPDX-License-Identifier: GPL-2.0+
+ */
+
+#ifndef _ASM_PE_H
+#define _ASM_PE_H
+
+/* Subsystem type */
+#define IMAGE_SUBSYSTEM_EFI_APPLICATION10
+#define IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER11
+#define IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER 12
+#define IMAGE_SUBSYSTEM_EFI_ROM13
+
+#endif /* _ASM_PE_H */
diff --git a/include/pe.h b/include/pe.h
index 4ef3e92efa..c3a19cef76 100644
--- a/include/pe.h
+++ b/include/pe.h
@@ -11,6 +11,8 @@
#ifndef _PE_H
#define _PE_H
+#include
+
typedef struct _IMAGE_DOS_HEADER {
uint16_t e_magic; /* 00: MZ Header signature */
uint16_t e_cblp;/* 02: Bytes on last page of file */
@@ -62,12 +64,6 @@ typedef struct _IMAGE_DATA_DIRECTORY {
#define IMAGE_NUMBEROF_DIRECTORY_ENTRIES 16
-/* PE32+ Subsystem type for EFI images */
-#define IMAGE_SUBSYSTEM_EFI_APPLICATION 10
-#define IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER 11
-#define IMAGE_SUBSYSTEM_EFI_RUNTIME_DRIVER 12
-#define IMAGE_SUBSYSTEM_SAL_RUNTIME_DRIVER 13
-
typedef struct _IMAGE_OPTIONAL_HEADER64 {
uin
Bug#815853: Cannot modprobe due to wrong kernel version string
The error was caused by the system not using the kernel installed in /boot but reading it from /dev/mmcblk0p1. Please, close the message. Best regards Heinrich Schuchardt
Bug#815853: Cannot modprobe due to wrong kernel version string
Package: linux-image-3.16.0-4-armmp-lpae Version: 3.16.7-ckt20-1+deb8u2 Severity: grave The package installs modules in /lib/modules/3.16.0-4-armmp-lpae but uname -r returns 3.16.0-4-armmp This means that modules cannot be loaded, e.g. $ sudo modprobe nls_cp437 modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/3.16.0-4-armmp/modules.dep.bin' For lpae kernels append -lpae to the kernel version string. Best regards Heinrich Schuchardt
Bug#740942: samba: now samba is not started at reboot at all
Disabling Samba cannot be the solution. If you mask samba.service you have to provide another solution to start Samba (smbd, nmbd, ...). Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745214: libglpk-java (1.0.33-1) does not build on Mips and PowerPC
Package: libglpk-java Version: 1.0.33-1 Severity: serious Justification: no longer builds from source On big endian systems memory addresses are not passed correctly to the JNI interface. This leads to a failure in make check: caught unhandled signal 11. I have corrected the error in upstream version 1.0.34. Please, package the new upstream version. Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
