Bug#864463: linux-headers-4.9.0-3-common-rt: Detecting -rt source with localversion-rt

[Ben Hutchings]

Control: block 864404 with -1

On Thu, 2017-06-08 at 23:17 +, Gavin Lambert wrote:
> Package: linux-headers-4.9.0-3-common-rt
> Version: 4.9.30-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> Using linux-headers-4.9.0-3-common-rt with lttng-modules-dkms causes
> a FTBFS because the -rt and non-rt APIs are different.

They shouldn't be...

> lttng-modules-dkms includes a mechanism to auto-detect the use of -rt
> source but this requires the presence of the localversion-rt file in
> the source tree, which is not currently included in the headers
> package.
> 
> Without that file I can't see any obvious way to discover that -rt
> patches are applied or to which rt-patchlevel.

I suppose we could do that.

> Can you please either include this file in the headers package or let
> the maintainer of lttng-modules-dkms know what is the preferred
> alternate method to discover that?

If CONFIG_PREEMPT_RT is defined you can infer that some version of the
PREEMPT_RT patchset has been applied.  But it is possible, though
unusual, to build with that patchset and select a different preemption 
model...

> For more information, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864404.

I see, this is related to tracepoints.  As they aren't intended to be
APIs, it's fine for -rt to be different here.

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.



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

Processed: Re: Bug#864463: linux-headers-4.9.0-3-common-rt: Detecting -rt source with localversion-rt

[Debian Bug Tracking System]

Processing control commands:

> block 864404 with -1
Bug #864404 [lttng-modules-dkms] lttng-modules-dkms: module FTBFS in stretch 
against Linux 4.9-rt (succeeds for non-rt)
864404 was not blocked by any bugs.
864404 was not blocking any bugs.
Added blocking bug(s) of 864404: 864463

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

Processed: reassign 864463 to src:linux

[Debian Bug Tracking System]

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

> reassign 864463 src:linux 4.9.30-1
Bug #864463 [linux-headers-4.9.0-3-common-rt] linux-headers-4.9.0-3-common-rt: 
Detecting -rt source with localversion-rt
Bug reassigned from package 'linux-headers-4.9.0-3-common-rt' to 'src:linux'.
No longer marked as found in versions linux/4.9.30-1.
Ignoring request to alter fixed versions of bug #864463 to the same values 
previously set
Bug #864463 [src:linux] linux-headers-4.9.0-3-common-rt: Detecting -rt source 
with localversion-rt
Marked as found in versions linux/4.9.30-1.
> thanks
Stopping processing here.

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

Processed: reassign 864453 to src:linux, tagging 864453

[Debian Bug Tracking System]

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

> reassign 864453 src:linux 4.9.30-1
Bug #864453 [linux] fanotify07 LTP testcase hangs process
Bug reassigned from package 'linux' to 'src:linux'.
No longer marked as found in versions 4.9.30.
Ignoring request to alter fixed versions of bug #864453 to the same values 
previously set
Bug #864453 [src:linux] fanotify07 LTP testcase hangs process
Marked as found in versions linux/4.9.30-1.
> tags 864453 + patch upstream fixed-upstream
Bug #864453 [src:linux] fanotify07 LTP testcase hangs process
Added tag(s) upstream, patch, and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: severity of 864437 is important

[Debian Bug Tracking System]

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

> severity 864437 important
Bug #864437 [src:linux] linux-image-4.9.0-3-amd64: Soft lockup of igb/e1000e 
driver at stats update
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#864463: linux-headers-4.9.0-3-common-rt: Detecting -rt source with localversion-rt

[Gavin Lambert]

Package: linux-headers-4.9.0-3-common-rt
Version: 4.9.30-1
Severity: wishlist

Dear Maintainer,

Using linux-headers-4.9.0-3-common-rt with lttng-modules-dkms causes a FTBFS 
because the -rt and non-rt APIs are different.

lttng-modules-dkms includes a mechanism to auto-detect the use of -rt source 
but this requires the presence of the localversion-rt file in the source tree, 
which is not currently included in the headers package.

Without that file I can't see any obvious way to discover that -rt patches are 
applied or to which rt-patchlevel.

Can you please either include this file in the headers package or let the 
maintainer of lttng-modules-dkms know what is the preferred alternate method to 
discover that?

For more information, see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864404.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-72-generic (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[garjola]

On Fri 02-Jun-2017 at 19:03:13 +0200, garj...@garjola.net wrote: 
> On Thu 01-Jun-2017 at 23:58:43 +0200, Ben Hutchings  
> wrote: 
>> On Thu, 2017-06-01 at 23:36 +0200, garj...@garjola.net wrote:
>>> On Thu 01-Jun-2017 at 00:15:29 +0200, Ben Hutchings >> .uk> wrote: 
>>> > Control: tag -1 moreinfo
>>> > 
>>> > On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi 
>>> > wrote:
>>> > [...]
>>> > > For several weeks now I have been having issues after resume (both
>>> > 
>>> > from RAM or from disk): my /home seems not to be accessible (at least
>>> > for writing). This does not happen every time, but more something like
>>> > once every 10 or 20 resume cycles.
>>> > [...]
>>> > 
>>> > Please send the messages that appear in the kernel log when you resume.
>>> > (Run 'dmesg' as root to show the kernel log.)
>>> > 
>>> > Ben.
>>> 
>>> Hi,
>>> 
>>> The problem appeared again. I ran dmesg and piped the output to a file
>>> (in one of the non encrypted partitions) just after the problematic
>>> resume, but after reboot (to be able to send this message), the file was
>>> gone.
>>> 
>>> Below is the output of dmesg after a fresh reboot and one successful
>>> suspend/resume cycle. I dont't know if is is useful, since the problem
>>> has not happened since the reboot.
>> [...]
>>
>> I really need to see what happens in the failing case.
>>
>> Ben.
>
> Hi,
>
> Here goes the output of dmesg after a failing resume. I have used a usb
> stick to save the output of dmesg so that I could send it to you. This
> is the sdc device which appears at the end of the log.
>
> Thanks.
>
[...]

Hi, 

Today, after a failed resume I noticed that hard reset with the power button 
tries to shutdown and I could see messages like (copied from a picture of the 
screen, since I don't know how to capture this info):

Timed out stopping /dev/disk/by-id/dm-uuid_CRYPT-LUKS1-..-sda5_crypt.
Timed out stopping /sys/devices/virtual/block/dm-0.
Timed out stopping /dev/disk/by-id/dm-name-sda5_crypt.
Timed out stopping /dev/dm-0.

And also:
(1 of 3) A stop job is running for /dev/mapper/sda5_crypt
(2 of 3) A stop job is running for Disk Manager

Then:

Failed unmounting /boot
Failed unmounting /home

Again, I am attaching the output of dmesg:

[0.00] Linux version 4.9.0-3-amd64 (debian-kernel@lists.debian.org) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-1 
(2017-06-04)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 
root=UUID=98ae6177-1de0-4af2-b905-687df457f1ca ro quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dbff] usable
[0.00] BIOS-e820: [mem 0x0009dc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc70fafff] usable
[0.00] BIOS-e820: [mem 0xc70fb000-0xc7c7efff] reserved
[0.00] BIOS-e820: [mem 0xc7c7f000-0xc7e7efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xc7e7f000-0xc7efefff] ACPI data
[0.00] BIOS-e820: [mem 0xc7eff000-0xc7ef] usable
[0.00] BIOS-e820: [mem 0xc7f0-0xcc7f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved
[0.00] BIOS-e820: [mem 0xfedf-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff70-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0008317f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] DMI: HP HP EliteBook 840 G3/8079, BIOS N75 Ver. 01.13 11/01/2016
[0.00] e820: 

Bug#864200: Problem solved with cold reboot!

[Alan W. Irwin]

After several days of extensive testing of both the sound hardware 
(with a reliable source of analog sound) and software, I discovered

that a cold reboot (where computer and analog TV card were both
completely powered down before the boot) solved this issue.

My mental model of what has gone on here is the system upgrade of
either/both the bttv and snd_bt87x kernel modules put my WINTV-GO card
in a peculiar hardware state where the video still worked but lineout
(the analog sound output from that card) did not work. And the warm
reboot I normally do after any kernel upgrade did not correct that
issue. Only power cycling that card with a cold reboot got it out of
that peculiar hardware state.  I feel cold reboots are something of a
last resort so I doubt you would want to advise all Debian users to do
a cold reboot after every kernel upgrade.  But that tactic was
effective this time.

This peculiar state has never happened before for something like a
decade of Debian experience with this card.  However, I doubt there is
anything you can do to fix the above modules to avoid such rare
peculiar results during system upgrades so feel free to close this bug
report.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

Bug#864453: fanotify07 LTP testcase hangs process

[Helge Deller]

Package: linux
Version: 4.9.30

The LTP testcase fanotify07 creates hanging processes
with debian kernel 4.9.30 on the hppa platform.

In the source code of LTP's fanotify07.c testcase one can read:
 * Kernel crashes should be fixed by:
 *  96d41019e3ac "fanotify: fix list corruption in fanotify_get_response()"
 *
 * Kernel hangs should be fixed by:
 *  05f0e38724e8 "fanotify: Release SRCU lock when waiting for userspace 
response"

It seems upstream commit 
05f0e38724e8 "fanotify: Release SRCU lock when waiting for userspace response"
is missing in stable kernel 4.9.30 (and debian kernel), which explains why the
testcase hangs.
I didn't checked if the kernel crash fix is in 4.9.30.

Can you backport at least the commit 05f0e38724e8 ?

Thanks,
Helge

Bug#864437: linux-image-4.9.0-3-amd64: Soft lockup of igb/e1000e driver at stats update

[Rouven Spreckels]

Package: src:linux
Version: 4.9.30-1
Severity: critical
Tags: patch upstream
Justification: causes serious data loss

Hello,

the igb/e1000e driver causes a soft lockup when doing stats updates. For 
instance, when using the ledtrig-netdev kernel module to visualize network 
activity via LEDs. The lockup mostly happens within the first 3 days of uptime, 
probably depending on network activity:

[168313.275259] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!
[kworker/2:1:46]
[168323.276973] INFO: rcu_sched self-detected stall on CPU
[168323.282239] 2-...: (1 GPs behind)
idle=337/142/0 softirq=359087/359089 fqs=14081745 
[168323.291202]  (t=28187367 jiffies g=247240 c=247239
q=1072734)

The attached patch fixes the problem and originates from: 
http://git.ipfire.org/?p=people/arne_f/ipfire-2.x.git;a=commit;h=fcffac1340f61923786af8a860c12056a9ef3706

-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-1 (2017-06-04)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 
root=UUID=77a53576-9972-4229-b526-b41dac38844a ro console=ttyS0,115200 
earlyprint=serial,ttyS0,115200 quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[3.620382] igb :02:00.0 enp2s0: renamed from eth1
[3.766809] ata2: SATA link down (SStatus 0 SControl 300)
[3.767950] usb 1-1: new high-speed USB device number 2 using ehci-pci
[3.916363] usb 1-1: New USB device found, idVendor=0438, idProduct=7900
[3.916369] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[3.917813] hub 1-1:1.0: USB hub found
[3.917945] hub 1-1:1.0: 4 ports detected
[3.927913] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[3.928179] ata1.00: ATA-11: SATA SSD, SBFM01.0, max UDMA/133
[3.928184] ata1.00: 31277232 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[3.928445] ata1.00: configured for UDMA/133
[3.929358] scsi 0:0:0:0: Direct-Access ATA  SATA SSD 01.0 
PQ: 0 ANSI: 5
[3.970427] sd 0:0:0:0: [sda] 31277232 512-byte logical blocks: (16.0 
GB/14.9 GiB)
[3.970824] sd 0:0:0:0: [sda] Write Protect is off
[3.970831] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[3.970907] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[3.972327]  sda: sda1
[3.973719] sd 0:0:0:0: [sda] Attached SCSI disk
[4.095895] raid6: sse2x1   gen()   479 MB/s
[4.163885] raid6: sse2x1   xor()   709 MB/s
[4.231873] raid6: sse2x2   gen()  1157 MB/s
[4.299855] raid6: sse2x2   xor()   911 MB/s
[4.367891] raid6: sse2x4   gen()  1466 MB/s
[4.435908] raid6: sse2x4   xor()   997 MB/s
[4.435912] raid6: using algorithm sse2x4 gen() 1466 MB/s
[4.435914] raid6:  xor() 997 MB/s, rmw enabled
[4.435918] raid6: using ssse3x2 recovery algorithm
[4.435993] clocksource: Switched to clocksource tsc
[4.436784] xor: automatically using best checksumming function   avx   
[4.456601] Btrfs loaded, crc32c=crc32c-intel
[4.473946] BTRFS: device label root devid 1 transid 38792 /dev/sda1
[4.508781] BTRFS info (device sda1): disk space caching is enabled
[4.508800] BTRFS info (device sda1): has skinny extents
[4.519800] BTRFS info (device sda1): detected SSD devices, enabling SSD mode
[4.711926] random: fast init done
[4.760742] ip_tables: (C) 2000-2006 Netfilter Core Team
[4.772255] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[4.772993] systemd[1]: Detected architecture x86-64.
[4.774225] systemd[1]: Set hostname to .
[4.928434] systemd[1]: Created slice System Slice.
[4.929098] systemd[1]: Created slice system-getty.slice.
[4.929339] systemd[1]: Listening on Journal Socket.
[4.933803] systemd[1]: Starting Load Kernel Modules...
[4.934229] systemd[1]: Listening on Journal Audit Socket.
[4.934561] systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
[4.937822] systemd[1]: Starting Remount Root and Kernel File Systems...
[4.964485] ledtrig_netdev: loading out-of-tree module taints kernel.
[4.969080] BTRFS info (device sda1): disk space caching is enabled
[4.969906] leds-apu2: request GPIO LED driver module
[4.987415] leds-apu2: request Polled GPIO Buttons driver module
[5.006219] leds-apu2: load APU2/LED GPIO driver module
[5.006522] leds-apu2: PCI Revision ID: 0x42
[5.007123] leds-apu2: APU2 GPIO/LED driver module loaded
[5.007947] input: gpio-keys-polled as 
/devices/platform/gpio-keys-polled/input/input0
[5.193456] systemd-journald[215]: Received request to flush runtime journal 
from PID 1
[5.303098] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[5.314072] input: 

Re: Bug#864312: BUG: soft lockup - CPU#0 stuck for 22s!

[Harald Dunkel]

I had a similar effect for kernel linux-image-4.8.0-0.bpo.2-amd64-unsigned
(even though a reset on the front panel was sufficient to reboot). Some say
this problem has been introduced by memory cgroups.

Does this ring a bell? Are you using dockers or LXCs with cgroup_enable=memory ?

Regards
Harri

Bug#857081: linux-image-4.9.0-2-rt-amd64-unsigned: NOHZ: local_softirq_pending 80

[Laurent Bonnaud]

Hi,

this bug is still there in kernel 4.9.30 :

$ uname -a
Linux irancy.iut2.upmf-grenoble.fr 4.9.0-3-rt-amd64 #1 SMP PREEMPT RT Debian 
4.9.30-1 (2017-06-04) x86_64 GNU/Linux

$ dmesg
[...]
[187203.776023] NOHZ: local_softirq_pending 80

-- 
Laurent.