Bug#912936: linux: kernel WARNING in ieee80211_delayed_tailroom_dec

2018-11-04 Thread Thorsten Glaser
Package: src:linux
Version: 4.18.10-2+b1
Severity: minor

I got the warning you see below, and the WLAN reset after a while.

-- Package-specific info:
** Version:
Linux version 4.18.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.10-2 (2018-10-07)

** Command line:
BOOT_IMAGE=/vmlinuz-4.18.0-2-amd64 root=/dev/sda4 ro rootdelay=5 syscall.x32=y 
vsyscall=emulate net.ifnames=0 kaslr pcie_aspm=force consoleblank=0

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

** Kernel log:
[9.549441] EXT4-fs (sda2): mounted filesystem without journal. Opts: 
auto_da_alloc
[9.754104] random: dd: uninitialized urandom read (512 bytes read)
[9.877824] tun: Universal TUN/TAP device driver, 1.6
[9.886225] systemd-udevd[1084]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
[9.891566] systemd-udevd[1084]: Could not generate persistent MAC address 
for tap4: No such file or directory
[9.899906] IPv6: ADDRCONF(NETDEV_UP): tap4: link is not ready
[   10.646921] random: edac-ctl: uninitialized urandom read (4 bytes read)
[   10.877000] random: mktemp: uninitialized urandom read (8 bytes read)
[   10.899966] random: arngc-slrd: uninitialized urandom read (16 bytes read)
[   22.473625] random: crng init done
[   44.544893] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   48.923166] wlan0: authenticate with 38:10:d5:48:ea:c0
[   48.935976] wlan0: send auth to 38:10:d5:48:ea:c0 (try 1/3)
[   48.943379] wlan0: authenticated
[   48.947404] wlan0: waiting for beacon from 38:10:d5:48:ea:c0
[   49.044119] wlan0: associate with 38:10:d5:48:ea:c0 (try 1/3)
[   49.053519] wlan0: RX AssocResp from 38:10:d5:48:ea:c0 (capab=0x431 status=0 
aid=6)
[   49.083221] wlan0: associated
[   50.121982] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   70.989126] systemd-udevd[2529]: link_config: autonegotiation is unset or 
enabled, the speed and duplex are not writable.
[53281.316867] yenta_cardbus :05:00.0: CardBus bridge to [bus 06-07]
[53281.323237] yenta_cardbus :05:00.0:   bridge window [io  0x4000-0x40ff]
[53281.329552] yenta_cardbus :05:00.0:   bridge window [io  0x4400-0x44ff]
[53281.335692] yenta_cardbus :05:00.0:   bridge window [mem 
0xd800-0xdbff pref]
[53281.335704] yenta_cardbus :05:00.0:   bridge window [mem 
0xc000-0xc3ff]
[57283.196066] systemd-udevd[375]: Network interface NamePolicy= disabled on 
kernel command line, ignoring.
[57326.418304] systemd-udevd[375]: Network interface NamePolicy= disabled on 
kernel command line, ignoring.
[57326.422419] device-mapper: uevent: version 1.0.3
[57326.422665] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
[65468.521360] atkbd serio0: Unknown key released (translated set 2, code 0x5b 
on isa0060/serio0).
[65468.521374] atkbd serio0: Use 'setkeycodes 5b ' to make it known.
[69219.864468] b1: revision 1.1.2.2
[69219.870212] c4: revision 1.1.2.2
[100425.180073] iwl4965 :03:00.0: Queue 4 stuck for 2048 ms.
[100425.180097] iwl4965 :03:00.0: On demand firmware reload
[100425.184134] iwl4965 :03:00.0: Timeout stopping DMA channel 1 
[0xa5a5a5a2]
[100425.186121] iwl4965 :03:00.0: Timeout stopping DMA channel 3 
[0xa5a5a5a2]
[100425.186121] iwl4965 :03:00.0: Timeout stopping DMA channel 4 
[0xa5a5a5a2]
[100425.186121] iwl4965 :03:00.0: Timeout stopping DMA channel 6 
[0xa5a5a5a2]
[100425.199265] ieee80211 phy0: Hardware restart was requested
[100425.449449] WARNING: CPU: 1 PID: 15591 at 
/build/linux-s3QDK1/linux-4.18.10/net/mac80211/key.c:741 
ieee80211_enable_keys+0x114/0x120 [mac80211]
[100425.449454] Modules linked in: c4 b1 kernelcapi dm_mod cpuid snd_seq_dummy 
ctr ccm devlink cpufreq_conservative cpufreq_userspace cpufreq_powersave 
binfmt_misc nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c nft_compat nf_tables 
x_tables nfnetlink tun snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq 
snd_seq_device snd_hda_codec_analog snd_hda_codec_generic arc4 ppdev pcmcia 
iwl4965 coretemp iwlegacy kvm_intel snd_hda_intel snd_hda_codec mac80211 kvm 
snd_hda_core irqbypass snd_hwdep snd_pcm_oss snd_mixer_oss pcspkr serio_raw 
iTCO_wdt yenta_socket sg iTCO_vendor_support pcmcia_rsrc pcmcia_core cfg80211 
snd_pcm thinkpad_acpi snd_timer nvram snd soundcore ac rfkill battery 
pcc_cpufreq parport_pc parport button acpi_cpufreq evdev
[100425.449515]  ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb 
crypto_simd cryptd glue_helper aes_x86_64 sd_mod ata_generic ahci libahci 
ata_piix psmouse sdhci_pci i2c_i801 cqhci libata sdhci mmc_core i915 scsi_mod 
lpc_ich i2c_algo_bit drm_kms_helper video uhci_hcd ehci_pci ehci_hcd drm 
usbcore e1000e usb_common thermal
[100425.449554] CPU: 1 PID: 15591 Comm: kworker/1:1 Not tainted 4.18.0-2-amd64 
#1 Debian 4.18.10-2
[100425.449556] Hardware name: LENOVO 7673AG4/7673AG4, BIOS 

