Bug#1063387: linux: should there be a dependency on xz-utils?
Source: linux Version: 6.6.3-1~exp1 Severity: normal Since module compression was recently enabled, I'm wondering whether some package (probably kbuild or headers) should add a dependency on xz-utils to ensure the tools are available when building out-of-tree modules. The missing xz was noticed in the dkms CI: https://github.com/dell/dkms/pull/393 Andreas
Re: Upcoming changes to Debian Linux kernel packages
On 03/10/2023 19.30, Bastian Blank wrote: thread. Or freak out because meta packages remain uninstallable in backports for days. ... plus gcc or we change how backports works. If uninstallable packages in backports are a problem, perhaps backports needs something like britney to migrate packages from an uploading area to the publishing area (once a package set is installable, no need for delays). That should solve the problem where several source packages need to be updated together. (It would also solve problems with unsatisfiable dependencies where the backporter-uploaded binaries were built by accident in sid instead of stable, requiring a binNMU before migration.) (but this should be discussed elsewhere) Andreas
Re: Upcoming changes to Debian Linux kernel packages
On 25/09/2023 00.50, Bastian Blank wrote: Already built modules remain until someone deletes it. So you can also switch back to the still installed older kernel version and it will have the still working module available. This is what I expect not to work. Assume I have Linux 6.6 and a third-party gpu driver module installed (so there are dkms and the Linux 6.6 headers as well) and everything is working fine. Then I upgrade the system, which brings Linux 6.7 (along linux-image-6.6 which is kept installed) and a new version of the gpu driver (which adds support for 6.7). So the old gpu module for 6.6 gets removed and a new one is built for 6.7 only (since there are only 6.7 headers now). Unfortunately 6.7 breaks some exotic in-tree driver (which I desperately need), so I need to go back to 6.6. Oops, there is no gpu driver module any more. Recovery now needs manual intervention. I'm not sure which class of bugs you are trying to solve with this proposed unversioned linux-headers change. IMO the current scheme of linux-headers-$version-$abi-$flavor matching linux-image-$version-$abi-$flavor works well. But perhaps something could be improved on the metapackage side. Ideally a user should install either meta-linux-image-without-headers-$flavor OR meta-linux-image-with-headers-$flavor (and ideally installing dkms should "automatically switch" to the with-headers variant, not sure how this could be done). The current scheme of having to install linux-image-$flavor AND linux-headers-$flavor is a bit tricky. I'm open to implement improvements on the dkms side. Andreas PS: the proposed "more versioning in the linux-image packages" will solve some rare dkms issues where modules didn't get rebuilt after linux-headers-* was upgraded but $(uname -r) didn't change
Re: Upcoming changes to Debian Linux kernel packages
On 24/09/2023 15.01, Bastian Blank wrote: ## Kernel modules will be signed with an ephemeral key The modules will not longer be signed using the Secure Boot CA like the EFI kernel image itself. Instead a key will be created during the build and thrown away after. Do I correctly assume that change only affects the modules shipped by the linux-image packages and not third-party modules built with dkms? ## Header and tool packages will not longer contain version This means that only headers of one single version can be available on the system at one time. This might be a bit inconvinient for dkms, as it can't longer build modules for multiple versions. That sounds problematic in case of third party modules. If it is possible to have multiple linux-image-* packages installed, but only headers for one of them, the third-party modules will only be available for one of the kernel versions for sure (maybe there are still old module builds available, but no guarantee especially after the third-party module got updated). This will make switching between different kernel versions difficult to impossible, e.g. it may be hard to go back to a working older kernel version in case the new one does not work properly (or the third-party module cannot be built or does not work for the new version). Regarding getting the correct linux-header-* packages installed for the installed linux-image-* packages: Maybe linux-image-* could have Recommends: linux-headers-* | no-linux-headers s.t. the correct linux-headers-* are installed by default (installation of recommends is enabled by default) for all installed linux-image-* packages. no-linux-headers would be an opt-out package that can be installed manually if someone does not want to get linux-headers-* installed at all. It should never be installed automatically. For dkms it is hard recommend the correct linux-header-* package, right now we have Recommends: linux-headers-generic | linux-headers-686-pae | linux-headers-amd64 | linux-headers which does not really work for the non-default kernel flavor, e.g. the -cloud or -i386 kernel. So some improvement on the kernel side would be nice here. Andreas
Bug#1037425: linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages
Package: linux-kbuild-6.1 Version: 6.1.27-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, one change in dkms in bookworm is that it actually returns an error when failing to build a module, as a result /etc/kernel/header_postinst.d/dkms may fail and cause linux-headers---.postinst to fail. (Up to bullseye, dkms returned 0 on failure and the failure was only noticable when someone studied the install/upgrade log.) As a consequence, if cruft *-dkms packages are still installed, but fail to build the module for current kernels, this may result in upgrade failures. Therefore please add Breaks against cruft *-dkms packages that may be left over from previous releases to ensure they get removed. I chose linux-kbuild-6.1 for the addition of these Breaks since all linux-headers-* packages depend on that. I'm trying to build a list: Breaks: # in bullseye, not in bookworm: nvidia-tesla-418-kernel-dkms (<< 418.226.00-9~), nvidia-tesla-460-kernel-dkms (<< 460.106.00-9~), # in buster, not in bullseye sl-modem-dkms (<< 2.9.11~20110321-16.0), # in stretch, not in buster blktap-dkms (<< 2.0.93-0.10.0), # in jessie, not in stretch oss4-dkms (<< 4.2-build2020-1~), # in wheezy, not in jessie blcr-dkms (<< 0.8.6~b3-1.0), Maybe there are more, but I haven't seen them, yet. In case this was fixed in sid (but not in bookworm), I've used that version suffixed with '~', otherwise (i.e. not fixed in sid) I've invented a version based on the last version in sid with NMU suffix .0 The typical upgrade failure if one of these obsolete packages is still installed looks like this: ... Setting up linux-headers-6.1.0-9-amd64 (6.1.27-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-9-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Certificate or key are missing, generating self signed certificate for MOK... openssl not found, can't generate key and certificate. Building module: Cleaning build area... make -j84 KERNELRELEASE=6.1.0-9-amd64 -C /lib/modules/6.1.0-9-amd64/build M=/var/lib/dkms/blcr/0.8.5/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. dkms autoinstall on 6.1.0-9-amd64/x86_64 failed for blcr(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-9-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-9-amd64.postinst line 11. dpkg: error processing package linux-headers-6.1.0-9-amd64 (--configure): installed linux-headers-6.1.0-9-amd64 package post-installation script subprocess returned error exit status 1 Setting up gnupg (2.2.40-1.1) ... dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.1.0-9-amd64 (= 6.1.27-1); however: Package linux-headers-6.1.0-9-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for systemd (252.6-1.1~deb12anbe1) ... Processing triggers for debianutils (5.7-0.4) ... Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: linux-headers-6.1.0-9-amd64 linux-headers-amd64 while on bullseye the ignored failure looked like this: ... Setting up linux-headers-5.10.0-22-amd64 (5.10.178-3) ... /etc/kernel/header_postinst.d/dkms: Error! Bad return status for module build on kernel: 5.10.0-22-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. Andreas
Bug#1035282: firmware-brcm80211: broken symlinks: /lib/firmware/brcm/brcmfmac4356-sdio.*,*.txt -> brcmfmac4356-sdio.AP6356S.txt
Package: firmware-brcm80211 Version: 20230210-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m14.9s ERROR: WARN: Broken symlinks: /lib/firmware/brcm/brcmfmac4356-sdio.khadas,vim2.txt -> brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211) /lib/firmware/brcm/brcmfmac4356-sdio.vamrs,rock960.txt -> brcmfmac4356-sdio.AP6356S.txt (firmware-brcm80211) Severity serious, since this likely means that the kernel cannot find the firmware at the expected location. cheers, Andreas firmware-brcm80211_20230210-4.log.gz Description: application/gzip
Bug#1035281: firmware-intel-sound: broken symlinks: /lib/firmware/intel/dsp_fw_*.bin -> avs/*/dsp_basefw.bin
Package: firmware-intel-sound Version: 20230310-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks. >From the attached log (scroll to the bottom...): 0m13.1s ERROR: WARN: Broken symlinks: /lib/firmware/intel/dsp_fw_bxtn.bin -> avs/apl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_cnl.bin -> avs/cnl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_glk.bin -> avs/apl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_kbl.bin -> avs/skl/dsp_basefw.bin (firmware-intel-sound) /lib/firmware/intel/dsp_fw_release.bin -> avs/skl/dsp_basefw.bin (firmware-intel-sound) Severity serious, since that likely means the firmware is missing at the expected location. cheers, Andreas firmware-intel-sound_20230310-1~exp1.log.gz Description: application/gzip
Bug#1014633: linux-headers-5.19.0-rc4-common: file check-local-export does not exist
Followup-For: Bug #1014633 What about adding a superficial autopkgtest that tries to compile a dummy third-party kernel module using kbuild? That should help noticing such breakage earlier. Andreas
Bug#990662: nouveau 0000:01:00.0: firmware: failed to load nouveau/nvd9_fuc084 (-2)
On 16/07/2022 17.05, Mathieu Malaterre wrote: If I understand correctly, all I need is the file `NVIDIA-Linux-x86-340.108.run` which is distributed directly in contrib in package nvidia-graphics-drivers-legacy-340xx-340.108. I'll see if I can patch this package directly instead of duplicating the code in another package. The 340 series is long EoL, not in stable and won't return to testing. For extracting the firmware, it's probably better to have a downloader package that wgets the .run file from nvidia, validates against a known hash and runs the script on it. Andreas
Bug#1014811: linux-headers-all metapackage for autopkgtests
Source: linux Version: 4.19.235-1 Severity: wishlist Hi, for autopkgtests that test building out-of-tree modules it would be helpful to have an unversioned metapackage that depends on all kernel header packages. If that is used as dependency of an autopkgtest, the test itself can easily enumerate all kernels (/lib/modules/*/build/) and try to build the module for them. Andreas
Bug#990662: nouveau 0000:01:00.0: firmware: failed to load nouveau/nvd9_fuc084 (-2)
On 11/07/2022 18.35, Mathieu Malaterre wrote: Since the nvidia* package do the heavy lifting of downloading locally binary, it would make sense to add yet-another package for firmware related within the group. Putting a downloader package in contrib under the Nvidia Team umbrella is fine, but someone needs to come up with an initial implementation. A quick glance at the script gave me the impression that you need to extract firmware from the 340xx legacy or older drivers. Looking at existing packages (e.g. firmware-b43-installer), a name of firmware-nouveau-installer might work. Andreas
Bug#1001083: linux-headers-5.16.0-rc3-common: KBUILD_CFLAGS contains quoted string "-Wimplicit-fallthrough=5"
Source: linux Version: 5.16~rc3-1~exp1 Severity: important Control: block 1001007 with -1 KBUILD_CFLAGS in 5.16 contains a quoted string, and at some point of passing the flags through the build system of the kernel and third party modules, the quotes get "protected" and finally passed as part of an argument to gcc, which fails with gcc-11: error: "-Wimplicit-fallthrough=5": linker input file not found: No such file or directory This has so far been reported for the nvidia kernel module (#1001007), but I would expect that it can happen for other modules as well. The origin of this quoted value: it's a quoted string in .config: /usr/src/linux-headers-5.16.0-rc3-amd64/.config:CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5" /usr/src/linux-headers-5.16.0-rc3-common/Makefile:KBUILD_CFLAGS += $(KBUILD_CFLAGS-y) $(CONFIG_CC_IMPLICIT_FALLTHROUGH) Probably KBUILD_CFLAGS += $(KBUILD_CFLAGS-y) $(patsubst "%",%,$(CONFIG_CC_IMPLICIT_FALLTHROUGH)) would be sufficient to fix this. Andreas
Bug#987575: Acknowledgement (linux-kbuild-5.10: please add Breaks: sl-modem-dkms (<< 2.9.11~20110321-16.0))
Hi, while you are at it, you could also add Breaks: dahdi-dkms (<< 1:2.11.1.0.20170917~dfsg-7.0) since dahdi-dkms had a similar problem (#982334) which got fixed for bullseye. Andreas
Bug#987575: linux-kbuild-5.10: please add Breaks: sl-modem-dkms (<< 2.9.11~20110321-16.0)
Package: linux-kbuild-5.10 Version: 5.10.28-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + sl-modem-dkms Hi, during a test with piuparts I noticed sl-modem-dkms (buster) removes include/generated/autoconf.h that was installed by linux-headers-5.10.0-*-*. >From the attached log (scroll to the bottom...): debsums: missing file /usr/src/linux-headers-5.10.0-6-amd64/include/generated/autoconf.h (from linux-headers-5.10.0-6-amd64 package) sl-modem-dkms fails to build a module for Linux 5.10 (#983650) because it somehow manages to delete include/generated/autoconf.h while building the module. This also breaks building other dkms modules with very confusing error messages. This is unfixed in sid and sl-modem-dkms won't be in bullseye, so please ensure the obsolete package gets removed on upgrades before attempting to build a module for newer headers. The version I chose for the breaks will still work if this gets fixed in sl-modem-dkms either -17 or -16.1. cheers, Andreas sl-modem-dkms_None.log.gz Description: application/gzip
Bug#985743: firmware-qcom-soc: broken symlink: /lib/firmware/qcom/sdm845/wlanmdsp.mbn -> ../../ath10k/WCN3990/hw1.0/wlanmdsp.mbn
Package: firmware-qcom-soc Version: 20210315-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m15.9s ERROR: FAIL: Broken symlinks: /lib/firmware/qcom/sdm845/wlanmdsp.mbn -> ../../ath10k/WCN3990/hw1.0/wlanmdsp.mbn (firmware-qcom-soc) Is firmware-qcom-soc missing a dependency on firmware-atheros ? cheers, Andreas firmware-qcom-soc_20210315-1.log.gz Description: application/gzip
Bug#985740: firmware-brcm80211: broken symlink: /lib/firmware/brcm/brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt
Package: firmware-brcm80211 Version: 20210315-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m14.6s ERROR: FAIL: Broken symlinks: /lib/firmware/brcm/brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt (firmware-brcm80211) cheers, Andreas firmware-brcm80211_20210315-1.log.gz Description: application/gzip
Bug#975571: linux: No rule to make target 'scripts/module.lds' while building out-of-tree modules
Source: linux Version: 5.10~rc4-1~exp1 Severity: important Hi, building out-of-tree modules againt Linux 5.10 headers in experimental fails with No rule to make target 'scripts/module.lds', needed by '/path/to/module.ko'. Stop. e.g. make[3]: *** No rule to make target 'scripts/module.lds', needed by '/var/lib/dkms/r8168/8.048.03/build/r8168.ko'. Stop. make[4]: *** No rule to make target 'scripts/module.lds', needed by '/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko'. Stop. make[5]: *** No rule to make target 'scripts/module.lds', needed by '/usr/src/modules/nvidia-kernel/nvidia-drm.ko'. Stop. Andreas
Bug#966025: firmware-qcom-soc: missing Breaks+Replaces: firmware-qcom-media (<< 20200421)
Package: firmware-qcom-soc Version: 20200421-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../firmware-qcom-soc_20200421-1_all.deb ... Unpacking firmware-qcom-soc (20200421-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-qcom-soc_20200421-1_all.deb (--unpack): trying to overwrite '/lib/firmware/qcom/a300_pfp.fw', which is also in package firmware-qcom-media 20190114-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/firmware-qcom-soc_20200421-1_all.deb cheers, Andreas firmware-qcom-media=20190114-2_firmware-qcom-soc=20200421-1.log.gz Description: application/gzip
Bug#964234: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root
Source: dpkg,firmware-nonfree Version: 20190717-2 Severity: serious Tags: ftbfs Justification: fails to build from source Control: found -1 20190717-2 Control: found -1 1.20.3 Hi, src:firmware-nonfree fails to unpack in sid with latest dpkg: dpkg-source: info: extracting firmware-nonfree in firmware-nonfree-20190717 dpkg-source: info: unpacking firmware-nonfree_20190717.orig.tar.xz dpkg-source: info: unpacking firmware-nonfree_20190717-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying gitignore.patch Use of uninitialized value $canon_pathname in pattern match (m//) at /usr/share/perl5/Dpkg/Source/Package.pm line 550. dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root Since this could also be a dpkg error (see the perl warning before the failure) I'm assigning this bug to both packages, please reassign as appropriate. Andreas
Bug#928226: uninstallable cruft package
Package: firefox-esr-dev,thunderbird-dev,lightning-l10n-bn-bd,lightning-l10n-pa-in,lightning-l10n-ta-lk,thunderbird-l10n-bn-bd,thunderbird-l10n-pa-in,thunderbird-l10n-ta-lk,linux-headers-4.9.0-8-amd64,linux-headers-4.9.0-8-rt-amd64,iceweasel-l10n-ak,iceweasel-l10n-csb,iceweasel-l10n-ku,iceweasel-l10n-lg,iceweasel-l10n-nso,iceweasel-l10n-ta-lk,iceweasel-l10n-zu,iceweasel-l10n-be Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 firefox-esr/52.9.0esr-1~deb8u1 Control: found -1 firefox-esr/52.9.0esr-1~deb9u1 Control: found -1 thunderbird/1:52.9.1-1~deb8u1 Control: found -1 thunderbird/1:52.9.1-1~deb9u1 Control: found -1 linux/4.9.110-3+deb9u6 Control: found -1 iceweasel/1:17.0.10esr-1~deb7u1 Control: found -1 iceweasel/1:38.8.0esr-1~deb7u1 Control: close -1 This cruft package is no longer built by the current version of its source package, but the obsolete binaries are still lingering around in the (old)(old)stable/updates repository. This package is no longer installable since it has versioned dependencies on no longer available package versions built from its source package. This bug is intended for tracking these packages which fail their piuparts tests. Andreas
Bug#914966: linux-perf-4.19: missing Breaks+Replaces: linux-perf-4.18
Package: linux-perf-4.19 Version: 4.19.5-1~exp1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../linux-perf-4.19_4.19.5-1~exp1_amd64.deb ... Unpacking linux-perf-4.19 (4.19.5-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/linux-perf-4.19_4.19.5-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/perf/examples/bpf/5sec.c', which is also in package linux-perf-4.18 4.18.20-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-perf-4.19_4.19.5-1~exp1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/perf/examples/bpf/5sec.c usr/lib/perf/examples/bpf/empty.c usr/lib/perf/include/bpf/bpf.h Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html linux-perf-4.18=4.18.20-2_linux-perf-4.19=4.19.5-1~exp1.log.gz Description: application/gzip
Bug#910207: linux-headers-4.18.0-*: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Source: linux
Version: 4.18.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + linux-headers-4.18.0-1-amd64
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>From the attached log (scroll to the bottom...):
0m31.8s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/linux-headers-4.18.0-1-amd64/changelog.Debian.gz
(linux-headers-4.18.0-1-amd64) !=
/usr/share/doc/linux-headers-4.18.0-1-common/changelog.Debian.gz
(linux-headers-4.18.0-1-common)
/usr/share/doc/linux-headers-4.18.0-1-amd64 -> linux-headers-4.18.0-1-common
/usr/share/doc/linux-headers-4.18.0-1-amd64/copyright
(linux-headers-4.18.0-1-amd64) !=
/usr/share/doc/linux-headers-4.18.0-1-common/copyright
(linux-headers-4.18.0-1-common)
/usr/share/doc/linux-headers-4.18.0-1-amd64 -> linux-headers-4.18.0-1-common
This seems to happen in all linux-headers-VERSION-ABI-FLAVOR packages.
(This will probably resolve automatically with the next ABI bump.)
cheers,
Andreas
linux-headers-4.18.0-1-amd64_4.18.8-1.log.gz
Description: application/gzip
Bug#903778: linux-image-amd64-signed-template: copyright file missing (policy 12.5)
Package: linux-image-amd64-signed-template Version: 4.18~rc4-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/#copyright-information >From the attached log (scroll to the bottom...): 0m28.3s ERROR: WARN: Inadequate results from running adequate! linux-image-amd64-signed-template: missing-copyright-file /usr/share/doc/linux-image-amd64-signed-template/copyright MISSING COPYRIGHT FILE: /usr/share/doc/linux-image-amd64-signed-template/copyright # ls -lad /usr/share/doc/linux-image-amd64-signed-template ls: cannot access '/usr/share/doc/linux-image-amd64-signed-template': No such file or directory # ls -la /usr/share/doc/linux-image-amd64-signed-template/ ls: cannot access '/usr/share/doc/linux-image-amd64-signed-template/': No such file or directory cheers, Andreas linux-image-amd64-signed-template_4.18~rc4-1~exp1.log.gz Description: application/gzip
Bug#720528: nvidia: driver fails kernel 3.10+ (GeForce 600M and 700M series)
Control: tag -1 moreinfo On Sat, 23 Aug 2014 22:53:48 -0700 Ben Hutchings wrote: > On Sat, 2014-08-23 at 20:14 -0700, Andres Cimmarusti wrote: > > Let me re-state: worked with debian 3.9, broke with debian 3.11 (but > > works with Ubuntu vanilla LTS 3.11.10.x series), worked with debian > > 3.12, broke again with debian 3.13 (but worked again with Ubuntu > > vanilla LTS 3.13.11.x series) and finally doesn't work with debian > > 3.14 and also not with 3.15, I have yet to try 3.16. > > My guess is that a configuration option I'm using (processor timer > > frequency 1000 Hz) when building the Ubuntu vanilla LTS kernels is > > doing the trick, but then again I don't know why debian 3.12 did work. > > Could this faster 1000 Hz vs 250 Hz (default in debian) have anything > > to do with this ACPI issue Nvidia reported... Is this still an issue with the latest driver (390.67) and kernels available in sid, buster, and stretch-backports? Andreas
Bug#872263: linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports
Package: linux-image-4.11.0-1-amd64-dbg Version: 4.11.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + linux-image-amd64-dbg Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch-backports'. It installed fine in 'stretch-backports', then the upgrade to 'buster' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package linux-image-4.11.0-1-amd64-dbg. Preparing to unpack .../linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb ... Unpacking linux-image-4.11.0-1-amd64-dbg (4.11.6-1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/debug/.build-id/25/99e5c063eeb45c3b0068e66a8251a66f313afa.debug', which is also in package linux-image-4.11.0-0.bpo.1-amd64-dbg 4.11.6-1~bpo9+1 Preparing to unpack .../linux-image-amd64-dbg_4.11+82_amd64.deb ... Unpacking linux-image-amd64-dbg (4.11+82) over (4.11+82~bpo9+1) ... Errors were encountered while processing: /var/cache/apt/archives/linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb cheers, Andreas linux-image-amd64-dbg_4.11+82.log.gz Description: application/gzip
Bug#822671: initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie
Followup-For: Bug #822671
Control: tag -1 patch
Hi Ben,
attached is a patch that improves the handling of initramfs.conf
That's a lot of code - but most of it was stolen from
dpkg-maintscript-helper :-) (preinst/postrm from rm_conffile, postinst
from from mv_conffile with slight modifications)
It's currently set to be very verbose: mvverbose=-v
that should be changed to mvverbose=#-v for production.
There is also a 1-line .maintscript file being added that takes care of
/etc/bash_completion.d/initramfs-tools conffile removal
This passed a piuparts jessie -> stretch upgrade (unmodified conffile)
and a manual jessie -> stretch upgrade with a modified conffile.
Andreas
diff -Nru initramfs-tools-0.125/debian/initramfs-tools-core.postinst initramfs-tools-0.125+nmu1/debian/initramfs-tools-core.postinst
--- initramfs-tools-0.125/debian/initramfs-tools-core.postinst 2016-04-17 21:39:22.0 +0200
+++ initramfs-tools-0.125+nmu1/debian/initramfs-tools-core.postinst 2016-04-30 20:41:44.0 +0200
@@ -7,15 +7,57 @@
> /etc/initramfs-tools/modules
fi
+mvverbose=-v
+
+# from dpkg-maintscript-helper
+ensure_package_owns_file() {
+ local PACKAGE="$1"
+ local FILE="$2"
+
+ if ! dpkg-query -L "$PACKAGE" | grep -q -x "$FILE"; then
+ debug "File '$FILE' not owned by package " \
+ "'$PACKAGE', skipping $command"
+ return 1
+ fi
+ return 0
+}
+
+# from dpkg-maintscript-helper
+debug() {
+ if [ -n "$DPKG_DEBUG" ]; then
+ echo "DEBUG: $PROGNAME: $*" >&2
+ fi
+}
+
+# from dpkg-maintscript-helper, modified
+finish_mv_conffile() {
+ local OLDCONFFILE="$1"
+ local NEWCONFFILE="$2"
+ local PACKAGE="$3"
+
+ rm $mvverbose -f $NEWCONFFILE.dpkg-remove
+
+ [ -e "$OLDCONFFILE" ] || return 0
+ #ensure_package_owns_file "$PACKAGE" "$OLDCONFFILE" || return 0
+ ensure_package_owns_file "$PACKAGE" "$NEWCONFFILE" || return 0
+
+ echo "Preserving user changes to $NEWCONFFILE (renamed from $OLDCONFFILE)..."
+ if [ -e "$NEWCONFFILE" ]; then
+ mv $mvverbose -f "$NEWCONFFILE" "$NEWCONFFILE.dpkg-new"
+ fi
+ mv $mvverbose -f "$OLDCONFFILE" "$NEWCONFFILE"
+}
+
# When installing as a new dependency of initramfs-tools, or upgrading
# from <0.123, we need to move initramfs.conf back into place.
-if [ "$1" = configure ] && dpkg --compare-versions "$2" lt 0.123~ && \
- [ -f /etc/initramfs-tools/initramfs.conf.dpkg-backup ]; then
- # On fresh installation ($2 is empty), overwrite the shipped
- # initramfs.conf. Otherwise use -n to avoid overwriting user
- # configuration if somehow both files exist.
- mv ${2:+-n} /etc/initramfs-tools/initramfs.conf.dpkg-backup \
- /etc/initramfs-tools/initramfs.conf
+LASTVERSION=0.123~
+CONFFILE=/etc/initramfs-tools/initramfs.conf
+PACKAGE=initramfs-tools-core
+OLDCONFFILE="$CONFFILE.dpkg-backup"
+NEWCONFFILE="$CONFFILE"
+if [ "$1" = "configure" ] &&
+ dpkg --compare-versions "$2" le "$LASTVERSION"; then
+ finish_mv_conffile "$OLDCONFFILE" "$NEWCONFFILE" "$PACKAGE"
fi
#DEBHELPER#
diff -Nru initramfs-tools-0.125/debian/initramfs-tools.maintscript initramfs-tools-0.125+nmu1/debian/initramfs-tools.maintscript
--- initramfs-tools-0.125/debian/initramfs-tools.maintscript 1970-01-01 01:00:00.0 +0100
+++ initramfs-tools-0.125+nmu1/debian/initramfs-tools.maintscript 2016-04-30 20:41:44.0 +0200
@@ -0,0 +1 @@
+rm_conffile /etc/bash_completion.d/initramfs-tools 0.126~
diff -Nru initramfs-tools-0.125/debian/initramfs-tools.postinst initramfs-tools-0.125+nmu1/debian/initramfs-tools.postinst
--- initramfs-tools-0.125/debian/initramfs-tools.postinst 2016-04-17 21:39:22.0 +0200
+++ initramfs-tools-0.125+nmu1/debian/initramfs-tools.postinst 2016-04-30 20:41:44.0 +0200
@@ -2,12 +2,57 @@
set -e
+mvverbose=-v
+
+# from dpkg-maintscript-helper
+ensure_package_owns_file() {
+ local PACKAGE="$1"
+ local FILE="$2"
+
+ if ! dpkg-query -L "$PACKAGE" | grep -q -x "$FILE"; then
+ debug "File '$FILE' not owned by package " \
+ "'$PACKAGE', skipping $command"
+ return 1
+ fi
+ return 0
+}
+
+# from dpkg-maintscript-helper
+debug() {
+ if [ -n "$DPKG_DEBUG" ]; then
+ echo "DEBUG: $PROGNAME: $*" >&2
+ fi
+}
+
+# from dpkg-maintscript-helper, modified
+finish_mv_conffile() {
+ local OLDCONFFILE="$1"
+ local NEWCONFFILE="$2"
+ local PACKAGE="$3"
+
+ rm $mvverbose -f $NEWCONFFILE.dpkg-remove
+
+ [ -e "$OLDCONFFILE" ] || return 0
+ #ensure_package_owns_file "$PACKAGE" "$OLDCONFFILE" || return 0
+ ensure_package_owns_file "$PACKAGE" "$NEWCONFFILE" || return 0
+
+ echo "Preserving user changes to $NEWCONFFILE (renamed from $OLDCONFFILE)..."
+ if [ -e "$NEWCONFFILE" ]; then
+ mv $mvverbose -f "$NEWCONFFILE" "$NEWCONFFILE.dpkg-new"
+ fi
+ mv $mvverbose -f "$OLDCONFFILE" "$NEWCONFFILE"
+}
+
# If initramfs-tools-core was fully upgraded to 0.123 before our
# preinst ran, we need to move initramfs.conf back into place.
-if [ "$1" = configure ] && [ -n "$2" ] && dpkg --compare-versions "$2" lt 0.123~ && \
- [ -f /etc/initramfs-tools/initramfs.conf.dpkg-backup ]; then
- mv -n
Bug#822671: initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie
Package: initramfs-tools Version: 0.125 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package causes some trouble with /etc/initramfs-tools/initramfs.conf upon upgrades from jessie: 1m18.3s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/initramfs-tools/initramfs.conf Rerunning the test manually and analyzing the situation lead to this conclusion: The initramfs.conf from jessie is always preserved, regardless of whether it contained user modifications. This will cause a dpkg modified-conffile prompt the next time an upgrade to initramfs-tools-core with an updated version of that conffile is performed. (This is a policy violation if the conffile was not modified by the admin.) Taking over conffiles (and modifying them at the same time) is not an easy task :-) You probably need to do something even more resembling dpkg-maintscript-helper mv_conffile in your maintainer scripts, quoting from the manpage: Current implementation: the preinst checks if the conffile has been modified, if yes it's left on place otherwise it's renamed to old-conffile.dpkg-remove. On configuration, the postinst removes old- conffile.dpkg-remove and renames old-conffile to new-conffile if old-conffile is still available. On abort-upgrade/abort-install, the postrm renames old-conffile.dpkg-remove back to old-conffile if required. You currently use .dpkg-backup for the old conffile, but you should probably use .dpkg-remove instead *if the old conffile was unmodified*. The postinst should then probably move .dpkg-backup back (as done now), delete .dpkg-remove. And in the abort-upgrade case, you have two choices to restore (but only one will exist). There is probably no easy way to recover systems that have upgraded from jessie (with pristine initramfs.conf) to stretch. (To avoid unneccessary future dpkg prompting.) (Maybe: compare md5sum againt the version shipped in jessie, restore the conffile from /usr/share/initramfsfoo in case that matches ...) Andreas
Bug#821741: linux-perf-4.6: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/perf-tip/tips.txt
Package: linux-perf-4.6 Version: 4.6~rc3-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package linux-perf-4.6. Preparing to unpack .../linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb ... Unpacking linux-perf-4.6 (4.6~rc3-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/perf-tip/tips.txt', which is also in package linux-perf-4.5 4.5.1-1 Errors were encountered while processing: /var/cache/apt/archives/linux-perf-4.6_4.6~rc3-1~exp1_amd64.deb cheers, Andreas linux-perf-4.5=4.5.1-1_linux-perf-4.6=4.6~rc3-1~exp1.log.gz Description: application/gzip
Bug#816500: linux-tools: should not migrate to testing before the corresponding src:linux
Source: linux-tools Version: 4.4-4 Severity: important Hi, new major upstream releases (e.g. 4.4) of src:linux and src:linux-tools should migrate together to testing. Right now src:linux-tools 4.4-4 is already in testing, which doesn't look too useful to me without src:linux 4.4.x-y. Does any of the binary packages built from linux-tools have a dependency on something from src:linux that could be made versioned? Or add a linux-tools-dummy package which Depends: linux-source-X.Y Andreas
Bug#783449: linux-image-3.16.0-0.bpo.4-amd64: Xorg fails to start with Radeon HD 7600M on Vostro 3560 after upgrade to 3.16
(this bug should probably be reassigned to fglrx-driver) On 2016-02-22 07:26, Vincas Dargis wrote: > P.S. My other registered bug #783449 still applies - I can't use backported > fglrx with backported Linux 3.16 on Wheezy. Does that conbination even build the kernel module? Old drivers ususally don't work on newer kernels ... The wheezy backport just got updated to 15.9 to follow the update in jessie, maybe that helps. You may get a file conflict with xvba-va-driver, it's safe to deinstall that package (that functionality now comes with fglrx-driver). Andreas
Bug#813080: linux-perf-4.4: fails to upgrade from 'sid' - trying to overwrite /usr/share/perf-core/strace/groups/file
Package: linux-perf-4.4 Version: 4.4-1~exp2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package linux-perf-4.4. Preparing to unpack .../linux-perf-4.4_4.4-1~exp2_amd64.deb ... Unpacking linux-perf-4.4 (4.4-1~exp2) ... dpkg: error processing archive /var/cache/apt/archives/linux-perf-4.4_4.4-1~exp2_amd64.deb (--unpack): trying to overwrite '/usr/share/perf-core/strace/groups/file', which is also in package linux-perf-4.3 4.3.1-2 Errors were encountered while processing: /var/cache/apt/archives/linux-perf-4.4_4.4-1~exp2_amd64.deb cheers, Andreas
Bug#810154: remove busybox hook, leave responsibility to busybox package
Followup-For: Bug #810154 Control: found -1 0.121~rc2 Control: severity -1 serious Right now the default configuration in experimental is broken: * busybox is enabled by default * missing busybox is a hard failure * nothing depends on busybox as noticed by piuparts: [...] Selecting previously unselected package initramfs-tools-core. Preparing to unpack .../initramfs-tools-core_0.121~rc2_all.deb ... Unpacking initramfs-tools-core (0.121~rc2) ... Selecting previously unselected package initramfs-tools. Preparing to unpack .../initramfs-tools_0.121~rc2_all.deb ... Unpacking initramfs-tools (0.121~rc2) ... [...] Setting up initramfs-tools-core (0.121~rc2) ... Setting up initramfs-tools (0.121~rc2) ... update-initramfs: deferring update (trigger activated) Setting up piuparts-depends-dummy (0.invalid.0) ... Processing triggers for systemd (228-3) ... Processing triggers for libc-bin (2.22-0experimental1) ... Processing triggers for initramfs-tools (0.121~rc2) ... Selecting previously unselected package linux-image-4.4.0-rc8-amd64. (Reading database ... (Reading database ... 7678 files and directories currently installed.) Preparing to unpack .../linux-image-4.4.0-rc8-amd64_4.4~rc8-1~exp1_amd64.deb ... Unpacking linux-image-4.4.0-rc8-amd64 (4.4~rc8-1~exp1) ... Setting up linux-image-4.4.0-rc8-amd64 (4.4~rc8-1~exp1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.4.0-rc8-amd64 E: busybox is required but not installed E: /usr/share/initramfs-tools/hooks/busybox failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-rc8-amd64 with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-rc8-amd64.postinst line 634, line 2. dpkg: error processing package linux-image-4.4.0-rc8-amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-4.4.0-rc8-amd64 Andreas
Bug#774436: linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1
Package: src:linux Version: 3.2.65-1 Severity: important sorry for the brief report (and running the wrong kernel) there seems to be a suspend2ram regression in 3.2.65-1, suspending works, but resuming seems to reset inbetween and reboot regularily. I'm now back to 3.2.63-2+deb7u2 which works fine. Offline for a few days before I could do more testing. Andreas -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2+deb7u2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=634eb47e-814e-4e4d-a558-5259b7fb0823 ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 566.999750] i915 :00:02.0: power state changed by ACPI to D0 [ 566.999885] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [ 566.29] xhci_hcd :00:14.0: power state changed by ACPI to D0 [ 566.50] xhci_hcd :00:14.0: setting latency timer to 64 [ 567.43] e1000e :00:19.0: wake-up capability disabled by ACPI [ 567.64] e1000e :00:19.0: setting latency timer to 64 [ 567.000154] e1000e :00:19.0: irq 41 for MSI/MSI-X [ 567.000200] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [ 567.000211] snd_hda_intel :00:1b.0: setting latency timer to 64 [ 567.000279] ahci :00:1f.2: setting latency timer to 64 [ 567.000291] snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X [ 567.000307] i915 :00:02.0: power state changed by ACPI to D0 [ 567.000316] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [ 567.000325] i915 :00:02.0: setting latency timer to 64 [ 567.000332] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [ 567.000353] ehci_hcd :00:1a.0: setting latency timer to 64 [ 567.000365] ehci_hcd :00:1d.0: setting latency timer to 64 [ 567.012602] sd 0:0:0:0: [sda] Starting disk [ 567.052598] firewire_core: skipped bus generations, destroying all nodes [ 567.075865] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 567.228474] usb 3-4: reset high-speed USB device number 5 using xhci_hcd [ 567.244429] usb 3-4: device firmware changed [ 567.316360] usb 1-1.4: reset full-speed USB device number 5 using ehci_hcd [ 567.340087] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 567.340121] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 567.340916] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 567.340924] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 567.341567] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 567.341574] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 567.341877] ata1.00: configured for UDMA/133 [ 567.348031] ata5: SATA link down (SStatus 0 SControl 300) [ 567.352529] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded [ 567.359055] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded [ 567.372694] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded [ 567.378956] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded [ 567.384805] ata2.00: configured for UDMA/100 [ 567.410068] btusb 1-1.4:1.0: no reset_resume for driver btusb? [ 567.410074] btusb 1-1.4:1.1: no reset_resume for driver btusb? [ 567.480072] usb 1-1.6: reset high-speed USB device number 6 using ehci_hcd [ 567.499886] sdhci-pci :02:00.0: setting latency timer to 64 [ 567.551779] firewire_core: rediscovered device fw0 [ 567.793847] PM: resume of devices complete after 795.554 msecs [ 567.794441] PM: Finishing wakeup. [ 567.794445] Restarting tasks ... done. [ 567.796898] video LNXVIDEO:00: Restoring backlight state [ 567.798500] video LNXVIDEO:01: Restoring backlight state [ 567.807331] usb 3-4: USB disconnect, device number 5 [ 567.808984] cdc_ncm 3-4:1.6: usb0: unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM [ 567.824457] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88042a5174c0 [ 567.824466] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88042a517500 [ 567.824473] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88042a517d40 [ 567.824479] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88042a517d80 [ 567.824486] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88042a517440 [ 567.824492] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88042a517480 [ 567.824498] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880420ec2b80 [ 567.824505] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8804176302c0 [ 567.824512] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880417630300 [ 567.824519] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep
Bug#724569: Virtual package linux-image should be removed
Hi Ben, On Wednesday, 25. September 2013 06:42:06 Ben Hutchings wrote: Further, any level of dependency (Depends, Recommends or Suggests) on 'linux-image' prevents APT auto-removing any of the packages that provide it, making any use of the virtual package actually harmful. I opened bugs on all the packages that do recommend or suggest linux-image (none depend on it): I don't think they need to block this bug, as removing the Provides won't make them unininstallable. linux (3.11.5-1) unstable; urgency=low [ Ben Hutchings ] * Stop providing virtual packages linux-image (Closes: #724569), linux-headers and linux-source Dropping the linux-headers virtual package has made several *-dkms packages uninstallable: west-chamber-dkms (0, 0) (Ying-Chun Liu (PaulLiu) paul...@debian.org) dependency linux-headers-generic is does-not-exist alternative dependency linux-headers is does-not-exist blcr-dkms (0, 0) (Alan Woodland awoodl...@debian.org) dependency linux-headers-2.6-686 is does-not-exist alternative dependency linux-headers-2.6-amd64 is does-not-exist alternative dependency linux-headers-generic is does-not-exist alternative dependency linux-headers is does-not-exist (I just rescheduled all dkms packages in sid to see if there are more affected.) Please file RC bugs giving advice how to adjust this dependency properly. Or reinstate that virtual package. Andreas -- 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/201310292138.12459.a...@debian.org
Bug#701690: nvidia: disagrees about version of symbol efi_enabled
On 2013-02-27 06:53, Antti Salmela wrote: On Tue, Feb 26, 2013 at 10:54:42PM +0100, Andreas Beckmann wrote: On Tue, 2013-02-26 at 10:35 +0200, Antti Salmela wrote: ABI seems to have changed with the latest 3.2.39-1 kernel. Proprietary nvidia driver (313.18-2) from experimental fails to load if compiled against previous (or maybe even original...) linux-headers-3.2.0-4-amd64 packages, but works after recompile. Antti, did you use the -dkms package or the -source package and module-assistant? -dkms package. That's weird. The module should have been rebuilt after updating the linux-headers-* package. Or did you only update linux-image-* and keep the old linux-headers-*? Andreas -- 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/512e76de.6020...@debian.org
Bug#701690: nvidia: disagrees about version of symbol efi_enabled
On 2013-02-26 14:44, Ben Hutchings wrote: On Tue, 2013-02-26 at 13:24 +, Ben Hutchings wrote: On Tue, 2013-02-26 at 10:35 +0200, Antti Salmela wrote: ABI seems to have changed with the latest 3.2.39-1 kernel. Proprietary nvidia driver (313.18-2) from experimental fails to load if compiled against previous (or maybe even original...) linux-headers-3.2.0-4-amd64 packages, but works after recompile. Antti, did you use the -dkms package or the -source package and module-assistant? [ 14.383562] nvidia: module license 'NVIDIA' taints kernel. [ 14.386689] nvidia: disagrees about version of symbol efi_enabled [ 14.386692] nvidia: Unknown symbol efi_enabled (err -22) [...] Sorry, I ignored this ABI change because codesearch.debian.net didn't show the symbol being used by out-of-tree modules. Perhaps it doesn't include non-free code, or this was changed between unstable and experimental. Oh, now I see, the code is packaged up in a way that can't be searched. Ben. I'll see what I can do to fix this. (And unfortunately if the change is reverted then you'll need to rebuild the module again.) Ben, Should I upload nvidia-graphics-modules rebuilt against 3.2.39-1? Andreas -- 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/512d2f22.7080...@debian.org
Bug#701690: nvidia: disagrees about version of symbol efi_enabled
On 2013-02-26 23:42, Ben Hutchings wrote:
I'll see what I can do to fix this. (And unfortunately if the change is
reverted then you'll need to rebuild the module again.)
Ben, Should I upload nvidia-graphics-modules rebuilt against 3.2.39-1?
No, I believe I can fix this.
Also, if you rebuild without changing the nvidia source you'll
introduce a bug, because the test of efi_enabled will always return
true now that it's the name of a function...
nvidia-kernel-{source,dkms} don't use upstream's conftest.sh to test for
availability of features, instead we ship (probably for historic reasons
where conftest.sh was not working properly) a manually generated
conftest.h that says
/* Implement conftest.sh function efi_enabled */
#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,1)
#define NV_EFI_ENABLED_PRESENT
#else
#undef NV_EFI_ENABLED_PRESENT
#endif
Anyway, checks for efi.h and efi_enabled were only introduced in 310.14
and have not been backported to the 304.xx series by Nvidia so far. So
this only affects the Nvidia driver in experimental.
Andreas
--
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/512d3fa2.8050...@debian.org
Re: autobuilding src:nvidia-* [non-free]
I'm afraid, this is getting a bit off-topic ... On 2012-08-06 23:28, Philipp Kern wrote: I'm a bit confused why that is. If I'm installing a nvidia-graphics-driver package that does all the magic using dkms at install time, how is that more sophisticated than providing pre-built module packages, There are a few people that don't like the dkms way (to many dependencies: compiler, kernel headers; leaves cruft around (I tried to fix a bit of this in my dkms NMU); ) and prefer to take the responsibility to provide their own kernel module packages for local deployment. So with the current state a foo-dkms package is an alternative to foo-source, but not a replacement for it. But I think there were enough threads about this topic already, no need to start a new one ... especially in the light that it's the only one left doing it that way? (Why isn't it the same for fglrx? unfortunately the license does not permit distribution of precompiled kernel modules Where's that 3.2.0-3 module for virtualbox?) in my private repository :-) I have a generic branch of nvidia-graphics-modules.git with all the nvidia specific bits made configurable that can be used to quickly build module packages with module-assistant for any foo-source package (tested with fglrx-source and virtualbox-source on i386 and amd64), if anyone is interested, I can push this somewhere. Nice way for getting prebuilt modules (+ corresponding meta-packages) into a local repository. Andreas PS: I also maintain r8168-dkms which is dkms only (and only in sid) - primarily to get some more experience with dkms ... -- 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/502045d7.6000...@abeckmann.de
Re: autobuilding src:nvidia-* [non-free]
On 2012-08-06 19:32, Ben Hutchings wrote: There is actually no attempt to check or maintain ABI stability for packages with the rt featureset (or openvz or vserver, in squeeze), as their stable updates have been comparatively less stable. This fact hasn't been advertised nearly as widely as it should be. In that case we should probably drop the RT prebuilt modules (like we did for openvz and xen in squeeze) - or do semi-automatic binNMUs whenever a new linux_3.2* gets out. I think we should do better and actually change the ABI numbers per-featureset, as the current arrangement obviously works really badly with OOT modules. But it will require more trips through NEW and more linux-latest updates. (I'm a little sceptical that many OOT modules work properly with rt, but let's assume some of them do.) I think nvidia works with RT, although I haven't tried this myself. I picked up a patch from arch linux earlier this year that worked around some GPL-only symbols getting pulled in by the RT patch, but that is no longer neccessary. Andreas -- 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/502048d9.6060...@abeckmann.de
Bug#624297: closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#681011: Removed package(s) from unstable)
reassign 624297 linux-tools reopen 624297 severity 624297 wishlist thanks that should not be forgotten, although the patch probably needs updating for 3.X Andreas -- 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/4ffc2669.2090...@abeckmann.de
Bug#624297: build-linux-kbuild.sh: add support for -rcX kernels (needs version mangling)
Package: linux-kbuild-2.6
Severity: normal
Tags: patch
Hi,
attached is a patch for the build-linux-kbuild.sh referenced from
http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage
It adds support for -rcX kernels by doing version mangling from -rcX to
~rcX as needed by Debian.
Also it would be nice if the build-linux-kbuild.sh would be kept in the
SVN repository and a comment like the following be added to the script:
# The latest version of this script can be retrived via
# svn export URL/build-linux-kbuild.sh
Andreas
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (500,
'stable-updates'), (130, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- build-linux-kbuild.orig.sh 2010-11-12 17:55:22.0 +0100
+++ build-linux-kbuild.sh 2011-04-27 08:50:17.770352638 +0200
@@ -9,11 +9,12 @@
# changelog)
set -ex
-VERSION=2.6.36
+UPSTREAM_VERSION=2.6.39-rc4
+VERSION=$(echo ${UPSTREAM_VERSION} | sed -e 's/-rc/~rc/')
DEBIAN_VERSION=${VERSION}-1~experimental.1
CHANGELOG_MESSAGE=${VERSION}
-[ -e linux-${VERSION}.tar.bz2 ]
+[ -e linux-${UPSTREAM_VERSION}.tar.bz2 ]
cleanme=orig linux-kbuild-2.6 linux-kbuild-2.6-${VERSION}
@@ -31,7 +32,7 @@
cd linux-kbuild-2.6
dch -v ${DEBIAN_VERSION} ${CHANGELOG_MESSAGE}
-./debian/bin/genorig.py ../linux-${VERSION}.tar.bz2
+./debian/bin/genorig.py ../linux-${UPSTREAM_VERSION}.tar.bz2
cd ..
tar -xzf orig/linux-kbuild-2.6_${VERSION}.orig.tar.gz
cd linux-kbuild-2.6-${VERSION}
Bug#624297: ship build-linux-kbuild.sh in the documentation of the linux-kbuild-KVERS binary package
Hi, I also suggest to add the build-linux-kbuild.sh script to the documentation of the linux-kbuild-KVERS binary packages, that way it should be easy to find for the people that need a current version of the linux-kbuild-KVERS package to build modules for the latest kernel in experimental. Andreas -- 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/4db84a78.5070...@abeckmann.de
Bug#575283: /usr/sbin/update-initramfs: treats kernel version 2.6.32-trunk-amd64 as newer than 2.6.32-3-amd64
Package: initramfs-tools Version: 0.93.4 Severity: normal File: /usr/sbin/update-initramfs Hi, update-initramfs considers linux-image-2.6.32-trunk-amd64 to be newer than linux-image-2.6.32-3-amd64 causing the initrd of an outdated kernel to be updated. Even though the 2.6.32-trunk kernels are no longer available in the archive, they are probably installed on some machines tracking sid or squeeze and are not going to be removed automatically (that is a good thing), so they will continue to confuse update-initramfs unless they are uninstalled manually. From popcon I got the following counts: $ zgrep image-2.6.32-trunk all-popcon-results.txt.gz | sort -nr -k 3 Package: linux-image-2.6.32-trunk-6864075 756 313 7 Package: linux-image-2.6.32-trunk-amd64 2907 611 200 6 So there seems to be a significant amount of machines having them still installed (only looking at the main variants amd64 and 686). See also bugs #568160 and #570318 covering grub-legacy/grub2 to wrongly sort the -trunk kernel ahead of the newer kernels. Andreas -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-1 GNU cpio -- a program to manage ar ii findutils4.4.2-1 utilities for finding files--find, ii klibc-utils 1.5.15-1small utilities built with klibc f ii module-init-tools3.12~pre2-1 tools for managing Linux kernel mo ii udev 151-3 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.14.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 Archive: http://lists.debian.org/20100324180716.21446.73279.report...@calzone.localnet
Bug#572123: may be fixed in 2.6.33.1
According to the changelog of 2.6.33.1 there have been some off-by-one errors fixed that may have caused this behaviour: commit a5489ec13965fc30adbf309a066242e25be4424a Author: Jean Delvare kh...@linux-fr.org Date: Fri Mar 5 22:17:26 2010 +0100 hwmon: Fix off-by-one kind values commit dc71afe5ac7e8d049bb991330518e4c898a7d92e upstream. Recent changes on the I2C front have left off-by-one array indexes in 3 hwmon drivers. Fix them. Faulty commit: e5e9f44c2 i2c: Drop I2C_CLIENT_INSMOD_2 to 8 Reported-by: Dan Carpenter erro...@gmail.com Signed-off-by: Jean Delvare kh...@linux-fr.org Cc: Hans de Goede hdego...@redhat.com Cc: Andre Prendel andre.pren...@gmx.de Signed-off-by: Greg Kroah-Hartman gre...@suse.de http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=dc71afe5ac7e8d049bb991330518e4c898a7d92e I can't test this right now as I'm currently on a trip but I'll keep you informed about the outcome of a kernel update once I'm in physical range of such a machine again end of next week. Andreas -- 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/4ba0de32.9020...@abeckmann.de
Bug#572123: may be fixed in 2.6.33.1
maximilian attems wrote: well this is a regression fix, so not applyable to 2.6.32. I didn't have any problems regarding fschmd with 2.6.32 (ABI -2 was the latest version I tested). Andreas -- 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/4ba1013c.2000...@abeckmann.de
Bug#573483: linux-kbuild-2.6: please upload 2.6.33 to experimental
Package: linux-kbuild-2.6 Severity: normal Hi, please build a new version of linux-kbuild-2.6 for 2.6.33 and upload it to experimental to accompany the 2.6.33 kernel there. That way we can build kernel modules for 2.6.33 and give the new kernel more testing. Thanks. Andreas -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100311194734.20522.96242.report...@chili.ae.cs.uni-frankfurt.de
Bug#572123: linux-image-2.6.33-2-amd64: loading fschmd module reboots the machine
Package: linux-2.6 Version: 2.6.33-1~experimental.2 Severity: normal Hi, something is broken with the fschmd module in 2.6.33, once the module is loaded the machine reboots immediately. Also on the serial console there is no output from the module except for (sometimes) a timestamp starting a truncated message. If you need more information, please let me know. Andreas -- Package-specific info: ** Version: Linux version 2.6.33-2-amd64 (Debian 2.6.33-1~experimental.2) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Sun Feb 28 18:30:42 UTC 2010 ** Command line: root=UUID=bfc4d8de-5304-4285-adf0-1a5f7f57e765 ro console=tty0 console=ttyS0,115200n8 ** Not tainted ** Kernel log: [3.309687] sda: sda1 sda2 sda3 [3.326628] input: USB Keyboard as /devices/pci:00/:00:1a.1/usb2/2-2/2-2:1.0/input/input1 [3.326671] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-:00:1a.1-2/input0 [3.333581] sda5 [3.353597] Uniform CD-ROM driver Revision: 3.20 [3.358338] sr 2:0:0:0: Attached scsi CD-ROM sr0 [3.358434] sd 0:0:0:0: [sda] Attached SCSI disk [3.372848] sd 0:0:0:0: Attached scsi generic sg0 type 0 [3.378240] sr 2:0:0:0: Attached scsi generic sg1 type 5 [3.435526] input: USB Keyboard as /devices/pci:00/:00:1a.1/usb2/2-2/2-2:1.1/input/input2 [3.444659] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID v1.10 Device [ USB Keyboard] on usb-:00:1a.1-2/input1 [3.456122] usbcore: registered new interface driver usbhid [3.461733] usbhid: USB HID core driver [3.849364] device-mapper: uevent: version 1.0.3 [3.854181] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-de...@redhat.com [3.870378] PM: Starting manual resume from disk [3.875447] PM: Resume from partition 8:2 [3.875448] PM: Checking hibernation image. [3.875577] PM: Error -22 checking image file [3.875579] PM: Resume from disk failed. [3.883284] REISERFS (device sda1): found reiserfs format 3.6 with standard journal [3.891601] REISERFS (device sda1): using ordered data mode [3.929610] REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [3.945203] REISERFS (device sda1): checking transaction log (sda1) [3.991520] REISERFS (device sda1): Using r5 hash to sort names [6.135026] udevd version 125 started [6.482635] EDAC MC: Ver: 2.1.0 Feb 28 2010 [6.704201] EDAC MC0: Giving out device to 'x38_edac' 'x38': DEV :00:00.0 [6.821417] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [6.830412] ACPI: Power Button [PWRB] [6.846189] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [6.872169] ACPI: Power Button [PWRF] [7.230071] i801_smbus :00:1f.3: PCI INT B - GSI 19 (level, low) - IRQ 19 [8.127185] HDA Intel :00:1b.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [8.134538] alloc irq_desc for 30 on node -1 [8.134540] alloc kstat_irqs on node -1 [8.134551] HDA Intel :00:1b.0: irq 30 for MSI/MSI-X [8.134586] HDA Intel :00:1b.0: setting latency timer to 64 [8.336169] hda_codec: ALC262: BIOS auto-probing. [8.342099] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input5 [ 83.411874] Adding 7815612k swap on /dev/sda2. Priority:-1 extents:1 across:7815612k [ 92.353447] loop: module loaded [ 92.996100] fuse init (API version 7.13) [ 93.141444] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 93.152693] SGI XFS Quota Management subsystem [ 93.167912] XFS mounting filesystem sda5 [ 93.256338] Ending clean XFS mount for filesystem: sda5 [ 94.060633] ip_tables: (C) 2000-2006 Netfilter Core Team [ 94.474674] Netfilter messages via NETLINK v0.30. [ 94.516043] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 94.520753] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 94.522347] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 94.529799] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 94.537764] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 94.576603] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 94.577507] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 95.111251] ctnetlink v0.93: registering with nfnetlink. [ 95.447600] ClusterIP Version 0.8 loaded successfully [ 96.105894] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 96.113444] :00:19.0: eth0: 10/100 speed: disabling TSO [ 96.119906] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 98.291567] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 100.435606] RPC: Registered udp transport module. [ 100.440358] RPC: Registered tcp transport module. [ 100.445101] RPC: Registered
Bug#571662: linux-base: mishandles /boot/grub/menu.lst
Package: linux-base Version: 2.6.33-1~experimental.1+r15282 Severity: normal Hi, the /dev/sdX to UUID= messes up /boot/grub/menu.lst: * the file header (everthing before ### BEGIN AUTOMAGIC KERNELS LIST is lost (timeout, color, default, ... are lost, would be more critical with console on serial port) * instead all old settings in magic comments in the AUTOMAGIC KERNELS LIST are inserted as comments at the beginning of the file * update-grub interprets some of these comments, e.g. altoptions which are appended to the settings in AUTOMAGIC KERNELS LIST, causing exploding number of kernels each time update-grub is called Andreas -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libapt-pkg-perl 0.1.22+b1 Perl interface to libapt-pkg linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual: * linux-base/disk-id-convert-plan: true * linux-base/disk-id-convert-auto: true # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #grub-md5-crypt, /usr/share/doc/grub #and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not change this entry to 'saved' or your # array will desync and will not let you boot your system. default 0 #default2 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 5 # Pretty colours color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel/vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/sda1 ro quiet ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions= ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(single-user) single # altoptions=(single-user mode) single # altoptions=(Limit RAM) mem=1280M ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false #
Bug#571662: linux-base: mishandles /boot/grub/menu.lst
Also checking a bit more reveals that the quiet option was removed from the kopt settings. If there were more custom options - would they survive? -# kopt=root=/dev/sda1 ro quiet +# kopt=root=UUID=bfc4d8de-5304-4285-adf0-1a5f7f57e765 ro Also what would happen to static stanzas before/after the automagic list? There were none in my case. Andreas -- 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/4b884969.7080...@abeckmann.de
Bug#548021: linux-kbuild-2.6: needs building instructions
Package: linux-kbuild-2.6 Severity: normal Hi, the linux-kbuild-2.6 package needs information on a) how to generate a new orig tarball (for me worked: debian/bin/genorig.py ../linux-2.6.31.tar.bz2) b) how to rebuild the package if you checked it out from svn An adjusted version of debian/README.build from linux-2.6 might do. Andreas -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (800, 'stable'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-0-amd64 (SMP w/4 CPU cores) Locale: LANG=C, 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
Bug#548028: linux-2.6: debian/README.build should mention required packages for orig.tar.gz generation
Package: linux-2.6 Severity: normal Hi, please document in debian/README.build which packages are required to be installed in order to perform the steps mentioned there. Testing this in a clean minimal chroot with only build-essential and subversion installed required me to install the following packages: python, unifdef (for debian/bin/genorig.py tarball ...) rsync (for debian/rules orig) Andreas -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (800, 'stable'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-0-amd64 (SMP w/4 CPU cores) Locale: LANG=C, 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
Bug#524632: linux-support-2.6.29-1: rules.include uses wrong regexp to detect binary NMU
Package: linux-support-2.6.29-1 Version: 2.6.29-3 Severity: normal Tags: patch Hi, /usr/src/linux-support-*/modules/rules.include uses a wrong sed expression to detect binary NMUs: dpkg-parsechangelog | sed -ne 's,^Version: .*\+b\(.*\)$$,\1,p' This incorrectly triggers on versions like 1.2.3~beta1-1 1.2.3-4.0anbe2 because (in sed) \+ is a regexp commmand char, while + is a char literal. Please change this to sed -ne 's,^Version: .*+b\(.*\)$$,\1,p' You may also consider restricting it to +b followed by a number: sed -ne 's,^Version: .*+b\([0-9]\+\)$$,\1,p' Thanks. Andreas -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable'), (130, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-support-2.6.29-1 depends on: ii python2.5.4-2An interactive high-level object-o ii python-central0.6.11 register and build utility for Pyt linux-support-2.6.29-1 recommends no packages. linux-support-2.6.29-1 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#482164: firmware-qlogic: new firmware available
Package: firmware-qlogic Version: 0.10 Severity: normal Hi, on ftp://ftp.qlogic.com/outgoing/linux/firmware/ there is updated and new firmware available: ql2400_fw.bin -- 4.04.00 IP (in firmware-qlogic: 4.00.27) ql2500_fw.bin -- 4.04.00 (not yet in firmware-qlogic) Andreas -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable'), (130, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412915: linux-image-2.6.18-4-686: mmc/sdhci problems after resume from ram
Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: normal Hi, after resuming from suspend-to-ram (suspended with s2ram from uswsusp/unstable) mmc_core and sdhci spit out tons of errors and make the system very unresponsive. Eventually the system freezes (or unresponsiveness my patience), a quick shutdown after resume usually helps. a few lines from syslog: Feb 27 04:15:18 lembas kernel: mmc0: Controller never released inhibit bit(s). Please report this to [EMAIL PROTECTED]. Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x2 never completed. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x4 never completed. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:18 lembas kernel: mmc0: Controller never released inhibit bit(s). Please report this to [EMAIL PROTECTED]. Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x2 never completed. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x4 never completed. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x1 never completed. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:33 lembas kernel: mmc0: Got command interrupt even though no command operation was in progress. Feb 27 04:15:33 lembas kernel: mmc0: Please report this to [EMAIL PROTECTED]. Feb 27 04:15:33 lembas kernel: mmc0: Card is consuming too much power! Feb 27 04:15:33 lembas kernel: mmc0: Unexpected interrupt 0x0080. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:33 lembas kernel: mmc0: Got command interrupt even though no command operation was in progress. Feb 27 04:15:33 lembas kernel: mmc0: Please report this to [EMAIL PROTECTED]. Feb 27 04:15:33 lembas kernel: mmc0: Card is consuming too much power! Feb 27 04:15:33 lembas kernel: mmc0: Unexpected interrupt 0x0080. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:35 lembas kernel: mmc0: Controller never released inhibit bit(s). Please report this to [EMAIL PROTECTED]. Feb 27 04:15:35 lembas kernel: mmc0: Reset 0x2 never completed. Please report this to [EMAIL PROTECTED]. Feb 27 04:15:35 lembas kernel: mmc0: Reset 0x4 never completed. Please report this to [EMAIL PROTECTED]. The mmc messages are repeated in differing amounts of the single messages again and again, each message is followed (or preceded?) by the following sdhci messages: Feb 27 04:15:18 lembas kernel: sdhci: == REGISTER DUMP == Feb 27 04:15:18 lembas kernel: sdhci: Sys addr: 0x | Version: 0x Feb 27 04:15:18 lembas kernel: sdhci: Blk size: 0x | Blk cnt: 0x Feb 27 04:15:18 lembas kernel: sdhci: Argument: 0x | Trn mode: 0x Feb 27 04:15:18 lembas kernel: sdhci: Present: 0x | Host ctl: 0x00ff Feb 27 04:15:18 lembas kernel: sdhci: Power:0x00ff | Blk gap: 0x00ff Feb 27 04:15:18 lembas kernel: sdhci: Wake-up: 0x00ff | Clock: 0x Feb 27 04:15:18 lembas kernel: sdhci: Timeout: 0x00ff | Int stat: 0x Feb 27 04:15:18 lembas kernel: sdhci: Int enab: 0x | Sig enab: 0x Feb 27 04:15:18 lembas kernel: sdhci: AC12 err: 0x | Slot int: 0x Feb 27 04:15:18 lembas kernel: sdhci: Caps: 0x | Max curr: 0x Feb 27 04:15:18 lembas kernel: sdhci: === Suspend-to-Ram (and resume) with the two modules mmc_core and sdhci unloaded just works fine. Since I don't need the card reader (not sure if it even works) I'll probably just blacklist these modules ... Andreas -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369150: linux-image-2.6.16-1-k7: oops while writing to a reiserfs partition
Package: linux-image-2.6.16-1-k7 Version: 2.6.16-12 Severity: normal Hi, I just experienced an oops while writing to a reiserfs partition. The partition was newly created with current reiserfsprogs (1:3.6.19-2), is about 64GB large and had a block size of 512 bytes. The oops information from kern.log is attached. Andreas -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.16-1-k7 depends on: ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-9 Yet Another mkInitRD Versions of packages linux-image-2.6.16-1-k7 recommends: ii libc6-i6862.3.6-7GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-1-k7/preinst/initrd-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/lilo-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/abort-overwrite-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/depmod-error-2.6.16-1-k7: false linux-image-2.6.16-1-k7/preinst/elilo-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-k7/prerm/removing-running-kernel-2.6.16-1-k7: true * linux-image-2.6.16-1-k7/preinst/overwriting-modules-2.6.16-1-k7: false linux-image-2.6.16-1-k7/postinst/old-system-map-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/failed-to-move-modules-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/abort-install-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/bootloader-test-error-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/bootloader-error-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/bootloader-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/kimage-is-a-directory: linux-image-2.6.16-1-k7/postinst/old-initrd-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/prerm/would-invalidate-boot-loader-2.6.16-1-k7: true * linux-image-2.6.16-1-k7/preinst/already-running-this-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/depmod-error-initrd-2.6.16-1-k7: false linux-image-2.6.16-1-k7/postinst/old-dir-initrd-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/create-kimage-link-2.6.16-1-k7: true May 27 19:28:35 palantir kernel: Unable to handle kernel paging request at virtual address 41186508 May 27 19:28:35 palantir kernel: printing eip: May 27 19:28:35 palantir kernel: b01a3e42 May 27 19:28:35 palantir kernel: *pde = May 27 19:28:35 palantir kernel: Oops: [#1] May 27 19:28:35 palantir kernel: Modules linked in: nfsd exportfs lockd nfs_acl sunrpc cls_u32 sch_ingress xt_length ipt_tos xt_MARK iptable_mangle cls_fw sch_sfq sch_htb thermal fan button processor ac battery ipt_MASQUERADE ipt_REJECT xt_tcpudp xt_state ipt_LOG iptable_filter ip_nat_ftp iptable_nat ip_nat ip_conntrack_irc ip_conntrack_ftp ip_conntrack nfnetlink ip_tables x_tables ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc it87 hwmon_vid eeprom i2c_isa i2c_dev reiserfs evdev snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd i2c_sis630 uhci_hcd ehci_hcd 8139too ohci_hcd i2c_core pcspkr parport_pc parport sis_agp agpgart rtc sis900 soundcore mii usbcore snd_page_alloc ext3 jbd mbcache ide_disk generic sis5513 ide_core May 27 19:28:35 palantir kernel: CPU:0 May 27 19:28:35 palantir kernel: EIP:0060:[_mmx_memcpy+104/292]Not tainted VLI May 27 19:28:35 palantir kernel: EFLAGS: 00210212 (2.6.16-1-k7 #2) May 27 19:28:35 palantir kernel: EIP is at _mmx_memcpy+0x68/0x124 May 27 19:28:35 palantir kernel: eax: b5db4000 ebx: 0215b884 ecx: b1c1f9f8 edx: 36efa940 May 27 19:28:35 palantir kernel: esi: 41186508 edi: b1818818 ebp: 856e2128 esp: b5db5950 May 27 19:28:35 palantir kernel: ds: 007b es: 007b ss: 0068 May 27 19:28:35 palantir kernel: Process tar (pid: 19467, threadinfo=b5db4000 task=c4c1dab0) May 27 19:28:35 palantir kernel: Stack: 0b1818818 41186508 856e2128 c8abecd4 b1818818 41186508 856e2128 May 27 19:28:35 palantir kernel:b5db5b68 b1c1f9f8 b5db59d4 b1818800 b33bba60 01e8 May 27 19:28:35 palantir kernel:b1c1f9f8 b5db59d4 b1818800 451b6949 b1c1f9f8 b5db59d4 May 27 19:28:35 palantir kernel: Call Trace: May 27 19:28:35 palantir kernel: [pg0+410467540/1338717184] leaf_copy_items_entirely+0xa2/0x201 [reiserfs] May 27 19:28:35 palantir kernel: [pg0+410475238/1338717184] leaf_move_items+0x2a5/0x2fb [reiserfs] May 27 19:28:35 palantir kernel: [pg0+410397397/1338717184] do_balance+0x2135/0x29f4 [reiserfs] May 27 19:28:35 palantir kernel: [find_get_page+18/45] find_get_page+0x12/0x2d May 27 19:28:35 palantir kernel: [__find_get_block+286/317] __find_get_block+0x11e/0x13d May 27 19:28:35 palantir kernel:
Bug#360758: linux-image-2.6.16-1-vserver-k7: module binary incompatibility between 2.6.16-4 and 2.6.16-5 ?
Package: linux-image-2.6.16-1-vserver-k7 Version: 2.6.16-5 Severity: normal After upgrading linux-image-2.6.16-1-vserver-k7 from 2.6.16-4 to 2.6.16-5 I had to rebuild the third party modules. Errors reported when inserting the old modules were: kernel: nvidia: disagrees about version of symbol struct_module There were no problems upgrading linux-image-2.6.16-1-k7, i.e. modules built against 2.6.16-4 (and earlier) are still working fine. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable'), (30, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-vserver-k7 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-1-vserver-k7 depends on: ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-8 Yet Another mkInitRD Versions of packages linux-image-2.6.16-1-vserver-k7 recommends: ii libc6-i6862.3.6-3GNU C Library: Shared libraries [i -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
