Bug#842971: bumblebeed on ppc32 ? (was: loading nouveau causes screen to become unresponsive)

[Karl-Philipp Richter]

Hi,

Am 07.11.2016 um 07:44 schrieb Mathieu Malaterre:
> You have a really surprising setup. How is it even possible to have
> bumblebeed on PPC32 ? the package is supposed to be empty for this
> arch.
It's on an iMac G4 PowerMac6,1.

> What's the output of:
> 
> $ apt-cache policy bumblebee

bumblebee:
  Installiert:   3.2.1-13
  Installationskandidat: 3.2.1-13
  Versionstabelle:
 *** 3.2.1-13 100
100 /var/lib/dpkg/status

> $ dpkg -L bumblebee

/.
/etc
/etc/bumblebee
/etc/bumblebee/bumblebee.conf
/etc/bumblebee/xorg.conf.d
/etc/bumblebee/xorg.conf.d/10-dummy.conf
/etc/bumblebee/xorg.conf.nouveau
/etc/bumblebee/xorg.conf.nvidia
/etc/init
/etc/init/bumblebeed.conf
/etc/init.d
/etc/init.d/bumblebeed
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/bumblebeed.service
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/99-bumblebee-nvidia-dev.rules
/usr
/usr/bin
/usr/bin/bumblebee-bugreport
/usr/bin/optirun
/usr/sbin
/usr/sbin/bumblebeed
/usr/share
/usr/share/bash-completion
/usr/share/bash-completion/completions
/usr/share/bash-completion/completions/bumblebee
/usr/share/bumblebee
/usr/share/bumblebee/default-conf
/usr/share/bumblebee/default-conf/bumblebee.conf
/usr/share/bumblebee/default-conf/xorg.conf.d
/usr/share/bumblebee/default-conf/xorg.conf.d/10-dummy.conf
/usr/share/bumblebee/default-conf/xorg.conf.nouveau
/usr/share/bumblebee/default-conf/xorg.conf.nvidia
/usr/share/bumblebee/modprobe.d
/usr/share/bumblebee/modprobe.d/bumblebee.conf
/usr/share/doc
/usr/share/doc/bumblebee
/usr/share/doc/bumblebee/README.Debian
/usr/share/doc/bumblebee/README.markdown
/usr/share/doc/bumblebee/RELEASE_NOTES_3_2_1
/usr/share/doc/bumblebee/changelog.Debian.gz
/usr/share/doc/bumblebee/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/bumblebeed.1.gz
/usr/share/man/man1/optirun.1.gz

Thank you for you interest. It'd be interesting to get a desktop running
to the old iMac.



signature.asc
Description: OpenPGP digital signature

Bug#842971: bumblebeed on ppc32 ? (was: loading nouveau causes screen to become unresponsive)

[Mathieu Malaterre]

Hi,

On Sun, Nov 6, 2016 at 8:28 PM, Karl-Philipp Richter  wrote:
[...]
> Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Service
> hold-off time over, scheduling restart.
> Nov  6 20:24:45 debian systemd[1]: Stopped Bumblebee C Daemon.
> Nov  6 20:24:45 debian systemd[1]: Started Bumblebee C Daemon.
> Nov  6 20:24:45 debian bumblebeed[1105]: [  136.560197] [ERROR]No
> integrated video card found, quitting.
> Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Main process
> exited, code=exited, status=1/FAILURE
> Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Unit entered
> failed state.
> Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Failed with
> result 'exit-code'.
[...]

You have a really surprising setup. How is it even possible to have
bumblebeed on PPC32 ? the package is supposed to be empty for this
arch.

What's the output of:

$ apt-cache policy bumblebee
$ dpkg -L bumblebee

Thanks

Processed: your mail

[Debian Bug Tracking System]

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

> block 842971 by 842964
Bug #842971 [src:linux] linux-image-4.7.0-1-powerpc: loading nouveau causes 
screen to become unresponsive
842971 was not blocked by any bugs.
842971 was not blocking any bugs.
Added blocking bug(s) of 842971: 842964
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 842971 https://bugzilla.kernel.org/show_bug.cgi?id=187111
Bug #842971 [src:linux] linux-image-4.7.0-1-powerpc: loading nouveau causes 
screen to become unresponsive
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=187111'.
> tags 842971 upstream
Bug #842971 [src:linux] linux-image-4.7.0-1-powerpc: loading nouveau causes 
screen to become unresponsive
Added tag(s) upstream.
>
End of message, stopping processing here.

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

Bug#843485: mention () vs (()) of filename

[積丹尼 Dan Jacobson]

Package: linux-doc-4.8
Version: 4.8.5-1
Severity: wishlist
File: /usr/share/doc/linux-doc-4.8/Documentation/filesystems/proc.txt.gz

One only sees
  tcomm filename of the executable

But no explanation of () vs (())

$ perl -anwle 'print $F[1]' /proc/[0-9]*/stat|sort -u|head
((sd-pam))
(Xorg)
(acpi_thermal_pm)

Bug#842971: loading nouveau causes screen to become unresponsive

[Karl-Philipp Richter]

Hi,

