Bug#854771: linux kernel 4.9 causes vt and xserver freeze/not display

2017-02-09 Thread Linas Vepstas
Package: linux-image-4.9.0-1-amd64
Version: 4.9.6-3

Everything works under kernel 4.8, but have display problems
with x-server, virtual terminals when booting 4.9.  Diffs reveal
that the two kernels load different firmware for the graphics card.

Symptoms:
graphics card is wired up to drive three displays.
When xserver/gdm greater starts, third screen never
lights up; monitor states "no input signal".

virtual terminal switching (alt-pf1 through alt-pf6) fails
to change the display. The vt switch did occur: I can
blindly login to a virtual terminal, and run commands
in it; display stays frozen.

Killing/starting X11 fails to do anything at all to display:
no blinking, no refresh; display is frozen.

Graphics hardware:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Tonga PRO [Radeon R9 285/380] (rev f1)

Diffing the failed and the good boots, I see different firmware
being loaded for these two kernels.  Failing boot loads
amdgpu/tonga_k_smc.bin while the working boot loads
amdgpu/tonga_smc.bin


Failing boot looks like this:
cat /var/log/kern.log |grep firmware

Feb  9 21:52:37 fanny kernel: [4.240162] GHES: APEI firmware first
mode is enabled by WHEA _OSC.
Feb  9 21:52:37 fanny kernel: [   10.419654] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_mc.bin
Feb  9 21:52:37 fanny kernel: [   10.448529] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_pfp.bin
Feb  9 21:52:37 fanny kernel: [   10.462440] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_me.bin
Feb  9 21:52:37 fanny kernel: [   10.468253] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_ce.bin
Feb  9 21:52:37 fanny kernel: [   10.475209] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_rlc.bin
Feb  9 21:52:37 fanny kernel: [   10.477127] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_mec.bin
Feb  9 21:52:37 fanny kernel: [   10.478621] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_mec2.bin
Feb  9 21:52:37 fanny kernel: [   10.480364] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_sdma.bin
Feb  9 21:52:37 fanny kernel: [   10.480600] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_sdma1.bin
Feb  9 21:52:37 fanny kernel: [   10.482542] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_uvd.bin
Feb  9 21:52:37 fanny kernel: [   10.482548] [drm] Found UVD firmware
Version: 1.65 Family ID: 10
Feb  9 21:52:37 fanny kernel: [   10.483839] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_vce.bin
Feb  9 21:52:37 fanny kernel: [   10.483844] [drm] Found VCE firmware
Version: 52.8 Binary ID: 3
Feb  9 21:52:37 fanny kernel: [   10.681430] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_k_smc.bin


Working boot looks like this:
cat /var/log/kern.log |grep firmware

Feb  9 21:56:39 fanny kernel: [4.123908] GHES: APEI firmware first
mode is enabled by WHEA _OSC.
Feb  9 21:56:39 fanny kernel: [9.326443] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_mc.bin
Feb  9 21:56:39 fanny kernel: [9.738087] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_pfp.bin
Feb  9 21:56:39 fanny kernel: [9.738518] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_me.bin
Feb  9 21:56:39 fanny kernel: [9.738820] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_ce.bin
Feb  9 21:56:39 fanny kernel: [9.739161] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_rlc.bin
Feb  9 21:56:39 fanny kernel: [9.745141] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_mec.bin
Feb  9 21:56:39 fanny kernel: [9.746675] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_mec2.bin
Feb  9 21:56:39 fanny kernel: [9.747554] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_sdma.bin
Feb  9 21:56:39 fanny kernel: [9.747784] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_sdma1.bin
Feb  9 21:56:39 fanny kernel: [9.749821] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_uvd.bin
Feb  9 21:56:39 fanny kernel: [9.749828] [drm] Found UVD firmware
Version: 1.65 Family ID: 10
Feb  9 21:56:39 fanny kernel: [9.751288] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_vce.bin
Feb  9 21:56:39 fanny kernel: [9.751293] [drm] Found VCE firmware
Version: 52.8 Binary ID: 3
Feb  9 21:56:39 fanny kernel: [9.854098] amdgpu :04:00.0:
firmware: direct-loading firmware amdgpu/tonga_smc.bin



