Bug#808246: Should almost certainly be unmerged
I just tried building and installing binutils from sid on jessie, and then building a kernel module for the current kernel on the machine. Module built with binutils from jessie loads fine, modules built with binutils from sid has the mcount symbol error. So I would agree, these two bugs do not appear to be the same even though they seem to have appeared at the same time (both are triggered by changes in binutils, but not the same change most likely). The ppc64le does look like the missing weak symbols are the problem, and powerpc64 seems to be something else (since the powerpc64 kernel never had the symbol that ppc64le says it can't find). -- Len Sorensen
[PATCH initramfs-tools 2/4] scripts/local: Name parameters to local_device_setup
Using $1 and $2 in a function of this length isn't good practice. Signed-off-by: Ben Hutchings--- scripts/local | 21 - 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/scripts/local b/scripts/local index 7ae9117..2631df0 100644 --- a/scripts/local +++ b/scripts/local @@ -42,6 +42,9 @@ local_bottom() # $2=optionname (for root and etc) local_device_setup() { + local dev="$1" + local name="$2" + wait_for_udev 10 # Load ubi with the correct MTD partition and return since fstype @@ -53,7 +56,7 @@ local_device_setup() # Don't wait for a root device that doesn't have a corresponding # device in /dev (ie, mtd0) - if [ "${1#/dev}" = "$1" ]; then + if [ "${dev#/dev}" = "${dev}" ]; then return fi @@ -61,8 +64,8 @@ local_device_setup() # to allow for asynchronous device discovery (e.g. USB). We # also need to keep invoking the local-block scripts in case # there are devices stacked on top of those. - if [ ! -e "$1" ] || ! $(get_fstype "$1" >/dev/null); then - log_begin_msg "Waiting for $2 file system" + if [ ! -e "${dev}" ] || ! $(get_fstype "${dev}" >/dev/null); then + log_begin_msg "Waiting for ${name} file system" # Timeout is max(30, rootdelay) seconds (approximately) slumber=30 @@ -72,8 +75,8 @@ local_device_setup() while true; do sleep 1 - local_block "$1" - if [ -e "$1" ] && get_fstype "$1" >/dev/null; then + local_block "${dev}" + if [ -e "${dev}" ] && get_fstype "${dev}" >/dev/null; then wait_for_udev 10 log_end_msg 0 break @@ -87,15 +90,15 @@ local_device_setup() fi # We've given up, but we'll let the user fix matters if they can - while [ ! -e "$1" ]; do - echo "Gave up waiting for $2 device. Common problems:" + while [ ! -e "${dev}" ]; do + echo "Gave up waiting for ${name} device. Common problems:" echo " - Boot args (cat /proc/cmdline)" echo " - Check rootdelay= (did the system wait long enough?)" - if [ "$2" = root ]; then + if [ "${name}" = root ]; then echo " - Check root= (did the system wait for the right device?)" fi echo " - Missing modules (cat /proc/modules; ls /dev)" - panic "ALERT! $1 does not exist. Dropping to a shell!" + panic "ALERT! ${dev} does not exist. Dropping to a shell!" done } signature.asc Description: Digital signature
[PATCH initramfs-tools 1/4] scripts/local: Remove residual support for separate /etc filesystem
Signed-off-by: Ben Hutchings--- scripts/local | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/scripts/local b/scripts/local index 0f1d5b9..7ae9117 100644 --- a/scripts/local +++ b/scripts/local @@ -91,9 +91,8 @@ local_device_setup() echo "Gave up waiting for $2 device. Common problems:" echo " - Boot args (cat /proc/cmdline)" echo " - Check rootdelay= (did the system wait long enough?)" - # Only applies to root= and etc=: - if [ "${2#/}" = "$2" ]; then - echo " - Check $2= (did the system wait for the right device?)" + if [ "$2" = root ]; then + echo " - Check root= (did the system wait for the right device?)" fi echo " - Missing modules (cat /proc/modules; ls /dev)" panic "ALERT! $1 does not exist. Dropping to a shell!" signature.asc Description: Digital signature
Re: [PATCH initramfs-tools 0/4] Fix resolution of device IDs
On Tue, 2015-12-22 at 21:41 +, Ben Hutchings wrote: > This series fixes a serious regression on the master branch caused by > using blkid directly to resolve device IDs. It also fixes an > earlier regression in version 0.117. As I didn't receive any review comments on previous patches, I'm not going to wait for them this time. Instead I will merge these and make a release straight away. Since there are so many changes since 0.120 I'll call this a release candidate (0.121~rc1 rather than 0.121). Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Bug#808792: firmware-iwlwifi: iwlwifi-7260-17.ucode is missing
Package: firmware-iwlwifi Version: 20151207-1 Severity: normal # dmesg | grep iwlwifi | head -5 [7.473576] iwlwifi :06:00.0: enabling device ( -> 0002) [7.475332] iwlwifi :06:00.0: firmware: failed to load iwlwifi-7260-17.ucode (-2) [7.475337] iwlwifi :06:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2 [7.479873] iwlwifi :06:00.0: firmware: direct-loading firmware iwlwifi-7260-16.ucode [7.480478] iwlwifi :06:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.120 -- no debconf information
Bug#808563: really should be serious bug: data loss
Rotational. watch outscrambled data fsck forced can't boot stay away...
Bug#808720:
I did just upgraded to linux-image-4.3.0-1-amd64 and can report the same thing I suppose. [4.910005] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_drrs (expected 1, found 0) [4.910007] [ cut here ] [4.910037] WARNING: CPU: 1 PID: 6 at /build/linux-s8yg92/linux-4.3.3/drivers/gpu/drm/i915/intel_display.c:12700 intel_atomic_commit+0xd7a/0x12f0 [i915]() [4.910037] pipe state doesn't match! [4.910069] Modules linked in: xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables x_tables br_netfilter nf_nat nf_conntrack bridge stp llc joydev btusb btrtl btbcm btintel bluetooth hp_wmi sparse_keymap hid_generic hid_multitouch intel_rapl iosf_mbi uvcvideo x86_pkg_temp_thermal videobuf2_vmalloc intel_powerclamp videobuf2_memops videobuf2_core coretemp v4l2_common videodev kvm_intel media kvm crct10dif_pclmul crc32_pclmul jitterentropy_rng sha256_ssse3 sha256_generic hmac efi_pstore drbg ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd evdev psmouse serio_raw pcspkr efivars usbhid hid dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c tpm_infineon arc4 loop dm_mod [4.910100] binfmt_misc iwlmvm mac80211 iwlwifi rtsx_pci_ms i2c_i801(+) cfg80211 snd_hda_codec_idt sg snd_hda_codec_generic memstick lpc_ich(+) rfkill mei_me mei wmi battery shpchp 8250_fintek i915(+) snd_hda_intel snd_hda_codec snd_hda_core intel_smartconnect snd_hwdep video hp_accel(+) snd_pcm drm_kms_helper lis3lv02d tpm_tis hp_wireless input_polldev snd_timer drm tpm snd ac soundcore i2c_algo_bit button processor parport_pc ppdev lp parport efivarfs autofs4 ext4 crc16 mbcache jbd2 sd_mod rtsx_pci_sdmmc mmc_core crc32c_intel ahci libahci libata xhci_pci rtsx_pci ehci_pci scsi_mod mfd_core ehci_hcd xhci_hcd e1000e ptp pps_core usbcore usb_common thermal [4.910102] CPU: 1 PID: 6 Comm: kworker/u16:0 Not tainted 4.3.0-1-amd64 #1 Debian 4.3.3-2 [4.910103] Hardware name: Hewlett-Packard HP EliteBook 840 G1/198F, BIOS L71 Ver. 01.21 09/03/2014 [4.910107] Workqueue: events_unbound async_run_entry_fn [4.910109] 4d803f94 812ddc89 88042c6cb988 [4.910111] 81072b1d 8804283c8c00 88042c6cb9e0 880427c1c000 [4.910112] 8800b241ba00 8800b244c000 81072bac a05722e2 [4.910112] Call Trace: [4.910119] [] ? dump_stack+0x40/0x57 [4.910121] [] ? warn_slowpath_common+0x7d/0xb0 [4.910123] [] ? warn_slowpath_fmt+0x5c/0x80 [4.910152] [] ? intel_atomic_commit+0xd7a/0x12f0 [i915] [4.910169] [] ? drm_atomic_check_only+0x214/0x540 [drm] [4.910176] [] ? drm_atomic_helper_set_config+0x1af/0x410 [drm_kms_helper] [4.910187] [] ? drm_mode_set_config_internal+0x5e/0xf0 [drm] [4.910193] [] ? restore_fbdev_mode+0xaa/0x110 [drm_kms_helper] [4.910199] [] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x20/0x60 [drm_kms_helper] [4.910204] [] ? drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper] [4.910232] [] ? intel_fbdev_set_par+0x16/0x60 [i915] [4.910234] [] ? fbcon_init+0x54d/0x5e0 [4.910237] [] ? visual_init+0xc3/0x120 [4.910239] [] ? do_bind_con_driver+0x1e3/0x3d0 [4.910240] [] ? do_take_over_console+0x13b/0x190 [4.910242] [] ? do_fbcon_takeover+0x53/0xb0 [4.910245] [] ? notifier_call_chain+0x45/0x70 [4.910248] [] ? __blocking_notifier_call_chain+0x41/0x60 [4.910250] [] ? register_framebuffer+0x20b/0x340 [4.910252] [] ? vga_switcheroo_client_fb_set+0x19/0x70 [4.910258] [] ? drm_fb_helper_initial_config+0x26c/0x420 [drm_kms_helper] [4.910260] [] ? async_run_entry_fn+0x45/0x130 [4.910262] [] ? process_one_work+0x19f/0x3d0 [4.910263] [] ? worker_thread+0x4d/0x450 [4.910264] [] ? process_one_work+0x3d0/0x3d0 [4.910266] [] ? kthread+0xcd/0xf0 [4.910269] [] ? kthread_create_on_node+0x190/0x190 [4.910272] [] ? ret_from_fork+0x3f/0x70 [4.910274] [] ? kthread_create_on_node+0x190/0x190 [4.910275] ---[ end trace 8b2f2a96e8705ef9 ]---
Processing of initramfs-tools_0.121~rc2_source.changes
initramfs-tools_0.121~rc2_source.changes uploaded successfully to localhost along with the files: initramfs-tools_0.121~rc2.dsc initramfs-tools_0.121~rc2.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
Processing of initramfs-tools_0.121~rc2_multi.changes
initramfs-tools_0.121~rc2_multi.changes uploaded successfully to localhost along with the files: initramfs-tools_0.121~rc2.dsc initramfs-tools_0.121~rc2.tar.xz initramfs-tools-core_0.121~rc2_all.deb initramfs-tools_0.121~rc2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
linux_3.2.73-2+deb7u1_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 14 Dec 2015 21:28:02 + Source: linux Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha linux-headers-3.2.0-4-common linux-image-3.2.0-4-alpha-generic linux-headers-3.2.0-4-alpha-generic linux-image-3.2.0-4-alpha-smp linux-headers-3.2.0-4-alpha-smp linux-image-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-alpha-legacy linux-headers-3.2.0-4-all-amd64 kernel-image-3.2.0-4-amd64-di nic-modules-3.2.0-4-amd64-di nic-extra-modules-3.2.0-4-amd64-di nic-wireless-modules-3.2.0-4-amd64-di nic-shared-modules-3.2.0-4-amd64-di serial-modules-3.2.0-4-amd64-di usb-serial-modules-3.2.0-4-amd64-di ppp-modules-3.2.0-4-amd64-di pata-modules-3.2.0-4-amd64-di cdrom-core-modules-3.2.0-4-amd64-di firewire-core-modules-3.2.0-4-amd64-di scsi-core-modules-3.2.0-4-amd64-di scsi-modules-3.2.0-4-amd64-di scsi-common-modules-3.2.0-4-amd64-di scsi-extra-modules-3.2.0-4-amd64-di plip-modules-3.2.0-4-amd64-di floppy-modules-3.2.0-4-amd64-di loop-modules-3.2.0-4-amd64-di btrfs-modules-3.2.0-4-amd64-di ext2-modules-3.2.0-4-amd64-di ext3-modules-3.2.0-4-amd64-di ext4-modules-3.2.0-4-amd64-di isofs-modules-3.2.0-4-amd64-di jfs-modules-3.2.0-4-amd64-di ntfs-modules-3.2.0-4-amd64-di reiserfs-modules-3.2.0-4-amd64-di xfs-modules-3.2.0-4-amd64-di fat-modules-3.2.0-4-amd64-di ufs-modules-3.2.0-4-amd64-di qnx4-modules-3.2.0-4-amd64-di md-modules-3.2.0-4-amd64-di multipath-modules-3.2.0-4-amd64-di usb-modules-3.2.0-4-amd64-di usb-storage-modules-3.2.0-4-amd64-di pcmcia-storage-modules-3.2.0-4-amd64-di fb-modules-3.2.0-4-amd64-di input-modules-3.2.0-4-amd64-di event-modules-3.2.0-4-amd64-di mouse-modules-3.2.0-4-amd64-di irda-modules-3.2.0-4-amd64-di parport-modules-3.2.0-4-amd64-di nic-pcmcia-modules-3.2.0-4-amd64-di pcmcia-modules-3.2.0-4-amd64-di nic-usb-modules-3.2.0-4-amd64-di sata-modules-3.2.0-4-amd64-di core-modules-3.2.0-4-amd64-di acpi-modules-3.2.0-4-amd64-di i2c-modules-3.2.0-4-amd64-di crc-modules-3.2.0-4-amd64-di crypto-modules-3.2.0-4-amd64-di crypto-dm-modules-3.2.0-4-amd64-di efi-modules-3.2.0-4-amd64-di ata-modules-3.2.0-4-amd64-di mmc-core-modules-3.2.0-4-amd64-di mmc-modules-3.2.0-4-amd64-di nbd-modules-3.2.0-4-amd64-di squashfs-modules-3.2.0-4-amd64-di speakup-modules-3.2.0-4-amd64-di virtio-modules-3.2.0-4-amd64-di uinput-modules-3.2.0-4-amd64-di sound-modules-3.2.0-4-amd64-di zlib-modules-3.2.0-4-amd64-di hyperv-modules-3.2.0-4-amd64-di udf-modules-3.2.0-4-amd64-di fuse-modules-3.2.0-4-amd64-di linux-image-3.2.0-4-amd64 linux-headers-3.2.0-4-amd64 linux-image-3.2.0-4-amd64-dbg xen-linux-system-3.2.0-4-amd64 linux-headers-3.2.0-4-common-rt linux-image-3.2.0-4-rt-amd64 linux-headers-3.2.0-4-rt-amd64 linux-image-3.2.0-4-rt-amd64-dbg linux-headers-3.2.0-4-all-armel kernel-image-3.2.0-4-iop32x-di nic-modules-3.2.0-4-iop32x-di nic-shared-modules-3.2.0-4-iop32x-di usb-serial-modules-3.2.0-4-iop32x-di ppp-modules-3.2.0-4-iop32x-di pata-modules-3.2.0-4-iop32x-di cdrom-core-modules-3.2.0-4-iop32x-di scsi-core-modules-3.2.0-4-iop32x-di loop-modules-3.2.0-4-iop32x-di ipv6-modules-3.2.0-4-iop32x-di btrfs-modules-3.2.0-4-iop32x-di ext2-modules-3.2.0-4-iop32x-di ext3-modules-3.2.0-4-iop32x-di ext4-modules-3.2.0-4-iop32x-di isofs-modules-3.2.0-4-iop32x-di jffs2-modules-3.2.0-4-iop32x-di jfs-modules-3.2.0-4-iop32x-di reiserfs-modules-3.2.0-4-iop32x-di fat-modules-3.2.0-4-iop32x-di md-modules-3.2.0-4-iop32x-di multipath-modules-3.2.0-4-iop32x-di usb-modules-3.2.0-4-iop32x-di usb-storage-modules-3.2.0-4-iop32x-di event-modules-3.2.0-4-iop32x-di nic-usb-modules-3.2.0-4-iop32x-di sata-modules-3.2.0-4-iop32x-di core-modules-3.2.0-4-iop32x-di crc-modules-3.2.0-4-iop32x-di crypto-modules-3.2.0-4-iop32x-di crypto-dm-modules-3.2.0-4-iop32x-di ata-modules-3.2.0-4-iop32x-di nbd-modules-3.2.0-4-iop32x-di squashfs-modules-3.2.0-4-iop32x-di zlib-modules-3.2.0-4-iop32x-di udf-modules-3.2.0-4-iop32x-di fuse-modules-3.2.0-4-iop32x-di kernel-image-3.2.0-4-kirkwood-di nic-modules-3.2.0-4-kirkwood-di nic-shared-modules-3.2.0-4-kirkwood-di usb-serial-modules-3.2.0-4-kirkwood-di ppp-modules-3.2.0-4-kirkwood-di cdrom-core-modules-3.2.0-4-kirkwood-di scsi-core-modules-3.2.0-4-kirkwood-di loop-modules-3.2.0-4-kirkwood-di ipv6-modules-3.2.0-4-kirkwood-di btrfs-modules-3.2.0-4-kirkwood-di ext2-modules-3.2.0-4-kirkwood-di ext3-modules-3.2.0-4-kirkwood-di ext4-modules-3.2.0-4-kirkwood-di isofs-modules-3.2.0-4-kirkwood-di jfs-modules-3.2.0-4-kirkwood-di reiserfs-modules-3.2.0-4-kirkwood-di fat-modules-3.2.0-4-kirkwood-di minix-modules-3.2.0-4-kirkwood-di md-modules-3.2.0-4-kirkwood-di multipath-modules-3.2.0-4-kirkwood-di usb-modules-3.2.0-4-kirkwood-di usb-storage-modules-3.2.0-4-kirkwood-di fb-modules-3.2.0-4-kirkwood-di input-modules-3.2.0-4-kirkwood-di event-modules-3.2.0-4-kirkwood-di
Bug#808246: Maybe the bugs are related
I found indications that perhaps both problems are in fact caused by ld no longer including undefined symbols in the output. Here is a section from the working module built with old binutils: 0012980: 0047 4343 3a20 2844 6562 6961 6e20 342e .GCC: (Debian 4. 0012990: 392e 322d 3130 2920 342e 392e 3200 0047 9.2-10) 4.9.2..G 00129a0: 4343 3a20 2844 6562 6961 6e20 342e 392e CC: (Debian 4.9. 00129b0: 322d 3130 2920 342e 392e 3200 0047 4343 2-10) 4.9.2..GCC 00129c0: 3a20 2844 6562 6961 6e20 342e 392e 322d : (Debian 4.9.2- 00129d0: 3130 2920 342e 392e 3200 0047 4343 3a20 10) 4.9.2..GCC: 00129e0: 2844 6562 6961 6e20 342e 392e 322d 3130 (Debian 4.9.2-10 00129f0: 2920 342e 392e 3200 0047 4343 3a20 2844 ) 4.9.2..GCC: (D 0012a00: 6562 6961 6e20 342e 392e 322d 3130 2920 ebian 4.9.2-10) 0012a10: 342e 392e 3200 0047 4343 3a20 2844 6562 4.9.2..GCC: (Deb 0012a20: 6961 6e20 342e 392e 322d 3130 2920 342e ian 4.9.2-10) 4. 0012a30: 392e 3200 0047 4343 3a20 2844 6562 6961 9.2..GCC: (Debia 0012a40: 6e20 342e 392e 322d 3130 2920 342e 392e n 4.9.2-10) 4.9. 0012a50: 3200 0047 4343 3a20 2844 6562 6961 6e20 2..GCC: (Debian 0012a60: 342e 392e 322d 3130 2920 342e 392e 3200 4.9.2-10) 4.9.2. 0012a70: 002e 7379 6d74 6162 002e 7374 7274 6162 ..symtab..strtab 0012a80: 002e 7368 7374 7274 6162 002e 6e6f 7465 ..shstrtab..note 0012a90: 2e67 6e75 2e62 7569 6c64 2d69 6400 2e72 .gnu.build-id..r 0012aa0: 656c 612e 7465 7874 002e 7265 6c61 2e69 ela.text..rela.i 0012ab0: 6e69 742e 7465 7874 002e 7265 6c61 2e66 nit.text..rela.f 0012ac0: 6978 7570 002e 7265 6c61 2e65 7869 742e ixup..rela.exit. 0012ad0: 7465 7874 002e 7265 6c61 2e74 6578 742e text..rela.text. 0012ae0: 756e 6c69 6b65 6c79 002e 7265 6c61 5f5f unlikely..rela__ 0012af0: 6b73 796d 7461 625f 6770 6c00 2e72 656c ksymtab_gpl..rel 0012b00: 612e 726f 6461 7461 002e 7265 6c61 5f5f a.rodata..rela__ 0012b10: 6275 675f 7461 626c 6500 2e72 6f64 6174 bug_table..rodat 0012b20: 612e 7374 7231 2e38 002e 7265 6c61 5f5f a.str1.8..rela__ 0012b30: 6d63 6f75 6e74 5f6c 6f63 002e 7265 6c61 mcount_loc..rela 0012b40: 5f5f 6578 5f74 6162 6c65 005f 5f6b 7379 __ex_table.__ksy 0012b50: 6d74 6162 5f73 7472 696e 6773 002e 6d6f mtab_strings..mo 0012b60: 6469 6e66 6f00 5f5f 7665 7273 696f 6e73 dinfo.__versions 0012b70: 002e 7265 6c61 5f5f 6b63 7263 7461 625f ..rela__kcrctab_ 0012b80: 6770 6c00 2e72 656c 612e 6461 7461 002e gpl..rela.data.. 0012b90: 7265 6c61 2e64 6174 612e 7265 6c2e 726f rela.data.rel.ro 0012ba0: 002e 7265 6c61 2e6f 7064 002e 7265 6c61 ..rela.opd..rela 0012bb0: 2e74 6f63 002e 7265 6c61 2e67 6e75 2e6c .toc..rela.gnu.l 0012bc0: 696e 6b6f 6e63 652e 7468 6973 5f6d 6f64 inkonce.this_mod 0012bd0: 756c 6500 2e62 7373 002e 7374 7562 7300 ule..bss..stubs. 0012be0: 2e66 7472 6163 652e 7472 616d 7000 2e63 .ftrace.tramp..c 0012bf0: 6f6d 6d65 6e74 omment.. And the same section from the new binutils build (the disassenmbled module is totally identical as far as code is concerned): 0012980: 0047 4343 3a20 2844 6562 6961 6e20 342e .GCC: (Debian 4. 0012990: 392e 322d 3130 2920 342e 392e 3200 0047 9.2-10) 4.9.2..G 00129a0: 4343 3a20 2844 6562 6961 6e20 342e 392e CC: (Debian 4.9. 00129b0: 322d 3130 2920 342e 392e 3200 0047 4343 2-10) 4.9.2..GCC 00129c0: 3a20 2844 6562 6961 6e20 342e 392e 322d : (Debian 4.9.2- 00129d0: 3130 2920 342e 392e 3200 0047 4343 3a20 10) 4.9.2..GCC: 00129e0: 2844 6562 6961 6e20 342e 392e 322d 3130 (Debian 4.9.2-10 00129f0: 2920 342e 392e 3200 0047 4343 3a20 2844 ) 4.9.2..GCC: (D 0012a00: 6562 6961 6e20 342e 392e 322d 3130 2920 ebian 4.9.2-10) 0012a10: 342e 392e 3200 0047 4343 3a20 2844 6562 4.9.2..GCC: (Deb 0012a20: 6961 6e20 342e 392e 322d 3130 2920 342e ian 4.9.2-10) 4. 0012a30: 392e 3200 0047 4343 3a20 2844 6562 6961 9.2..GCC: (Debia 0012a40: 6e20 342e 392e 322d 3130 2920 342e 392e n 4.9.2-10) 4.9. 0012a50: 3200 0047 4343 3a20 2844 6562 6961 6e20 2..GCC: (Debian 0012a60: 342e 392e 322d 3130 2920 342e 392e 3200 4.9.2-10) 4.9.2. 0012a70: 0012a80: 0300 0001 0012a90: So some stuff was dropped by the new binutils, just like it was from vmlinux on ppc64el, and that could very well be what the module loading code was looking for. I can't find any way to undo this change to ld about dropping undefined symbols from the output. -- Len Sorensen
Processed: unmerging 808246
Processing commands for cont...@bugs.debian.org: > unmerge 808246 Bug #808246 [src:linux] Stretch fails to install on OpenPOWER systems Bug #808043 [src:linux] [powerpc] Modules fail to load following toolchain upgrade Disconnected #808246 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 808043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808043 808246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[PATCH initramfs-tools 4/4] scripts/functions: Stop resolving symlinks in resolve_device
Now that we use blkid directly, there is no need to resolve /dev/disk symlinks. We shouldn't resolve any other symlinks we're given either, as this causes /proc/mounts to be inconsistent with /etc/fstab. Closes: #791754 Signed-off-by: Ben Hutchings--- scripts/functions | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/scripts/functions b/scripts/functions index 5916a94..499a430 100644 --- a/scripts/functions +++ b/scripts/functions @@ -307,8 +307,7 @@ resolve_device() { fi ;; esac - [ -e "$DEV" ] || return 1 - readlink -f "$DEV" + [ -e "$DEV" ] && echo "$DEV" } # Check a file system. signature.asc Description: Digital signature
[PATCH initramfs-tools 3/4] Defer resolving block device IDs to local_device_setup
Since we now invoke blkid to resolve block device IDs rather than relying on symlinks under /dev/disk, resolve_device just doesn't work until the specified device exists. So we need to use it in the multiple existence checks in local_device_setup, and nowhere else. Signed-off-by: Ben Hutchings--- init | 1 - scripts/functions | 8 scripts/local | 37 ++--- 3 files changed, 26 insertions(+), 20 deletions(-) diff --git a/init b/init index 5a5123c..60e76c3 100755 --- a/init +++ b/init @@ -79,7 +79,6 @@ for x in $(cat /proc/cmdline); do ;; root=*) ROOT=${x#root=} - ROOT=$(resolve_device "$ROOT") if [ -z "${BOOT}" ] && [ "$ROOT" = "/dev/nfs" ]; then BOOT=nfs fi diff --git a/scripts/functions b/scripts/functions index 4ac898d..5916a94 100644 --- a/scripts/functions +++ b/scripts/functions @@ -300,15 +300,15 @@ resolve_device() { case "$DEV" in LABEL=* | UUID=* | PARTLABEL=* | PARTUUID=*) if command -v blkid >/dev/null 2>&1; then - DEV="$(blkid -l -t "$DEV" -o device)" + DEV="$(blkid -l -t "$DEV" -o device)" || return 1 else log_warning_msg "blkid not present, so cannot resolve $DEV" + return 1 fi ;; esac - # Only canonicalise if a valid file, in case $DEV isn't a filename - [ -e "$DEV" ] && DEV=$(readlink -f "$DEV") - echo "$DEV" + [ -e "$DEV" ] || return 1 + readlink -f "$DEV" } # Check a file system. diff --git a/scripts/local b/scripts/local index 2631df0..af56e66 100644 --- a/scripts/local +++ b/scripts/local @@ -38,12 +38,14 @@ local_bottom() local_top_used=no } -# $1=device to mount +# $1=device ID to mount # $2=optionname (for root and etc) +# Sets $DEV to the resolved device node local_device_setup() { - local dev="$1" + local dev_id="$1" local name="$2" + local real_dev wait_for_udev 10 @@ -51,12 +53,15 @@ local_device_setup() # doesn't work with a char device like ubi. if [ -n "$UBIMTD" ]; then modprobe ubi mtd=$UBIMTD + DEV="${dev_id}" return fi - # Don't wait for a root device that doesn't have a corresponding - # device in /dev (ie, mtd0) - if [ "${dev#/dev}" = "${dev}" ]; then + # Don't wait for a device that doesn't have a corresponding + # device in /dev and isn't resolvable by blkid (e.g. mtd0) + if [ "${dev_id#/dev}" = "${dev_id}" ] && + [ "${dev_id#*=}" = "${dev_id}" ]; then + DEV="${dev_id}" return fi @@ -64,7 +69,8 @@ local_device_setup() # to allow for asynchronous device discovery (e.g. USB). We # also need to keep invoking the local-block scripts in case # there are devices stacked on top of those. - if [ ! -e "${dev}" ] || ! $(get_fstype "${dev}" >/dev/null); then + if ! real_dev=$(resolve_device "${dev_id}") || + ! get_fstype "${real_dev}" >/dev/null; then log_begin_msg "Waiting for ${name} file system" # Timeout is max(30, rootdelay) seconds (approximately) @@ -75,8 +81,9 @@ local_device_setup() while true; do sleep 1 - local_block "${dev}" - if [ -e "${dev}" ] && get_fstype "${dev}" >/dev/null; then + local_block "${dev_id}" + if real_dev=$(resolve_device "${dev_id}") && + get_fstype "${real_dev}" >/dev/null; then wait_for_udev 10 log_end_msg 0 break @@ -90,7 +97,8 @@ local_device_setup() fi # We've given up, but we'll let the user fix matters if they can - while [ ! -e "${dev}" ]; do + while ! real_dev=$(resolve_device "${dev_id}") || + ! get_fstype "${real_dev}" >/dev/null; do echo "Gave up waiting for ${name} device. Common problems:" echo " - Boot args (cat /proc/cmdline)" echo " - Check rootdelay= (did the system wait long enough?)" @@ -98,14 +106,17 @@ local_device_setup() echo " - Check root= (did the system wait for the right device?)" fi echo " - Missing modules (cat /proc/modules; ls /dev)" - panic "ALERT! ${dev} does not exist. Dropping to a shell!" + panic "ALERT! ${dev_id} does not exist. Dropping to a shell!" done + + DEV="${real_dev}" } local_mount_root() { local_top local_device_setup "${ROOT}" root +
initramfs-tools_0.121~rc2_source.changes REJECTED
Source-only uploads to NEW are not allowed. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
[PATCH initramfs-tools 0/4] Fix resolution of device IDs
This series fixes a serious regression on the master branch caused by using blkid directly to resolve device IDs. It also fixes an earlier regression in version 0.117. Ben. Ben Hutchings (4): scripts/local: Remove residual support for separate /etc filesystem scripts/local: Name parameters to local_device_setup Defer resolving block device IDs to local_device_setup scripts/functions: Stop resolving symlinks in resolve_device init | 1 - scripts/functions | 7 +++ scripts/local | 47 --- 3 files changed, 31 insertions(+), 24 deletions(-) -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
initramfs-tools_0.121~rc2_multi.changes is NEW
binary:initramfs-tools-core is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html
Processed: tagging 808792
Processing commands for cont...@bugs.debian.org: > tags 808792 + upstream Bug #808792 [firmware-iwlwifi] firmware-iwlwifi: iwlwifi-7260-17.ucode is missing Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 808792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#808563: really should be serious bug: data loss
On 21/12/2015 17:20, 積丹尼 Dan Jacobson wrote: ata1.00: exception Emask 0x60 SAct 0x1c SErr 0x800 action 0x6 frozen ata1.00: irq_stat 0x2000, host bus error ata1: SError: { HostInt } ata1.00: failed command: WRITE FPDMA QUEUED ata1.00: cmd 61/00:10:00:a8:10/08:00:26:00:00/40 tag 2 ncq 1048576 out res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error) ata1.00: status: { DRDY } ata1.00: failed command: WRITE FPDMA QUEUED ata1.00: cmd 61/00:18:00:b0:10/08:00:26:00:00/40 tag 3 ncq 1048576 out res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error) ata1.00: status: { DRDY } ata1.00: failed command: WRITE FPDMA QUEUED ata1.00: cmd 61/98:20:00:48:11/03:00:26:00:00/40 tag 4 ncq 471040 out res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error) ata1.00: status: { DRDY } ata1: hard resetting link I have a RAID1 (mdadm) with two SSD Samsung 850 EVO and these days i was affected by the same problem with linux-image-4.3.0-1-686-pae (4.3.3-2). During these errors the system is somehow not responsive for about 30-60 seconds but at the end the operation completes and all keep working without error or data loss. Mdadm doesn't notice nothing about these errors: the RAID doesn't get degraded. But it's quite annoying because happens frequently: about one time every few minutes. An excerpt of my errors: - dic 22 09:14:26 barone kernel: ata1.00: exception Emask 0x0 SAct 0x700 SErr 0x0 action 0x6 frozen dic 22 09:14:26 barone kernel: ata1.00: failed command: WRITE FPDMA QUEUED dic 22 09:14:26 barone kernel: ata1.00: cmd 61/20:40:00:b8:76/07:00:01:00:00/40 tag 8 ncq 933888 out res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) dic 22 09:14:26 barone kernel: ata1.00: status: { DRDY } dic 22 09:14:26 barone kernel: ata1.00: failed command: WRITE FPDMA QUEUED dic 22 09:14:26 barone kernel: ata1.00: cmd 61/e0:48:20:bf:76/08:00:01:00:00/40 tag 9 ncq 1163264 out res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) dic 22 09:14:26 barone kernel: ata1.00: status: { DRDY } dic 22 09:14:26 barone kernel: ata1.00: failed command: WRITE FPDMA QUEUED dic 22 09:14:26 barone kernel: ata1.00: cmd 61/98:50:00:18:77/0e:00:01:00:00/40 tag 10 ncq 1912832 out res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) dic 22 09:14:26 barone kernel: ata1.00: status: { DRDY } dic 22 09:14:26 barone kernel: ata1: hard resetting link - Like you i have an 686-pae 32 bit kernel. Have you got an SSD disk or a rotational disk? This morning i've tried linux-image-4.4.0-rc5-686 (4.4~rc5-1~exp1) from experimental and everything works fine without errors. Tomorrow i'll try the pae version from experimental to see if it works too. Cesare.
Bug#808374: freeradius stopped working after kernel upgrade
I can confirm this. This bug hit us for Windows clients which suddenly could no longer authenticate via EAP-TLS or 802.1x. It seems that it has something to do with large UDP packets. Freeradius did no longer process UDP packets that were fragmented. This was also reported by someone else for the freeradius package as bug 808293. We tested the following versions: Affected: linux-image-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u1 linux-image-3.2.0-4-rt-amd64 3.2.73-2 Not affected: linux-image-3.2.0-4-rt-amd64 3.2.71-2 Regards Sebastian -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant
Bug#808246: Stretch fails to install on OpenPOWER systems
On 2015-12-17 11:51, Timothy Pearson wrote: > Package: linux-image-4.2.0-1-powerpc64le > Version: 4.2.6-3 > Severity: grave > > Using the latest debian-installer netboot kernel to install on an > OpenPOWER server; install proceeds normally until disk detection when it > fails stating no disks can be found. dmesg shows a slew of errors similar > to the following: > > fat: no symbol version for TOC. > fat: Unknown symbol TOC. (err -22) > ext4: no symbol version for TOC. > ext4: Unknown symbol TOC. (err -22) > ahci: no symbol version for TOC. > ahci: Unknown symbol TOC. (err -22) > > Forcibly loading the modules (modprobe --force ext4, etc.) and resuming > the installer allows the system to install normally, however the same > issue shows up on reboot. This causes a boot failure that cannot be > overridden as the modprobe version in the initramfs does not support the > force parameter. > > Jessie installs normally on the same system. The problem is that recent binutils versions strip undefined symbols from vmlinux. Normally a ppc64el kernel has the following undefined symbols: | 44809: 0 NOTYPE WEAK DEFAULT UND mach_powermac | 52870: 0 NOTYPE WEAK DEFAULT UND mach_chrp | 62021: 0 NOTYPE WEAK DEFAULT UND mach_cell | 62383: 0 NOTYPE WEAK DEFAULT UND __crc_TOC. However this is not the case anymore. This is due to the following change on the binutils side: | commit d983c8c5503d680c6d4955ceb610a9beebc64460 | Author: Alan Modra| Date: Wed Feb 18 17:02:39 2015 +1030 | | Strip undefined symbols from .symtab | | bfd/ | PR ld/4317 | * elflink.c (elf_link_input_bfd): Drop undefined local syms. | (elf_link_output_extsym): Drop local and global undefined syms. | Tidy. Expand comment. | ld/testsuite/ | PR ld/4317 | * ld-aarch64/gc-tls-relocs.d, * ld-cris/locref2.d, | * ld-elf/ehdr_start-weak.d, * ld-elf/group1.d, | * ld-i386/compressed1.d, * ld-ia64/error1.d, * ld-ia64/error2.d, | * ld-ia64/error3.d, * ld-mips-elf/pic-and-nonpic-1.nd, | * ld-mmix/undef-3.d, * ld-powerpc/tlsexe.r, * ld-powerpc/tlsexetoc.r, | * ld-powerpc/tlsso.r, * ld-powerpc/tlstocso.r, | * ld-x86-64/compressed1.d, * ld-x86-64/pie1.d: Update. I am not sure the powerpc and ppc64el are actually due to the same bug in binutils. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Freeradius/Kernel bug
Processing commands for cont...@bugs.debian.org: > affects 808293 + src:linux Bug #808293 [freeradius] freeradius stopped working after kernel upgrade Added indication that 808293 affects src:linux > affects 808374 + freeradius Bug #808374 [src:linux] linux-image-3.16.0-4-686-pae: FreeRADIUS EAP-TLS stopped working when kernel was updated Added indication that 808374 affects freeradius > -- Stopping processing here. Please contact me if you need assistance. -- 808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293 808374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#801925: Linux Null Pointer Dereference on boot
Hi, Same here, last working debian kernel is linux-image-4.1.0-2-amd64 . Kernel hangs on early boot, after a while it notices and drops to an initramfs shell, lacking a root device. I managed to capture de OOPS using the handy netconsole module (attached). > On second thought, it seems more likely that this issue probably was > _caused_ by that commit. The fix can be found in these two emails: > > http://marc.info/?l=linux-scsi=144185206825609=2 > http://marc.info/?l=linux-scsi=144185208525611=2 > > which have not been merged yet as far as I know even though they were > submitted back in September. Those patches do not fix the problem for me. I tested using debian/bin/test-patches from the Debian Linux source. Thanks, Alex [2.561223] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.561719] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [2.561775] ata2.00: supports DRM functions and may not be fully accessible [2.565750] ata2.00: disabling queued TRIM support [2.565758] ata2.00: ATA-9: Crucial_CT256M550SSD1, MU01, max UDMA/133 [2.565762] ata2.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [2.570661] ata2.00: supports DRM functions and may not be fully accessible [2.579029] ata2.00: configured for UDMA/133 [2.905416] ata4: SATA link down (SStatus 0 SControl 300) [2.910964] BUG: unable to handle kernel NULL pointer dereference at 0008 [2.911135] PGD 0 [2.911215] Modules linked in: sd_mod(+) crc32c_intel ahci libahci libata xhci_pci scsi_mod xhci_hcd i915 ehci_pci ehci_hcd sdhci_pci sdhci mmc_core i2c_algo_bit drm_kms_helper usbcore usb_common e1000e ptp drm pps_core wmi thermal video button [2.911552] Hardware name: Hewlett-Packard HP ProBook 6470b/179C, BIOS 68ICE Ver. F.45 10/07/2013 [2.911665] RIP: 0010:[] [] sd_resume+0xd/0x70 [sd_mod] [2.911731] RSP: 0018:8801390a3a60 EFLAGS: 00010246 [2.911818] RDX: 0001 RSI: 880139398168 RDI: 880139398168 [2.911918] R10: 81827b86 R11: 000e R12: a0019220 [2.912017] FS: 7fc6c2e168c0() GS:88013fac() knlGS: [2.912113] CR2: 0008 CR3: 0001390c7000 CR4: 001406e0 [2.912161] Stack: [2.912247] 81403aae 880139398168 a03f2a20 [2.912382] Call Trace: [2.912470] [] ? __rpm_callback+0x2e/0x70 [2.912519] [] ? scsi_autopm_put_device+0x20/0x20 [scsi_mod] [2.912619] [] ? scsi_autopm_put_device+0x20/0x20 [scsi_mod] [2.912744] [] ? __pm_runtime_resume+0x47/0x70 [2.912848] [] ? sd_probe+0x35/0x340 [sd_mod] [2.912959] [] ? __driver_attach+0x7b/0x80 [2.913064] [] ? bus_for_each_dev+0x67/0xb0 [2.913152] [] ? 0xa0024000 [2.913190] [] ? driver_register+0x57/0xc0 [2.913312] [] ? do_one_initcall+0xb2/0x200 [2.913417] [] ? load_module+0x2173/0x2780 [2.913504] [] ? kernel_read+0x4b/0x70 [2.913623] [] ? system_call_fast_compare_end+0xc/0x67 [2.914161] RIP [] sd_resume+0xd/0x70 [sd_mod] [2.914212] RSP [2.914239] CR2: 0008 [2.916695] ---[ end trace 6a25c092cd6e126d ]---