Am 04.11.2016 um 08:04 schrieb Mathieu Malaterre:
> Here is what I would do:
> 
> #1. Have an ssh connection ready. Right after doing your `modprobe
> nouveau`, run `dmesg` from the ssh connection and copy/paste.
> 
> #2. All logs are stored in /var/log/syslog. Then they are archived in
> gz form. So you should be able to do something like `zgrep nouveau
> /var/log/syslog*.gz`. It may be more difficult to search through this,
> so I would suggest #1 first if you can.

The changes in `/var/log/syslog` after `modprobe nouveau` (are the same
as in `dmesg`):

Nov  6 20:24:41 debian kernel: [  132.889027] [drm] Initialized drm
1.1.0 20060810
Nov  6 20:24:42 debian kernel: [  133.287204] checking generic
(98004000 c) vs hw (9800 800)
Nov  6 20:24:42 debian kernel: [  133.287226] fb: switching to
nouveaufb from OFfb NVDA,NVMac
Nov  6 20:24:42 debian kernel: [  133.287498] Console: switching to
colour dummy device 80x25
Nov  6 20:24:42 debian kernel: [  133.291700] nouveau :00:10.0:
NVIDIA NV11 (011000b2)
Nov  6 20:24:42 debian kernel: [  133.303059] nouveau :00:10.0:
bios: version 03.11.00.15.00
Nov  6 20:24:42 debian kernel: [  133.303102] nouveau :00:10.0:
bios: DCB table not found
Nov  6 20:24:42 debian kernel: [  133.315098] nouveau :00:10.0:
bios: DCB table not found
Nov  6 20:24:42 debian kernel: [  133.316476] nouveau :00:10.0:
bios: DCB table not found
Nov  6 20:24:42 debian kernel: [  133.316501] nouveau :00:10.0:
bios: DCB table not found
Nov  6 20:24:42 debian kernel: [  133.316555] nouveau :00:10.0:
bios: DCB table not found
Nov  6 20:24:42 debian kernel: [  133.505732] nouveau :00:10.0:
tmr: unknown input clock freq
Nov  6 20:24:42 debian kernel: [  133.506519] nouveau :00:10.0:
fb: 64 MiB DDR1
Nov  6 20:24:42 debian kernel: [  133.512136] [TTM] Zone  kernel:
Available graphics memory: 125276 kiB
Nov  6 20:24:42 debian kernel: [  133.512159] [TTM] Initializing
pool allocator
Nov  6 20:24:42 debian kernel: [  133.512245] nouveau :00:10.0:
DRM: VRAM: 63 MiB
Nov  6 20:24:42 debian kernel: [  133.512253] nouveau :00:10.0:
DRM: GART: 128 MiB
Nov  6 20:24:42 debian kernel: [  133.512267] nouveau :00:10.0:
DRM: BMP version 5.16
Nov  6 20:24:42 debian kernel: [  133.512278] nouveau :00:10.0:
DRM: No DCB data found in VBIOS
Nov  6 20:24:42 debian kernel: [  133.517274] nouveau :00:10.0:
DRM: Adaptor not initialised, running VBIOS init tables.
Nov  6 20:24:42 debian kernel: [  133.519035] nouveau :00:10.0:
DRM: Saving VGA fonts
Nov  6 20:24:42 debian kernel: [  133.571915] nouveau :00:10.0:
DRM: No DCB data found in VBIOS
Nov  6 20:24:42 debian kernel: [  133.578176] [drm] Supports vblank
timestamp caching Rev 2 (21.10.2013).
Nov  6 20:24:42 debian kernel: [  133.578198] [drm] Driver supports
precise vblank timestamp query.
Nov  6 20:24:42 debian kernel: [  133.586305] nouveau :00:10.0:
DRM: MM: using M2MF for buffer copies
Nov  6 20:24:42 debian kernel: [  133.640067] nouveau :00:10.0:
fifo: DMA_PUSHER - ch 0 [DRM] get 80086078 put 016c state c16c
(err: MEM_FAULT) push 
Nov  6 20:24:42 debian kernel: [  133.640093] nouveau :00:10.0:
fifo: intr 0001
Nov  6 20:24:42 debian kernel: [  133.640123] nouveau :00:10.0:
DRM: allocated 1024x768 fb: 0x8000, bo cc34
Nov  6 20:24:42 debian kernel: [  133.647447] Console: switching to
colour frame buffer device 128x48
Nov  6 20:24:42 debian kernel: [  133.647500] nouveau :00:10.0:
fb0: nouveaufb frame buffer device
Nov  6 20:24:42 debian kernel: [  133.647539] [drm] Initialized
nouveau 1.3.1 20120801 for :00:10.0 on minor 0
Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Service
hold-off time over, scheduling restart.
Nov  6 20:24:45 debian systemd[1]: Stopped Bumblebee C Daemon.
Nov  6 20:24:45 debian systemd[1]: Started Bumblebee C Daemon.
Nov  6 20:24:45 debian bumblebeed[1105]: [  136.560197] [ERROR]No
integrated video card found, quitting.
Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Main process
exited, code=exited, status=1/FAILURE
Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Unit entered
failed state.
Nov  6 20:24:45 debian systemd[1]: bumblebeed.service: Failed with
result 'exit-code'.

Thanks for your suggestions.

-Kalle



signature.asc
Description: OpenPGP digital signature

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Vagrant Cascadian]

Package: src:linux
Version: 4.8.5-1
Severity: important

When upgrading to linux 4.8.x on an Odroid-XU4 system, it no longer
detects the USB sata adapter where rootfs is located.

Downgrading to the 4.7.x kernel from jessie-backports works fine.

I didn't see anything obviously missing when diffing /boot/config-*.

Boot log attached.

If there's nothing obvious fromt the boot log, I can try taking it
offline and doing an install with stretch or sid to do more debugging.


live well,
  vagrant

-- Package-specific info:
** Model information
Hardware: SAMSUNG EXYNOS (Flattened Device Tree)
Revision: 
Device Tree model: Hardkernel Odroid XU4

** PCI devices:

** USB devices:
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. 
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 174c:55aa ASMedia Technology Inc. ASMedia 2105 SATA 
bridge
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental'), 
(1, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.7.0-0.bpo.1-armmp-lpae (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.8.0-1-armmp-lpae depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.120+deb8u2
ii  kmod18-3
ii  linux-base  4.3~bpo8+1

Versions of packages linux-image-4.8.0-1-armmp-lpae recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3

Versions of packages linux-image-4.8.0-1-armmp-lpae suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.8   

Versions of packages linux-image-4.8.0-1-armmp-lpae is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information



odxu4c.log
Description: Binary data


signature.asc
Description: PGP signature

Re: linux-image-3.2.0-4-486

[Miroslav Skoric]

On 11/05/2016 10:37 PM, Ben Hutchings wrote:



Please use 'reportbug kernel' to open a bug report and attach the file
to the report.



Done.

Processed: retitle Bug#843262

[Debian Bug Tracking System]

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

> retitle 843262 linux-image-4.7.0-0.bpo.1-amd64: CPU gets stuck in nouveau 
> driver
Bug #843262 [src:linux] linux-image-4.7.0-0.bpo.1-amd64: Xorg hangs in nouveau 
driver
Changed Bug title to 'linux-image-4.7.0-0.bpo.1-amd64: CPU gets stuck in 
nouveau driver' from 'linux-image-4.7.0-0.bpo.1-amd64: Xorg hangs in nouveau 
driver'.
>
End of message, stopping processing here.

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

Bug#843262: linux-image-4.7.0-0.bpo.1-amd64: CPU gets stuck in nouveau driver

[Leon Weber]

I forgot to add: That last freeze had occurred while trying to open
icedove. I noticed some of these lines in dmesg:

[23107.779526] nouveau :01:00.0: icedove[3647]: failed to idle channel 5 
[icedove[3647]]


signature.asc
Description: PGP signature

Bug#843262: linux-image-4.7.0-0.bpo.1-amd64: Xorg hangs in nouveau driver

[Leon Weber]

retitle 843262 CPU stuck in nouveau driver

The freeze has occured again, however this time, the call trace looks
different and the process affected is not Xorg but kworker. Full dmesg
output attached.
[0.00] Linux version 4.7.0-0.bpo.1-amd64 
(debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP 
Debian 4.7.8-1~bpo8+1 (2016-10-19)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-0.bpo.1-amd64 
root=UUID=92ce493a-b1cd-4d80-a9e3-9c0d2929812d ro quiet
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[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: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009abff] usable
[0.00] BIOS-e820: [mem 0x0009ac00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbf55afff] usable
[0.00] BIOS-e820: [mem 0xbf55b000-0xbf5aafff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbf5ab000-0xbf5cbfff] reserved
[0.00] BIOS-e820: [mem 0xbf5cc000-0xbf5cdfff] usable
[0.00] BIOS-e820: [mem 0xbf5ce000-0xbf5eefff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbf5ef000-0xbf5fcfff] reserved
[0.00] BIOS-e820: [mem 0xbf5fd000-0xbf607fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbf608000-0xbf641fff] reserved
[0.00] BIOS-e820: [mem 0xbf642000-0xbf684fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbf685000-0xbf7f] usable
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00013f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.6 present.
[0.00] DMI: LENOVO Lenovo H420/To be filled by O.E.M., BIOS DPKT15A 
02/25/2011
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x13f800 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-C write-protect
[0.00]   D-E7FFF uncachable
[0.00]   E8000-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0 mask F write-back
[0.00]   1 base 1 mask FC000 write-back
[0.00]   2 base 0C000 mask FC000 uncachable
[0.00]   3 base 13F80 mask FFF80 uncachable
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: update [mem 0xc000-0x] usable ==> reserved
[0.00] e820: last_pfn = 0xbf800 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fcd00-0x000fcd0f] mapped at 
[880fcd00]
[0.00] Base memory trampoline at [88094000] 94000 size 24576
[0.00] BRK [0x14d4e000, 0x14d4efff] PGTABLE
[0.00] BRK [0x14d4f000, 0x14d4] PGTABLE
[0.00] BRK [0x14d5, 0x14d50fff] PGTABLE
[0.00] BRK [0x14d51000, 0x14d51fff] PGTABLE
[0.00] BRK [0x14d52000, 0x14d52fff] PGTABLE
[0.00] RAMDISK: [mem 0x360c8000-0x3705bfff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F0430 24 (v02 LENOVO)
[0.00] ACPI: XSDT 0xBF5A3068 54 (v01 LENOVO TC-03
0115 AMI  00010013)
[0.00] ACPI: FACP 0xBF5A9D68 F4 (v04 LENOVO TC-03
0115 AMI  00010013)
[0.00] ACPI: DSDT 0xBF5A3150 006C11 (v02 LENOVO TC-03
0115 INTL 20051117)
[0.00] ACPI: FACS 0xBF5FFF80 40
[0.00] ACPI: APIC 0xBF5A9E60 72 (v03 LENOVO TC-03
0115 AMI  00010013)
[0.00] ACPI: SSDT 0xBF5A9ED8 000102 (v01 LENOVO TC-03
0115 MSFT 0301)
[0.00] ACPI: MCFG 0xBF5A9FE0 3C (v01 LENOVO TC-03
0115 MSFT 0097)
[0.00] ACPI: SLIC 0xBF5AA020 000176 (v01 LENOVO TC-03
0115 AMI  00010013)
[0.00] ACPI: 

Bug#843153: [Pkg-samba-maint] Bug#843153: Provide a means to wake-up (reconnect) an existing share

[martin f krafft]

also sprach Mathieu Parent  [2016-11-05 20:59 +0100]:
> > After a laptop suspend, SMB sessions are usually disconnected on the
> > server, and even the client will have a hard time just resuming.
> 
> This is most probably kernel-side.

Yes, I agree. Per se it's not a bug. I filed this against cifs-utils
because I was imagining a user-space interface to influence the
kernel.

> > This will either lead to soft-errors or hard-blocks, until on
> > the client, eventually, the kernel states
>
> eventually? Meaning not always?

No, always. I should have used another word. In English, eventually
means that something will happen, whereas in German and possibly
French, it might suggest that something possibly happens, or not.

> > I don't really want to shorten the 120 seconds (and I wouldn't know
> > how, there seems to be no mount option),
> 
> 120 comes from echo_interval [1] which looks undocumented.
> 
> [1] http://sources.debian.net/src/linux/4.8.5-1/fs/cifs/connect.c/?hl=496#L496

Seems a bit weird that this is hard-coded.

> Again, have you tried mount -o remount?

Yes, but unfortunately it doesn't have the desired effect. It just
blocks until the 120 seconds are over. It'd be a nice interface
though!

> > which would immediately cause a reconnection, not only after 120
> > seconds. This could then be executed by systemd for the resume
> > target…
> 
> Looking at the NFS kernel code, I don't see any resume handling.
> I don't know if it's affected too.

As far as I know, it's not affected, because NFS is datagram-based,
whereas CIFS is session-based. It's a bit like mosh and SSH…

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"in any hierarchy, each individual rises
 to his own level of incompetence,
 and then remains there."
 -- murphy (after dr. laurence j. peter)


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#843349: linux-image-4.7.0-1-amd64: Intermittently high system load, sluggish response, no /proc//stat utime,stime,etc. reported

[Tom Lee]

Package: src:linux
Version: 4.7.8-1
Severity: important

Dear Maintainer,

Experienced poor system-wide performance since linux-image-amd64 pulled
down 4.7.0-1. Tried to investigate what was going on, only to discover that
tools like top/htop were unable to report per-process
CPU time (though system-wide CPU stats based on /proc/stat were still
reporting fine). Further analysis shows /proc//stat CPU fields stuck at
zero.

The impact seems to be emphasized when a brief but moderately heavy load
occurs (e.g. kicking off CMake, performing certain operations within
CLion/other IDEs, etc.): in 4.6.0-1 you see a brief uptick in CPU burn in
top/htop that settles quickly; with 4.7.0-1 the effect of the burst of
activity
seems to be emphasized -- load average drastically and quickly increases,
CPU activity goes through the roof and the system becomes intermittently
unresponsive.

The system is ultimately usable, but feels very sluggish overall.

Downgrading to linux-image-4.6.0-1-amd64 fixed all symptoms. Haven't yet
tried 4.8.0-1 from unstable, not sure if it's impacted.

Thank you!
Tom

-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version
5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64
root=UUID=4c115ce4-a646-41dc-a1b0-7120b87bfdd9 ro quiet

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[3.995767] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[3.995774] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1
(0x1b/0x0/0x0/0x0/0x0)
[3.995778] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[3.995782] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[3.995784] snd_hda_codec_realtek hdaudioC0D0:inputs:
[3.995789] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[3.995793] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[3.995796] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[4.017080] input: HDA Intel PCH Front Mic as
/devices/pci:00/:00:1b.0/sound/card0/input7
[4.017326] input: HDA Intel PCH Rear Mic as
/devices/pci:00/:00:1b.0/sound/card0/input8
[4.017626] input: HDA Intel PCH Line as
/devices/pci:00/:00:1b.0/sound/card0/input9
[4.017809] input: HDA Intel PCH Line Out Front as
/devices/pci:00/:00:1b.0/sound/card0/input10
[4.019047] iTCO_vendor_support: vendor-support=0
[4.021209] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[4.021286] iTCO_wdt: Found a Patsburg TCO device (Version=2,
TCOBASE=0x0460)
[4.024186] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[4.024256] input: HDA Intel PCH Line Out Surround as
/devices/pci:00/:00:1b.0/sound/card0/input11
[4.024510] input: HDA Intel PCH Line Out CLFE as
/devices/pci:00/:00:1b.0/sound/card0/input12
[4.024745] input: HDA Intel PCH Line Out Side as
/devices/pci:00/:00:1b.0/sound/card0/input13
[4.024899] input: HDA Intel PCH Front Headphone as
/devices/pci:00/:00:1b.0/sound/card0/input14
[4.057280] hid-generic 0003:187C:0513.0001: hiddev0,hidraw0: USB HID
v1.01 Device [Alienware Gaming Desktop] on usb-:00:1d.0-1.5/input0
[4.057546] input: Logitech USB Keyboard as
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1.4/4-1.1.4.1/4-1.1.4.1:1.0/0003:046D:C31C.0002/input/input15
[4.116721] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID
v1.10 Keyboard [Logitech USB Keyboard] on usb-:00:1d.0-1.1.4.1/input0
[4.129214] input: Logitech USB Keyboard as
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1.4/4-1.1.4.1/4-1.1.4.1:1.1/0003:046D:C31C.0003/input/input16
[4.184284] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID
v1.10 Device [Logitech USB Keyboard] on usb-:00:1d.0-1.1.4.1/input1
[4.184534] input: Logitech USB Keyboard as
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1.4/4-1.1.4.1/4-1.1.4.1:1.2/0003:046D:C31C.0004/input/input17
[4.184746] hid-generic 0003:046D:C31C.0004: input,hidraw3: USB HID
v1.10 Mouse [Logitech USB Keyboard] on usb-:00:1d.0-1.1.4.1/input2
[4.225123] EDAC MC: Ver: 3.0.0
[4.229203] EDAC sbridge: Seeking for: PCI ID 8086:3ca0
[4.229221] EDAC sbridge: Seeking for: PCI ID 8086:3ca0
[4.229226] EDAC sbridge: Seeking for: PCI ID 8086:3ca8
[4.229234] EDAC sbridge: Seeking for: PCI ID 8086:3ca8
[4.229237] EDAC sbridge: Seeking for: PCI ID 8086:3c71
[4.229244] EDAC sbridge: Seeking for: PCI ID 8086:3c71
[4.229248] EDAC sbridge: Seeking for: PCI ID 8086:3caa
[4.229255] EDAC sbridge: Seeking for: PCI ID 8086:3caa
[4.229258] EDAC sbridge: Seeking for: PCI ID 8086:3cab
[4.229265] EDAC sbridge: Seeking for: PCI ID 8086:3cab
[4.229268] EDAC sbridge: Seeking for: PCI ID 8086:3cac
[4.229276] EDAC sbridge: