2016-11-05 23:46:40

by Linus Torvalds

[permalink] [raw]
Subject: Linux 4.9-rc4

So it's once again a Saturday afternoon rather than Sunday, this time
because I felt this rc was already big enough.

Part of the size likely comes just from the fact that 4.9 is big and
has some fundamental changes: we have various fixups for drivers and
filesystems that triggered the whole "stack is now viirtually mapped,
and physical addresses don't work" issue.

But a larger part is simply that the first batch of networking fixes
came in just after the rc3 release, which accounts for a large portion
of this rc (about a third in bulk, slightly more in number of commits
- spread out both over network drivers and core networking).

So I'm not going to lie: this is not a small rc, and I'd have been
happier if it was. But it's not unreasonably large for this (big)
release either, so it's not like I'd start worrying. I'm currently
still assuming that we'll end up with the usual seven release
candidates, assuming things start calming down. We'll see how that
goes as we get closer to a release.

Anyway, about half the changes are to drivers (networking being a
notable part of it, but also media and gpu, with misc other noise).
About a third is architecture updates (sparc and mips stand out, but
there's some x86 and parisc too, and some tiny arm updates). The
remainder is mostly core networking, with a smattering of other
changes (filesystems, tests). And Arnd continues to get his
uninitialized variable warning fixes in, so that we hopefully can
re-enable that warning for 4.9 final. Let's see.

The appended shortlog isn't tiny, but you can kind of scan it for an
overview of the kinds of things that happened the past week.

Linus

---

Adam Williamson (1):
ath6kl: add Dell OEM SDIO I/O for the Venue 8 Pro

Alex Deucher (10):
drm/amdgpu/powerplay/smu7: fix static checker warning
drm/amdgpu: drop atom scratch save/restore in gpu reset
drm/amdgpu: move atom scratch register save/restore to common code
drm/amdgpu/st: move ATC CG golden init from gfx to mc
drm/amdgpu: explicitly set pg_flags for ST
drm/amdgpu: cancel reset work on fini
drm/amdgpu/dpm: flush any thermal work on fini
drm/amdgpu/vce3: only enable 3 rings on new enough firmware (v2)
drm/radeon/si_dpm: workaround for SI kickers
drm/amdgpu/si_dpm: workaround for SI kickers

Alexander Alemayhu (1):
Documentation/networking: update git urls to use https over http

Alexey Khoroshilov (1):
vmxnet3: avoid assumption about invalid dma_pa in vmxnet3_set_mc()

Anders K. Pedersen (1):
netfilter: nft_dynset: fix element timeout for HZ != 1000

Andy Lutomirski (1):
fork: Add task stack refcounting sanity check and prevent
premature task stack freeing

Ard Biesheuvel (2):
r8169: set coherent DMA mask as well as streaming DMA mask
mac80211: move struct aead_req off the stack

Arnd Bergmann (10):
drm/imx: hide an unused label
netfilter: nf_tables: avoid uninitialized variable warning
net: bcm63xx: avoid referencing uninitialized variable
net/hyperv: avoid uninitialized variable
rocker: fix maybe-uninitialized warning
spi: fsl-espi: avoid processing uninitalized data on error
kalmia: avoid potential uninitialized variable use
flow_dissector: fix vlan tag handling
mtd: mtk: avoid warning in mtk_ecc_encode
IB/mlx4: avoid a -Wmaybe-uninitialize warning

Atish Patra (1):
sparc64: Setup a scheduling domain for highest level cache.

Boris Brezillon (2):
MAINTAINERS: add more people to the MTD maintainer team
mtd: nand: Fix data interface configuration logic

Borislav Petkov (1):
kvm/x86: Show WRMSR data is in hex

Brenden Blanco (1):
net/mlx4_en: fixup xdp tx irq to match rx

Charles Keepax (1):
regmap: Rename ret variable in regmap_read_poll_timeout

Ching Huang (1):
scsi: arcmsr: Send SYNCHRONIZE_CACHE command to firmware

Chris Wilson (1):
drm/i915: Use fence_write() from rpm resume

Chuck Lever (2):
svcrdma: backchannel cannot share a page for send and rcv buffers
nfsd: Fix general protection fault in release_lock_stateid()

Colin Ian King (2):
cxgb4: fix memory leak of qe on error exit path
net: bgmac: fix spelling mistake: "connecton" -> "connection"

Craig Gallek (1):
inet: Fix missing return value in inet6_hash

Cyrille Pitchen (1):
MAINTAINERS: add a maintainer for the SPI NOR subsystem

Dan Carpenter (7):
afs: unmapping the wrong buffer
stmmac: fix an error code in stmmac_ptp_register()
netfilter: nf_tables: underflow in nft_parse_u32_check()
netfilter: nft_exthdr: fix error handling in nft_exthdr_init()
drm/imx: drm_dev_alloc() returns error pointers
Btrfs: remove some no-op casts
drm/i915: fix a read size argument

Daniel Borkmann (2):
bpf, test: fix ld_abs + vlan push/pop stress test
bpf: fix samples to add fake KBUILD_MODNAME

Daniel Jurgens (2):
{net, ib}/mlx5: Make cache line size determination at runtime.
net/mlx5: Always Query HCA caps after setting them

Daniel Stone (1):
drm: i915: Wait for fences on new fb, not old

David Ahern (3):
net: Require exact match for TCP socket lookups if dif is l3mdev
net: ipv6: Fix processing of RAs in presence of VRF
net: ipv6: Do not consider link state for nexthop validation

David Ertman (1):
i40e: Fix configure TCs after initial DCB disable

David Howells (3):
rxrpc: Fix checker warning by not passing always-zero value to ERR_PTR()
rxrpc: Fix checking of error from ip6_route_output()
afs: call->operation_ID sometimes used as __be32 sometimes as u32

David S. Miller (17):
sparc64: Delete __ret_efault.
sparc64: Prepare to move to more saner user copy exception handling.
sparc64: Convert copy_in_user to accurate exception reporting.
sparc64: Convert GENcopy_{from,to}_user to accurate exception reporting.
sparc64: Convert U1copy_{from,to}_user to accurate exception reporting.
sparc64: Convert NG4copy_{from,to}_user to accurate exception reporting.
sparc64: Convert NGcopy_{from,to}_user to accurate exception reporting.
sparc64: Convert NG2copy_{from,to}_user to accurate exception reporting.
sparc64: Convert U3copy_{from,to}_user to accurate exception reporting.
sparc64: Delete now unused user copy assembler helpers.
sparc64: Delete now unused user copy fixup functions.
sparc64: Fix illegal relative branches in hypervisor patched TLB code.
sparc64: Handle extremely large kernel TSB range flushes sanely.
sparc64: Fix instruction count in comment for
__hypervisor_flush_tlb_pending.
sparc64: Fix illegal relative branches in hypervisor patched TLB
cross-call code.
sparc64: Handle extremely large kernel TLB range flushes more gracefully.
Revert "ibmvnic: Fix releasing of sub-CRQ IRQs in interrupt context"

Dmitry Tunin (1):
Input: psmouse - cleanup Focaltech code

Elad Raz (1):
mlxsw: switchx2: Fix ethernet port initialization

Eli Cooper (1):
ip6_tunnel: Update skb->protocol to ETH_P_IPV6 in ip6_tnl_xmit()

Emil Tantilov (1):
ixgbe: fix panic when using macvlan with l2-fwd-offload enabled

Erez Shitrit (1):
net/mlx4_en: Process all completions in RX rings after port goes up

Eric Dumazet (6):
net: pktgen: remove rcu locking in pktgen_change_name()
soreuseport: do not export reuseport_add_sock()
tcp: do not export sysctl_tcp_low_latency
udp: must lock the socket in udp_disconnect()
ipv4: disable BH in set_ping_group_range()
udp: fix IP_CHECKSUM handling

Eric Garver (1):
flow_dissector: Check skb for VLAN only if skb specified.

Eugenia Emantayev (3):
net/mlx4_en: Resolve dividing by zero in 32-bit system
net/mlx4_en: Fix panic during reboot
net/mlx4: Fix firmware command timeout during interrupt test

Evan Quan (1):
drm/amd/amdgpu: expose max engine and memory clock for powerplay
enabled case

Ewan D. Milne (1):
scsi: scsi_debug: Fix memory leak if LBP enabled and module is unloaded

Fabio Estevam (2):
net: fec: Call swap_buffer() prior to IP header alignment
mtd: nand: gpmi: disable the clocks on errors

Felix Fietkau (1):
Revert "ath9k_hw: implement temperature compensation support for AR9003+"

Felix Monninger (1):
drm: Release reference from blob lookup after replacing property

Florian Fainelli (4):
net: dsa: bcm_sf2: Prevent GPHY shutdown for kexec'd kernels
kexec: Export kexec_in_progress to modules
Revert "kexec: Export kexec_in_progress to modules"
net: dsa: bcm_sf2: Do not rely on kexec_in_progress

Florian Westphal (1):
netfilter: x_tables: suppress kmemcheck warning

Ganesh Goudar (2):
cxgb4: Fix number of queue sets corssing the limit
cxgb4: Fix error handling in alloc_uld_rxqs().

Gavin Shan (4):
net/ncsi: Avoid if statements in ncsi_suspend_channel()
net/ncsi: Fix stale link state of inactive channels on failover
net/ncsi: Choose hot channel as active one if necessary
net/ncsi: Improve HNCDSC AEN handler

Geert Uytterhoeven (1):
netfilter: xt_hashlimit: Add missing ULL suffixes for 64-bit constants

Gerd Hoffmann (1):
virtio-gpu: fix vblank events

Giuseppe CAVALLARO (2):
stmmac: fix and review the ptp registration.
stmmac: display the descriptors if DES0 = 0

Goldwyn Rodrigues (1):
btrfs: qgroup: Prevent qgroup->reserved from going subzero

Govindarajulu Varadarajan (1):
enic: fix rq disable

Grazvydas Ignotas (5):
drm/amd/powerplay: don't give up if DPM is already running
drm/amdgpu: fix sched fence slab teardown
drm/amdgpu: fix a vm_flush fence leak
drm/amdgpu: update kernel-doc for some functions
drm/amdgpu: fix fence slab teardown

Guenter Roeck (1):
net: asix: Avoid looping when the device does not respond

Guilherme G Piccoli (1):
i40e: disable MSI-X interrupts if we cannot reserve enough vectors

H. Nikolaus Schaller (1):
regulator: core: silence warning: "VDD1: ramp_delay not set"

Helge Deller (3):
parisc: use KERN_CONT when printing device inventory
parisc: Use LINUX_GATEWAY_ADDR define instead of hardcoded value
parisc: Ignore the pkey system calls for now

Huaibin Wang (1):
i40e: fix call of ndo_dflt_bridge_getlink()

Ido Schimmel (2):
net: core: Correctly iterate over lower adjacency list
switchdev: Execute bridge ndos only for bridge ports

Ido Yariv (1):
KVM: x86: fix wbinvd_dirty_mask use-after-free

Imre Deak (1):
drm/i915: Fix mismatched INIT power domain disabling during suspend

Ivan Vecera (2):
bnx2: fix locking when netconsole is used
arch/powerpc: Update parameters for csum_tcpudp_magic & csum_tcpudp_nofold

J. Bruce Fields (1):
sunrpc: don't pass on-stack memory to sg_set_buf

Jack Morgenstein (3):
net/mlx4_core: Fix the resource-type enum in res tracker to
conform to FW spec
net/mlx4_core: Do not access comm channel if it has not yet been
initialized
net/mlx4_en: Fix potential deadlock in port statistics flow

Jacob Siverskog (1):
Bluetooth: btwilink: Fix probe return value

Jaehoon Chung (1):
mmc: dw_mmc-pltfm: fix the potential NULL pointer dereference

Jamal Hadi Salim (1):
net sched filters: fix notification of filter delete with proper handle

James Clarke (1):
sparc: Handle negative offsets in arch_jump_label_transform

James Hogan (5):
KVM: MIPS: Fix lazy user ASID regenerate for SMP
KVM: MIPS: Make ERET handle ERL before EXL
KVM: MIPS: Precalculate MMIO load resume PC
MIPS: dump_tlb: Fix printk continuations
MIPS: Fix max_low_pfn with disabled highmem

Jani Nikula (3):
mac80211: fix some sphinx warnings
drm/i915: keep declarations in i915_drv.h
drm/i915: workaround sparse warning on variable length arrays

Janosch Frank (1):
KVM: s390: Fix STHYI buffer alignment for diag224

Jarkko Sakkinen (1):
tpm: remove invalid min length check from tpm_do_selftest()

Jason A. Donenfeld (1):
ipv6: do not increment mac header when it's unset

Jason Gunthorpe (2):
net: mv643xx_eth: Fetch the phy connection type from DT
gpio/mvebu: Use irq_domain_add_linear

Javier Martinez Canillas (10):
net: wan: slic_ds26522: add SPI device ID table to fix module autoload
net: wan: slic_ds26522: Export OF module alias information
net: wan: slic_ds26522: Allow driver to built if COMPILE_TEST is enabled
net: nps_enet: Fix module autoload
net: ethernet: nb8800: Fix module autoload
net: hns: Fix hns_dsaf module autoload for OF registration
net: qcom/emac: Fix module autoload for OF registration
net: hisilicon: Fix hns_mdio module autoload for OF registration
net: dsa: b53: Fix module autoload
net: dsa: bcm_sf2: Fix module autoload for OF registration

Jeff Layton (2):
nfsd: move blocked lock handling under a dedicated spinlock
sunrpc: fix some missing rq_rbuffer assignments

Jes Sorensen (4):
rtl8xxxu: Fix memory leak in handling rxdesc16 packets
rtl8xxxu: Fix big-endian problem reporting mactime
rtl8xxxu: Fix rtl8723bu driver reload issue
rtl8xxxu: Fix rtl8192eu driver reload issue

Jesse Brandeburg (1):
ethtool: silence warning on bit loss

Jim Mattson (2):
kvm: nVMX: Fix kernel panics induced by illegal INVEPT/INVVPID types
kvm: nVMX: VMCLEAR an active shadow VMCS after last use

Jiri Bohac (3):
IPv6: Drop the temporary address regen_timer
IPv6: fix DESYNC_FACTOR
ipv6: properly prevent temp_prefered_lft sysctl race

Jiri Pirko (6):
rtnetlink: Add rtnexthop offload flag to compare mask
mlxsw: spectrum_router: Use correct tree index for binding
mlxsw: spectrum_router: Make mlxsw_sp_router_fib4_del return
void and remove warn
mlxsw: pci: Fix reset wait for SwitchX2
mlxsw: spectrum_router: Save requested prefix bitlist when creating tree
mlxsw: spectrum_router: Compare only trees which are in use
during tree get

Jiri Slaby (1):
net: sctp, forbid negative length

Johannes Berg (6):
mac80211: discard multicast and 4-addr A-MSDUs
cfg80211: let ieee80211_amsdu_to_8023s() take only header-less SKB
cfg80211: add ability to check DA/SA in A-MSDU decapsulation
mac80211: validate DA/SA during A-MSDU decapsulation
cfg80211: process events caused by suspend before suspending
net_sched actions: use nla_parse_nested()

John David Anglin (2):
parisc: Avoid trashing sr2 and sr3 in LWS code
parisc: Ensure consistent state when switching to kernel stack
at syscall entry

Jon Paul Maloy (1):
tipc: fix broadcast link synchronization problem

Juergen Gross (1):
virtio: remove config.c

Jérôme de Bretagne (1):
Bluetooth: hci_bcm: Fix autosuspend PM for Lenovo ThinkPad 8

Kashyap Desai (1):
scsi: megaraid_sas: Fix data integrity failure for JBOD
(passthrough) devices

Kees Cook (2):
gcc-plugins: Export symbols needed by gcc
latent_entropy: Fix wrong gcc code generation with 64 bit variables

Konstantin Neumoin (1):
virtio: update balloon size in balloon "probe"

Ladi Prosek (1):
virtio_ring: Make interrupt suppression spec compliant

Larry Finger (1):
rtlwifi: Fix regression caused by commit d86e64768859

Lars-Peter Clausen (1):
gpio: GPIO_GET_LINE{HANDLE,EVENT}_IOCTL: Fix file descriptor leak

Linus Lüssing (1):
batman-adv: fix splat on disabling an interface

Linus Torvalds (2):
sched/core: Remove pointless printout in sched_show_task()
Linux 4.9-rc4

Liping Zhang (3):
netfilter: xt_NFLOG: fix unexpected truncated packet
netfilter: xt_ipcomp: add "ip[6]t_ipcomp" module alias name
netfilter: nft_hash: add missing NFTA_HASH_OFFSET's nla_policy

Liu Bo (1):
Btrfs: kill BUG_ON in do_relocation

Liu Ying (3):
drm/imx: ipuv3-plane: Switch EBA buffer only when we don't need modeset
drm/imx: ipuv3-plane: Skip setting u/vbo only when we don't need modeset
drm/imx: ipuv3-plane: Access old u/vbo properly in
->atomic_check for YU12/YV12

Lucas Stach (1):
drm/radeon: drop register readback in cayman_cp_int_cntl_setup

Maciej W. Rozycki (6):
MIPS: ptrace: Also initialize the FP context on individual FCSR writes
MIPS: Fix FCSR Cause bit handling for correct SIGFPE issue
MIPS: Fix ISA I FP sigcontext access violation handling
MIPS: Remove FIR from ISA I FP signal context
MIPS: Fix ISA I/II FP signal context offsets
MIPS: Correct MIPS I FP sigcontext layout

Manish Chopra (1):
qede: Fix incorrrect usage of APIs for un-mapping DMA memory

Maor Gottlieb (1):
net/mlx4_core: Avoid setting ports to auto when only one port
type is supported

Marcelo Ricardo Leitner (1):
sctp: validate chunk len before actually using it

Markus Elfring (2):
virtio_blk: Use kmalloc_array() in init_vq()
virtio_blk: Delete an unnecessary initialisation in init_vq()

Marty Faltesek (1):
ath10k: cache calibration data when the core is stopped

Masahiro Yamada (2):
regmap: include <linux/delay.h> from include/linux/regmap.h
gpio: of: fix GPIO drivers with multiple gpio_chip for a single node

Matt Redfearn (7):
virtio: console: Unlock vqs while freeing buffers
MIPS: KASLR: Fix handling of NULL FDT
MIPS: generic: Fix KASLR for generic kernel.
MIPS: Fix build of compressed image
MIPS: traps: Fix output of show_backtrace
MIPS: traps: Fix output of show_stacktrace
MIPS: traps: Fix output of show_code

Mauro Carvalho Chehab (31):
[media] af9005: don't do DMA on stack
[media] cinergyT2-core: don't do DMA on stack
[media] cinergyT2-core: handle error code on RC query
[media] cinergyT2-fe: cache stats at cinergyt2_fe_read_status()
[media] cinergyT2-fe: don't do DMA on stack
[media] cxusb: don't do DMA on stack
[media] dib0700: be sure that dib0700_ctrl_rd() users can do DMA
[media] dib0700_core: don't use stack on I2C reads
[media] dibusb: don't do DMA on stack
[media] dibusb: handle error code on RC query
[media] digitv: don't do DMA on stack
[media] dtt200u-fe: don't keep waiting for lock at set_frontend()
[media] dtt200u-fe: don't do DMA on stack
[media] dtt200u-fe: handle errors on USB control messages
[media] dtt200u: don't do DMA on stack
[media] dtt200u: handle USB control message errors
[media] dtv5100: don't do DMA on stack
[media] gp8psk: don't do DMA on stack
[media] gp8psk: don't go past the buffer size
[media] nova-t-usb2: don't do DMA on stack
[media] pctv452e: don't do DMA on stack
[media] pctv452e: don't call BUG_ON() on non-fatal error
[media] technisat-usb2: use DMA buffers for I2C transfers
[media] nova-t-usb2: handle error code on RC query
[media] dw2102: return error if su3000_power_ctrl() fails
[media] digitv: handle error code on RC query
[media] cpia2_usb: don't use stack for DMA
[media] s2255drv: don't use stack for DMA
[media] stk-webcam: don't use stack for DMA
[media] flexcop-usb: don't use stack for DMA
[media] radio-bcm2048: don't ignore errors

Michael Braun (1):
mac80211: fix CMD_FRAME for AP_VLAN

Michael S. Tsirkin (2):
virtio/vhost: add Jason to list of maintainers
virtio_ring: mark vring_dma_dev inline

Michał Narajowski (1):
Bluetooth: Fix append max 11 bytes of name to scan rsp data

Michel Dänzer (1):
Revert "drm/radeon: fix DP link training issue with second 4K monitor"

Miklos Szeredi (3):
ovl: update S_ISGID when setting posix ACLs
ovl: fix get_acl() on tmpfs
ovl: fsync after copy-up

Mintz, Yuval (2):
MAINTAINERS: Update qlogic networking drivers
qede: Fix out-of-bound fastpath memory access

Mohamad Haj Yahia (5):
net/mlx5e: Unregister netdev before detaching it
net/mlx5: Change the acl enable prototype to return status
net/mlx5: Clear health sick bit when starting health poll
net/mlx5: Fix race between PCI error handlers and health work
net/mlx5: PCI error recovery health care simulation

Moshe Lazer (1):
net/mlx4_core: Change the default value of enable_qos

NeilBrown (1):
md: be careful not lot leak internal curr_resync value into
metadata. -- (all)

Nicolas Dichtel (3):
ipv6: correctly add local routes when lo goes up
netfilter: conntrack: remove obsolete sysctl
(nf_conntrack_events_retry_timeout)
netfilter: conntrack: restart gc immediately if GC_MAX_EVICTS is reached

Niklas Cassel (3):
dwc_eth_qos: do not clear pause flags from phy_device->supported
dwc_eth_qos: enable flow control by default
PCI: designware: Check for iATU unroll support after initializing host

Nikolay Aleksandrov (1):
bridge: multicast: restore perm router ports on multicast enable

Noa Osherovich (1):
net/mlx5: Avoid passing dma address 0 to firmware

Owen Hofmann (1):
kvm: x86: Check memopp before dereference (CVE-2016-8630)

Pablo Neira Ayuso (2):
netfilter: nft_range: validate operation netlink attribute
netfilter: fix nf_queue handling

Paolo Abeni (1):
IB/ipoib: move back IB LL address into the hard header

Paolo Bonzini (6):
KVM: fix OOPS on flush_work
KVM: document lock orders
ringtest: use link-time optimization
ringtest: commonize implementation of poll_avail/poll_used
ringtest: poll for new buffers once before updating event index
KVM: x86: drop TSC offsetting kvm_x86_ops to fix KVM_GET/SET_CLOCK

Patrick Scheuring (1):
Input: i8042 - add XMG C504 to keyboard reset table

Paul Blakey (4):
net/sched: act_mirred: Use passed lastuse argument
net/mlx5: Keep autogroups list ordered
net/mlx5: Fix autogroups groups num not decreasing
net/mlx5: Correctly initialize last use of flow counters

Paul Burton (3):
MIPS: CPC: Provide default mips_cpc_default_phys_base to ignore CPC
MIPS: Malta: Fixup reboot
MIPS: Fix __show_regs() output

Paul Moore (1):
netns: revert "netns: avoid disabling irq for netns id"

Paulo Zanoni (3):
drm/i915/gen9: fix DDB partitioning for multi-screen cases
drm/i915/gen9: fix watermarks when using the pipe scaler
drm/i915/fbc: fix CFB size calculation for gen8+

Peter Wu (1):
drm/nouveau/acpi: fix check for power resources support

Philipp Zabel (2):
drm/imx: ipuv3-plane: make sure x/y offsets are even in case of
chroma subsampling
drm/imx: ipuv3-plane: disable local alpha for planes without alpha channel

Ralf Ramsauer (1):
spi: mark device nodes only in case of successful instantiation

Rex Zhu (3):
drm/amd/powerplay: fix static checker warning in process_pptables_v1_0.c
drm/amdgpu: fix s3 resume back, uvd dpm randomly can't disable.
drm/amd/powerplay: fix bug get wrong evv voltage of Polaris.

Roger Quadros (1):
net: phy: dp83848: add dp83822 PHY support

Russell King (2):
ARM: fix oops when using older ARMv4T CPUs
ARM: wire up new pkey syscalls

Sabrina Dubroca (1):
net: add recursion limit to GRO

Saeed Mahameed (1):
net/mlx5e: Choose best nearest LRO timeout

Shaohua Li (3):
RAID1: ignore discard error
RAID10: ignore discard error
raid5-cache: correct condition for empty metadata write

Srinivas Kandagatla (1):
PCI: qcom: Fix pp->dev usage before assignment

Stefan Richter (2):
firewire: net: guard against rx buffer overflows
firewire: net: fix fragmented datagram_size off-by-one

Stephen Hemminger (3):
doc: update docbook annotations for socket and skb
netvsc: fix incorrect receive checksum offloading
Revert "hv_netvsc: report vmbus name in ethtool"

Sudarsana Reddy Kalluru (7):
qede: get_channels() need to populate max tx/rx coalesce values
qede: Do not allow RSS config for 100G devices
qede: Loopback implementation should ignore the normal traffic
qed*: Reduce the memory footprint for Rx path
qede: Reconfigure rss indirection direction table when rss count
is updated
qed: Zero-out the buffer paased to dcbx_query() API
bnx2x: Use the correct divisor value for PHC clock readings.

Sven Eckelmann (2):
batman-adv: Modify neigh_list only with rcu-list functions
batman-adv: Add BATADV_DBG_TP_METER to BATADV_DBG_ALL

Takashi Iwai (1):
drm/fb-helper: Don't call dirty callback for untouched clips

Tariq Toukan (1):
net/mlx4_en: Save slave ethtool stats command

Tetsuo Handa (1):
sched/core: Fix oops in sched_show_task()

Thomas Falcon (6):
ibmvnic: Driver Version 1.0.1
ibmvnic: Fix GFP_KERNEL allocation in interrupt context
ibmvnic: Update MTU after device initialization
ibmvnic: Fix releasing of sub-CRQ IRQs in interrupt context
ibmvnic: Fix releasing of sub-CRQ IRQs in interrupt context
ibmvnic: Fix missing brackets in init_sub_crq_irqs

Timur Tabi (1):
net: qcom/emac: disable interrupts before calling phy_disconnect

Tobias Brunner (1):
macsec: Fix header length if SCI is added if explicitly disabled

Tobias Klauser (5):
net/hsr: Remove unused but set variable
ipv4: Remove unused but set variable
tcp: Remove unused but set variable
sparc64: Fix old style declaration GCC warnings
sparc32: Fix old style declaration GCC warnings

Tom St Denis (1):
drm/radeon/si_dpm: Limit clocks on HD86xx part

Tomasz Majchrzak (2):
md: report 'write_pending' state when array in sync
raid1: handle read error also in readonly mode

Tvrtko Ursulin (2):
drm/i915: Rotated view does not need a fence
drm/i915: Remove two invalid warns

Vadim Fedorenko (1):
ip6_tunnel: fix ip6_tnl_lookup

Ville Syrjälä (8):
drm/fb-helper: Fix connector ref leak on error
drm: Don't force all planes to be added to the state due to zpos
drm/fb-helper: Keep references for the current set of used connectors
drm/dp/mst: Clear port->pdt when tearing down the i2c adapter
drm/dp/mst: Check peer device type before attempting EDID read
drm/i915: Respect alternate_aux_channel for all DDI ports
drm/i915: Clean up DDI DDC/AUX CH sanitation
drm/i915: Fix SKL+ 90/270 degree rotated plane coordinate computation

Vlad Tsyrklevich (1):
vfio/pci: Fix integer overflows, bitmask check

Vladimir Zapolskiy (1):
i2c: core: fix NULL pointer dereference under race condition

WANG Cong (2):
ipv6: fix a potential deadlock in do_ipv6_setsockopt()
ipv4: use the right lock for ping_group_range

Wang Xiaoguang (3):
btrfs: make file clone aware of fatal signals
btrfs: pass correct args to btrfs_async_run_delayed_refs()
btrfs: fix WARNING in btrfs_select_ref_head()

Wei Yongjun (5):
wlcore: sdio: drop kfree for memory allocated with devm_kzalloc
gpu: ipu-v3: Use ERR_CAST instead of ERR_PTR(PTR_ERR())
qed: Use list_move_tail instead of list_del/list_add_tail
rocker: fix error return code in rocker_world_check_init()
mmc: sdhci-msm: Fix error return code in sdhci_msm_probe()

Will Deacon (1):
virtio_pci: Limit DMA mask to 44 bits for legacy virtio devices

Willem de Bruijn (1):
packet: on direct_xmit, limit tso and csum to supported devices

Xin Long (1):
sctp: fix the panic caused by route update

Yuan Yao (1):
spi: dspi: clear SPI_SR before enable interrupt

Yuval Mintz (3):
qed: Fix static checker warning.
qed*: Fix Kconfig dependencies with INFINIBAND_QEDR
qed: Additional work toward cleaning C=1

Zefir Kurtisi (2):
Revert "at803x: fix suspend/resume for SGMII link"
at803x: double check SGMII side autoneg

Zhengyuan Liu (2):
md/raid5: initialize next_checkpoint field before use
md/raid5: write an empty meta-block when creating log super-block

jimqu (1):
drm/amdgpu: avoid drm error log during S3 on RHEL7.3

kbuild test robot (1):
[media] pctv452e: fix semicolon.cocci warnings

pravin shelar (2):
vxlan: avoid using stale vxlan socket.
geneve: avoid using stale geneve socket.

shamir rabinovitch (1):
rds: debug messages are enabled by default


2016-11-06 14:54:46

by Martin Steigerwald

[permalink] [raw]
Subject: [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Hi.

Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> So it's once again a Saturday afternoon rather than Sunday, this time
> because I felt this rc was already big enough.

With kernel 4.9-rc4 I saw gfx corruptions like

https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png

in Konversation, Konsole, Akregator and other KDE/Qt related apps up to the
point of not being able to use these applications in a meaningful way.

I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
glitches like that anymore.

Anything known about this?

Machine is ThinkPad T520 with Sandybridge graphics.

Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.

Next week and weekend will be pretty busy and this is a production machine, so
bisection or any other time-consuming work on this is out of question for me.
I can provide additional details in case they are easy and quick enough to
obtain.


System information (now back on 4.8 kernel):

# phoronix-test-suite system-info

Phoronix Test Suite v5.2.1
System Information

Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205

Software:
OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE Frameworks
5, Display Server: X Server 1.18.4, Display Driver: modesetting 1.18.4,
OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0 20161103, File-System: btrfs,
Screen Resolution: 3840x1080


# apt-show-versions | egrep "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
core)" | grep amd64
libdrm-intel1:amd64/sid 2.4.71-1 uptodate
libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate


Excerpt of glxinfo:

Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)
Version: 12.0.3
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0

X.org runs with modesetting driver (default was changed in Debian Sid a while
back).

Thanks,

2016-11-06 15:25:20

by Mihai Donțu

[permalink] [raw]
Subject: Re: [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

On Sun, 06 Nov 2016 15:48:36 +0100 Martin Steigerwald wrote:
> Hi.
>
> Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> > So it's once again a Saturday afternoon rather than Sunday, this time
> > because I felt this rc was already big enough.
>
> With kernel 4.9-rc4 I saw gfx corruptions like
>
> https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
>
> in Konversation, Konsole, Akregator and other KDE/Qt related apps up to the
> point of not being able to use these applications in a meaningful way.
>
> I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
> after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
> glitches like that anymore.
>
> Anything known about this?

https://bugzilla.kernel.org/show_bug.cgi?id=177701

The proposed patch appears to be:
https://patchwork.freedesktop.org/patch/116808/

Have not tested it yet.

> Machine is ThinkPad T520 with Sandybridge graphics.
>
> Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.
>
> Next week and weekend will be pretty busy and this is a production machine, so
> bisection or any other time-consuming work on this is out of question for me.
> I can provide additional details in case they are easy and quick enough to
> obtain.
>
>
> System information (now back on 4.8 kernel):
>
> # phoronix-test-suite system-info
>
> Phoronix Test Suite v5.2.1
> System Information
>
> Hardware:
> Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
> 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
> Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
> Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
> Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
>
> Software:
> OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE Frameworks
> 5, Display Server: X Server 1.18.4, Display Driver: modesetting 1.18.4,
> OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0 20161103, File-System: btrfs,
> Screen Resolution: 3840x1080
>
>
> # apt-show-versions | egrep "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
> core)" | grep amd64
> libdrm-intel1:amd64/sid 2.4.71-1 uptodate
> libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
> xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate
>
>
> Excerpt of glxinfo:
>
> Extended renderer info (GLX_MESA_query_renderer):
> Vendor: Intel Open Source Technology Center (0x8086)
> Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)
> Version: 12.0.3
> Accelerated: yes
> Video memory: 1536MB
> Unified memory: yes
> Preferred profile: core (0x1)
> Max core profile version: 3.3
> Max compat profile version: 3.0
> Max GLES1 profile version: 1.1
> Max GLES[23] profile version: 3.0
>
> X.org runs with modesetting driver (default was changed in Debian Sid a while
> back).

