Re: Iproute2 for Debian testing and backports

2017-12-13 Thread Stephen Hemminger 
On Thu, 14 Dec 2017 08:26:07 +0100
Alexander Wirt  wrote:

> On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> 
> > Iproute2 gains new features every release to keep up with the upstream 
> > kernel.
> > 
> > How do I request that iproute for Debian testing (buster) and backports 
> > (stretch-backports)
> > be kept in sync?  
> > kernel  iproute
> > sid 4.144.9
> > buster  4.134.9
> > stretch-backports   4.134.9
> > stretch 4.9 4.9
> > 
> > Do you need resources to be applied to Debian maintenance for this?  
> Yes, we need more manpower. 
> 
> Alex

I am not an official Debian maintainer but could make a tree on github that was 
ready to go.
David could also feed any Cumulus patches back in.

Re: Iproute2 for Debian testing and backports

2017-12-13 Thread Alexander Wirt 
On Wed, 13 Dec 2017, Stephen Hemminger wrote:

> On Thu, 14 Dec 2017 08:26:07 +0100
> Alexander Wirt  wrote:
> 
> > On Wed, 13 Dec 2017, Stephen Hemminger wrote:
> > 
> > > Iproute2 gains new features every release to keep up with the upstream 
> > > kernel.
> > > 
> > > How do I request that iproute for Debian testing (buster) and backports 
> > > (stretch-backports)
> > > be kept in sync?  
> > >   kernel  iproute
> > > sid   4.144.9
> > > buster4.134.9
> > > stretch-backports 4.134.9
> > > stretch   4.9 4.9
> > > 
> > > Do you need resources to be applied to Debian maintenance for this?  
> > Yes, we need more manpower. 
> > 
> > Alex
> 
> I am not an official Debian maintainer but could make a tree on github that 
> was ready to go.
> David could also feed any Cumulus patches back in.
Thanks, I will try to give the packaging a shot in the weekend. 

Alex

Re: Iproute2 for Debian testing and backports

2017-12-13 Thread Alexander Wirt 
On Wed, 13 Dec 2017, Stephen Hemminger wrote:

> Iproute2 gains new features every release to keep up with the upstream kernel.
> 
> How do I request that iproute for Debian testing (buster) and backports 
> (stretch-backports)
> be kept in sync?  
>   kernel  iproute
> sid   4.144.9
> buster4.134.9
> stretch-backports 4.134.9
> stretch   4.9 4.9
> 
> Do you need resources to be applied to Debian maintenance for this?
Yes, we need more manpower. 

Alex

Processed: reassign 881352 to linux-image-4.13.0-1-686-pae, severity of 881352 is important

2017-12-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 881352 linux-image-4.13.0-1-686-pae
Bug #881352 [udisks2] udisks2: Breaks installation with kernel panic
Bug reassigned from package 'udisks2' to 'linux-image-4.13.0-1-686-pae'.
No longer marked as found in versions udisks2/2.7.4-1.
Ignoring request to alter fixed versions of bug #881352 to the same values 
previously set
> severity 881352 important
Bug #881352 [linux-image-4.13.0-1-686-pae] udisks2: Breaks installation with 
kernel panic
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

linux_3.16.51-3_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new

2017-12-13 Thread Debian FTP Masters 
Mapping jessie to oldstable.
Mapping oldstable to oldstable-proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 13 Dec 2017 20:11:46 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 
linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all 
linux-headers-3.16.0-4-all-alpha kernel-image-3.16.0-4-alpha-generic-di 
nic-modules-3.16.0-4-alpha-generic-di 
nic-wireless-modules-3.16.0-4-alpha-generic-di 
nic-shared-modules-3.16.0-4-alpha-generic-di 
serial-modules-3.16.0-4-alpha-generic-di 
usb-serial-modules-3.16.0-4-alpha-generic-di 
ppp-modules-3.16.0-4-alpha-generic-di pata-modules-3.16.0-4-alpha-generic-di 
cdrom-core-modules-3.16.0-4-alpha-generic-di 
scsi-core-modules-3.16.0-4-alpha-generic-di 
scsi-modules-3.16.0-4-alpha-generic-di 
scsi-common-modules-3.16.0-4-alpha-generic-di 
scsi-extra-modules-3.16.0-4-alpha-generic-di 
loop-modules-3.16.0-4-alpha-generic-di btrfs-modules-3.16.0-4-alpha-generic-di 
ext4-modules-3.16.0-4-alpha-generic-di isofs-modules-3.16.0-4-alpha-generic-di 
jfs-modules-3.16.0-4-alpha-generic-di xfs-modules-3.16.0-4-alpha-generic-di 
fat-modules-3.16.0-4-alpha-generic-di
 md-modules-3.16.0-4-alpha-generic-di 
multipath-modules-3.16.0-4-alpha-generic-di 
usb-modules-3.16.0-4-alpha-generic-di 
usb-storage-modules-3.16.0-4-alpha-generic-di 
fb-modules-3.16.0-4-alpha-generic-di input-modules-3.16.0-4-alpha-generic-di 
event-modules-3.16.0-4-alpha-generic-di mouse-modules-3.16.0-4-alpha-generic-di 
nic-pcmcia-modules-3.16.0-4-alpha-generic-di 
pcmcia-modules-3.16.0-4-alpha-generic-di 
nic-usb-modules-3.16.0-4-alpha-generic-di 
sata-modules-3.16.0-4-alpha-generic-di core-modules-3.16.0-4-alpha-generic-di 
crc-modules-3.16.0-4-alpha-generic-di crypto-modules-3.16.0-4-alpha-generic-di 
crypto-dm-modules-3.16.0-4-alpha-generic-di 
ata-modules-3.16.0-4-alpha-generic-di nbd-modules-3.16.0-4-alpha-generic-di 
squashfs-modules-3.16.0-4-alpha-generic-di 
virtio-modules-3.16.0-4-alpha-generic-di zlib-modules-3.16.0-4-alpha-generic-di 
fuse-modules-3.16.0-4-alpha-generic-di srm-modules-3.16.0-4-alpha-generic-di 
linux-headers-3.16.0-4-common
 linux-image-3.16.0-4-alpha-generic linux-headers-3.16.0-4-alpha-generic 
