Bug#884803: linux-image-4.13.0-1-686-pae: kernel traces output when using wifi (ath9k)

[cacatoes]

Package: src:linux
Version: 4.13.13-1

Dear Maintainer,

This problem isn't exactly new (several months, with various kernels), but I 
mostly use ethernet so am usually not annoyed by it.
After connecting to wifi networks, and usually when there is network activity, 
my terminals/consoles are filled with kernel debug traces, which you will find 
in the given attachments.
The network itself goes on working, it doesn't seem to interrupt/disconnect, so 
the annoyance is limited.

Good luck with bug sorting, hope this report makes sense.

-- Package-specific info:
** Version:
Linux version 4.13.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 
6.4.0 20171112 (Debian 6.4.0-10)) #1 SMP Debian 4.13.13-1 (2017-11-16)

** Command line:
BOOT_IMAGE=/vmlinuz-4.13.0-1-686-pae root=/dev/mapper/cacacomp--vg-root ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information

** Loaded modules:
ctr
ccm
appletalk
ax25
ipx
p8023
p8022
psnap
llc
fuse
snd_hda_codec_realtek
snd_hda_codec_generic
snd_hda_codec_hdmi
wmi_bmof
arc4
nouveau
ath9k
ath9k_common
ath9k_hw
uvcvideo
ath
mxm_wmi
videobuf2_vmalloc
ttm
mac80211
videobuf2_memops
drm_kms_helper
videobuf2_v4l2
videobuf2_core
videodev
snd_hda_intel
coretemp
cfg80211
media
snd_hda_codec
drm
snd_hda_core
snd_hwdep
i2c_algo_bit
joydev
snd_pcm
snd_timer
snd
evdev
soundcore
serio_raw
sg
shpchp
asus_laptop
sparse_keymap
rfkill
battery
input_polldev
wmi
ac
video
nv_tco
button
acpi_cpufreq
sunrpc
ip_tables
x_tables
autofs4
hid_generic
usbhid
hid
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
crypto_simd
cryptd
aes_i586
dm_mod
sr_mod
cdrom
sd_mod
psmouse
ahci
libahci
libata
atl1e
scsi_mod
ohci_pci
ehci_pci
ohci_hcd
ehci_hcd
usbcore
usb_common
i2c_nforce2
thermal

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

# The primary network interface
allow-hotplug enp3so
iface enp3s0 inet dhcp
# This is an autoconfigured IPv6 interface
iface enp3s0 inet6 auto

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc pfifo_fast state 
DOWN group default qlen 1000
link/ether e0:cb:4e:ff:c5:27 brd ff:ff:ff:ff:ff:ff
3: wlp4s0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 1c:4b:d6:7c:f9:84 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.8/24 brd 192.168.0.255 scope global wlp4s0
   valid_lft forever preferred_lft forever
inet6 fe80::1e4b:d6ff:fe7c:f984/64 scope link 
   valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
wlp4s0: 224889522  177230000 0  0 0 11590038  
116391000 0   0  0
lo:   0   0000 0  0 00  
 0000 0   0  0
enp3s0:   0   0000 0  0 00  
 0000 0   3  0

*** Protocol statistics:
Ip:
Forwarding: 2
166849 total packets received
3 with invalid addresses
0 forwarded
0 incoming packets discarded
164197 incoming packets delivered
115643 requests sent out
128 dropped because of missing route
Icmp:
0 ICMP messages received
0 input ICMP message failed
ICMP input histogram:
0 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
Tcp:
884 active connection openings
0 passive connection openings
0 failed connection attempts
6 connection resets received
3 connections established
163688 segments received
115055 segments sent out
192 segments retransmitted
20 bad segments received
988 resets sent
Udp:
397 packets received
0 packets to unknown port received
0 packet receive errors
396 packets sent
0 receive buffer errors
0 send buffer errors
IgnoredMulti: 112
UdpLite:
TcpExt:
282 TCP sockets finished time wait in fast timer
1160 delayed acks sent
1 delayed acks further delayed because of locked socket
Quick ack mode was activated 233 times
10 packets directly queued to recvmsg prequeue
TCPDirectCopyFromPrequeue: 5
130093 packet headers predicted

Bug#884638: 4.13 also seems unaffected

[John Eikenberry]

Been running linux-image-4.13.0-0.bpo.1-amd64 (4.13.13-1~bpo9+1) for a few days
now without incident. So it seems free from the bug as well.

-- 

John Eikenberry
[ j...@zhar.net - http://zhar.net ]
[ PGP public key @ http://zhar.net/jae_at_zhar_net.gpg ]

"Perfection is attained, not when no more can be added, but when no more
 can be removed." -- Antoine de Saint-Exupery


signature.asc
Description: PGP signature

Bug#883938: fixed in linux 3.16.51-3

[Ben Hutchings]

On Tue, 2017-12-19 at 12:09 -0600, Phil Kauffman wrote:
> Can we also make sure that this bug gets fixed in the netboot kernel?
> 
> http://ftp.us.debian.org/debian/dists/jessie/main/installer-amd64/cur
> rent/images/netboot/debian-installer/amd64/linux

The netboot kernel won't be updated until the next point release.  See
https://lists.debian.org/debian-stable-announce/2017/12/msg2.html

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


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

Bug#883938: fixed in linux 3.16.51-3

[Phil Kauffman]

Can we also make sure that this bug gets fixed in the netboot kernel?

http://ftp.us.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux

Cheers,

Phil

Bug#884762: linux-image-3.16.0-4-amd64: Kernel panic on boot (rest_init / build_sched_domains) make system unbootable

[Olivier Hanesse]

Hello,

We got the same issue on Vmware with this specific kernel.
VMs with more than 12 vcpus (we got 12 cpus / socket)  crashed at boot time.

Setting cpus to 12 is a workaround (if this can help people .. )

Regards

Re: Bug#880502: [pkg-apparmor] Bug#880502: [pkg-lxc-devel] Bug#880502: lxc: cannot start container with kernel 4.13.10

[Antonio Terceiro]

Hi,

On Sun, Nov 05, 2017 at 01:09:10PM +0100, intrigeri wrote:
> Hi,
> 
> Antonio Terceiro:
> > The workaround that works is using the setting in the container
> > configuration:
> 
> > lxc.aa_profile = unconfined
> 
> > with disables apparmor entirely.
> 
> > I have just uploaded lxc 1:2.0.9-4 setting this for all containers. This
> > is not the greatest solution, but it's also not worse than the state of
> > affairs before apparmor was enabled by default in the Debian kernel: it
> > was already not possible to use lxc with apparmor in Debian.
> 
> Fully agreed: top priority is to ensure AppArmor doesn't break things,
> so let's disable any profile that is not ready for prime time.
> 
> Adding AppArmor confinement where we had none previously can
> come later.

FWIW, since apparmor 2.11.1-4 this issue is no longer reproducible, so I
am closing this bug.

I will also make a new lxc upload removing the workaround mentioned
above.


signature.asc
Description: PGP signature