--
Mihai Donțu

2016-11-06 15:40:47

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Sonntag, 6. November 2016, 17:25:15 CET schrieb Mihai Donțu:
> On Sun, 06 Nov 2016 15:48:36 +0100 Martin Steigerwald wrote:
> > Hi.
> >
> > Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> > > So it's once again a Saturday afternoon rather than Sunday, this time
> > > because I felt this rc was already big enough.
> >
> > With kernel 4.9-rc4 I saw gfx corruptions like
> >
> > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
> >
> > in Konversation, Konsole, Akregator and other KDE/Qt related apps up to
> > the
> > point of not being able to use these applications in a meaningful way.
> >
> > I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
> > after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
> > glitches like that anymore.
> >
> > Anything known about this?
>
> https://bugzilla.kernel.org/show_bug.cgi?id=177701
>
> The proposed patch appears to be:
> https://patchwork.freedesktop.org/patch/116808/
>
> Have not tested it yet.

Thank you.

It applies cleanly. I think I get a chance to test it this week.

Thanks,
Martin

> > Machine is ThinkPad T520 with Sandybridge graphics.
> >
> > Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.
> >
> > Next week and weekend will be pretty busy and this is a production
> > machine, so bisection or any other time-consuming work on this is out of
> > question for me. I can provide additional details in case they are easy
> > and quick enough to obtain.
> >
> >
> > System information (now back on 4.8 kernel):
> >
> > # phoronix-test-suite system-info
> >
> > Phoronix Test Suite v5.2.1
> > System Information
> >
> > Hardware:
> > Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
> > 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
> > Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
> > Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
> > Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
> >
> > Software:
> > OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE
> > Frameworks 5, Display Server: X Server 1.18.4, Display Driver:
> > modesetting 1.18.4, OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0
> > 20161103, File-System: btrfs, Screen Resolution: 3840x1080
> >
> >
> > # apt-show-versions | egrep
> > "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
> > core)" | grep amd64
> > libdrm-intel1:amd64/sid 2.4.71-1 uptodate
> > libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
> > xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate
> >
> >
> > Excerpt of glxinfo:
> >
> > Extended renderer info (GLX_MESA_query_renderer):
> > Vendor: Intel Open Source Technology Center (0x8086)
> > Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)
> > Version: 12.0.3
> > Accelerated: yes
> > Video memory: 1536MB
> > Unified memory: yes
> > Preferred profile: core (0x1)
> > Max core profile version: 3.3
> > Max compat profile version: 3.0
> > Max GLES1 profile version: 1.1
> > Max GLES[23] profile version: 3.0
> >
> > X.org runs with modesetting driver (default was changed in Debian Sid a
> > while back).