linux-image-3.16.0-4-alpha-smp linux-headers-3.16.0-4-alpha-smp 
linux-headers-3.16.0-4-all-amd64 kernel-image-3.16.0-4-amd64-di 
nic-modules-3.16.0-4-amd64-di nic-wireless-modules-3.16.0-4-amd64-di 
nic-shared-modules-3.16.0-4-amd64-di serial-modules-3.16.0-4-amd64-di 
usb-serial-modules-3.16.0-4-amd64-di ppp-modules-3.16.0-4-amd64-di 
pata-modules-3.16.0-4-amd64-di cdrom-core-modules-3.16.0-4-amd64-di 
firewire-core-modules-3.16.0-4-amd64-di scsi-core-modules-3.16.0-4-amd64-di 
scsi-modules-3.16.0-4-amd64-di scsi-common-modules-3.16.0-4-amd64-di 
scsi-extra-modules-3.16.0-4-amd64-di loop-modules-3.16.0-4-amd64-di 
btrfs-modules-3.16.0-4-amd64-di ext4-modules-3.16.0-4-amd64-di 
isofs-modules-3.16.0-4-amd64-di jfs-modules-3.16.0-4-amd64-di 
ntfs-modules-3.16.0-4-amd64-di xfs-modules-3.16.0-4-amd64-di 
fat-modules-3.16.0-4-amd64-di md-modules-3.16.0-4-amd64-di 
multipath-modules-3.16.0-4-amd64-di
 usb-modules-3.16.0-4-amd64-di usb-storage-modules-3.16.0-4-amd64-di 
pcmcia-storage-modules-3.16.0-4-amd64-di fb-modules-3.16.0-4-amd64-di 
input-modules-3.16.0-4-amd64-di event-modules-3.16.0-4-amd64-di 
mouse-modules-3.16.0-4-amd64-di nic-pcmcia-modules-3.16.0-4-amd64-di 
pcmcia-modules-3.16.0-4-amd64-di nic-usb-modules-3.16.0-4-amd64-di 
sata-modules-3.16.0-4-amd64-di core-modules-3.16.0-4-amd64-di 
acpi-modules-3.16.0-4-amd64-di i2c-modules-3.16.0-4-amd64-di 
crc-modules-3.16.0-4-amd64-di crypto-modules-3.16.0-4-amd64-di 
crypto-dm-modules-3.16.0-4-amd64-di efi-modules-3.16.0-4-amd64-di 
ata-modules-3.16.0-4-amd64-di mmc-core-modules-3.16.0-4-amd64-di 
mmc-modules-3.16.0-4-amd64-di nbd-modules-3.16.0-4-amd64-di 
squashfs-modules-3.16.0-4-amd64-di speakup-modules-3.16.0-4-amd64-di 
virtio-modules-3.16.0-4-amd64-di uinput-modules-3.16.0-4-amd64-di 
sound-modules-3.16.0-4-amd64-di hyperv-modules-3.16.0-4-amd64-di 
udf-modules-3.16.0-4-amd64-di fuse-modules-3.16.0-4-amd64-di
 linux-image-3.16.0-4-amd64 linux-headers-3.16.0-4-amd64 
linux-image-3.16.0-4-amd64-dbg xen-linux-system-3.16.0-4-amd64 
linux-headers-3.16.0-4-all-arm64 kernel-image-3.16.0-4-arm64-di 
nic-modules-3.16.0-4-arm64-di nic-wireless-modules-3.16.0-4-arm64-di 
nic-shared-modules-3.16.0-4-arm64-di ppp-modules-3.16.0-4-arm64-di 
cdrom-core-modules-3.16.0-4-arm64-di scsi-core-modules-3.16.0-4-arm64-di 
scsi-modules-3.16.0-4-arm64-di loop-modules-3.16.0-4-arm64-di 
btrfs-modules-3.16.0-4-arm64-di ext4-modules-3.16.0-4-arm64-di 
isofs-modules-3.16.0-4-arm64-di jfs-modules-3.16.0-4-arm64-di 
xfs-modules-3.16.0-4-arm64-di fat-modules-3.16.0-4-arm64-di 
md-modules-3.16.0-4-arm64-di multipath-modules-3.16.0-4-arm64-di 
usb-modules-3.16.0-4-arm64-di usb-storage-modules-3.16.0-4-arm64-di 
input-modules-3.16.0-4-arm64-di event-modules-3.16.0-4-arm64-di 
n

Processing of linux_3.16.51-3_multi.changes

2017-12-13 Thread Debian FTP Masters 
linux_3.16.51-3_multi.changes uploaded successfully to localhost
along with the files:
  linux_3.16.51-3.dsc
  linux_3.16.51-3.debian.tar.xz
  linux-support-3.16.0-4_3.16.51-3_all.deb
  linux-doc-3.16_3.16.51-3_all.deb
  linux-manual-3.16_3.16.51-3_all.deb
  linux-source-3.16_3.16.51-3_all.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#884001: [src:linux] Graphics flickering and system freeze after last kernel upgrade

2017-12-13 Thread Abou Al Montacir 
Package: src:linux

