firmware-nonfree_20161130-1_amd64.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Dec 2016 21:20:01 +
Source: firmware-nonfree
Binary: firmware-linux firmware-linux-nonfree firmware-amd-graphics 
firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 
firmware-cavium firmware-intelwimax firmware-intel-sound firmware-ipw2x00 
firmware-ivtv firmware-iwlwifi firmware-libertas firmware-misc-nonfree 
firmware-myricom firmware-netxen firmware-qlogic firmware-realtek 
firmware-samsung firmware-siano firmware-ti-connectivity
Architecture: all
Version: 20161130-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description:
 firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
 firmware-atheros - Binary firmware for Atheros wireless cards
 firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
 firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
 firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
 firmware-cavium - Binary firmware for Cavium Ethernet adapters
 firmware-intel-sound - Binary firmware for Intel sound DSPs
 firmware-intelwimax - Binary firmware for Intel WiMAX Connection
 firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and 
pvrusb2 d
 firmware-iwlwifi - Binary firmware for Intel Wireless cards
 firmware-libertas - Binary firmware for Marvell wireless cards
 firmware-linux - Binary firmware for various drivers in the Linux kernel 
(meta-pac
 firmware-linux-nonfree - Binary firmware for various drivers in the Linux 
kernel (meta-pac
 firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel
 firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
 firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 
3100 Se
 firmware-qlogic - Binary firmware for QLogic HBAs
 firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters
 firmware-samsung - Binary firmware for Samsung MFC video codecs
 firmware-siano - Binary firmware for Siano MDTV receivers
 firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and 
BT/FM/GPS adapters
Closes: 823637 826996 838476 838858 841092 842762
Changes:
 firmware-nonfree (20161130-1) unstable; urgency=medium
 .
   * New upstream version
 - Upstream version is commit 87941021a622c882b1921df85d6115940a4e568a,
   dated 2016-11-30
 - amd-graphics: Update SMC microcode for Radeon HD 7790/7800/7900/
   8500/8600/8700/8770/8950 series, R9 290 series, "Fiji", "Polaris",
   and "Topaz" chips
 - amd-graphics: Update UVD microcode for "Carrizo" chips to version
   1.87, for "Fiji" chips to version 1.87.12, for "Stoney" chips to
   version 1.38.15, and for "Tonga" chips to version 1.65.10
 - amd-graphics: Update VCE microcode for "Fiji" and "Topaz" chips to
   version 52.8.3
 - intel-sound: Update "Bay Trail" SST DSP firmware to version
   01_0C_00_01
 - iwlwifi: Update Intel Wireless Bluetooth firmware patch for
   3160 (B6) to version 39, for 7260 (B6) to version 39, and for
   7265 (C0) to version 59
 - iwlwifi: Update Intel Wireless Bluetooth configuration and firmware
   for 8260 to version REL0351, and for 8264 to version REL0082
   * amd-graphics: Include SMC microcode for newer Radeon HD, "Tonga" and
 "Iceland" chips (Closes: #838858)
   * misc-nonfree: Include Nvidia GM200, GM204, GM206, GM20B and GP100
 signed firmware (Closes: #823637, #826996)
   * atheros: Include Bluetooth firmware for QCA61x4 (thanks to Mario
 Limonciello) (Closes: #841092)
   * misc-nonfree: Include Intel "Kabylake" DMC firmware and Intel
 "Skylake" GuC firmware version 6.1 (Closes: #838476, #842762)
   * brcm80211: Include Broadcom BCM43430 firmware
   * libertas: Include Marvell Avastar 88W8997 firmware
   * libertas: Update descriptions of supported chips
   * realtek: Include Realtek RTL8822B Bluetooth config and firmware,
 RTl8192EU firmare and RTl8723BU firmware
   * Use debhelper compatibility level 9
   * debian/control: Update Standards-Version to 3.9.8; no changes needed
   * copyright: Fix structured copyright files to follow the machine-
 readable debian/copyright format version 1.0
   * Update to linux-support 4.8.0-1
Checksums-Sha1:
 32f56475aa0b469a44783b1fb835316019f48a29 1563940 
firmware-amd-graphics_20161130-1_all.deb
 672ac26d476688bdea85ed9af83a6f83ecee57ab 3131420 
firmware-atheros_20161130-1_all.deb
 7cbc8eada07d673fa1755be45cdffe2f8a1c29d5 98472 firmware-bnx2_20161130-1_all.deb
 65c84fcfeaa9bbd4463cf2b035ea39731b72cf4b 2815904 
firmware-bnx2x_20161130-1_all.deb
 b040b3a68d0d44a246939f379b20ea399c9aec6f 3601930 
firmware-brcm80211_20161130-1_all.deb
 21aa94b5dbc581362c73e36cafd7686c801c1afb 435764 
firmware-cavium_20161130-1_all.deb
 

Processed: Re: X11 segfault with AMD GPU since 4.8.x / Firmware issue

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 firmware-amd-graphics
Bug #844605 [linux] X11 segfault with AMD GPU since 4.8.x / Firmware issue
Bug reassigned from package 'linux' to 'firmware-amd-graphics'.
No longer marked as found in versions linux/4.8.5-1 and 4.8.7-1.
Ignoring request to alter fixed versions of bug #844605 to the same values 
previously set
> forcemerge -1 838858
Bug #844605 [firmware-amd-graphics] X11 segfault with AMD GPU since 4.8.x / 
Firmware issue
Bug #844605 [firmware-amd-graphics] X11 segfault with AMD GPU since 4.8.x / 
Firmware issue
Marked as fixed in versions firmware-nonfree/20161130-1.
Marked as found in versions firmware-nonfree/20160824-1.
Added tag(s) patch.
Bug #843061 {Done: Ben Hutchings } 
[firmware-amd-graphics] radeon/hawaii_k_smc.bin fails to load with 4.8 kernel
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions firmware-nonfree/20161130-1.
No longer marked as fixed in versions firmware-nonfree/20161130-1.
Bug #838858 [firmware-amd-graphics] firmware-amd-graphics: missing SI/CI smc 
firmware files
Marked as fixed in versions firmware-nonfree/20161130-1.
Marked as fixed in versions firmware-nonfree/20161130-1.
Merged 838858 843061 844605

-- 
838858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838858
843061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843061
844605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#844605: X11 segfault with AMD GPU since 4.8.x / Firmware issue

[Ben Hutchings]

Control: reassign -1 firmware-amd-graphics
Control: forcemerge -1 838858

On Thu, 17 Nov 2016 16:04:51 +0100 Patrick Matthäi
 wrote:
[...]
> dmesg reports a firmware missmatch:
[...]
> [3.262451] radeon :01:00.0: firmware: failed to load 
> radeon/bonaire_k_smc.bin (-2)
> [3.262454] radeon :01:00.0: Direct firmware load 
> forradeon/bonaire_k_smc.bin failed with error -2
> [3.262845] radeon :01:00.0: firmware: direct-loading 
> firmwareradeon/BONAIRE_smc.bin
> [3.262846] ci_fw: mixing new and old firmware!
[...]

Missing firmware isn't a kernel bug, it's a bug in a firmware package.
(And X blowing up is probably an X driver bug.)

The missing firmware is fixed in the latest firmware-nonfree upload.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


signature.asc
Description: This is a digitally signed message part

Processed: Re: upgrade-reports: After dist-upgrade from jessie to testing, kernel doesn't load, not a single message on screen

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #842458 [src:linux] upgrade-reports: After dist-upgrade from jessie to 
testing, kernel doesn't load, not a single message on screen
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #842458 [src:linux] upgrade-reports: After dist-upgrade from jessie to 
testing, kernel doesn't load, not a single message on screen
Added tag(s) moreinfo.

-- 
842458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842458: upgrade-reports: After dist-upgrade from jessie to testing, kernel doesn't load, not a single message on screen

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Sat, 29 Oct 2016 15:10:01 +0300 Pyotr  wrote: 
[...]
>* What was the outcome of this action?
>   System doesn't load. Instead of "Loading initramfs" just blinking '_'.

That message is no longer printed by default, so this doesn't tell us
how far boot progressed.

Please try the 'recovery mode' option under 'Advanced options' in the
GRUB menu.  That enables, among other things, verbose output from the
kernel and initramfs code.  Send us the boot messages (a photograph is
fine as long as the text is readable).

>* What outcome did you expect instead?
>   That system would load just like it was after fresh install.
> 
> This is probably due to my PC is being very old - Celeron 1.1 Ghz,
> 512Mb Ram, motherboard Elitegroup P6VXAT.

All Celeron processors should still be supported.  We've only dropped
support for 586-class processors (like the original Pentium).

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



signature.asc
Description: This is a digitally signed message part

Bug#834386: linux-image-4.6.0-1-amd64: Locks hard on boot.

[Ben Hutchings]

Nathan, I'm sorry we didn't answer this report much sooner.

Have you tried upgrading to a newer kernel version, and did that
resolve the problem?  The latest version in testing is now 4.8.7-1.

If the latest version has the same problem, does adding the kernel
parameter 'nomodeset' allow the system to boot all the way to a text-
mode login prompt?

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



signature.asc
Description: This is a digitally signed message part

Processed: severity of 834386 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 834386 important
Bug #834386 [src:linux] linux-image-4.6.0-1-amd64: Locks hard on boot.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 834386

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 834386 + moreinfo
Bug #834386 [src:linux] linux-image-4.6.0-1-amd64: Locks hard on boot.
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

[Ben Hutchings]

On Thu, 10 Nov 2016 21:45:54 +0800 Sharuzzaman Ahmat Raslan  wrote:
> Hi Ben,
> 
> I'm using Testing, and the package is not in testing yet.
> 
> I have seen that the migration to testing was blocked by block-udeb..
> 
> Hopefully the package can be migrated to testing soon.

testing now has 4.8.7-1; please report whether it works for you.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


signature.asc
Description: This is a digitally signed message part

Please auto-build firmware-nonfree

[Ben Hutchings]

The firmware-nonfree package is non-free because:
- No real source code is provided for the firmware
- Some licences do not permit creation of derivatives, or reverse-
  engineering
- Some licences only permit use with a particular manufacturer's
  products
- Some licences require presentation of a click-wrap licence when
  the firmware is distributed to end-users (see
  debian/config/ivtv/LICENSE and debian/config/ipw2x00/LICENSE)

None of the licences appear to preclude auto-building.

I'm assuming that there is an arch:all builder for non-free packages;
if not then we'll just have to remember not to do 'source' uploads of
this package.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


signature.asc
Description: This is a digitally signed message part

Processed: tagging 842458, tagging 770052, tagging 844256, tagging 846658, tagging 847041 ..., tagging 847189

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 842458 + sid stretch
Bug #842458 [src:linux] upgrade-reports: After dist-upgrade from jessie to 
testing, kernel doesn't load, not a single message on screen
Added tag(s) stretch and sid.
> tags 770052 + sid stretch
Bug #770052 [src:xvt] xvt: Uses absolute obsolete path for dpkg-statoverride
Added tag(s) sid and stretch.
> tags 844256 + sid
Bug #844256 [jclic] jclic: all bugs have been resolved at mainstream, but 
Debian package has not been updated for more than 6 years
Added tag(s) sid.
> tags 846658 + sid stretch
Bug #846658 {Done: Sebastian Ramacher } [rpl] rpi: rpl 
causes crashes in unrelated software when using pkg_resources
Added tag(s) sid and stretch.
> tags 847041 + sid stretch
Bug #847041 [httpie] ImportError: cannot import name is_windows
Added tag(s) sid and stretch.
> notfound 846385 6.9.9.6+dfsg-1
Bug #846385 [imagemagick] imagemagick: Potential ABI break upstream (without 
SONAME change)
There is no source info for the package 'imagemagick' at version 
'6.9.9.6+dfsg-1' with architecture ''
Unable to make a source version for version '6.9.9.6+dfsg-1'
No longer marked as found in versions 6.9.9.6+dfsg-1.
> found 846385 8:6.9.9.6+dfsg-1
Bug #846385 [imagemagick] imagemagick: Potential ABI break upstream (without 
SONAME change)
There is no source info for the package 'imagemagick' at version 
'8:6.9.9.6+dfsg-1' with architecture ''
Unable to make a source version for version '8:6.9.9.6+dfsg-1'
Marked as found in versions 8:6.9.9.6+dfsg-1.
> tags 847189 + sid stretch
Bug #847189 {Done: gregor herrmann } [libbusiness-issn-perl] 
libbusiness-issn-perl: FTBFS: t/prereq.t failure
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
770052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770052
842458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842458
844256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844256
846385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846385
846658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846658
847041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847041
847189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

[Olaf Meeuwissen]

Ian Campbell writes:

> On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote:
>> 
>> But perhas we should more explicit in this message, e.g.:
>> 
>> "This breaks (e)glibc 2.13 and earlier, which may still be installed in
>> a chroot or container environment based on Debian 7, RHEL/CentOS 6 or
>> earlier versions."
>
> That's a good idea!

And is what I actually wanted to achieve because the message as is did
not make this "obvious" for me.  Sorry for not being clear.

@Ian Thanks for the pointers, will have a look.
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Join the Free Software Foundationhttps://my.fsf.org/join

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Hi Salvatore

Thanks for your help.

Am 2016-12-04 um 06:42 schrieb Salvatore Bonaccorso:

> No that actually is enought, since the commit is is is in upstream
> version 4.9-rc1 and thus already included in the most recent package
> from experimental.
> 
> Thanks for testing that. So it looks might not be the same issue. Can
> you report what you did to me directly to the bug to keep the triage
> history?


I've just installed the kernel 4.9.0-rc7-amd64 from experimental and
rebooted... And the delay was again here.

Do you need some information about my hardware or BIOS (its HP-EFI or is
it UEFI? :) )
I posted the Version in my bugreport.

Regards

Jakob

Re: firmware-linux obsolete?

[Ben Hutchings]

On Wed, 2016-12-07 at 03:16 +0800, 積丹尼 Dan Jacobson wrote:
> Hello, do I just purge these?
> # aptitude search ~o~i~nfirm
> i   firmware-amd-graphics
> i   firmware-linux
> i   firmware-linux-nonfree
> i   firmware-misc-nonfree
> i   firmware-realtek
> Won't my computer stop working?

Don't remove them.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett



signature.asc
Description: This is a digitally signed message part

firmware-linux obsolete?

[積丹尼 Dan Jacobson]

Hello, do I just purge these?
# aptitude search ~o~i~nfirm
i   firmware-amd-graphics
i   firmware-linux
i   firmware-linux-nonfree
i   firmware-misc-nonfree
i   firmware-realtek
Won't my computer stop working?

Re: Website Resources Won’t Open

[Catherine Trammell]

Hi there,

I sent you an email about some resources on your site, but never heard
back. Is there someone else I should talk to about fixing them?

Thanks,

On Mon, Nov 7, 2016 at 5:33 PM, Catherine Trammell <
c.tramm...@sc-student.org> wrote:

> Hi,
>
> I was just checking out your website and noticed that I couldn’t open
> some of the resources on the page. Is there someone I should notify? I
> can send them a list of the broken resources.
>
> Thanks,
>
> --
> Catherine
>



-- 
Catherine

Processed: user debian...@lists.debian.org, usertagging 846783, affects 822671 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 846783 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 822671 + cgroupfs-mount
Bug #822671 [initramfs-tools] initramfs-tools: preserves unmodified 
/etc/initramfs-tools/initramfs.conf on upgrades from jessie
Added indication that 822671 affects cgroupfs-mount
> found 822671 cgroupfs-mount/1.3
Bug #822671 [initramfs-tools] initramfs-tools: preserves unmodified 
/etc/initramfs-tools/initramfs.conf on upgrades from jessie
Marked as found in versions cgroupfs-mount/1.3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
822671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822671
846783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reopening 847154

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 847154
Bug #847154 {Done: Ian Campbell } [linux-image-amd64] 
linux-image-amd64: Disabling vsyscall interface may break docker run
Bug reopened
Ignoring request to alter fixed versions of bug #847154 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

[Ian Campbell]

On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote:
> 
> But perhas we should more explicit in this message, e.g.:
> 
> "This breaks (e)glibc 2.13 and earlier, which may still be installed in
> a chroot or container environment based on Debian 7, RHEL/CentOS 6 or
> earlier versions."

That's a good idea!

Ian.

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

[Ben Hutchings]

On Tue, 2016-12-06 at 10:02 +, Ian Campbell wrote:
> On Tue, 2016-12-06 at 12:56 +0900, Olaf Meeuwissen wrote:
> > You may want to add to the NEWS blurb that disabling the old 'virtual
> > syscall' interface can lead to crashes when trying to run a Docker
> > container.  With upstream's docker-engine-1.12.3-0~stretch, I see
> 
> This was also reported as #845085 against docker.io.
> 
> Ben mentioned somewhere that NEWS is not displayed for newly installed
> packages (such as linux-image-$ABI) and so the message is instead part
> of the NEWS in the meta package:
>
> $ zcat /usr/share/doc/linux-image-amd64/NEWS.Debian.gz | head -n18
> linux-latest (76) unstable; urgency=medium
> 
>   * From Linux 4.8, several changes have been made in the kernel
> configuration to 'harden' the system, i.e. to mitigate security bugs.
> Some changes may cause legitimate applications to fail, and can be
> reverted by run-time configuration:
> - On 64-bit PCs (amd64), the old 'virtual syscall' interface is
>   disabled.  This breaks (e)glibc 2.13 and earlier.  To re-enable it,
>   set the kernel parameter: vsyscall=emulate
> - On most architectures, the /dev/mem device can no longer be used to
>   access devices that also have a kernel driver.  This breaks dosemu
>   and some old user-space graphics drivers.  To allow this, set the
>   kernel parameter: iomem=relaxed
> - The kernel log is no longer readable by unprivileged users.  To
>   allow this, set the sysctl: kernel.dmesg_restrict=0
> 
> >  -- Ben Hutchings   Sat, 29 Oct 2016 02:05:32 +0100
> 
> $
> 
> This was also displayed for me just now on upgrade of linux-image-amd64 
> from 4.7+75 to 4.8+76. Since this is already present in the version you
> reported the wishlist issue against I'm closing with this mail.
[...]

But perhas we should more explicit in this message, e.g.:

"This breaks (e)glibc 2.13 and earlier, which may still be installed in
a chroot or container environment based on Debian 7, RHEL/CentOS 6 or
earlier versions."

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett



signature.asc
Description: This is a digitally signed message part

Bug#847204: nfs-kernel-server: `systemctl status` incorrectly reports server "active" even if not started

[Riccardo Murri]

Package: nfs-kernel-server
Version: 1:1.2.8-9

The systemd service unit file for `nfs-kernel-server` incorrectly
reports the service status as "active" even when the NFS server is *not*
running (e.g., empty exports file).

This causes scripts (e.g., Ansible) that use `systemctl status` to check
for the NFS server to fail in a way that is difficult to debug because
the actual reported error might be in a loosely-related task (e.g., when
doing `exportfs -r` or when mounting fs from a client).

Steps to reproduce on a Debian "jessie" VM:

* starting from a basic "jessie" install, install the `nfs-kernel-server`::

debian@debian-nfs-bug:~$ sudo apt install nfs-kernel-server
[...]
The following extra packages will be installed:
  libevent-2.0-5 libldap-2.4-2 libnfsidmap2 libsasl2-2 libsasl2-modules 
libsasl2-modules-db libtirpc1 nfs-common rpcbind
Suggested packages:
  libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql 
libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal open-iscsi watchdog
The following NEW packages will be installed:
  libevent-2.0-5 libldap-2.4-2 libnfsidmap2 libsasl2-2 libsasl2-modules 
libsasl2-modules-db libtirpc1 nfs-common nfs-kernel-server rpcbind
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 1123 kB of archives.
After this operation, 3018 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://http.debian.net/debian/ jessie/main libevent-2.0-5 amd64 
2.0.21-stable-2 [152 kB]
[...]
Setting up libnfsidmap2:amd64 (0.25-5) ...
Setting up libtirpc1:amd64 (0.2.5-1) ...
Setting up rpcbind (0.2.1-6+deb8u1) ...
Setting up nfs-common (1:1.2.8-9) ...

Creating config file /etc/idmapd.conf with new version
Adding system user `statd' (UID 106) ...
Adding new user `statd' (UID 106) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
Setting up libsasl2-modules:amd64 (2.1.26.dfsg1-13+deb8u1) ...
Setting up nfs-kernel-server (1:1.2.8-9) ...

Creating config file /etc/exports with new version

Creating config file /etc/default/nfs-kernel-server with new version
Processing triggers for libc-bin (2.19-18+deb8u6) ...
Processing triggers for systemd (215-17+deb8u5) ...

* note that the NFS server has *not* been started yet, as the rpcbind
  daemon does not know about it::

debian@debian-nfs-bug:~$ sudo rpcinfo -p
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  56360  status
1000241   tcp  39499  status

  Still, `systemctl status` reports it already as loaded/active::

debian@debian-nfs-bug:~$ sudo systemctl status nfs-kernel-server.service
* nfs-kernel-server.service - LSB: Kernel NFS server support
   Loaded: loaded (/etc/init.d/nfs-kernel-server)
   Active: active (exited) since Tue 2016-12-06 12:12:58 UTC; 1min 13s ago

Dec 06 12:12:58 debian-nfs-bug nfs-kernel-server[1544]: Not starting NFS 
kernel daemon: no exports. ... (warning).
Dec 06 12:12:58 debian-nfs-bug systemd[1]: Started LSB: Kernel NFS server 
support.

* now add an export and try to start it again::

debian@debian-nfs-bug:~$ echo "/home localhost(rw,async.no_subtree_check)" 
| sudo tee -a /etc/exports
/home localhost(rw,async.no_subtree_check)

debian@debian-nfs-bug:~$ sudo systemctl start nfs-kernel-server

  (last command produces no output)

* `systemctl status` reports the server as loaded/active (green on
  terminal, so "ok")::

debian@debian-nfs-bug:~$ sudo systemctl status nfs-kernel-server.service
* nfs-kernel-server.service - LSB: Kernel NFS server support
   Loaded: loaded (/etc/init.d/nfs-kernel-server)
   Active: active (exited) since Tue 2016-12-06 12:12:58 UTC; 1min 36s ago

Dec 06 12:12:58 debian-nfs-bug nfs-kernel-server[1544]: Not starting NFS 
kernel daemon: no exports. ... (warning).
Dec 06 12:12:58 debian-nfs-bug systemd[1]: Started LSB: Kernel NFS server 
support.
Dec 06 12:14:33 debian-nfs-bug systemd[1]: Started LSB: Kernel NFS server 
support.

* still `exportfs -r` fails with a strange error message (due to
  `/proc/fs/nfsd` not being mounted) and the NFS server is not running nor
  registered with rpcbind/portmapper::

debian@debian-nfs-bug:~$ sudo exportfs -r
exportfs: localhost:/home: Function not implemented

debian@debian-nfs-bug:~$ sudo showmount -e localhost
clnt_create: RPC: Program not registered
debian@debian-nfs-bug:~$ sudo rpcinfo -p
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
  

linux_4.9~rc8-1~exp1_multi.changes ACCEPTED into experimental, experimental

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Dec 2016 05:02:30 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-rc8 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-rc8-common linux-libc-dev 
linux-headers-4.9.0-rc8-all linux-headers-4.9.0-rc8-all-alpha 
kernel-image-4.9.0-rc8-alpha-generic-di nic-modules-4.9.0-rc8-alpha-generic-di 
nic-wireless-modules-4.9.0-rc8-alpha-generic-di 
nic-shared-modules-4.9.0-rc8-alpha-generic-di 
serial-modules-4.9.0-rc8-alpha-generic-di 
usb-serial-modules-4.9.0-rc8-alpha-generic-di 
ppp-modules-4.9.0-rc8-alpha-generic-di pata-modules-4.9.0-rc8-alpha-generic-di 
cdrom-core-modules-4.9.0-rc8-alpha-generic-di 
scsi-core-modules-4.9.0-rc8-alpha-generic-di 
scsi-modules-4.9.0-rc8-alpha-generic-di loop-modules-4.9.0-rc8-alpha-generic-di 
btrfs-modules-4.9.0-rc8-alpha-generic-di 
ext4-modules-4.9.0-rc8-alpha-generic-di 
isofs-modules-4.9.0-rc8-alpha-generic-di jfs-modules-4.9.0-rc8-alpha-generic-di
 xfs-modules-4.9.0-rc8-alpha-generic-di fat-modules-4.9.0-rc8-alpha-generic-di 
md-modules-4.9.0-rc8-alpha-generic-di 
multipath-modules-4.9.0-rc8-alpha-generic-di 
usb-modules-4.9.0-rc8-alpha-generic-di 
usb-storage-modules-4.9.0-rc8-alpha-generic-di 
fb-modules-4.9.0-rc8-alpha-generic-di input-modules-4.9.0-rc8-alpha-generic-di 
event-modules-4.9.0-rc8-alpha-generic-di 
mouse-modules-4.9.0-rc8-alpha-generic-di 
nic-pcmcia-modules-4.9.0-rc8-alpha-generic-di 
pcmcia-modules-4.9.0-rc8-alpha-generic-di 
nic-usb-modules-4.9.0-rc8-alpha-generic-di 
sata-modules-4.9.0-rc8-alpha-generic-di crc-modules-4.9.0-rc8-alpha-generic-di 
crypto-modules-4.9.0-rc8-alpha-generic-di 
crypto-dm-modules-4.9.0-rc8-alpha-generic-di 
ata-modules-4.9.0-rc8-alpha-generic-di nbd-modules-4.9.0-rc8-alpha-generic-di 
squashfs-modules-4.9.0-rc8-alpha-generic-di 
virtio-modules-4.9.0-rc8-alpha-generic-di 
zlib-modules-4.9.0-rc8-alpha-generic-di fuse-modules-4.9.0-rc8-alpha-generic-di
 srm-modules-4.9.0-rc8-alpha-generic-di linux-image-4.9.0-rc8-alpha-generic 
linux-headers-4.9.0-rc8-alpha-generic 
linux-image-4.9.0-rc8-alpha-generic-dbgsym linux-image-4.9.0-rc8-alpha-smp 
linux-headers-4.9.0-rc8-alpha-smp linux-image-4.9.0-rc8-alpha-smp-dbgsym 
linux-headers-4.9.0-rc8-all-amd64 linux-image-4.9.0-rc8-amd64-unsigned 
linux-headers-4.9.0-rc8-amd64 linux-image-4.9.0-rc8-amd64-dbgsym 
linux-headers-4.9.0-rc8-all-arm64 linux-image-4.9.0-rc8-arm64-unsigned 
linux-headers-4.9.0-rc8-arm64 linux-image-4.9.0-rc8-arm64-dbgsym 
linux-headers-4.9.0-rc8-all-armel kernel-image-4.9.0-rc8-marvell-di 
nic-modules-4.9.0-rc8-marvell-di nic-shared-modules-4.9.0-rc8-marvell-di 
usb-serial-modules-4.9.0-rc8-marvell-di ppp-modules-4.9.0-rc8-marvell-di 
cdrom-core-modules-4.9.0-rc8-marvell-di scsi-core-modules-4.9.0-rc8-marvell-di 
loop-modules-4.9.0-rc8-marvell-di ipv6-modules-4.9.0-rc8-marvell-di 
btrfs-modules-4.9.0-rc8-marvell-di ext4-modules-4.9.0-rc8-marvell-di
 isofs-modules-4.9.0-rc8-marvell-di jffs2-modules-4.9.0-rc8-marvell-di 
jfs-modules-4.9.0-rc8-marvell-di fat-modules-4.9.0-rc8-marvell-di 
minix-modules-4.9.0-rc8-marvell-di md-modules-4.9.0-rc8-marvell-di 
multipath-modules-4.9.0-rc8-marvell-di usb-modules-4.9.0-rc8-marvell-di 
usb-storage-modules-4.9.0-rc8-marvell-di fb-modules-4.9.0-rc8-marvell-di 
input-modules-4.9.0-rc8-marvell-di event-modules-4.9.0-rc8-marvell-di 
mouse-modules-4.9.0-rc8-marvell-di nic-usb-modules-4.9.0-rc8-marvell-di 
sata-modules-4.9.0-rc8-marvell-di crc-modules-4.9.0-rc8-marvell-di 
crypto-modules-4.9.0-rc8-marvell-di crypto-dm-modules-4.9.0-rc8-marvell-di 
mmc-modules-4.9.0-rc8-marvell-di nbd-modules-4.9.0-rc8-marvell-di 
squashfs-modules-4.9.0-rc8-marvell-di uinput-modules-4.9.0-rc8-marvell-di 
zlib-modules-4.9.0-rc8-marvell-di leds-modules-4.9.0-rc8-marvell-di 
udf-modules-4.9.0-rc8-marvell-di fuse-modules-4.9.0-rc8-marvell-di 
mtd-modules-4.9.0-rc8-marvell-di linux-image-4.9.0-rc8-marvell
 linux-headers-4.9.0-rc8-marvell linux-image-4.9.0-rc8-marvell-dbgsym 
linux-headers-4.9.0-rc8-all-armhf linux-image-4.9.0-rc8-armmp-unsigned 
linux-headers-4.9.0-rc8-armmp linux-image-4.9.0-rc8-armmp-dbgsym 
linux-image-4.9.0-rc8-armmp-lpae-unsigned linux-headers-4.9.0-rc8-armmp-lpae 
linux-image-4.9.0-rc8-armmp-lpae-dbgsym linux-headers-4.9.0-rc8-all-hppa 
kernel-image-4.9.0-rc8-parisc-di nic-modules-4.9.0-rc8-parisc-di 
nic-shared-modules-4.9.0-rc8-parisc-di serial-modules-4.9.0-rc8-parisc-di 
usb-serial-modules-4.9.0-rc8-parisc-di ppp-modules-4.9.0-rc8-parisc-di 
pata-modules-4.9.0-rc8-parisc-di cdrom-core-modules-4.9.0-rc8-parisc-di 
scsi-core-modules-4.9.0-rc8-parisc-di scsi-modules-4.9.0-rc8-parisc-di 
loop-modules-4.9.0-rc8-parisc-di btrfs-modules-4.9.0-rc8-parisc-di 
ext4-modules-4.9.0-rc8-parisc-di isofs-modules-4.9.0-rc8-parisc-di 
jfs-modules-4.9.0-rc8-parisc-di xfs-modules-4.9.0-rc8-parisc-di 
fat-modules-4.9.0-rc8-parisc-di 

Bug#847198: src:linux: dmesg should be allowed to print the kernel ring buffer for admins

[Vincent Lefevre]

Package: src:linux
Severity: wishlist

In the past, admins could get dmesg output without running it as root,
but this is no longer possible:

  * security,printk: Enable SECURITY_DMESG_RESTRICT, preventing non-root users
reading the kernel log by default (sysctl: kernel.dmesg_restrict)

(in changelog.linux.gz). It is good that normal users cannot read
the kernel log, but for admins (typically users in the adm group,
who can already read /var/log/kern.log, thus have access to the same
information), this is a regression.

Note: "journalctl -b" also gives kernel logs (among other logs).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#847154: marked as done (linux-image-amd64: Disabling vsyscall interface may break docker run)

[Debian Bug Tracking System]

Your message dated Tue, 06 Dec 2016 10:02:11 +
with message-id <1481018531.4509.120.ca...@debian.org>
and subject line Re: Bug#847154: linux-image-amd64: Disabling vsyscall 
interface may break docker run
has caused the Debian Bug report #847154,
regarding linux-image-amd64: Disabling vsyscall interface may break docker run
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 4.8+76
Severity: wishlist

Dear Maintainer,

You may want to add to the NEWS blurb that disabling the old 'virtual
syscall' interface can lead to crashes when trying to run a Docker
container.  With upstream's docker-engine-1.12.3-0~stretch, I see

  docker run -it --rm centos:6.8 /bin/bash

exit with a 139 status (and may leave a core file).  Adding a

  vsyscall=emulate

to the kernel parameters fixed this for me.

When using the centos:7 image, this problem does not occur.
On 4.7.0-1-amd64, both centos:6.8 and centos:7 Docker images work
without any problems.

Seeing that the centos:7 image works fine, I am inclined to think that
this problem may be limited to older Docker images.  I have not done any
research to back this up, nor do I plan to.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.8.0-1-amd64  4.8.7-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Hope this helps,
--
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Join the Free Software Foundationhttps://my.fsf.org/join
--- End Message ---
--- Begin Message ---
On Tue, 2016-12-06 at 12:56 +0900, Olaf Meeuwissen wrote:
> You may want to add to the NEWS blurb that disabling the old 'virtual
> syscall' interface can lead to crashes when trying to run a Docker
> container.  With upstream's docker-engine-1.12.3-0~stretch, I see

This was also reported as #845085 against docker.io.

Ben mentioned somewhere that NEWS is not displayed for newly installed
packages (such as linux-image-$ABI) and so the message is instead part
of the NEWS in the meta package:

$ zcat /usr/share/doc/linux-image-amd64/NEWS.Debian.gz | head -n18
linux-latest (76) unstable; urgency=medium

  * From Linux 4.8, several changes have been made in the kernel
configuration to 'harden' the system, i.e. to mitigate security bugs.
Some changes may cause legitimate applications to fail, and can be
reverted by run-time configuration:
- On 64-bit PCs (amd64), the old 'virtual syscall' interface is
  disabled.  This breaks (e)glibc 2.13 and earlier.  To re-enable it,
  set the kernel parameter: vsyscall=emulate
- On most architectures, the /dev/mem device can no longer be used to
  access devices that also have a kernel driver.  This breaks dosemu
  and some old user-space graphics drivers.  To allow this, set the
  kernel parameter: iomem=relaxed
- The kernel log is no longer readable by unprivileged users.  To
  allow this, set the sysctl: kernel.dmesg_restrict=0

 -- Ben Hutchings   Sat, 29 Oct 2016 02:05:32 +0100

$

This was also displayed for me just now on upgrade of linux-image-amd64 
from 4.7+75 to 4.8+76. Since this is already present in the version you
reported the wishlist issue against I'm closing with this mail.

> Seeing that the centos:7 image works fine, I am inclined to think that
> this problem may be limited to older Docker images.  I have not done any
> research to back this up, nor do I plan to.

It is due to old eglibc in older distros. There's some more info in htt
ps://github.com/docker/docker/issues/28705. I think https://github.com/
docker/docker/issues/28705#issuecomment-264564406 is pertinent also
IMHO.

Ian.--- End Message ---