--
Martin

2016-11-06 17:50:42

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Sonntag, 6. November 2016, 17:25:15 CET schrieb Mihai Donțu:
> On Sun, 06 Nov 2016 15:48:36 +0100 Martin Steigerwald wrote:
> > Hi.
> >
> > Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> > > So it's once again a Saturday afternoon rather than Sunday, this time
> > > because I felt this rc was already big enough.
> >
> > With kernel 4.9-rc4 I saw gfx corruptions like
> >
> > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
> >
> > in Konversation, Konsole, Akregator and other KDE/Qt related apps up to
> > the
> > point of not being able to use these applications in a meaningful way.
> >
> > I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
> > after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
> > glitches like that anymore.
> >
> > Anything known about this?
>
> https://bugzilla.kernel.org/show_bug.cgi?id=177701
>
> The proposed patch appears to be:
> https://patchwork.freedesktop.org/patch/116808/
>
> Have not tested it yet.

This patch does not fix the issue for me. Still the same graphical glitches.

Thanks,
Martin

> > Machine is ThinkPad T520 with Sandybridge graphics.
> >
> > Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.
> >
> > Next week and weekend will be pretty busy and this is a production
> > machine, so bisection or any other time-consuming work on this is out of
> > question for me. I can provide additional details in case they are easy
> > and quick enough to obtain.
> >
> >
> > System information (now back on 4.8 kernel):
> >
> > # phoronix-test-suite system-info
> >
> > Phoronix Test Suite v5.2.1
> > System Information
> >
> > Hardware:
> > Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
> > 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
> > Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
> > Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
> > Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
> >
> > Software:
> > OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE
> > Frameworks 5, Display Server: X Server 1.18.4, Display Driver:
> > modesetting 1.18.4, OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0
> > 20161103, File-System: btrfs, Screen Resolution: 3840x1080
> >
> >
> > # apt-show-versions | egrep
> > "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
> > core)" | grep amd64
> > libdrm-intel1:amd64/sid 2.4.71-1 uptodate
> > libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
> > xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate
> >
> >
> > Excerpt of glxinfo:
> >
> > Extended renderer info (GLX_MESA_query_renderer):
> > Vendor: Intel Open Source Technology Center (0x8086)
> > Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)
> > Version: 12.0.3
> > Accelerated: yes
> > Video memory: 1536MB
> > Unified memory: yes
> > Preferred profile: core (0x1)
> > Max core profile version: 3.3
> > Max compat profile version: 3.0
> > Max GLES1 profile version: 1.1
> > Max GLES[23] profile version: 3.0
> >
> > X.org runs with modesetting driver (default was changed in Debian Sid a
> > while back).