--- Please enter the report below this line. ---Just after upgrade of kernel
image last WE, I've got graphics flickering and system hangs.The freeze issue is
100% reproducible by pressing tab key on a gnome-terminal running bash.The
system become unresponsive and could not ping it using WIFI (did not test wired
connection though).
Upgrade was according to aptitude.log:[UPGRADE] linux-compiler-gcc-6-x86:amd64
4.9.51-1 -> 4.9.65-3[UPGRADE] linux-headers-4.9.0-4-amd64:amd64 4.9.51-1 ->
4.9.65-3[UPGRADE] linux-headers-4.9.0-4-common:amd64 4.9.51-1 -> 4.9.65-
3[UPGRADE] linux-image-4.9.0-4-amd64:amd64 4.9.51-1 -> 4.9.65-3[UPGRADE] linux-
kbuild-4.9:amd64 4.9.51-1 -> 4.9.65-3[UPGRADE] linux-libc-dev:amd64 4.9.51-1 ->
4.9.65-3[UPGRADE] linux-libc-dev:i386 4.9.51-1 -> 4.9.65-3
# uname -aLinux lt-mazen 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3 (2017-12-03)
x86_64 GNU/Linux
# lsmodModule  Size  Used
byrfcomm 77824  2ip6table_filter16384  0ip6_tables  
   28672  1
ip6table_filteriptable_filter 16384  0tun28672  0ctr
16384  4ccm20480  2bbswitch 
  16384  0cmac   16384  1cpufreq_userspace  16384  0cpufreq_
conservative16384  0cpufreq_powersave  16384  0bnep   20
480  2binfmt_misc20480  1nls_ascii  16384  1nls_cp437   
   20480  1vfat   20480  1fat69632  
1
vfatfuse   98304  7joydev 20480  0intel_rapl
 20480  0x86_pkg_temp_thermal16384  0intel_powerclamp   16384  0
coretemp   16384  0arc4   16384  2kvm_intel 
192512  0iwlmvm245760  0btusb  45056  0kvm  
 589824  1
kvm_inteluvcvideo   90112  0videobuf2_vmalloc  16384  1
uvcvideovideobuf2_memops   16384  1
videobuf2_vmallocvideobuf2_v4l2 24576  1
uvcvideomac80211  671744  1 iwlmvmirqbypass  16384  1
kvmintel_cstate   16384  0intel_uncore  118784  0videobuf2_core 
36864  2 uvcvideo,videobuf2_v4l2videodev  176128  3
uvcvideo,videobuf2_core,videobuf2_v4l2snd_hda_codec_hdmi 49152  1btrtl  
16384  1 btusbbtbcm  16384  1
btusbdell_led   16384  1media  40960  2
uvcvideo,videodeviTCO_wdt   16384  0intel_rapl_perf16384  0i
TCO_vendor_support16384  1
iTCO_wdtdell_wmi   16384  0sparse_keymap  16384  1
dell_wmimxm_wmi16384  0dell_laptop20480  0btintel   
 16384  1 btusbbluetooth 552960  31
btrtl,btintel,bnep,btbcm,rfcomm,btusbsnd_hda_codec_realtek90112  1rtsx_usb_m
s20480  0dell_smbios16384  3
dell_wmi,dell_led,dell_laptopmemstick   20480  1
rtsx_usb_msdcdbas 16384  1
dell_smbiosdell_smm_hwmon 16384  0snd_hda_codec_generic69632  1
snd_hda_codec_realtekiwlwifi   151552  1
iwlmvmhid_multitouch 20480  0pcspkr 16384  0snd_soc_rt56
40118784  0efi_pstore 16384  0efivars20480  
1
efi_pstoreevdev  24576  34serio_raw  16384  0snd_hda
_intel  36864  10snd_soc_ssm456716384  0snd_soc_rl6231 1
6384  1
snd_soc_rt5640dw_dmac16384  0snd_soc_core  212992  2
snd_soc_ssm4567,snd_soc_rt5640sg 32768  0dw_dmac_core   
24576  1 dw_dmacsnd_hda_codec 135168  4
snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realteki915
 1236992  40cfg80211  589824  3
iwlmvm,iwlwifi,mac80211snd_hda_core   81920  5
snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_cod
ec_realteksnd_hwdep  16384  1
snd_hda_codecsnd_compress   20480  1
snd_soc_coresnd_pcm   110592  6
snd_hda_intel,snd_hda_codec,snd_hda_core,snd_soc_rt5640,snd_hda_codec_hdmi,snd_s
oc_coresnd_soc_sst_acpi   16384  0battery20480  0snd_timer  
32768  1 snd_pcmwmi16384  3
dell_wmi,dell_led,mxm_wmimei_me 36864  0mei   10
2400  1 mei_mevideo  40960  3
dell_wmi,dell_laptop,i915drm_kms_helper155648  1
i915drm   360448  14
i915,drm_kms_helperlpc_ich24576  0elan_i2c   36864  
0snd_soc_sst_match  16384  1
snd_soc_sst_acpidell_rbtn  16384  0shpchp 36864  0sn
d86016  30
snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,
snd_hda_codec_generic,snd_hda_codec_realtek,snd_soc_core,snd_pcmi2c_algo_bit
   16384  1
i915ac 16384  0butto

Bug#884183: linux-image-3.16.0-4-amd64: Kernel panic at boot

2017-12-13 Thread Benjamin Moody 
Package: src:linux
Followup-For: Bug #884183

Same problem here.  3.16.43-2+deb8u5 works, 3.16.51-2 is broken.

Supermicro H8QM3

Quad-Core AMD Opteron(tm) Processor 8347 HE (fam: 10, model: 02,
stepping: 03)

Two 3ware 9650SE RAID cards

I can get the system to boot by doing the following:

  * installing linux-image-3.16.0-4-amd64_3.16.43-2+deb8u5_amd64.deb
 (but booting the kernel and initrd from the 3.16.51-2 package)

  * adding the option 'nosmp'

  * adding the option 'blacklist=3w-9xxx'

If I don't set 'nosmp', the kernel panics immediately.  I don't
currently have a way to get a serial console on this machine, so I
don't have a complete log, but what I can see
(https://nofile.io/f/Nfc2FPR83st/IMG_20171213_144202.jpg) appears to
match the logs reported by Gerald Schroll.

If I set 'nosmp' but not 'blacklist=3w-9xxx', it goes into a seemingly
infinite loop (it appears to be trying to initialize one or both RAID
cards, but eventually times out and then tries again.)

If I set both of those options, the system boots up (slowly), and
eventually launches an emergency shell.  After five minutes, one of
the two RAID devices becomes visible.  (I assume that in this case,
something is loading 3w-9xxx.ko from the root filesystem, which is
version 3.16.43-2+deb8u5.)

In case it is useful, below is the log from the *old, working kernel*
(3.16.43-2+deb8u5).


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=9927902d-f34d-44ff-b316-b06fdbab989f ro quiet

** Not tainted

** Kernel log:
[   18.018936] [drm]   HPD2
[   18.018938] [drm]   DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
[   18.018939] [drm]   Encoders:
[   18.018940] [drm] CRT2: INTERNAL_DAC2
[   18.018942] [drm] DFP2: INTERNAL_DVO1
[   18.083633] [drm] fb mappable at 0xD004
[   18.083638] [drm] vram apper at 0xD000
[   18.083640] [drm] size 786432
[   18.083641] [drm] fb depth is 8
[   18.083643] [drm]pitch is 1024
[   18.083755] fbcon: radeondrmfb (fb0) is primary device
[   18.236979] Console: switching to colour frame buffer device 128x48
[   18.244485] radeon :01:01.0: fb0: radeondrmfb frame buffer device
[   18.244488] radeon :01:01.0: registered panic notifier
[   18.263937] [drm] Initialized radeon 2.39.0 20080528 for :01:01.0 on 
minor 0
[   18.810759] 3w-9xxx: scsi9: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.810764] 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.810780] sd 0:0:0:0: [sda] Invalid command failure
[   18.810787] sd 9:0:0:0: [sdb] Invalid command failure
[   18.810790] sd 9:0:0:0: [sdb]  
[   18.810793] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   18.810795] sd 9:0:0:0: [sdb]  
[   18.810798] Sense Key : Illegal Request [current] 
[   18.810806] sd 0:0:0:0: [sda]  
[   18.810807] sd 9:0:0:0: [sdb]  
[   18.810814] Add. Sense: Invalid command operation code
[   18.810818] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   18.810821] sd 0:0:0:0: [sda]  
[   18.810824] Sense Key : Illegal Request [current] 
[   18.810829] sd 9:0:0:0: [sdb] CDB: 
[   18.810831] ATA command pass through(16): 85 06
[   18.810837] sd 0:0:0:0: [sda]  
[   18.810842]  20
[   18.810844] Add. Sense: Invalid command operation code
[   18.810846] sd 0:0:0:0: [sda] CDB: 
[   18.810848] ATA command pass through(16): 85
[   18.810853]  00
[   18.810855]  06 20 00 05
[   18.810860]  05
[   18.810861]  00 fe 00 00
[   18.810867]  00
[   18.810869]  fe
[   18.810871]  00
[   18.810873]  00
[   18.810874]  00
[   18.810876]  00
[   18.810877]  00
[   18.810879]  00
[   18.810880]  40
[   18.810882]  ef
[   18.810883]  00

[   18.810887]  00
[   18.810889]  00 00 00 40 ef 00
[   18.811173] 3w-9xxx: scsi9: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.811231] 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.811429] 3w-9xxx: scsi9: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.811498] 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.835037] 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.835048] sd 0:0:0:0: [sda] Invalid command failure
[   18.835054] sd 0:0:0:0: [sda]  
[   18.835056] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   18.835059] sd 0:0:0:0: [sda]  
[   18.835061] Sense Key : Illegal Request [current] 
[   18.835065] sd 0:0:0:0: [sda]  
[   18.835068] Add. Sense: Invalid command operation code
[   18.835071] sd 0:0:0:0: [sda] CDB: 
[   18.835073] ATA command pass through(16): 85 06 20 00 05 00 fe 00 00 00 00 
00 00 40 ef 00
[   18.835462] 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   18.835732] 3w-9xxx: scsi0: ERROR: (0x03:0x0101): Invalid command 
opcode:opcode=0x85.
[   19.133918]

Iproute2 for Debian testing and backports

2017-12-13 Thread Stephen Hemminger 
Iproute2 gains new features every release to keep up with the upstream kernel.

How do I request that iproute for Debian testing (buster) and backports 
(stretch-backports)
be kept in sync?  
kernel  iproute
sid 4.144.9
buster  4.134.9
stretch-backports   4.134.9
stretch 4.9 4.9

Do you need resources to be applied to Debian maintenance for this?

Processed: reassign 884183 to src:linux, forcibly merging 883938 884183

2017-12-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 884183 src:linux
Bug #884183 [linux-image-3.16.0-4-amd64] linux-image-3.16.0-4-amd64: Kernel 
panic at boot
Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #884183 to the same values 
previously set
Ignoring request to alter fixed versions of bug #884183 to the same values 
previously set
> forcemerge 883938 884183
Bug #883938 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after 
upgrading to debian 8.10 kernel 3.16.51
Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Bug #884140 [src:linux] Kernel 3.16.51-2 general protection fault in 
sched_init_smp()
Bug #884183 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic at boot
Severity set to 'grave' from 'important'
Summary recorded from message bug 884183 message 
Added indication that 884183 affects release.debian.org
Marked as found in versions linux/3.16.51-2.
Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Bug #884140 [src:linux] Kernel 3.16.51-2 general protection fault in 
sched_init_smp()
Merged 883938 884069 884140 884183
> thanks
Stopping processing here.

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

Bug#883558: linux: not yet ready to enter testing

2017-12-13 Thread Tianon Gravi 
Salvatore Bonaccorso wrote:
> We think 4.14.2-1 should not yet enter testing, thus filling a
> blocking bug to preventing migration.
>
> We will close the bug as soon we think 4.14.2-1 or an increment is
> good.