Bug#854353: linux-image-4.9.0-1-amd64: wifi internet is lost, using driver rtl8192ce

2017-02-09 Thread Ye, Quanzhi
This might be identical/related to bug #853073.

Quanzhi



CONFIG_DRM_AST on arm64? (was: Bug#820168: debian-installer vs. MP30-AR0)

2017-02-09 Thread Cyril Brulebois
Hi Ronald,

Ronald Maas  (2017-02-08):
> Good news. I was able to successfully install Stretch RC2 on the
> Gigabyte MP30-AR0 motherboard. Also the installer was able to
> recognize the network properly, so this bug and also bug 820022 can be
> closed.
> 
> Attached the dmesg output for reference.

This is great news, thanks for following up.

> A minor issue remaining is that the AST2400 VGA adapter is not
> recognized out of the box. Serial console did work and I was also able
> to ssh into the machine after installation and reboot. Reason is
> CONFIG_DRM_AST is not set in the kernel configuration. Hope Debian
> kernel team could consider changing it to compile it as a module.

Looking at the current sid branch of linux.git:
| kibi@armor:~/debian-kernel/linux.git$ git grep CONFIG_DRM_AST
| debian/config/config:# CONFIG_DRM_AST is not set
| debian/config/kernelarch-powerpc/config-arch-64:CONFIG_DRM_AST=m
| debian/config/kernelarch-x86/config:CONFIG_DRM_AST=m

Kernel team, it seems it would make sense to enable this module as well
for arm64?


KiBi.


signature.asc
Description: Digital signature


Bug#844446: Starting version should be 4.8-rc8

2017-02-09 Thread Lucien AT
Same problem here, E3-1230 v5. Stretch guest VM on RHEL 6.6 host.

Actually on my guest VM, this bug was from *4.8-rc8*, while 4.8-rc7 boots
well.

I do not have access to the host machine, so cannot test if those changes
in configuration works or not.

cpuinfo:
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 94
model name: Intel(R) Xeon(R) CPU E3-1230 v5 @ 3.40GHz
stepping: 3
microcode: 0x1
cpu MHz: 3407.998
cache size: 4096 KB
physical id: 0
siblings: 1
core id: 0
cpu cores: 1
apicid: 0
initial apicid: 0
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb lm
constant_tsc arch_perfmon nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand hypervisor lahf_lm abm 3dnowprefetch xsaveopt fsgsbase bmi1 hle avx2
smep bmi2 invpcid rtm rdseed adx
bogomips: 6815.99
clflush size: 64
cache_alignment: 64
address sizes: 39 bits physical, 48 bits virtual
power management:


Bug#853100: Classification of Bug

2017-02-09 Thread Thomas Vaughan
When I submitted this bug report, I classified it as "normal".

But I suspect that it is graver than that. My system is currently unusable
with the kernel in testing and the kernel in unstable.

Only by pulling the ancient kernel from stable can I use my system at all.

-- 
Thomas E. Vaughan


Bug#854695: firmware-linux-nonfree: more missing i915 firmware

2017-02-09 Thread Thorsten Glaser
Package: firmware-linux-nonfree
Version: 20161130-2
Severity: normal

Related to #838476:

W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20161130-2
ii  firmware-misc-nonfree  20161130-2

Versions of packages firmware-linux-nonfree recommends:
pn  amd64-microcode  
ii  intel-microcode  3.20161104.1

firmware-linux-nonfree suggests no packages.

-- no debconf information



Bug#854677: linux-image-amd64 - patches from kernel source required

2017-02-09 Thread Narayanan R S
Package: linux-image-amd64
Version: 4.9+78

The current (backported) version of linux-image-amd64 (for Jessie) appears
to need a few important fixes from the kernel source (upstream).

Please see:

https://www.spinics.net/lists/kernel/msg2406212.html
https://bugzilla.redhat.com/show_bug.cgi?id=1402695

It appears that this has been fixed in the 4.9 series after 4.9.5 (per the
bugzilla link above) - so can the package be suitably updated to
incorporate this fix?

Thanks in advance.

Regards,

Narayanan.


Bug#854662: linux-image-4.9.0-0.bpo.1-marvell: please enable CONFIG_SENSORS_G762

2017-02-09 Thread Scott Barker
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: wishlist

Dear Maintainer,

I am installing debian on a Netgear ReadyNAS Duo v2, and so far everything 
works except some of the sensors, because CONFIG_SENSORS_G762 is not set:

$ grep CONFIG_SENSORS_G762 /boot/config-4.9.0-0.bpo.1-marvell
# CONFIG_SENSORS_G762 is not set

Please consider enabling this feature. Thank you.

-- Package-specific info:
** Version:
Linux version 4.9.0-0.bpo.1-marvell (debian-kernel@lists.debian.org) (gcc 
version 4.9.2 (Debian 4.9.2-10) ) #1 Debian 4.9.2-2~bpo8+1 (2017-01-26)

** Command line:
root=/dev/md0 console=ttyS0,115200 earlyprintk reason=normal 
mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2);

** Not tainted

** Kernel log:
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.0-0.bpo.1-marvell 
(debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 
Debian 4.9.2-2~bpo8+1 (2017-01-26)
[0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), 
cr=0005397f
[0.00] CPU: VIVT data cache, VIVT instruction cache
[0.00] OF: fdt:Machine model: NETGEAR ReadyNAS Duo v2
[0.00] bootconsole [earlycon0] enabled
[0.00] Memory policy: Data cache writeback
[0.00] On node 0 totalpages: 65536
[0.00] free_area_init_node: node 0, pgdat c059d218, node_mem_map 
cfdf8000
[0.00]   Normal zone: 512 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 65536 pages, LIFO batch:15
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 65024
[0.00] Kernel command line: root=/dev/md0 console=ttyS0,115200 
earlyprintk reason=normal 
mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2);
[0.00] PID hash table entries: 1024 (order: 0, 4096 bytes)
[0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[0.00] Memory: 241080K/262144K available (3796K kernel code, 397K 
rwdata, 1124K rodata, 300K init, 298K bss, 21064K reserved, 0K cma-reserved, 0K 
highmem)
[0.00] Virtual kernel memory layout:
vector  : 0x - 0x1000   (   4 kB)
fixmap  : 0xffc0 - 0xfff0   (3072 kB)
vmalloc : 0xd080 - 0xff80   ( 752 MB)
lowmem  : 0xc000 - 0xd000   ( 256 MB)
pkmap   : 0xbfe0 - 0xc000   (   2 MB)
modules : 0xbf00 - 0xbfe0   (  14 MB)
  .text : 0xc0008000 - 0xc03bd2c8   (3797 kB)
  .init : 0xc04fd000 - 0xc0548000   ( 300 kB)
  .data : 0xc0548000 - 0xc05ab7e8   ( 398 kB)
   .bss : 0xc05ab7e8 - 0xc05f6060   ( 299 kB)
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] clocksource: orion_clocksource: mask: 0x max_cycles: 
0x, max_idle_ns: 9556302233 ns
[0.06] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 
10737418237ns
[0.008266] Console: colour dummy device 80x30
[0.012817] Calibrating delay loop... 1594.36 BogoMIPS (lpj=3188736)
[0.042766] pid_max: default: 32768 minimum: 301
[0.047596] Security Framework initialized
[0.051784] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.058590] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.065292] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.073254] CPU: Testing write buffer coherency: ok
[0.078286] ftrace: allocating 16938 entries in 34 pages
[0.109047] Setting up static identity map for 0x8200 - 0x823c
[0.115169] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[0.122672] devtmpfs: initialized
[0.130442] VFP support v0.3: not present
[0.134688] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[0.144697] pinctrl core: initialized pinctrl subsystem
[0.150947] NET: Registered protocol family 16
[0.155764] DMA: preallocated 256 KiB pool for atomic coherent allocations
[0.163874] cpuidle: using governor ladder
[0.168070] cpuidle: using governor menu
[0.172333] Feroceon L2: Enabling L2
[0.176022] Feroceon L2: Cache support initialised.
[0.181173] [Firmware Info]: 
/ocp@f100/ethernet-controller@72000/ethernet0-port@0: local-mac-address is 
not set
[0.195085] No ATAGs?
[0.201235] clocksource: Switched to clocksource orion_clocksource
[0.218696] VFS: Disk quotas dquot_6.6.0
[0.222792] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[0.236187] NET: Registered protocol family 2
[0.241328] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[0.248386] TCP bind hash