--
Martin

2016-11-07 11:04:32

by Jani Nikula

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

On Sun, 06 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> Hi.
>
> Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
>> So it's once again a Saturday afternoon rather than Sunday, this time
>> because I felt this rc was already big enough.
>
> With kernel 4.9-rc4 I saw gfx corruptions like
>
> https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png

Is this the same issue or a different issue from [1]? Since you mention
-rc4, was this introduced in -rc4, or earlier?

Please file a bug over at [2]. One issue per bug if this is different
from [1].

BR,
Jani.


[1] http://lkml.kernel.org/r/[email protected]
[2] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel


>
> in Konversation, Konsole, Akregator and other KDE/Qt related apps up to the
> point of not being able to use these applications in a meaningful way.
>
> I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
> after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
> glitches like that anymore.
>
> Anything known about this?
>
> Machine is ThinkPad T520 with Sandybridge graphics.
>
> Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.
>
> Next week and weekend will be pretty busy and this is a production machine, so
> bisection or any other time-consuming work on this is out of question for me.
> I can provide additional details in case they are easy and quick enough to
> obtain.
>
>
> System information (now back on 4.8 kernel):
>
> # phoronix-test-suite system-info
>
> Phoronix Test Suite v5.2.1
> System Information
>
> Hardware:
> Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
> 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
> Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
> Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
> Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
>
> Software:
> OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE Frameworks
> 5, Display Server: X Server 1.18.4, Display Driver: modesetting 1.18.4,
> OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0 20161103, File-System: btrfs,
> Screen Resolution: 3840x1080
>
>
> # apt-show-versions | egrep "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
> core)" | grep amd64
> libdrm-intel1:amd64/sid 2.4.71-1 uptodate
> libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
> xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate
>
>
> Excerpt of glxinfo:
>
> Extended renderer info (GLX_MESA_query_renderer):
> Vendor: Intel Open Source Technology Center (0x8086)
> Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)
> Version: 12.0.3
> Accelerated: yes
> Video memory: 1536MB
> Unified memory: yes
> Preferred profile: core (0x1)
> Max core profile version: 3.3
> Max compat profile version: 3.0
> Max GLES1 profile version: 1.1
> Max GLES[23] profile version: 3.0
>
> X.org runs with modesetting driver (default was changed in Debian Sid a while
> back).
>
> Thanks,
> _______________________________________________
> Intel-gfx mailing list
> [email protected]
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

--
Jani Nikula, Intel Open Source Technology Center

2016-11-07 14:30:20

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Montag, 7. November 2016, 13:04:16 CET schrieb Jani Nikula:
> On Sun, 06 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> > Hi.
> >
> > Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> >> So it's once again a Saturday afternoon rather than Sunday, this time
> >> because I felt this rc was already big enough.
> >
> > With kernel 4.9-rc4 I saw gfx corruptions like
> >
> > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
>
> Is this the same issue or a different issue from [1]? Since you mention
> -rc4, was this introduced in -rc4, or earlier?

Yes, the gfx corruption look similar. So I bet it is the same issue as in [1].


It is also the same kind of corruptions as shown in

[Bug 177701] warning in intel_dp_aux_transfer
https://bugzilla.kernel.org/show_bug.cgi?id=177701

Just compare

https://bugzilla.kernel.org/attachment.cgi?id=241801

with

https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png


However that bug report links to

https://bugs.freedesktop.org/show_bug.cgi?id=97344

yet the patch mentioned in there does not fix the issue. So I wonder whether
bug #97344 and bug #177701 are really the same.

> Please file a bug over at [2]. One issue per bug if this is different
> from [1].

As #177701 seem to have the same corruptions, yet I do not have any

merkaba:~#1> zgrep intel_dp_aux_transfer /var/log/kern.log*
merkaba:~#1>