In the quest for a little more detail (because I'm wanting to test
4.14 on a buster machine), I asked about this on IRC and received the
response from Ben that there's an embargoed security issue pending,
and got permission to add this short note as to the context for this
bug filing. :)

Cheers!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Processed (with 1 error): forcibly merging 883938 884183

2017-12-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forcemerge 883938 884183
Bug #883938 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after 
upgrading to debian 8.10 kernel 3.16.51
Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Bug #884140 [src:linux] Kernel 3.16.51-2 general protection fault in 
sched_init_smp()
Unable to merge bugs because:
package of #884183 is 'linux-image-3.16.0-4-amd64' not 'src:linux'
Failed to forcibly merge 883938: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#884001: Similar issue

2017-12-13 Thread Samuel Smith 
I've reported a similar issue here 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859639

Bug#859639: Similar issues here

2017-12-13 Thread Samuel Smith 
Having the same problems here on a Lenovo T520. It used to happen only 
if I had the internal screen and an external monitor both active. Now it 
happens randomly with only and external monitor hooked up since the 
upgrade to 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 
GNU/Linux.


I get random screen freezes where I can still move the mouse cursor, but 
clicking on anything doesn't do anything. Usually only happens when 
heavily using Firefox. Machine has 16GB of ram as well.


Xorg logs would have:
[201653.062] (WW) modeset(0): flip queue failed: Cannot allocate memory
[201653.062] (WW) modeset(0): Page flip failed: Cannot allocate memory
[201730.916] (WW) modeset(0): flip queue failed: Cannot allocate memory
[201730.916] (WW) modeset(0): Page flip failed: Cannot allocate memory
[201730.916] (WW) modeset(0): flip queue failed: Cannot allocate memory
[201730.916] (WW) modeset(0): Page flip failed: Cannot allocate memory

dmesg would have:
[drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun


I have since stopped using the modeset driver and added to 
/etc/X11/xorg.conf.d/20-intel.conf



Section "Device"
Identifier  "Intel Graphics"
Driver  "intel"
EndSection


No issues yet but I will post back if it happens.

Bug#883980: Experimenting with 4.9.0-4-amd64 and 4.9.0-3-amd64

2017-12-13 Thread Gerard M. Vignes 
Without installing, updating or removing any software, I am 
experimenting with kernels 4.9.0-4-amd64 and 4.9.0-3-amd64.


When I applied the Debian 9.3 upgrade, it installed a new kernel and 
retained the older kernel. I can select the newer or older kernel using 
the advanced boot menu.


When I boot with the newer 4.9.0-4-amd64 kernel, I experience the 
problem with screen going black for 1 second. This happens sporadically, 
but often enough to disrupt normal workstation activities.


When I boot with the older 4.9.0-3-amd64 kernel, I am not able to 
duplicate the problem.


I only discovered how to boot between old and new kernels last night, so 
I am going to continue booting on the older 4.9.0-3-amd64 kernel until a 
new kernel is released. I will post to this bug report again ONLY IF I 
discover that the problem occurs using the older 4.9.0-3-amd64 kernel.


I believe that the Debian 9.3 upgrade and/or newer 4.9.0-4-amd64 kernel 
introduced a problem that causes my screen to sporadically go black for 
1 second. The general conditions to duplicate this problem are outlined 
in my previous posts to this bug report. The simple diagnostics about my 
machine, which I provided as attachments, are also available in previous 
posts.


Thank you.

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-13 Thread Vladislav Kurz 
Package: src:linux
Followup-For: Bug #883938

Dear Maintainer,

I have run into this same problem on HP ProLiant DL380 G6 (fortunately this is 
only a backup server)

I confirm that numa=off workaround works for me.  That allowed me to install 
linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb which now boots OK even 
without numa=off.

Thanks for preparing the fixed version.

As a prevention I have installed the fixed kernel also on HP ProLiant DL380 
Gen9, but did not dare yet to reboot that one as it is the production box.

Best Regards
Vladislav Kurz

Bug#884183: Issues as well

2017-12-13 Thread Kees Meijs 
Hi list,

We've experienced lock-ups at boot time as well. After upgrading to
3.16.51-2 the system would just hang at loading the RAM disk.

Reverting back to 3.16.43-2 seems to solve the issue.

Relevant configuration: Supermicro X10DRi motherboard with two LSI Logic
/ Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) HBAs.

Sorry for the "me too" but hopefully it helps some.

Regards,
Kees

Bug#884094: register_key_type symbol missing, ABI counter not incremented

2017-12-13 Thread Liam Healy 
On Tue, Dec 12, 2017 at 2:25 AM, Sergio Gelato
 wrote:
> * Ben Hutchings [2017-12-11 15:59:38 +]:
>> I don't think there's any good way to deal with this
>> now, other than to force a rebuild of the module.
>
> Was afraid of that. It's what I did, of course, but it complicates the 
> rollout.
> (I ran "dkms remove openafs/1.6.20 -k $(uname -r); dkms install 
> openafs/1.6.20".)

Thanks for posting the workaround instructions. For the benefit of
others, these are the complete set of commands that I used to restore
AFS access

sudo dkms remove openafs/1.6.20 -k $(uname -r); sudo dkms install openafs/1.6.20
sudo modprobe openafs
sudo systemctl stop openafs-client.service
sudo systemctl start openafs-client.service
aklog

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-13 Thread Sebastian.Gerke 
Hello Ben,


Thank you for the fix. We have same issue as other people in this conversation.
When do you think that the fix will be rollout as stable?


Sebastian Gerke

--
Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)
Institut für Antriebstechnik | Linder Höhe | 51147 Köln

Sebastian Gerke | IT-Servicemanagement | Gebäude 45 Raum B01
Telefon 02203 601-2982 |  sebastian.ge...@dlr.de
www.DLR.de

Processed: your mail

