Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

2016-07-30 Thread Jose M Calhariz
Package: src:linux
Version: 4.7~rc7-1~exp1
Severity: important
Tags: upstream

Being affected by #833009 I decided to try a kernel from experimental.
Both of the kernels for amd64, the unsigned and the other, cause a
orderly shutodwn when I press any key of the keyboard.

I have no clue why this happens, but being a regression, I decided to
report.

Kind regards
Jose M Calhariz


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: E200HA
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E200HA.210
board_vendor: ASUSTeK COMPUTER INC.
board_name: E200HA
board_version: 1.0   

** 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

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Braswell SoC Transaction Router 
[8086:2280] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell SoC Transaction Router 
[1043:10b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:0b.0 Signal processing controller [1180]: Intel Corporation Braswell P-Unit 
Power Management [8086:22dc] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell P-Unit Power Management 
[1043:10b0]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Braswell USB xHCI Host 
Controller [8086:22b5] (rev 22) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Braswell USB xHCI Host Controller 
[1043:10b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:1a.0 Encryption controller [1080]: Intel Corporation Braswell Trusted 
Execution Engine Interface [8086:2298] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell Trusted Execution Engine 
Interface [1043:10b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:1c.0 PCI bridge [0604]: Intel Corporation Braswell PCIe Port 1 [8086:22c8] 
(rev 22) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1f.0 ISA bridge [0601]: Intel Corporation Braswell Platform Controller Unit 
LPC [8086:229c] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell Platform Controller Unit LPC 
[1043:10b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich

01:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter [168c:0042] (rev 30)
Subsystem: AzureWave QCA9377 802.11ac Wireless Network Adapter 
[1a3b:2b31]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci


** USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 001 Device 003: ID 13d3:3496 IMC Networks 
Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=locale: Cannot set LC_CTYPE to default 
locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No 

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

2016-07-30 Thread Jose M Calhariz
Package: src:linux
Version: 4.6.4-1
Severity: normal
Tags: upstream

I have problems that I can not suspend or hibernate my E200HA.  After
some reserach I found this Web page:
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

Maybe the suspend is not supported, but the hibernate should, because
of this message on kern.log:

Jul 28 22:56:00 lal kernel: [0.472724] ACPI: (supports S0 S4 S5)

So, doing some extra research I suspect the problem is in the module
i915 and on the module i2c_designware.  Because switching to a text
console and issuing the command: "echo disk > /sys/power/state" the
system hibernate and awakes when I request.  But it awakes without
keyboard and with following messages on the console:

[   50.827873] [drm] stuck on blitter ring
[   50.834932] [drm] stuck on bsd ring
[   50.841830] [drm] stuck on video enhancement ring
[   50.851177] [drm] GPU HANG: ecode 8:0:0x7a2af415, reason: Ring hung, action: 
reset
[   50.854730] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[   50.858380] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[   50.860886] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[   50.863336] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[   50.865839] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   50.868532] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, 
banning!
[   50.873485] drm/i915: Resetting chip after gpu hang
[   51.729188] IPv6: ADDRCONF(NETDEV_CHANGE): enx0019fd4cb596: link becomes 
ready
[   51.737806] asix 1-4:1.0 enx0019fd4cb596: link up, 100Mbps, full-duplex, lpa 
0xCDE1
[  129.340496] i2c_designware 808622C1:00: timeout in enabling adapter
[  130.348085] i2c_designware 808622C1:00: controller timed out
[  130.355959] i2c_designware 808622C1:00: Unknown Synopsys component type: 
0x

Kind regards
Jose M Calhariz


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n initcall_debug 
no_console_suspend

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   49.008511] call regulatory.0+ returned 0 after 0 usecs
[   49.010919] calling  intel_backlight+ @ 2728, parent: card0-eDP-1
[   49.013223] call intel_backlight+ returned 0 after 0 usecs
[   49.015521] calling  input6+ @ 2728, parent: LNXVIDEO:00
[   49.017797] call input6+ returned 0 after 0 usecs
[   49.020078] calling  input7+ @ 2728, parent: pcspkr
[   49.021968] call input7+ returned 0 after 17 usecs
[   49.023843] calling  input8+ @ 2728, parent: i2c-ELAN0100:00
[   49.025720] call input8+ returned 0 after 0 usecs
[   49.027601] calling  coretemp.0+ @ 2728, parent: platform
[   49.029487] call coretemp.0+ returned 0 after 0 usecs
[   49.031392] calling  asus-nb-wmi+ @ 2728, parent: platform
[   49.033284] call asus-nb-wmi+ returned 0 after 1 usecs
[   49.035181] calling  input9+ @ 2728, parent: asus-nb-wmi
[   49.037073] call input9+ returned 0 after 0 usecs
[   49.038960] calling  input10+ @ 2728, parent: 0018:0B05:8585.0001
[   49.040893] call input10+ returned 0 after 19 usecs
[   49.042822] calling  input10::numlock+ @ 2728, parent: input10
[   49.044753] call input10::numlock+ returned 0 after 0 usecs
[   49.046684] calling  input10::capslock+ @ 2728, parent: input10
[   49.048625] call input10::capslock+ returned 0 after 0 usecs
[   49.050570] calling  input10::scrolllock+ @ 2728, parent: input10
[   49.052528] call input10::scrolllock+ returned 0 after 0 usecs
[   49.054491] calling  input10::compose+ @ 2728, parent: input10
[   49.056460] call input10::compose+ returned 0 after 0 usecs
[   49.058429] calling  input10::kana+ @ 2728, parent: input10
[   49.060402] call input10::kana+ returned 0 after 0 usecs
[   49.062379] calling  rfkill1+ @ 2728, parent: phy0
[   49.064358] call rfkill1+ returned 0 after 10 usecs
[   49.066337] PM: restore of devices complete after 4600.592 msecs
[   49.068386] usb 1-4:1.0: rebind failed: -517
[   49.070372] usb 1-3:1.0: rebind failed: -517
[   49.072323] usb 1-3:1.1: rebind failed: -517
[   49.074671] PM: Image restored successfully.
[   49.074693] PM: Basic memory bitmaps freed
[   49.074699] Restarting tasks ... done.
[   49.089295] pci_bus :01: Allocating resources
[   49.089491] pcieport :00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 
01] add_size 1000
[   49.089498] pcieport :00:1c.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 01] add_size 20 add_align 10
[   49.089509] pcieport :00:1c.0: res[15]=[mem 0x0010-0x000f 64bit 
pref] res_to_dev_res add_size 20