Of course I can report a bug at fdo as well, but I am a bit confused whether
it may not already have been reported. Well I hope I get a chance to report it
there as well and you get to decide.

Thank you,
Martin

> [1] http://lkml.kernel.org/r/[email protected]
> [2]
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
> > in Konversation, Konsole, Akregator and other KDE/Qt related apps up to
> > the
> > point of not being able to use these applications in a meaningful way.
> >
> > I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
> > after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
> > glitches like that anymore.
> >
> > Anything known about this?
> >
> > Machine is ThinkPad T520 with Sandybridge graphics.
> >
> > Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.
> >
> > Next week and weekend will be pretty busy and this is a production
> > machine, so bisection or any other time-consuming work on this is out of
> > question for me. I can provide additional details in case they are easy
> > and quick enough to obtain.
> >
> >
> > System information (now back on 4.8 kernel):
> >
> > # phoronix-test-suite system-info
> >
> > Phoronix Test Suite v5.2.1
> > System Information
> >
> > Hardware:
> > Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
> > 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
> > Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
> > Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
> > Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
> >
> > Software:
> > OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE
> > Frameworks 5, Display Server: X Server 1.18.4, Display Driver:
> > modesetting 1.18.4, OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0
> > 20161103, File-System: btrfs, Screen Resolution: 3840x1080
> >
> >
> > # apt-show-versions | egrep
> > "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
> > core)" | grep amd64
> > libdrm-intel1:amd64/sid 2.4.71-1 uptodate
> > libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
> > xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate
> >
> >
> > Excerpt of glxinfo:
> >
> > Extended renderer info (GLX_MESA_query_renderer):
> > Vendor: Intel Open Source Technology Center (0x8086)
> > Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)
> > Version: 12.0.3
> > Accelerated: yes
> > Video memory: 1536MB
> > Unified memory: yes
> > Preferred profile: core (0x1)
> > Max core profile version: 3.3
> > Max compat profile version: 3.0
> > Max GLES1 profile version: 1.1
> > Max GLES[23] profile version: 3.0
> >
> > X.org runs with modesetting driver (default was changed in Debian Sid a
> > while back).
> >
> > Thanks,
> > _______________________________________________
> > Intel-gfx mailing list
> > [email protected]
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx


--
Martin

2016-11-07 17:09:50

by Jani Nikula

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

On Mon, 07 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> It is also the same kind of corruptions as shown in
>
> [Bug 177701] warning in intel_dp_aux_transfer
> https://bugzilla.kernel.org/show_bug.cgi?id=177701
>
> Just compare
>
> https://bugzilla.kernel.org/attachment.cgi?id=241801
>
> with
>
> https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
>
>
> However that bug report links to
>
> https://bugs.freedesktop.org/show_bug.cgi?id=97344
>
> yet the patch mentioned in there does not fix the issue. So I wonder whether
> bug #97344 and bug #177701 are really the same.

They are the same, it's just that #177701 conflates two issues, a
warning (tracked at fdo #973449) and a graphics corruption. The latter
appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402.

The fix has now been pushed to drm-intel-fixes branch of
http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen
latest fixes. Please try that and report back.

> Of course I can report a bug at fdo as well, but I am a bit confused
> whether it may not already have been reported. Well I hope I get a
> chance to report it there as well and you get to decide.

If drm-intel-fixes doesn't fix the issue for you, please file a *new*
bug over at the freedesktop.org bugzilla.

BR,
Jani.

--
Jani Nikula, Intel Open Source Technology Center

2016-11-07 22:59:51

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Montag, 7. November 2016, 19:09:36 CET schrieb Jani Nikula:
> On Mon, 07 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> > It is also the same kind of corruptions as shown in
> >
> > [Bug 177701] warning in intel_dp_aux_transfer
> > https://bugzilla.kernel.org/show_bug.cgi?id=177701
> >
> > Just compare
> >
> > https://bugzilla.kernel.org/attachment.cgi?id=241801
> >
> > with
> >
> > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
> >
> >
> > However that bug report links to
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=97344
> >
> > yet the patch mentioned in there does not fix the issue. So I wonder
> > whether bug #97344 and bug #177701 are really the same.
>
> They are the same, it's just that #177701 conflates two issues, a
> warning (tracked at fdo #973449) and a graphics corruption. The latter
> appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402.
>
> The fix has now been pushed to drm-intel-fixes branch of
> http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen
> latest fixes. Please try that and report back.

Thanks for clearing that up, Jani.

I think I get a chance to compile from drm-intel tomorrow and test it. If it
just happens on external displays – I didn´t actually check this – I can only
test it in the evening.

> > Of course I can report a bug at fdo as well, but I am a bit confused
> > whether it may not already have been reported. Well I hope I get a
> > chance to report it there as well and you get to decide.
>
> If drm-intel-fixes doesn't fix the issue for you, please file a *new*
> bug over at the freedesktop.org bugzilla.

Will do.

Thanks,
--
Martin

2016-11-08 15:11:37

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Montag, 7. November 2016, 19:09:36 CET schrieb Jani Nikula:
> On Mon, 07 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> > It is also the same kind of corruptions as shown in
> >
> > [Bug 177701] warning in intel_dp_aux_transfer
> > https://bugzilla.kernel.org/show_bug.cgi?id=177701
> >
> > Just compare
> >
> > https://bugzilla.kernel.org/attachment.cgi?id=241801
> >
> > with
> >
> > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
> >
> >
> > However that bug report links to
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=97344
> >
> > yet the patch mentioned in there does not fix the issue. So I wonder
> > whether bug #97344 and bug #177701 are really the same.
>
> They are the same, it's just that #177701 conflates two issues, a
> warning (tracked at fdo #973449) and a graphics corruption. The latter
> appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402.
>
> The fix has now been pushed to drm-intel-fixes branch of
> http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen
> latest fixes. Please try that and report back.

For now commit 54905ab5fe7aa453610e31cec640e528aaedb2e2 of drm-intel-fixes
branch seems to work okay. I can only test with laptop display at the moment.
But I will test with external display this evening – in case the issue at hand
is DisplayPort related.

I will add this information to fdo bug 98402 as well.

Thanks,
Martin

> > Of course I can report a bug at fdo as well, but I am a bit confused
> > whether it may not already have been reported. Well I hope I get a
> > chance to report it there as well and you get to decide.
>
> If drm-intel-fixes doesn't fix the issue for you, please file a *new*
> bug over at the freedesktop.org bugzilla.
>
> BR,
> Jani.


--
Martin

2016-11-08 15:18:03

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Dienstag, 8. November 2016, 16:11:31 CET schrieb Martin Steigerwald:
> Am Montag, 7. November 2016, 19:09:36 CET schrieb Jani Nikula:
> > On Mon, 07 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> > > It is also the same kind of corruptions as shown in
> > >
> > > [Bug 177701] warning in intel_dp_aux_transfer
> > > https://bugzilla.kernel.org/show_bug.cgi?id=177701
> > >
> > > Just compare
> > >
> > > https://bugzilla.kernel.org/attachment.cgi?id=241801
> > >
> > > with
> > >
> > > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
> > >
> > >
> > > However that bug report links to
> > >
> > > https://bugs.freedesktop.org/show_bug.cgi?id=97344
> > >
> > > yet the patch mentioned in there does not fix the issue. So I wonder
> > > whether bug #97344 and bug #177701 are really the same.
> >
> > They are the same, it's just that #177701 conflates two issues, a
> > warning (tracked at fdo #973449) and a graphics corruption. The latter
> > appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402.
> >
> > The fix has now been pushed to drm-intel-fixes branch of
> > http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen
> > latest fixes. Please try that and report back.
>
> For now commit 54905ab5fe7aa453610e31cec640e528aaedb2e2 of drm-intel-fixes

I ment not exactly this commit, but this is the last commit in the branch as I
compiled the kernel.

> branch seems to work okay. I can only test with laptop display at the
> moment. But I will test with external display this evening – in case the
> issue at hand is DisplayPort related.
>
> I will add this information to fdo bug 98402 as well.
>
> Thanks,
> Martin
>
> > > Of course I can report a bug at fdo as well, but I am a bit confused
> > > whether it may not already have been reported. Well I hope I get a
> > > chance to report it there as well and you get to decide.
> >
> > If drm-intel-fixes doesn't fix the issue for you, please file a *new*
> > bug over at the freedesktop.org bugzilla.
> >
> > BR,
> > Jani.


--
Martin

2016-11-09 08:21:32

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Dienstag, 8. November 2016, 16:17:59 CET schrieb Martin Steigerwald:
> Am Dienstag, 8. November 2016, 16:11:31 CET schrieb Martin Steigerwald:
> > Am Montag, 7. November 2016, 19:09:36 CET schrieb Jani Nikula:
> > > On Mon, 07 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> > > > It is also the same kind of corruptions as shown in
> > > >
> > > > [Bug 177701] warning in intel_dp_aux_transfer
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=177701
> > > >
> > > > Just compare
> > > >
> > > > https://bugzilla.kernel.org/attachment.cgi?id=241801
> > > >
> > > > with
> > > >
> > > > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.p
> > > > ng
> > > >
> > > >
> > > > However that bug report links to
> > > >
> > > > https://bugs.freedesktop.org/show_bug.cgi?id=97344
> > > >
> > > > yet the patch mentioned in there does not fix the issue. So I wonder
> > > > whether bug #97344 and bug #177701 are really the same.
> > >
> > > They are the same, it's just that #177701 conflates two issues, a
> > > warning (tracked at fdo #973449) and a graphics corruption. The latter
> > > appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402.
> > >
> > > The fix has now been pushed to drm-intel-fixes branch of
> > > http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen
> > > latest fixes. Please try that and report back.
> >
> > For now commit 54905ab5fe7aa453610e31cec640e528aaedb2e2 of drm-intel-fixes
>
> I ment not exactly this commit, but this is the last commit in the branch as
> I compiled the kernel.
>
> > branch seems to work okay. I can only test with laptop display at the
> > moment. But I will test with external display this evening – in case the
> > issue at hand is DisplayPort related.

Also no graphics glitches with external DisplayPort connected display.

*However*, I got a soft freeze and a hard freeze (well after about a minute I
gave up and rebooted by pressing power button long enough to forcefully switch
off the laptop) when playing PlaneShift using drm-intel-fixes branch.

Unfortunately I have no further time to debug any of this week, but it seems
not all fixes are there are ready for next stable kernel.

Ciao,
Martin

> > I will add this information to fdo bug 98402 as well.
> >
> > Thanks,
> > Martin
> >
> > > > Of course I can report a bug at fdo as well, but I am a bit confused
> > > > whether it may not already have been reported. Well I hope I get a
> > > > chance to report it there as well and you get to decide.
> > >
> > > If drm-intel-fixes doesn't fix the issue for you, please file a *new*
> > > bug over at the freedesktop.org bugzilla.
> > >
> > > BR,
> > > Jani.


--
Martin

2016-11-09 09:42:42

by Jani Nikula

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

On Wed, 09 Nov 2016, Martin Steigerwald <[email protected]> wrote:
> Also no graphics glitches with external DisplayPort connected display.

Thanks for confirming this. The fix should make it to -rc5.

> *However*, I got a soft freeze and a hard freeze (well after about a
> minute I gave up and rebooted by pressing power button long enough to
> forcefully switch off the laptop) when playing PlaneShift using
> drm-intel-fixes branch.
>
> Unfortunately I have no further time to debug any of this week, but it
> seems not all fixes are there are ready for next stable kernel.

Current drm-intel-fixes is just six commits on top of -rc4, and it's
very hard for me to believe any of those would cause the symptoms you
see. I presume the problem, whatever it is, is already in -rc4.

That, of course, is not a happy thing per se, but please don't block the
current batch of fixes by making unsubstantiated claims. Please do file
a bug about that issue over at [1] so we don't hijack this thread.

Thanks,
Jani.


[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel


--
Jani Nikula, Intel Open Source Technology Center

2016-11-09 09:59:59

by Martin Steigerwald

[permalink] [raw]
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4)

Am Mittwoch, 9. November 2016, 11:42:36 CET schrieb Jani Nikula:
> > *However*, I got a soft freeze and a hard freeze (well after about a
> > minute I gave up and rebooted by pressing power button long enough to
> > forcefully switch off the laptop) when playing PlaneShift using
> > drm-intel-fixes branch.
> >
> > Unfortunately I have no further time to debug any of this week, but it
> > seems not all fixes are there are ready for next stable kernel.
>
> Current drm-intel-fixes is just six commits on top of -rc4, and it's
> very hard for me to believe any of those would cause the symptoms you
> see. I presume the problem, whatever it is, is already in -rc4.
>
> That, of course, is not a happy thing per se, but please don't block the
> current batch of fixes by making unsubstantiated claims. Please do file
> a bug about that issue over at [1] so we don't hijack this thread.

You are right. I have no comparison with 4.9-rc4 due to the graphics glitches
I had in it.

--
Martin