Thanks for the offer Joseph! I have read your answer a bit late, so I am already on my 9th kernel (all good so far). The docs were quite good and I have wanted to try out "that bisect thing" for quite a while :)
(It's just a bit annoying that it takes about half an hour to compile on a i5-6500 with 16G RAM. I had expected a bit less.) But now I have run into the problem, that I cannot build the current bisect point. I have cloned the kernel repo via git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git I have attached the git bisect log up to the current point. When the compile is just about to be finished it fails with: EE: 36 symbols changed hash and weren't ignored II: Module hash change summary... vmlinux : 36 II: Done debian/rules.d/4-checks.mk:3: die Regel für Ziel „abi-check-generic“ scheiterte make: *** [abi-check-generic] Fehler 1 Sorry it's in German, I can redo it in english. I will attach a longer trace. I have always compiled doing a clean first: fakeroot debian/rules clean && fakeroot debian/rules binary-headers binary-generic So how do I go on from here? ** Attachment added: "git bisect log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755113/+files/git_bisect_log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Confirmed Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXXXXXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXXXXXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXXXXXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXXXXXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F.... pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lo no wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware 1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp