Bug#1057967: (no subject)
Hello, can also confirm, that "linux-image-6.1.0-15-amd64" completely hangs my Macbook Air system. I've also installed "broadcom-sta-dkms" for wifi. The test kernel from Salvatore in Message #72 fixes the problem for me, too. Regards, Darius
Bug#906158: intel-microcode: Update intel-microcode to 20180807
Hello maintainers, today I've installed intel-microcode (3.20180807a.1~bpo9+1) from stretch-backports to realize that firmware file "06-2c-02" is missing. snippet from dmesg: [ 290.754628] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.754701] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.754758] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.754812] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.754866] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.754919] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.754973] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755026] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755079] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755132] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755186] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755239] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755292] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755345] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755399] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755452] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755506] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.79] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755612] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755665] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755718] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755772] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755825] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) [ 290.755878] platform microcode: firmware: failed to load intel-ucode/06-2c-02 (-2) After downloading firmware from Intel (https://downloadmirror.intel.com/28087/eng/microcode-20180807a.tgz), unpacking and copying file "06-2c-02" to /lib/firmware/intel-ucode and executing "echo 1 > /sys/devices/system/cpu/microcode/reload" everything is fine. snippet from dmesg: [ 662.432843] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.433568] microcode: updated to revision 0x1f, date = 2018-05-08 [ 662.433702] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.434464] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.435062] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.435755] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.436408] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.437094] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.437767] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.438456] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.439115] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.439803] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.440465] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.441175] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.441802] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.442480] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.443098] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.443782] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.50] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.445149] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.445758] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.446698] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.447403] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.448272] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 [ 662.448936] platform microcode: firmware: direct-loading firmware intel-ucode/06-2c-02 System is an Intel Westmere E5645. Please add this firmware file as soon as possible. Kind regards Darius Hinweis zur DSGVO (Datenschutzgrundverordnung): Wir verarbeiten
Bug#871702: Latest Stretch qemu-system-i386 process balloons in Xen Dom0 RAM, crashes DomU
Hello, cannot tell if it works now or not > migrated all hosts to KVM.
Bug#871702: Latest Stretch qemu-system-i386 process balloons in Xen Dom0 RAM, crashes DomU
Hello, I can confirm this bug. Xen dom0 balloons endlessly and consumes all swap. Then dom0 kills one domU after another. Downgrading to qemu-system-x86 1:2.8+dfsg-6 helps solving the problem for me too. Same system with KVM is not affected.
Bug#782488: multipath-tools: updates for compatibility with property blacklist
Hello, I have this problem too on Debian Jessie. So I tried to compile 0.5.0+git0.770e6d0d-1 from experimental, but this ends up in an error... .. cc -fPIE -pie -Wl,-z,relro -Wl,-z,now -shared -o libprioweightedpath.so weightedpath.o cc -fPIE -pie -Wl,-z,relro -Wl,-z,now -shared -o libprioweightedpath.so weightedpath.o cc -fPIE -pie -Wl,-z,relro -Wl,-z,now -shared -o libprioiet.so iet.o cc -fPIE -pie -Wl,-z,relro -Wl,-z,now -shared -o libprioiet.so iet.o rm random.o weightedpath.o ontap.o hp_sw.o hds.o rdac.o const.o datacore.o emc.o iet.o make[2]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/libmultipath/prioritizers' make[2]: Entering directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/libmultipath/checkers' cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -static-libgcc -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wformat-security -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\lib\ -I.. -c -o libsg.o libsg.c cc: error: iet.o: No such file or directory Makefile:28: recipe for target 'libprioiet.so' failed make[2]: *** [libprioiet.so] Error 1 make[2]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/libmultipath/prioritizers' Makefile:41: recipe for target 'recurse' failed make[1]: *** [recurse] Error 2 make[1]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d' debian/rules:33: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 2 make: *** Waiting for unfinished jobs cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -static-libgcc -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wformat-security -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\lib\ -I.. -c -o cciss_tur.o cciss_tur.c cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -static-libgcc -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wformat-security -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\lib\ -I.. -c -o readsector0.o readsector0.c cc -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -static-libgcc -D_FORTIFY_SOURCE=2 -O2 -g -pipe -Wformat-security -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wunused -Wstrict-prototypes -fPIC -DLIB_STRING=\lib\ -I.. -c -o tur.o tur.c ... ... .. rm -f core *.o multipathd *.gz make[2]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/multipathd' make[2]: Entering directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/mpathpersist' rm -f *.o mpathpersist rm -f mpathpersist.8.gz make[2]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/mpathpersist' make[2]: Entering directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/kpartx' rm -f core *.o kpartx *.gz make[2]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d/kpartx' rm -f multipath-tools.spec rm -rf rpms make[1]: Leaving directory '/usr/local/src/neu/multipath-tools-0.5.0+git0.770e6d0d' touch build-multipath-udeb-stamp dpkg-buildpackage: error: debian/rules build gave error exit status 2 Multipath-tools 0.5.0-7 from sid also do not compile. Could it be that the build-dependencies are wrong or missing? Kind regards Darius * [http://www.rkt-online.com/images/rkt-logo.jpg] RKT ?bersetzungs- und Dokumentations-GmbH Dr.-Konstantin-Hank-Str. 3 D-78713 Schramberg Tel.: +49 (0)7422 / 99 20-0 Fax: +49 (0)7422 / 99 20-30 E-Mail: i...@rkt-online.com Web: www.rkt-online.com Amtsgericht Stuttgart HRB 480948 Gesch?ftsf?hrer: Roland K. Trost Umsatzsteuer-ID: DE 191737876 Kennen Sie schon unser Kundenportal eCon - easy Connect? eCon ist ein kleines Programm im Info-Bereich der Taskleiste, das die Verbindung zu Ihrem Partner RKT herstellt. Nur einen Mausklick entfernt sind damit: Ihre RKT-Auftragsverwaltung - der personalisierte Zugang zu IQT - die sichere Daten?bermittlung ?ber HTTPS. Weitere Informationen zu eCon k?nnen Sie hiermailto:market...@rkt-online.com?subject=Bitte%20senden%20Sie%20mir%20weitere%20Information%20zu%20eCon anfordern. Der Inhalt dieser E-Mail ist ausschliesslich fuer den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er
Bug#775781: mesa 10.4.2 from unstable won't build packages on jessie
Source: mesa
Version: 10.4.2
Severity: normal
Dear Maintainer,
since Mesa 10.4.x landed in Debian I cannot compile mesa anymore because
the build process does not know what to do with gallium_drv_video.so.
I know how to solve this, but I am wondering why you guys don't have
this problem and pushed mesa-10.4.2 into unstable already.
* What led up to the situation?
Can't build mesa 10.4.2 from sid on jessie x86_64
* What exactly did you do (or not do) that was effective (or
ineffective)?
Added deb-src http://ftp2.de.debian.org/debian/ sid main contrib
non-free to /etc/apt/sources.list
apt-get update OK.
apt-get build-dep mesa OK. All dependencies were installed.
cd /usr/local/src as root
apt-get source mesa
cd mesa-10.4.2
dpkg-buildpackage -tc -j8
* What was the outcome of this action?
These are the last few lines before package building begins...
...
...
...
dh_testdir
dh_testroot
dh_installchangelogs -s
dh_installchangelogs -pmesa-common-dev
dh_installdocs -s
dh_installexamples -s
# Also get rid of other files which aren't installed. Do not
# use -f to ensure we notice disappearing files:
set -e; for file in dri/usr/include/GL/wglext.h
dri/usr/include/GL/wmesa.h dri/usr/lib/*/libglapi.so
usr/include/GL/glcorearb.h usr/include/GL/glext.h usr/include/GL/gl.h
usr/include/GL/gl_mangle.h usr/include/GL/glxext.h usr/include/GL/glx.h
usr/include/GL/glx_mangle.h usr/include/GL/osmesa.h
usr/include/GL/wglext.h usr/include/GL/wmesa.h ; do rm debian/tmp/$file;
done
# Files only in git, not in tarballs, OK to use rm -f here:
set -e; for file in ; do rm -f debian/tmp/$file; done
# purge .la files
find debian/tmp/ -name '*.la' -exec rm '{}' ';'
# Copy the hardlinked *_dri.so correctly.
install -m755 -d debian/libgl1-mesa-dri/usr/lib/x86_64-linux-gnu/dri/
mv debian/tmp/dri/usr/lib/x86_64-linux-gnu/dri/*_dri.so \
debian/libgl1-mesa-dri/usr/lib/x86_64-linux-gnu/dri/
# Copy the hardlinked vdpau drivers correctly.
install -m755 -d debian/mesa-vdpau-drivers/usr/lib/x86_64-linux-gnu/vdpau/
mv debian/tmp/dri/usr/lib/x86_64-linux-gnu/vdpau/libvdpau*.so* \
debian/mesa-vdpau-drivers/usr/lib/x86_64-linux-gnu/vdpau/
dh_install -s --fail-missing
dh_install: dri/usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so exists
in debian/tmp but is not installed to anywhere
dh_install: missing files, aborting
debian/rules:259: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary gave error exit status 2
* What outcome did you expect instead?
All necessary mesa packages are being build.
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.7 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