2017-12-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 884183 linux-image-3.16.0-4-amd64: Kernel panic at boot
Bug #884183 [linux-image-3.16.0-4-amd64] linux-image-3.16.0-4-amd64 bug
Changed Bug title to 'linux-image-3.16.0-4-amd64: Kernel panic at boot' from 
'linux-image-3.16.0-4-amd64 bug'.
>
End of message, stopping processing here.

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

Processed: your mail

2017-12-13 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 884183 important
Bug #884183 [linux-image-3.16.0-4-amd64] linux-image-3.16.0-4-amd64 bug
Severity set to 'important' from 'normal'
>
End of message, stopping processing here.

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

Bug#884285: linux-image-4.9.0-4-rt-amd64: TP-link UE300 causes system hang

2017-12-13 Thread hendrik . sachse 
Package: src:linux
Version: 4.9.65-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?
usage of TP-link UE300 USB to ethernet adapter
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
plug in UE300 into USB port
   * What was the outcome of this action?
kernel messages and eventual system freeze

Dec  8 18:49:43 LxTE04 kernel: [16790.642451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 18:51:49 LxTE04 kernel: [16917.298453] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 18:53:55 LxTE04 kernel: [17043.314451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 19:01:18 LxTE04 kernel: [17486.322451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 19:03:24 LxTE04 kernel: [17612.274451] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped
Dec  8 19:04:27 LxTE04 kernel: [17675.314452] cdc_ether 1-1:2.0 eth0: 
kevent 11 may have been dropped

   * What outcome did you expect instead?
normal operation

refer to https://patchwork.kernel.org/patch/10022309/


-- Package-specific info:
** Version:
Linux version 4.9.0-4-rt-amd64 (debian-kernel@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP PREEMPT RT Debian 
4.9.65-3 (2017-12-03)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-4-rt-amd64 root=/dev/mapper/LxTE04-root ro quiet

** Not tainted

** Kernel log:
[78559.428637] usb 1-1: new high-speed USB device number 5 using xhci_hcd
[78559.569963] usb 1-1: New USB device found, idVendor=2357, 
idProduct=0601
[78559.569970] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
[78559.569973] usb 1-1: Product: USB 10/100/1000 LAN
[78559.569976] usb 1-1: Manufacturer: TP-LINK
[78559.569979] usb 1-1: SerialNumber: 0100
[78559.582728] cdc_ether 1-1:2.0 eth0: register 'cdc_ether' at 
usb-:00:14.0-1, CDC Ethernet Device, 18:a6:f7:1d:4d:d3
[78559.582766] usbcore: registered new interface driver cdc_ether
[78559.596244] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[78559.596360] cdc_ether 1-1:2.0 eth0: kevent 12 may have been dropped
[78559.611081] cdc_ether 1-1:2.0 eth0: kevent 12 may have been dropped

** Model information
sys_vendor: Shuttle Inc.
product_name: DS67U
product_version: V1.0
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1.01
board_vendor: Shuttle Inc.
board_name: FS67U
board_version: 1.0

** Loaded modules:
cdc_ether
usbnet
mii
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
intel_rapl
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
arc4
intel_cstate
intel_uncore
intel_rapl_perf
rtsx_usb_ms
serio_raw
pcspkr
evdev
memstick
snd_soc_skl
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
snd_hda_ext_core
snd_soc_sst_match
snd_soc_core
snd_compress
iTCO_wdt
iTCO_vendor_support
rtl8821ae
btcoexist
rtl_pci
btusb
btrtl
rtlwifi
snd_hda_intel
sg
snd_hda_codec
mac80211
snd_hda_core
snd_hwdep
cfg80211
snd_pcm
i915
snd_timer
snd
mei_me
soundcore
drm_kms_helper
shpchp
mei
drm
hci_uart
btbcm
btqca
btintel
bluetooth
battery
rfkill
video
intel_lpss_acpi
intel_lpss
acpi_pad
acpi_als
kfifo_buf
button
industrialio
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
dm_mod
rtsx_usb_sdmmc
mmc_core
rtsx_usb
mfd_core
sd_mod
hid_generic
usbhid
crc32c_intel
aesni_intel
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd
psmouse
ahci
libahci
igb
i2c_algo_bit
i2c_i801
e1000e
dca
i2c_smbus
ptp
libata
pps_core
scsi_mod
xhci_pci
xhci_hcd
usbcore
usb_common
fan
thermal
i2c_hid
hid

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: AFDX1A:  mtu 1500 qdisc mq 
state DOWN group default qlen 1000
link/ether 80:ee:73:bd:b3:a2 brd ff:ff:ff:ff:ff:ff
inet 10.10.1.1/16 brd 10.10.255.255 scope global AFDX1A
   valid_lft forever preferred_lft forever
3: AFDX1B:  mtu 1500 qdisc 
pfifo_fast state UP group default qlen 1000
link/ether 80:ee:73:bd:b3:a3 brd ff:ff:ff:ff:ff:ff
inet 10.10.1.2/16 brd 10.10.255.255 scope global AFDX1B
   valid_lft forever preferred_lft forever
inet6 fe80::82ee:73ff:febd:b3a3/64 scope link 
   valid_lft forever preferred_lft forever
4: wlp1s0:  mtu 1500 qdisc mq state DOWN group 
default qlen 1000
link/ether d6:7c:d3:04:a0:13 brd ff:ff:ff:ff:ff:ff
6: eth0:  mtu 1500 qdisc pfifo_fast state 
UP group default ql

Bug#884183: Bug 884183 - DELL

2017-12-13 Thread Matthias Hunstock 
Same here on DELL PowerEdges with megaraid_sas.

Find a bootlog of a successful boot with the previous kernel attached.

(The symbol errors seem to be related to the kernel downgrade.)

Matthias
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) 
(gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.43-2+deb8u5 
(2017-09-19)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.43 
root=UUID=0f974284-0e9a-4368-94de-d457a9070eda ro quiet
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0010-0xbd2e] usable
[0.00] BIOS-e820: [mem 0xbd2f-0xbd31bfff] reserved
[0.00] BIOS-e820: [mem 0xbd31c000-0xbd35afff] ACPI data
[0.00] BIOS-e820: [mem 0xbd35b000-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfe00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00183fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] DMI: Google Inc Google Search Appliance/0JP31P, BIOS 2.5.4 
01/22/2016
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] AGP: No AGP bridge found
[0.00] e820: last_pfn = 0x184 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-CBFFF write-protect
[0.00]   CC000-D3FFF write-back
[0.00]   D4000-EBFFF uncachable
[0.00]   EC000-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base  mask 3FFF8000 write-back
[0.00]   1 base 8000 mask 3FFFC000 write-back
[0.00]   2 base 0001 mask 3FFF write-back
[0.00]   3 base 0002 mask 3FFE write-back
[0.00]   4 base 0004 mask 3FFC write-back
[0.00]   5 base 0008 mask 3FF8 write-back
[0.00]   6 base 0010 mask 3FF8 write-back
[0.00]   7 base 0018 mask 3FFFC000 write-back
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[0.00] e820: update [mem 0xc000-0x] usable ==> reserved
[0.00] e820: last_pfn = 0xbd2f0 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at 
[880fe710]
[0.00] Base memory trampoline at [88098000] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] init_memory_mapping: [mem 0x-0x000f]
[0.00]  [mem 0x-0x000f] page 4k
[0.00] BRK [0x01af6000, 0x01af6fff] PGTABLE
[0.00] BRK [0x01af7000, 0x01af7fff] PGTABLE
[0.00] BRK [0x01af8000, 0x01af8fff] PGTABLE
[0.00] init_memory_mapping: [mem 0x183fe0-0x183fff]
[0.00]  [mem 0x183fe0-0x183fff] page 1G
[0.00] init_memory_mapping: [mem 0x183c00-0x183fdf]
[0.00]  [mem 0x183c00-0x183fdf] page 1G
[0.00] init_memory_mapping: [mem 0x18-0x183bff]
[0.00]  [mem 0x18-0x183bff] page 1G
[0.00] init_memory_mapping: [mem 0x10-0x17]
[0.00]  [mem 0x10-0x17] page 1G
[0.00] init_memory_mapping: [mem 0x0010-0xbd2e]
[0.00]  [mem 0x0010-0x001f] page 4k
[0.00]  [mem 0x0020-0x3fff] page 2M
[0.00]  [mem 0x4000-0x7fff] page 1G
[0.00]  [mem 0x8000-0xbd1f] page 2M
[0.00]  [mem 0xbd20-0xbd2e] page 4k
[0.00] init_memory_mapping: [mem 0x1-0xf]
[0.00]  [mem 0x1-0xf] page 1G
[0.00] RAMDISK: [mem 0x3620e000-0x370fefff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F0C70 24 (v02   )
[0.00] ACPI: XSDT 0x000F0DB8 A4 (v01 
0001 DELL 0001)
[0.00] ACPI: FACP 0xBD33534C F4 (v03 
0001 DELL 0001)
[0.00] ACPI: DSDT 0xBD31C000 008029 (v01 
0001 INTL 20110211)
[0.00] ACPI: FACS 0xBD337000 40
[0.00] ACPI: FACS 0xBD337000 40
[0.00] ACPI: APIC 0xBD334478 0001EA (v01

Bug#884284: nfs-kernel-server: NFSv4 broken

2017-12-13 Thread Anton Ivanov 
Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: important

Dear Maintainer,

NFSv4 in stretch is broken and unusable.

After some time the server exporting the directories starts throwing

[1130732.440356] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
[1130734.801510] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
[1173981.176268] NFS: nfs4_reclaim_open_state: Lock reclaim failed!

messages, read/writes slow down to a crawl and at the end there is
no choice but to reboot the server. Restarting nfs-kernel-server,
unmounting from all known clients and remouting does not help.

I have now been forced to downgrade back to nfsv3 across the board.
The same setup works fine with NFSv3.

NFSv4 used to work perfectly fine in jessie and before that.

I am not sure if this started from the stretch upgrade or after one
of the stretch mid-life kernel updates (I think it is the latter).

Setup: Standard mid-size classic Linux/Unix multiuser install. Server(s)
exporting $HOME and other directories to a local network. Clients mount
via autofs when needed. Most directories are mounted from at least 2 (usually
more) clients.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
151   udp  58357  mountd
151   tcp  37131  mountd
152   udp  54135  mountd
152   tcp  32951  mountd
153   udp  47587  mountd
153   tcp  41773  mountd
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
134   udp   2049  nfs
1002273   udp   2049
1000211   udp  46283  nlockmgr
1000213   udp  46283  nlockmgr
1000214   udp  46283  nlockmgr
1000211   tcp  40039  nlockmgr
1000213   tcp  40039  nlockmgr
1000214   tcp  40039  nlockmgr
142   udp856  ypserv
141   udp856  ypserv
142   tcp857  ypserv
141   tcp857  ypserv
191   udp866  yppasswdd
 6001000691   udp874  fypxfrd
 6001000691   tcp875  fypxfrd
172   udp969  ypbind
171   udp969  ypbind
172   tcp970  ypbind
171   tcp970  ypbind
1000241   udp  44513  status
1000241   tcp  58657  status
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/exports
192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide,fsid=root) 
127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide,fsid=root)
/exports/md0
192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide) 
127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide)
/exports/md1
192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide) 
127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide)
/exports/md2
192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide) 
127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs
/exports/md0
192.168.0.0/16(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,uuid=a114f04d:9e54427e:b051ce17:4dc02e9f,sec=1)
/exports
192.168.0.0/16(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,fsid=0,uuid=a3734f7a:774744b7:b41d4cea:bc2a4f0f,sec=1)
/exports
127.0.0.0/8(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,fsid=0,uuid=a3734f7a:774744b7:b41d4cea:bc2a4f0f,sec=1)
/exports/md0
127.0.0.0/8(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,uuid=a114f04d:9e54427e:b051ce17:4dc02e9f,sec=1)

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-kernel-server depends on:
ii  init-system-helpers  1.48
ii  keyutils 1.5.9-9
ii  libblkid12.29.2-1
ii  libc62.24-11+deb9u1
ii  libcap2  1:2.25-1
ii  libsqlite3-0 3.16.2-5
ii  libtirpc10.2.5-1.2
ii  libwrap0 7.6.q-26
ii  lsb-base 9.20161125
ii  netbase  5.4
ii  nfs-common   1:1.3.4-2.1
ii  ucf  3.0036

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information