Bug#852324: closed by Ben Hutchings (Re: [xen] x86/mm: Found insecure W+X mapping)

2018-11-04 Thread Diederik de Haas
On zaterdag 3 november 2018 03:02:07 CET Ben Hutchings wrote:
> > I was/am on the verge of upgrading that system from Stretch to Buster,
> > which would upgrade both Xen (to 4.11) and the kernel (some which would
> > include the fix).
> > Would it be useful to first upgrade just the kernel (and leave Xen at 4.8)
> > to verify it is indeed also fixed on my system?
> 
> You should be able to do that if you want.

Upgraded just the kernel:

with "4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64"
# dmesg | grep -i w+x 
[   37.316560] x86/mm: Checked W+X mappings: FAILED, 4090 W+X pages found.

with "4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-11-02) x86_64"
# dmesg | grep -i w+x 
[2.298828] x86/mm: Checked W+X mappings: passed, no W+X pages found.

\o/

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


Bug#912840: linux-image-4.18.0-2-amd64: kernel 4.18 with core2 cpu break kvm/qemu

2018-11-04 Thread John Wong
Package: src:linux
Version: 4.18.10-2+b1
Severity: normal

Dear Maintainer,

 I have a system with intel core2 cpu, running kvm/qemu (host),
 after upgrade to 4.18 kernel,
 (both linux-image-4.18.0-1-amd64 or linux-image-4.18.0-2-amd64),
 then some kvm/qemu quest can not boot.
 
 I think the system hit the bug.

 https://www.spinics.net/lists/kvm/msg175557.html
 https://patchwork.kernel.org/patch/10614795/

 Could you like to backport the patch, or upgrade the kernel version
 to 4.18.16/4.19?

 Thanks.



Bug#875621: Solve touchpad and trackpoint issue at LenovoX1CarbonGen6

2018-11-04 Thread Brilliantov Kirill Vladimirovich
Hello!
Problem solved after enable all RMI4 options and switch to linux-4.19

$ uname -a
Linux lenovo 4.19.0-trunk-amd64 #1 SMP Debian 4.19-1~exp1 (2018-10-08) x86_64 
GNU/Linux

$ grep rmi /proc/modules
rmi_smbus 16384 0 - Live 0x (E)
rmi_core 90112 1 rmi_smbus, Live 0x (E)
videobuf2_vmalloc 16384 2 uvcvideo,rmi_core, Live 0x (E)
videobuf2_v4l2 28672 2 uvcvideo,rmi_core, Live 0x (E)
videobuf2_common 53248 3 uvcvideo,rmi_core,videobuf2_v4l2, Live 
0x (E)
videodev 212992 4 uvcvideo,rmi_core,videobuf2_v4l2,videobuf2_common, Live 
0x (E)

$ cat /etc/modprobe.d/psmouse.conf
options psmouse synaptics_intertouch=1

$ grep RMI4 /boot/config-4.19.0-trunk-amd64
CONFIG_RMI4_CORE=m
CONFIG_RMI4_I2C=m
CONFIG_RMI4_SPI=m
CONFIG_RMI4_SMB=m
CONFIG_RMI4_F03=y
CONFIG_RMI4_F03_SERIO=m
CONFIG_RMI4_2D_SENSOR=y
CONFIG_RMI4_F11=y
CONFIG_RMI4_F12=y
CONFIG_RMI4_F30=y
CONFIG_RMI4_F34=y
CONFIG_RMI4_F54=y
CONFIG_RMI4_F55=y

$ dmesg | grep psmouse
[2.547109] psmouse serio1: synaptics: queried max coordinates: x [..5678], 
y [..4758]
[2.578804] psmouse serio1: synaptics: queried min coordinates: x [1266..], 
y [1094..]
[2.578807] psmouse serio1: synaptics: Trying to set up SMBus access
[3.023443] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x06, 
buttons: 3/3