Bug#971696: linux-image-4.19.0-11-armmp: network hangs, oops in ath9k_htc after upgrade
Sascha Silbe writes: > since the last kernel update (from linux-image-armmp:armhf > 4.19+105+deb10u5 / linux-image-4.19.0-10-armmp 4.19.132-1 to > linux-image-armmp 4.19+105+deb10u6 / linux-image-4.19.0-11-armmp > 4.19.146-1) our BeagleBone Black systems with AR9271 based WLAN adapter > (ath9k_htc driver) print a kernel warning or oops during boot and all > network related system calls hang, breaking not just WLAN but also > ethernet: [...] > If there's a git repository I can *cross*-build from with reasonable > effort I can try git bisect. I was unable to reproduce this bug using a kernel cross-built from tag debian/4.19.146-1 in the repository https://salsa.debian.org/kernel-team/linux.git on a Buster amd64 host or a Stretch amd64 host. I used the config from the official kernel with only CONFIG_LOCALVERSION and CONFIG_SYSTEM_TRUSTED_KEYS changed. Is debian/4.19.146-1 the right tag for the kernel sources used by linux-image-4.19.0-11-armmp 4.19.146-1? If so, why does this bug only happen with the official package but not with one I built locally? One thing that seems odd is that the package built from tag debian/4.19.146-1 identifies itself as 4.19.87, not 4.19.146. Sascha signature.asc Description: PGP signature
Bug#971696: linux-image-4.19.0-11-armmp: network hangs, oops in ath9k_htc after upgrade
Package: src:linux Version: 4.19.146-1 Severity: important Dear Maintainer, since the last kernel update (from linux-image-armmp:armhf 4.19+105+deb10u5 / linux-image-4.19.0-10-armmp 4.19.132-1 to linux-image-armmp 4.19+105+deb10u6 / linux-image-4.19.0-11-armmp 4.19.146-1) our BeagleBone Black systems with AR9271 based WLAN adapter (ath9k_htc driver) print a kernel warning or oops during boot and all network related system calls hang, breaking not just WLAN but also ethernet: === Begin === root@mavis:~# ip addr [no output, just hanging] === End === Kernel oops (from one boot): === Begin === [ OK ] Started Network Manager Script Dispatcher Service. [ 40.785065] IPv6: ADDRCONF(NETDEV_UP): wlx6cfdb9aac04b: link is not ready [ 41.258639] [ cut here ] [ 41.263512] kernel BUG at mm/slub.c:294! [ 41.267603] Internal error: Oops - BUG: 0 [#1] SMP ARM [ 41.272962] Modules linked in: cmac bnep arc4 btusb btrtl btbcm btintel bluetooth drbg ansi_cprng evdev ath9k_htc ath9k_common ath9k_hw ath ecdh_generic mac80211 hid_generic cfg80211 usbhid snd_usb_audio snd_usbmidi_lib rfkill snd_hwdep hid snd_rawmidi snd_seq_device nls_ascii nls_cp437 vfat fat snd_soc_simple_card snd_soc_spdif_rx snd_soc_simple_card_utils omap_rng rng_core snd_soc_davinci_mcasp snd_soc_edma snd_soc_sdma snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer cppi41 snd at24 soundcore omap_wdt leds_gpio ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb smsc musb_dsps musb_hdrc udc_core davinci_mdio usbcore phy_am335x phy_generic phy_am335x_control ti_cpsw cpsw_ale cpsw_common davinci_cpdma omap_hsmmc musb_am335x tps65217 [ 41.343301] CPU: 0 PID: 301 Comm: NetworkManager Not tainted 4.19.0-11-armmp #1 Debian 4.19.146-1 [ 41.352549] Hardware name: Generic AM33XX (Flattened Device Tree) [ 41.358916] PC is at kfree+0x1b4/0x1f0 [ 41.362826] LR is at 0xda4af800 [ 41.366100] pc : []lr : []psr: 600f0013 [ 41.372630] sp : da061570 ip : dfd2389c fp : da06159c [ 41.378073] r10: 2878 r9 : cf178000 r8 : dd1d1900 [ 41.383518] r7 : cf07ce88 r6 : r5 : da4af800 r4 : c0991234 [ 41.390320] r3 : c112abb0 r2 : da4af800 r1 : 2a33 r0 : de001a00 [ 41.397123] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 41.404561] Control: 10c5387d Table: 9a114019 DAC: 0051 [ 41.410554] Process NetworkManager (pid: 301, stack limit = 0x42389799) [ 41.417448] Stack: (0xda061570 to 0xda062000) [ 41.421991] 1560: da05d680 00041392 dd1d1900 [ 41.430520] 1580: dd1d1900 da4af940 cf07ce88 dd1d1900 da0615ac da0615a0 c0991234 c051adac [ 41.439050] 15a0: da0615cc da0615b0 c0995398 c0991210 dd1d1900 dd1d1900 bf716128 cf07ce88 [ 41.447578] 15c0: da0615e4 da0615d0 c09947f0 c099524c cf07cc00 dd1d1900 da061604 da0615e8 [ 41.456106] 15e0: c0994858 c09947cc cf07cc00 cf07cc0c ff92 cf07ce88 da06162c da061608 [ 41.464635] 1600: bf716128 c0994828 c1205dcc dd44ce20 ff0f ff0f cf178000 [ 41.473165] 1620: da06168c da061630 bf71bff8 bf715fb8 da061650 0004 0064 da061694 [ 41.481693] 1640: da4d1fa0 da4d18c0 da4d1f80 cf178000 da06168c da061660 bf6993c0 00041392 [ 41.490221] 1660: cf178000 bf71be94 cf17826c cf17826c c1205dcc 0001 [ 41.498751] 1680: da061704 da061690 bf6a2f38 bf71bea0 786c 48e09eb4 7854 [ 41.507279] 16a0: 0004 7820 0c04 7824 00d8abff 7868 84036086 783c [ 41.515807] 16c0: 72ee0a72 7838 0029 7828 66964300 00041392 000186a0 cf178000 [ 41.524336] 16e0: cf179000 cf17826c cf17826c cf17a000 da061744 da061708 [ 41.532866] 1700: bf6a3e1c bf6a2d60 cf17826c 0898 bf71be94 bf6a0aa0 da061744 cf178000 [ 41.541394] 1720: cf179000 cf17826c bf71be94 cf17a000 da0617bc da061748 [ 41.549922] 1740: bf69b548 bf6a3ce0 c03808e4 0100 0200 0001 2000 [ 41.558453] 1760: 00551139 c1205dcc cf178028 00023f60 0028 [ 41.566981] 1780: 2eb17382 bf7160f4 da0617bc 00041392 bf7160f4 dd44ce20 dd44c494 cf178000 [ 41.575509] 17a0: c1205dcc dd44d4ac dd44c480 cf17826c da06180c da0617c0 bf719a9c bf69aab4 [ 41.584040] 17c0: da0617d9 0001 01f4 0001 cf07c040 0100 00041392 [ 41.592568] 17e0: dd44c480 de5fe000 dd44c480 bf61c688 de5fe85c dd7db110 [ 41.601098] 1800: da06182c da061810 bf5af81c bf7199f8 de5fe588 de5fe000 dd44c480 bf61c688 [ 41.609628] 1820: da061864 da061830 bf5c6bc8 bf5af7e0 1002 0001 da06185c de5fe580 [ 41.618156] 1840: c1205dcc bf61c688 de5fe02c dd7db110 da06187c da061868 [ 41.626685] 1860: bf5c7140 bf5c679c de5fe000 c1205dcc da0618bc da061880 c09b0008 bf5c70f8 [ 41.635216] 1880: de5fe194 de5fe000 da0618a4 de5fe000 00041392 da0618bc de5fe000 [ 41.643744] 18a0: 0001 1003
Bug#944518: linux-image-4.19.0-6-armmp: please enable CONFIG_INPUT_TPS65218_PWRBUTTON
Source: linux Version: 4.19.67-2+deb10u1 Severity: wishlist Dear Maintainer, currently it's impossible to use the power button on the BeagleBone Black when running the Debian kernel. Please enable CONFIG_INPUT_TPS65218_PWRBUTTON. Kind regards, Sascha Silbe -- Package-specific info: ** Version: Linux version 4.19.0-6-armmp (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2 (2019-08-28) ** Command line: quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: Generic AM33XX (Flattened Device Tree) Revision: Device Tree model: TI AM335x BeagleBone Black ** Loaded modules: tun nls_ascii nls_cp437 vfat fat usbhid hid snd_soc_hdmi_codec snd_soc_simple_card snd_soc_simple_card_utils snd_soc_davinci_mcasp snd_soc_edma snd_soc_sdma tilcdc tda998x snd_soc_core omap_rng drm_kms_helper rng_core snd_pcm_dmaengine snd_pcm snd_timer drm snd soundcore cec at24 cppi41 omap_wdt leds_gpio sch_fq_codel ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb smsc davinci_mdio musb_dsps musb_hdrc udc_core usbcore phy_am335x phy_generic phy_am335x_control ti_cpsw cpsw_ale cpsw_common davinci_cpdma omap_hsmmc musb_am335x tps65217 ** PCI devices: not available ** USB devices: [removed] -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable'), (100, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-6-armmp (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-6-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-6-armmp recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-6-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-6-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#944256: linux-image-4.19.0-6-armmp: please enable cpufreq for AM335x (BBB)
Source: linux Version: 4.19.67-2+deb10u1 Severity: wishlist Dear Maintainer, currently it's impossible to reduce the CPU frequency (e.g. for thermal management) on AM335x based boards like the BeagleBone Black when running the Debian kernel. Please enable cpufreq support for those boards. For starters enabling CONFIG_ARM_TI_CPUFREQ will be required; not sure if other options are missing, too. Kind regards, Sascha Silbe -- Package-specific info: ** Version: Linux version 4.19.0-6-armmp (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2 (2019-08-28) ** Command line: quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: Generic AM33XX (Flattened Device Tree) Revision: Device Tree model: TI AM335x BeagleBone Black ** Loaded modules: tun nls_ascii nls_cp437 vfat fat usbhid hid snd_soc_hdmi_codec snd_soc_simple_card snd_soc_simple_card_utils snd_soc_davinci_mcasp snd_soc_edma snd_soc_sdma tilcdc tda998x snd_soc_core omap_rng drm_kms_helper rng_core snd_pcm_dmaengine snd_pcm snd_timer drm snd soundcore cec at24 cppi41 omap_wdt leds_gpio sch_fq_codel ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb smsc davinci_mdio musb_dsps musb_hdrc udc_core usbcore phy_am335x phy_generic phy_am335x_control ti_cpsw cpsw_ale cpsw_common davinci_cpdma omap_hsmmc musb_am335x tps65217 ** PCI devices: not available ** USB devices: [removed] -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable'), (100, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-6-armmp (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-6-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-6-armmp recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-6-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-6-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information signature.asc Description: PGP signature
Bug#868352: linux: Please enable USB_SERIAL_CONSOLE
Source: linux Version: 4.11.6-1 Severity: normal Dear Maintainer, on some amd64 systems no native or PCI(e) serial ports are available resp. possible. USB serial adapters are the only option to get a serial console for debugging boot problems in this case. Unfortunately the Debian amd64 kernels are built with USB_SERIAL_CONSOLE unset (because USB_SERIAL is not built-in) so even that option isn't available. When the BIOS text mode isn't working (e.g. high-res monitor with a BIOS that only supports up to FullHD) one is left without any working console device. So please enable USB_SERIAL_CONSOLE (requires USB_SERIAL=y) for future kernels and consider setting one of the USB serial adapter drivers to built-in as well so that it's available before module loading. But even just USB_SERIAL_CONSOLE alone (with all USB serial drivers as modules) is likely better than the current situation; AFAICT the USB serial console should get activated as soon the the USB serial driver is loaded (haven't tested it, though). Sascha -- System Information: Debian Release: 8.8 APT prefers oldstable APT policy: (990, 'oldstable'), (500, 'oldstable-updates'), (100, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#747871: mkinitramfs: breaks with LUKS root on MMC (mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry) and MODULES=dep
Package: initramfs-tools
Version: 0.109.1
Severity: normal
File: /usr/sbin/mkinitramfs
Dear Maintainer,
on a system with the rootfs living inside LUKS on an SD card,
mkinitramfs (and thus update-initramfs) fails with:
=== Begin ===
root@mimosa:/boot# update-initramfs -k 3.0.19-mimosa-8-01603-g1b85fba -c
update-initramfs: Generating /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba
mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry
mkinitramfs: workaround is MODULES=most
mkinitramfs: Error please report the bug
update-initramfs: failed for /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba
with 1.
=== End ===
Older versions displayed a warning (which I ignored since everything
needed for boot is built-in to the custom kernel anyway), but didn't
abort initramfs generation.
It looks like hook-functions is a bit overzealous in stripping down
the partition name to a device name, resulting in mmcblk rather than
mmcblk0. There's existing special casing in dep_add_modules for
device mapper (LVM/LUKS) on top of cciss or ida and for root on cciss,
ida, mmc and a few more in place already, but not for device mapper on
top of mmc. Maybe a recursive function would be a better fit for
determining the modules needed for the rootfs?
For reference, this is a trace of mkinitramfs:
=== Begin trace ===
+ CONFDIR=/etc/initramfs-tools
+ verbose=n
+ test -e /bin/busybox
+ BUSYBOXDIR=/bin
+ test -e /usr/lib/initramfs-tools/bin/busybox
+ export BUSYBOXDIR
++ getopt -o c:d:ko:r:v -n mkinitramfs -- -o
/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
3.0.19-mimosa-8-01603-g1b85fba
+ OPTIONS=' -o '\''/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new'\'' --
'\''3.0.19-mimosa-8-01603-g1b85fba'\'''
+ '[' 0 '!=' 0 ']'
+ eval set -- ' -o '\''/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new'\''
-- '\''3.0.19-mimosa-8-01603-g1b85fba'\'''
++ set -- -o /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new --
3.0.19-mimosa-8-01603-g1b85fba
+ true
+ case $1 in
+ outfile=/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
+ shift 2
+ true
+ case $1 in
+ shift
+ break
+ . /usr/share/initramfs-tools/scripts/functions
+ . /usr/share/initramfs-tools/hook-functions
+ . /etc/initramfs-tools/initramfs.conf
++ MODULES=dep
++ BUSYBOX=y
++ KEYMAP=n
++ COMPRESS=gzip
++ DEVICE=
++ NFSROOT=auto
+ EXTRA_CONF=
+ for i in '/usr/share/initramfs-tools/conf.d/*' '${CONFDIR}/conf.d/*'
+ '[' -e '/usr/share/initramfs-tools/conf.d/*' ']'
+ for i in '/usr/share/initramfs-tools/conf.d/*' '${CONFDIR}/conf.d/*'
+ '[' -e '/etc/initramfs-tools/conf.d/*' ']'
+ for i in '/usr/share/initramfs-tools/conf-hooks.d/*'
+ '[' -d /usr/share/initramfs-tools/conf-hooks.d/cryptsetup ']'
+ '[' -e /usr/share/initramfs-tools/conf-hooks.d/cryptsetup ']'
+ . /usr/share/initramfs-tools/conf-hooks.d/cryptsetup
++ KEYMAP=y
++ BUSYBOX=y
++ FRAMEBUFFER=y
+ '[' -n '' ']'
+ '[' -z /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new ']'
+ touch /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
++ readlink -f /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
+ outfile=/boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new
+ '[' 1 -ne 1 ']'
+ version=3.0.19-mimosa-8-01603-g1b85fba
+ case ${version} in
+ case ${version} in
+ '[' -z '' ']'
+ compress=gzip
+ command -v gzip
+ dpkg --compare-versions 3.0.19-mimosa-8-01603-g1b85fba lt 2.6.38
+ '[' gzip = lzop ']'
+ '[' gzip = xz ']'
+ '[' -d /boot/initrd.img-3.0.19-mimosa-8-01603-g1b85fba.new ']'
+ MODULESDIR=/lib/modules/3.0.19-mimosa-8-01603-g1b85fba
+ '[' '!' -e /lib/modules/3.0.19-mimosa-8-01603-g1b85fba ']'
+ '[' '!' -e /lib/modules/3.0.19-mimosa-8-01603-g1b85fba/modules.dep ']'
+ '[' -n '' ']'
++ mktemp -d /var/tmp/mkinitramfs_XX
+ DESTDIR=/var/tmp/mkinitramfs_K8XasF
+ chmod 755 /var/tmp/mkinitramfs_K8XasF
+ NOEXEC=
++ tail -1
++ awk '{print $6}'
++ df -P /var/tmp/mkinitramfs_K8XasF
+ fs=/
+ '[' -n / ']'
+ grep -q 'on / .*noexec'
+ mount
++ mktemp /var/tmp/mkinitramfs-OL_XX
+ __TMPCPIOGZ=/var/tmp/mkinitramfs-OL_OuJNFs
++ dpkg --print-architecture
+ DPKG_ARCH=armel
+ export MODULESDIR
+ export version
+ export CONFDIR
+ export DESTDIR
+ export DPKG_ARCH
+ export verbose
+ export KEYMAP
+ export MODULES
+ export BUSYBOX
+ export __TMPCPIOGZ
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/bin
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/conf/conf.d
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/etc
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/lib/modules
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/run
+ for d in bin conf/conf.d etc lib/modules run sbin scripts '${MODULESDIR}'
+ mkdir -p /var/tmp/mkinitramfs_K8XasF/sbin
+ for d in bin conf/conf.d etc lib/modules run sbin
Bug#699205: [3.7.1-3.7.3 regression] ps, pgrep and pkill segfault
Version: 3.8.5-1~experimental.1 This doesn't happen with linux-image-3.8-trunk-amd64 3.8.5-1~experimental.1 (currently available from experimental). The problematic kernel version (linux-image-3.7-trunk-amd64 3.7.3-1~experimental.1) isn't available from experimental anymore, so I'm considering this fixed. Kudos to whoever fixed it. Sascha pgpWsWS9Nx2tM.pgp Description: PGP signature
Bug#699205: linux-image-3.7-trunk-amd64: ps, pgrep and pkill segfault after upgrade from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1
Jonathan Nieder jrnie...@gmail.com writes: after updating the linux-image-3.7-trunk-amd64 from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting, the tools ps, pgrep and pkill (package procps) are always segfaulting: Just to check: if you downgrade to 3.7.1 again, do the segfaults go away? (Historical versions of Debian packages are available from http://snapshot.debian.org) Confirmed. I'll try to provide a backtrace at the end of the week if noone else can reproduce this in the meantime; debugging this issue is a pain as it requires reboots, especially since the procps test suite runs (and fails) despite 'nocheck' in DEB_BUILD_OPTIONS. Sounds like http://bugs.debian.org/656508 I'm afraid not. #656508 is also about the test suite failing, but the output is quite different. With 3.7.3-1~experimental.1 it caught the segfaults (good in general), but even with 3.7.1-1~experimental.2 it fails the lib tests because of a missing file: === Begin === === lib tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using ./config/unix.exp as tool-and-target-specific interface file. Running ./lib.test/fileutils.exp ... ERROR: tcl error sourcing ./lib.test/fileutils.exp. ERROR: couldn't execute /home/sascha.silbe/src/deb/procps-3.3.3/testsuite/lib.test/fileutils_badfd.sh: no such file or directory while executing spawn $badfd (file ./lib.test/fileutils.exp line 13) invoked from within source ./lib.test/fileutils.exp (uplevel body line 1) invoked from within uplevel #0 source ./lib.test/fileutils.exp invoked from within catch uplevel #0 source $test_file_name Running ./lib.test/strutils.exp ... === End === Have just filed a separate bug about that. A pre-built -dbg package would have been nice. Sounds worth a separate report. :) I've mentioned it in the FTBFS report. Maybe a gentle nudge is enough. :) I wonder what got of the Squeeze release goal Automatic creation of debug packages for the entire archive... I know that for my library package (liblzma) I haven't bothered but would be happy to take care of it if I knew there were a push for this systemwide. Might be worth starting a discussion on debian-policy@. Maybe one of these days I'll do (probably on debian-devel first, though). I seem to have a knack of triggering crashes, especially in applications using lots of libraries that don't ship a -dbg package. Sascha pgp_Ac1li8HE1.pgp Description: PGP signature
Bug#699205: linux-image-3.7-trunk-amd64: ps, pgrep and pkill segfault after upgrade from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1
Package: src:linux Version: 3.7.3-1~experimental.1 Severity: important Dear Maintainer, after updating the linux-image-3.7-trunk-amd64 from 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting, the tools ps, pgrep and pkill (package procps) are always segfaulting: === Begin === sascha.silbe@twin:~$ uname -r 3.7-trunk-amd64 sascha.silbe@twin:~$ ps Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report this bug sascha.silbe@twin:~$ pgrep scdaemon Segmentation fault sascha.silbe@twin:~$ pkill scdaemon Segmentation fault sascha.silbe@twin:~$ apt-cache policy linux-image-3.7-trunk-amd64 linux-image-3.7-trunk-amd64: Installed: 3.7.3-1~experimental.1 Candidate: 3.7.3-1~experimental.1 Version table: *** 3.7.3-1~experimental.1 0 1 http://ftp.de.debian.org/debian/ experimental/main amd64 Packages 100 /var/lib/dpkg/status sascha.silbe@twin:~$ grep linux-image-3.7-trunk-amd64 /var/log/dpkg.log 2013-01-06 20:34:07 install linux-image-3.7-trunk-amd64:amd64 none 3.7.1-1~experimental.2 2013-01-06 20:34:07 status half-installed linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-06 20:34:07 status half-installed linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-06 20:34:38 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-06 20:34:38 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-06 20:34:39 configure linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 none 2013-01-06 20:34:39 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-06 20:34:39 status half-configured linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-06 20:36:22 status installed linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-28 17:17:20 upgrade linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 3.7.3-1~experimental.1 2013-01-28 17:17:20 status half-configured linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-28 17:17:20 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-28 17:17:20 status half-installed linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-28 17:17:21 status half-installed linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-28 17:17:56 status half-installed linux-image-3.7-trunk-amd64:amd64 3.7.1-1~experimental.2 2013-01-28 17:17:56 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.3-1~experimental.1 2013-01-28 17:17:56 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.3-1~experimental.1 2013-01-28 17:17:57 configure linux-image-3.7-trunk-amd64:amd64 3.7.3-1~experimental.1 none 2013-01-28 17:17:57 status unpacked linux-image-3.7-trunk-amd64:amd64 3.7.3-1~experimental.1 2013-01-28 17:17:57 status half-configured linux-image-3.7-trunk-amd64:amd64 3.7.3-1~experimental.1 2013-01-28 17:18:14 status installed linux-image-3.7-trunk-amd64:amd64 3.7.3-1~experimental.1 sascha.silbe@twin:~$ === End === This may well be a bug in procps triggered by an API change (i.e. change of format in /proc files), but I wouldn't expect such an API change from an update within the kernel.org stable release series, so I'm filing this against the kernel package, rather than procps. Feel free to reassign or split the ticket. I'll try to provide a backtrace at the end of the week if noone else can reproduce this in the meantime; debugging this issue is a pain as it requires reboots, especially since the procps test suite runs (and fails) despite 'nocheck' in DEB_BUILD_OPTIONS. A pre-built -dbg package would have been nice. I wonder what got of the Squeeze release goal Automatic creation of debug packages for the entire archive... -- Package-specific info: ** Version: Linux version 3.7-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.7.3-1~experimental.1 ** Command line: BOOT_IMAGE=/vmlinuz-3.7-trunk-amd64 root=/dev/mapper/twin_vg-wheezy--root ro rootflags=data=journal usbcore.autosuspend=1 snd_hda_intel.power_save=1 resume=/dev/mapper/dmcrypt-swap-ssd quiet ** Not tainted ** Kernel log: [ 59.628580] WARNING! power/level is deprecated; use power/control instead [ 59.631595] kvm: Nested Virtualization enabled [ 59.631599] kvm: Nested Paging enabled [ 59.647230] [drm] ib test on ring 0 succeeded in 0 usecs [ 59.648314] [drm] Radeon Display Connectors [ 59.648316] [drm] Connector 0: [ 59.648318] [drm] HDMI-A-1 [ 59.648319] [drm] HPD1 [ 59.648322] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [ 59.648323] [drm] Encoders: [ 59.648325] [drm] DFP1: INTERNAL_UNIPHY2 [ 59.648326] [drm] Connector 1: [ 59.648327] [drm] VGA-1 [ 59.648329] [drm] HPD2 [ 59.648330] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [ 59.648331] [drm] Encoders: [ 59.648332] [drm] CRT1: INTERNAL_UNIPHY2 [ 59.648333]
Bug#640222: nfs-common: init script failure during installation, leaving package half-configured
Package: nfs-common
Version: 1:1.2.4-1
Severity: normal
For an unknown reason /etc/init.d/nfs-common start failed during
installation of nfs-common, leaving the package in half-configured state:
sascha.silbe@mimosa:~$ sudo aptitude install nfs-common
The following NEW packages will be installed:
libgssglue1{a} [0.3-2] +98.3 kB (D: libtirpc1, D: nfs-common) (for
nfs-common)
libnfsidmap2{a} [0.24-1] +123 kB (D: nfs-common) (for nfs-common)
libtirpc1{a} [0.2.2-5] +242 kB (D: nfs-common, D: rpcbind) (for nfs-common)
nfs-common [1:1.2.4-1] +721 kB
rpcbind{a} [0.2.0-6] +172 kB (D: nfs-common) (for nfs-common)
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 414 kB of archives. After unpacking 1,356 kB will be used.
Do you want to continue? [Y/n/?] y
Get:1 http://ftp.de.debian.org/debian/ wheezy/main libgssglue1 armel 0.3-2
[22.0 kB]
Get:2 http://ftp.de.debian.org/debian/ wheezy/main libtirpc1 armel 0.2.2-5
[76.2 kB]
Get:3 http://ftp.de.debian.org/debian/ wheezy/main libnfsidmap2 armel 0.24-1
[30.3 kB]
Get:4 http://ftp.de.debian.org/debian/ wheezy/main rpcbind armel 0.2.0-6 [41.3
kB]
Get:5 http://ftp.de.debian.org/debian/ wheezy/main nfs-common armel 1:1.2.4-1
[244 kB]
Fetched 414 kB in 1s (253 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously deselected package libgssglue1.
(Reading database ... 98059 files and directories currently installed.)
Unpacking libgssglue1 (from .../libgssglue1_0.3-2_armel.deb) ...
Selecting previously deselected package libtirpc1.
Unpacking libtirpc1 (from .../libtirpc1_0.2.2-5_armel.deb) ...
Selecting previously deselected package libnfsidmap2.
Unpacking libnfsidmap2 (from .../libnfsidmap2_0.24-1_armel.deb) ...
Selecting previously deselected package rpcbind.
Unpacking rpcbind (from .../rpcbind_0.2.0-6_armel.deb) ...
Selecting previously deselected package nfs-common.
Unpacking nfs-common (from .../nfs-common_1%3a1.2.4-1_armel.deb) ...
Processing triggers for man-db ...
Setting up libgssglue1 (0.3-2) ...
Setting up libtirpc1 (0.2.2-5) ...
Setting up libnfsidmap2 (0.24-1) ...
Setting up rpcbind (0.2.0-6) ...
Starting rpcbind daemon
Setting up nfs-common (1:1.2.4-1) ...
Creating config file /etc/idmapd.conf with new version
Creating config file /etc/default/nfs-common with new version
Adding system user `statd' (UID 107) ...
Adding new user `statd' (UID 107) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
Starting NFS common utilities: statd idmapd failed!
invoke-rc.d: initscript nfs-common, action start failed.
dpkg: error processing nfs-common (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
nfs-common
[master 294ea6f] committing changes in /etc after apt run
Author: sascha.silbe sascha.si...@mimosa.sascha.silbe.org
115 files changed, 525 insertions(+), 50 deletions(-)
create mode 100644 default/nfs-common
create mode 100644 gssapi_mech.conf
create mode 100644 idmapd.conf
rewrite init.d/.depend.start (69%)
rewrite init.d/.depend.stop (60%)
create mode 100755 init.d/nfs-common
create mode 100755 init.d/rpcbind
create mode 100644 insserv.conf.d/rpcbind
create mode 100644 netconfig
create mode 12 rc0.d/K05nfs-common
create mode 12 rc0.d/K05rpcbind
rename rc0.d/{K04hwclock.sh = K06hwclock.sh} (100%)
rename rc0.d/{K05networking = K06networking} (100%)
rename rc0.d/{K06ifupdown = K07ifupdown} (100%)
rename rc0.d/{K07umountfs = K08umountfs} (100%)
rename rc0.d/{K08cryptdisks = K09cryptdisks} (100%)
rename rc0.d/{K09cryptdisks-early = K10cryptdisks-early} (100%)
rename rc0.d/{K10umountroot = K11umountroot} (100%)
rename rc0.d/{K11halt = K12halt} (100%)
create mode 12 rc1.d/K05nfs-common
create mode 12 rc1.d/K05rpcbind
rename rc1.d/{S02bootlogs = S20bootlogs} (100%)
rename rc1.d/{S03single = S21single} (100%)
create mode 12 rc2.d/S16rpcbind
create mode 12 rc2.d/S17nfs-common
rename rc2.d/{S01nodm = S19nodm} (100%)
rename rc2.d/{S01rsyslog = S19rsyslog} (100%)
rename rc2.d/{S01sudo = S19sudo} (100%)
rename rc2.d/{S02bootlogs = S20bootlogs} (100%)
rename rc2.d/{S02cron = S20cron} (100%)
rename rc2.d/{S02dbus = S20dbus} (100%)
rename rc2.d/{S02nullmailer = S20nullmailer} (100%)
rename rc2.d/{S02pcscd = S20pcscd} (100%)
rename rc2.d/{S02rsync = S20rsync} (100%)
rename rc2.d/{S02ssh = S20ssh} (100%)
rename rc2.d/{S03avahi-daemon = S21avahi-daemon} (100%)
rename rc2.d/{S03network-manager = S21network-manager} (100%)
rename rc2.d/{S04rc.local = S22rc.local} (100%)
rename rc2.d/{S04rmnologin = S22rmnologin} (100%)
rename rc2.d/{S04stop-bootlogd = S22stop-bootlogd} (100%)
create mode 12 rc3.d/S16rpcbind
create mode 12 rc3.d/S17nfs-common
rename rc3.d/{S01nodm = S19nodm} (100%)
rename rc3.d/{S01rsyslog = S19rsyslog} (100%)
rename
Bug#584744: linux-2.6: built-in radeonfb breaks DRM
Package: linux-2.6 Severity: normal With the built-in radeonfb and KMS enabled by default, DRM is broken on eMacs. See e.g. FDO#27502 [1]. Disabling KMS in /etc/modprobe.d/radeon-kms.conf works around the issue. Not sure what a real fix would be in this case - is there a framebuffer driver that can coexist with drm? [1] https://bugs.freedesktop.org/show_bug.cgi?id=27502 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.32-5-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100725162322.1670.85918.report...@emac.sascha.silbe.org
Bug#542275: rtc-generic not working on Apple PowerBook G4
On Tue, Jan 12, 2010 at 02:18:10PM +0100, Jordi Mallach wrote: Sorry about this. I say close the bug and if I come back as a PPC user, I'll test 2.6.32-trunk to see what happens. I've been hit by this issue as well in the past (on an eMac), but don't have time to do any testing right now. It would be great if you could keep the bug open and ping me in a few weeks. CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature
Bug#531273: linux-image-2.6.26-2-amd64: not powering off: boot CPU gets halted
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny2 Severity: normal Often, but not always my desktop refuses to power down. The last messages are (copied manually): [34709.779040] ACPI: Preparing to enter system sleep state S5 [34709.779040] Disabling non-boot CPUs ... [34709.779040] CPU0 attach NULL sched-domain. [34709.779040] CPU1 attach NULL sched-domain. -- Package-specific info: ** Version: Linux version 2.6.26-2-amd64 (Debian 2.6.26-15lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed May 13 15:37:46 UTC 2009 ** Command line: root=/dev/twin_vg/root rootflags=data=journal ro usbcore.autosuspend=1 nomsi ** Tainted: P (1) ** Kernel log: [ 32.668128] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.668128] EXT3 FS on dm-3, internal journal [ 32.668128] EXT3-fs: mounted filesystem with journal data mode. [ 32.741477] kjournald starting. Commit interval 30 seconds [ 32.745475] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.745475] EXT3 FS on dm-6, internal journal [ 32.745475] EXT3-fs: mounted filesystem with journal data mode. [ 32.819547] kjournald starting. Commit interval 30 seconds [ 32.819547] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.819547] EXT3 FS on dm-7, internal journal [ 32.819547] EXT3-fs: mounted filesystem with journal data mode. [ 32.955547] kjournald starting. Commit interval 30 seconds [ 32.955667] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.955667] EXT3 FS on dm-9, internal journal [ 32.955667] EXT3-fs: mounted filesystem with journal data mode. [ 33.096664] kjournald starting. Commit interval 30 seconds [ 33.099579] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended [ 33.099843] EXT3 FS on dm-1, internal journal [ 33.099916] EXT3-fs: mounted filesystem with journal data mode. [ 33.174490] kjournald starting. Commit interval 30 seconds [ 33.174490] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 33.175538] EXT3 FS on dm-4, internal journal [ 33.175612] EXT3-fs: mounted filesystem with journal data mode. [ 33.339127] kjournald starting. Commit interval 30 seconds [ 33.340966] EXT3 FS on dm-19, internal journal [ 33.340966] EXT3-fs: mounted filesystem with journal data mode. [ 33.610890] kjournald starting. Commit interval 30 seconds [ 33.615114] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 33.615114] EXT3 FS on dm-11, internal journal [ 33.615114] EXT3-fs: mounted filesystem with journal data mode. [ 33.995726] Adding 4194296k swap on /dev/mapper/twin_vg-swap. Priority:-1 extents:1 across:4194296k [ 35.700773] NET: Registered protocol family 15 [ 37.710104] ip_tables: (C) 2000-2006 Netfilter Core Team [ 37.757428] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 38.029337] r8169: eth0: link down [ 38.080927] device eth0 entered promiscuous mode [ 38.922927] NET: Registered protocol family 10 [ 38.923630] lo: Disabled Privacy Extensions [ 38.924375] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.933439] powernow-k8: Found 1 AMD Athlon(tm) X2 Dual Core Processor BE-2300 processors (2 cpu cores) (version 2.20.00) [ 40.933439] powernow-k8:0 : fid 0xb (1900 MHz), vid 0xc [ 40.933444] powernow-k8:1 : fid 0xa (1800 MHz), vid 0xd [ 40.933447] powernow-k8:2 : fid 0x2 (1000 MHz), vid 0x16 [ 56.287861] pnp: the driver 'parport_pc' has been registered [ 56.290395] lp: driver loaded but no devices found [ 56.353332] ppdev: user-space parallel port driver [ 57.202148] Clocksource tsc unstable (delta = -125107490 ns) [ 65.094860] Bluetooth: Core ver 2.11 [ 65.096894] NET: Registered protocol family 31 [ 65.096924] Bluetooth: HCI device and connection manager initialized [ 65.096951] Bluetooth: HCI socket layer initialized [ 65.126865] Bluetooth: L2CAP ver 2.9 [ 65.126865] Bluetooth: L2CAP socket layer initialized [ 65.217296] Bluetooth: RFCOMM socket layer initialized [ 65.217340] Bluetooth: RFCOMM TTY layer initialized [ 65.217362] Bluetooth: RFCOMM ver 1.8 [ 66.324720] hda-intel: Invalid position buffer, using LPIB read method instead. [ 68.437317] ata2.00: configured for UDMA/133 [ 68.437348] ata2: EH complete [ 68.437412] sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB) [ 68.437454] sd 1:0:0:0: [sdb] Write Protect is off [ 68.437479] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 68.437512] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 68.441926] ata1.00: configured for UDMA/133 [ 68.441952] ata1: EH complete [ 68.442006] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [ 68.442045] sd 0:0:0:0: [sda] Write Protect is off [ 68.442069] sd
Bug#525606: initramfs-tools: update-initramfs breaks if /etc/mtab is a symlink to /proc/mounts
Package: initramfs-tools Version: 0.93.2 Severity: important update-initramfs breaks since /etc/mtab is a symlink to /proc/mounts on this system. The normal Debian init scripts (like mtab.sh) take special care to continue working in that case and the initramfs-tools documentation does not mention this case to be unsupported, so I'm assuming it's supposed to work (thus severity important instead of wishlist). Error encountered (during update): Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.26-2-amd64 /dev/root: error opening volume mkinitramfs: for root /dev/disk/by-uuid missing disk/by-uuid /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-2.6.26-2-amd64 dpkg: subprocess post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (2) A package failed to install. Trying to recover: Setting up initramfs-tools (0.93.2) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.26-2-amd64 /dev/root: error opening volume mkinitramfs: for root /dev/disk/by-uuid missing disk/by-uuid /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-2.6.26-2-amd64 dpkg: subprocess post-installation script returned error exit status 1 E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: Could not regain the system lock! (Perhaps another apt or dpkg is running?) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. === Begin /proc/mounts === rootfs / rootfs rw 0 0 /dev/root / ext3 rw,noatime,errors=remount-ro,user_xattr,acl,data=journal 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,mode=755 0 0 proc /proc proc rw,nosuid,nodev,noexec 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec 0 0 varrun /var/run tmpfs rw,nosuid,mode=755 0 0 varlock /var/lock tmpfs rw,nosuid,nodev,noexec 0 0 tmpfs /dev tmpfs rw,size=10240k,mode=755 0 0 shmfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,gid=5,mode=620 0 0 === End /proc/mounts === -- Package-specific info: -- /proc/cmdline root=/dev/hda1 ro rootflags=data=journal console=tty0 console=ttyS0,115200 -- /proc/filesystems ext3 ext2 fuseblk -- lsmod Module Size Used by loop 20364 0 -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-dextro-1 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9.90-3 GNU cpio -- a program to manage ar ii findutils 4.4.0-3utilities for finding files--find, ii klibc-utils 1.5.15-1 small utilities built with klibc f ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo ii udev 0.141-1/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#440176: closed by maximilian attems [EMAIL PROTECTED] (Re: Bug#440176: mkinitramfs: does not work properly with symlinked config files)
On Wed, Sep 05, 2007 at 10:47:57PM +, Debian Bug Tracking System wrote: [EMAIL PROTECTED]:~# ls -l /etc/udev/links.conf lrwxrwxrwx 1 root root 35 2007-08-30 14:25 /etc/udev/links.conf - ../infra/system-1.0/udev/links.conf it seems pretty evident that your /etc/udev/links.conf is pointing to /infra/system-1.0/udev/links.conf and not /etc/infra/system-1.0/udev/links.conf As you can see above this is NOT the case (/etc/udev/../infra/whatever = /etc/infra/whatever). I have also verified this again on the system itself. Even though symlinking config files might be unusual, I did not find anything in the policy or any documentation about this being discouraged or unsupported. It worked quite fine in the past, both with Debian and with other distributions like Gentoo. If you tell me which file to examine to find the bug, I'll try to provide a patch. This feature is quite critical to me. CU Sascha -- http://sascha.silbe.org/ pgpTcGeZd1dKJ.pgp Description: PGP signature
Bug#440176: mkinitramfs: does not work properly with symlinked config files
Package: initramfs-tools Version: 0.85h Severity: important mkinitramfs (called by update-initramfs, called in postinst) does not work properly if the config files to be included in the initramfs are symlinks: [EMAIL PROTECTED]:~# mkinitramfs -o /boot/initrd.img-2.6.18-5-686 2.6.18-5-686 cpio: ./etc/udev/links.conf: No such file or directory cpio: ./etc/udev/udev.conf: No such file or directory cpio: ./etc/modprobe.d/arch/i386: No such file or directory cpio: ./etc/modprobe.d/blacklist: No such file or directory cpio: ./etc/modprobe.d/pnp-hotplug: No such file or directory cpio: ./etc/modprobe.d/aliases: No such file or directory cpio: ./etc/modprobe.d/display_class: No such file or directory cpio: ./etc/modprobe.d/arch-aliases: No such file or directory [EMAIL PROTECTED]:~# ls -l /etc/udev/links.conf lrwxrwxrwx 1 root root 35 2007-08-30 14:25 /etc/udev/links.conf - ../infra/system-1.0/udev/links.conf [EMAIL PROTECTED]:~# ls -l /etc/infra/system-1.0/udev/links.conf -rw-r--r-- 1 root root 430 2007-03-23 16:30 /etc/infra/system-1.0/udev/links.conf strace shows that cpio is already called with --dereference. Since I didn't find anything about udev in /usr/sbin/mkinitramfs, I don't know how to proceed further to fix this bug. -- Package-specific info: -- /proc/cmdline root=/dev/md2 ro console=ttyS0,115200 TERM=vt100 -- /proc/filesystems cramfs ext3 ext2 -- lsmod Module Size Used by sha256 11104 0 aes28160 4 dm_crypt 10888 1 nfs 202828 0 nfsd 197936 17 exportfs5600 1 nfsd lockd 54344 3 nfs,nfsd nfs_acl 3584 2 nfs,nfsd sunrpc138812 13 nfs,nfsd,lockd,nfs_acl button 6672 0 ac 5188 0 battery 9636 0 iptable_mangle 2880 0 ipt_MASQUERADE 3712 1 iptable_nat 7044 1 ip_nat 16876 2 ipt_MASQUERADE,iptable_nat ip_conntrack 49088 3 ipt_MASQUERADE,iptable_nat,ip_nat nfnetlink 6680 2 ip_nat,ip_conntrack ipt_LOG 6112 1 xt_limit2752 1 ipt_REJECT 5248 2 ipt_TCPMSS 4096 1 xt_tcpudp 3136 18 iptable_filter 3104 1 ip_tables 13028 3 iptable_mangle,iptable_nat,iptable_filter x_tables 13316 8 ipt_MASQUERADE,iptable_nat,ipt_LOG,xt_limit,ipt_REJECT,ipt_TCPMSS,xt_tcpudp,ip_tables ipv6 226016 26 bridge 49404 0 tun10336 0 ext2 59048 2 loop 15048 0 snd_via82xx26008 0 gameport 14632 1 snd_via82xx snd_ac97_codec 83104 1 snd_via82xx snd_ac97_bus2400 1 snd_ac97_codec snd_pcm68676 2 snd_via82xx,snd_ac97_codec snd_timer 20996 1 snd_pcm snd_page_alloc 9640 2 snd_via82xx,snd_pcm snd_mpu401_uart 8064 1 snd_via82xx snd_rawmidi22560 1 snd_mpu401_uart snd_seq_device 7820 1 snd_rawmidi pcmcia 34140 0 firmware_class 9600 1 pcmcia snd47012 7 snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device evdev 9088 0 via82cxxx_audio24296 0 uart40111172 1 via82cxxx_audio sound 69768 2 via82cxxx_audio,uart401 soundcore 9248 3 snd,via82cxxx_audio,sound ac97_codec 17196 1 via82cxxx_audio parport_pc 32132 0 floppy 53156 0 parport33256 1 parport_pc pcspkr 3072 0 yenta_socket 24460 1 rsrc_nonstatic 11840 1 yenta_socket rtc12372 0 hisax_fcpcipnp 11392 0 hisax_isac 8116 1 hisax_fcpcipnp hisax 413248 2 hisax_fcpcipnp,hisax_isac psmouse35016 0 serio_raw 6660 0 isdn 120608 1 hisax slhc6528 1 isdn via_ircc 23188 0 irda 162588 1 via_ircc crc_ccitt 2240 2 hisax,irda i2c_viapro 8244 0 i2c_core 19680 1 i2c_viapro shpchp 33024 0 pci_hotplug28704 1 shpchp via_agp 9664 1 agpgart29896 1 via_agp pcmcia_core36852 3 pcmcia,yenta_socket,rsrc_nonstatic ext3 119240 10 jbd52456 1 ext3 mbcache 8356 2 ext2,ext3 dm_mirror 19152 0 dm_snapshot15552 0 dm_mod 50232 31 dm_crypt,dm_mirror,dm_snapshot raid1 21056 4 md_mod 70388 5 raid1 ide_generic 1408 0 [permanent] ide_cd 36064 0 cdrom