Bug#884183: Bug 884183

2017-12-13 Thread Gerald Schroll 
We encountered the same problem on 6 of our machines (3 different
models). Please find attached the bootlogs.
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) 
(gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.51-2 (2017-12-03)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=fdb8a0cf-5f7f-4f0d-99e2-09e1da1e6294 ro single console=tty0 
console=ttyS0,9600n8
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009afff] usable
[0.00] BIOS-e820: [mem 0x0009b000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x7823cfff] usable
[0.00] BIOS-e820: [mem 0x7823d000-0x7888efff] ACPI NVS
[0.00] BIOS-e820: [mem 0x7888f000-0x788dafff] ACPI data
[0.00] BIOS-e820: [mem 0x788db000-0x788ddfff] reserved
[0.00] BIOS-e820: [mem 0x788de000-0x78b8afff] ACPI data
[0.00] BIOS-e820: [mem 0x78b8b000-0x78c1cfff] reserved
[0.00] BIOS-e820: [mem 0x78c1d000-0x78c51fff] ACPI data
[0.00] BIOS-e820: [mem 0x78c52000-0x78c54fff] reserved
[0.00] BIOS-e820: [mem 0x78c55000-0x78c64fff] ACPI data
[0.00] BIOS-e820: [mem 0x78c65000-0x78c73fff] reserved
[0.00] BIOS-e820: [mem 0x78c74000-0x78c76fff] ACPI data
[0.00] BIOS-e820: [mem 0x78c77000-0x78c7afff] reserved
[0.00] BIOS-e820: [mem 0x78c7b000-0x78c8efff] ACPI data
[0.00] BIOS-e820: [mem 0x78c8f000-0x78c91fff] reserved
[0.00] BIOS-e820: [mem 0x78c92000-0x78caefff] ACPI data
[0.00] BIOS-e820: [mem 0x78caf000-0x78cd8fff] reserved
[0.00] BIOS-e820: [mem 0x78cd9000-0x78cf7fff] ACPI data
[0.00] BIOS-e820: [mem 0x78cf8000-0x78cfbfff] reserved
[0.00] BIOS-e820: [mem 0x78cfc000-0x78cfcfff] ACPI data
[0.00] BIOS-e820: [mem 0x78cfd000-0x78d00fff] reserved
[0.00] BIOS-e820: [mem 0x78d01000-0x78d01fff] ACPI data
[0.00] BIOS-e820: [mem 0x78d02000-0x78d05fff] reserved
[0.00] BIOS-e820: [mem 0x78d06000-0x78d06fff] ACPI data
[0.00] BIOS-e820: [mem 0x78d07000-0x78d09fff] reserved
[0.00] BIOS-e820: [mem 0x78d0a000-0x78d12fff] ACPI data
[0.00] BIOS-e820: [mem 0x78d13000-0x78d53fff] reserved
[0.00] BIOS-e820: [mem 0x78d54000-0x79093fff] ACPI data
[0.00] BIOS-e820: [mem 0x79094000-0x790c3fff] reserved
[0.00] BIOS-e820: [mem 0x790c4000-0x7946dfff] ACPI data
[0.00] BIOS-e820: [mem 0x7946e000-0x796edfff] ACPI NVS
[0.00] BIOS-e820: [mem 0x796ee000-0x798edfff] ACPI data
[0.00] BIOS-e820: [mem 0x798ee000-0x79903fff] reserved
[0.00] BIOS-e820: [mem 0x79904000-0x79919fff] ACPI data
[0.00] BIOS-e820: [mem 0x7991a000-0x79928fff] reserved
[0.00] BIOS-e820: [mem 0x79929000-0x79935fff] ACPI data
[0.00] BIOS-e820: [mem 0x79936000-0x79938fff] reserved
[0.00] BIOS-e820: [mem 0x79939000-0x7993dfff] ACPI data
[0.00] BIOS-e820: [mem 0x7993e000-0x7993] reserved
[0.00] BIOS-e820: [mem 0x7994-0x79e0cfff] ACPI data
[0.00] BIOS-e820: [mem 0x79e0d000-0x79e0efff] reserved
[0.00] BIOS-e820: [mem 0x79e0f000-0x79e34fff] ACPI data
[0.00] BIOS-e820: [mem 0x79e35000-0x79e9] reserved
[0.00] BIOS-e820: [mem 0x79ea-0x7bd5efff] ACPI data
[0.00] BIOS-e820: [mem 0x7bd5f000-0x7bdfefff] reserved
[0.00] BIOS-e820: [mem 0x7bdff000-0x7bdf] ACPI data
[0.00] BIOS-e820: [mem 0x7be0-0x7be4efff] reserved
[0.00] BIOS-e820: [mem 0x7be4f000-0x7bf82fff] ACPI data
[0.00] BIOS-e820: [mem 0x7bf83000-0x7bfcefff] ACPI NVS
[0.00] BIOS-e820: [mem 0x7bfcf000-0x7bffefff] ACPI data
[0.00] BIOS-e820: [mem 0x7bfff000-0x8fff] reserved
[0.00] BIOS-e820: [mem 0xfc00-0xfcff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.