Bug#908196: linux-image-4.9.0-8-armmp: Please set CONFIG_LEDS_PCA963X=m
Hi, Vincent. On Tue, Aug 17, 2021 at 04:41:20PM +0200, Vincent Blut wrote: > Package: src:linux > Followup-For: Bug #908196 > Is it still worthwhile to enable this option? IMO yes. I have the thing sitting on my desk now, it runs Debian, and it serves its function. > So if this router does not run on Linux 5.13+, it's probably not worth > to enable this option. I've just upgraded the device to bullseye, and installed linux-image-5.13.0-trunk from the experimental on it. I confirm that: - the device boots successfully with that kernel. - both LAN and WAN ports work. - USB ports work too. The kernel from the experimental just misses the usual: - pca963x for WAN/WIFI leds - wifi. Wifi requires out of tree module anyway, and its outside of the scope of this bug report. Sincerely yours, Reco
Bug#958904: linux-image-4.19.0-8-rpi: Please set CONFIG_RTC_DRV_DS1307=m
Package: src:linux Version: 4.19.98-1 Severity: wishlist Dear Maintainer, Raspberry Pi Model 1B I'm running this installation from does not have built-in RTC clock. DS1307-based RTCs are very popular addon for Raspberry Pi, and I happen to have one. The support of this particular chip is disabled in Debian kernels, so please consider building it as a module Sincerely yours, Reco -- Package-specific info: ** Version: Linux version 4.19.0-8-rpi (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 Debian 4.19.98-1 (2020-01-26) ** Command line: bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2708.boardrev=0x10 bcm2708.serial=0x631eea77 bcm2708.uart_clock=4800 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:1E:EA:77 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=tty0 console=ttyAMA0,115200 root=/dev/pi/root rw elevator=deadline fsck.repair=yes net.ifnames=0 cma=64M rootwait ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: BCM2835 Revision: Device Tree model: Raspberry Pi Model B Plus Rev 1.2 ** Loaded modules: cfg80211 rfkill 8021q garp stp mrp llc ip6t_REJECT nf_reject_ipv6 xt_mac nft_counter ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_comment nft_compat nf_tables nfnetlink nls_ascii nls_cp437 vfat fat vc4 smsc95xx snd_soc_core usbnet mii snd_pcm_dmaengine snd_pcm snd_timer snd raspberrypi_hwmon soundcore cec vchiq(C) bcm2835_rng rng_core leds_gpio zram zsmalloc auth_rpcgss sunrpc ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb dm_mod ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: armel (armv6l) Kernel: Linux 4.19.0-8-rpi Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-8-rpi depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-8-rpi recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-8-rpi suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-8-rpi is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190114-2 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#933265: linux-image-4.19.0-5-arm64: NULL pointer dereference at nf_tables_newrule
Package: src:linux Version: 4.19.37-5+deb10u1 Severity: normal Dear Maintainer, I've discovered recently that loading the following set of iptables rules with iptables-nft-restore: *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -i lo -j ACCEPT -A INPUT -m conntrack --ctstate INVALID -j DROP -A INPUT -p icmp --icmp-type 0 -m comment --comment "Ping" -j ACCEPT -A INPUT -p icmp --icmp-type 3 -m comment --comment "Ping" -j ACCEPT -A INPUT -p icmp --icmp-type 8 -m comment --comment "Ping" -j ACCEPT -A INPUT -p icmp --icmp-type any -m limit --limit 10/sec -j ACCEPT -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A INPUT -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -m hashlimit --hashlimit-upto 1/hour --hashlimit-burst 4 --hashlimit-mode srcip --hashlimit-name ssh --hashlimit-htable-expire 65536 -m comment --comment "SSH Blocker" -j ACCEPT -A INPUT -p tcp -m tcp --dport 22 --tcp-flags SYN,RST,ACK SYN -m comment --comment "SSH Blocker" -j DROP -A FORWARD -m conntrack --ctstate INVALID -j DROP -A OUTPUT -m conntrack --ctstate INVALID -j DROP -A OUTPUT -p udp -m udp -d 224/4 -j REJECT COMMIT Triggers the following NULL pointer dereference: [ 181.133805] Unable to handle kernel NULL pointer dereference at virtual address 0028 [ 181.135156] Mem abort info: [ 181.135313] ESR = 0x9604 [ 181.135484] Exception class = DABT (current EL), IL = 32 bits [ 181.135697] SET = 0, FnV = 0 [ 181.135819] EA = 0, S1PTW = 0 [ 181.135953] Data abort info: [ 181.136075] ISV = 0, ISS = 0x0004 [ 181.136218] CM = 0, WnR = 0 [ 181.136569] user pgtable: 4k pages, 48-bit VAs, pgdp = 6b2d46d6 [ 181.137242] [0028] pgd= [ 181.137752] Internal error: Oops: 9604 [#1] SMP [ 181.138038] Modules linked in: nft_limit nft_counter ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_tcpudp xt_limit xt_comment ip_tables xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nft_compat x_tables nf_tables nfnetlink autofs4 fuse 9p fscache nls_ascii nls_cp437 vfat fat evdev aes_ce_blk crypto_simd cryptd aes_ce_cipher ghash_ce gf128mul sha2_ce sha256_arm64 sha1_ce efi_pstore gpio_keys efivars 9pnet_virtio virtio_net 9pnet net_failover failover qemu_fw_cfg ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb aes_arm64 dm_mod virtio_blk virtio_rng rng_core virtio_mmio virtio_pci virtio_ring virtio [ 181.140242] Process iptables-restor (pid: 1886, stack limit = 0xeeeb9f00) [ 181.140676] CPU: 0 PID: 1886 Comm: iptables-restor Not tainted 4.19.0-5-arm64 #1 Debian 4.19.37-5+deb10u1 [ 181.140999] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 [ 181.141423] pstate: 8005 (Nzcv daif -PAN -UAO) [ 181.142111] pc : nf_tables_newrule+0x4b4/0x718 [nf_tables] [ 181.142331] lr : nf_tables_newrule+0x4bc/0x718 [nf_tables] [ 181.142532] sp : 099037a0 [ 181.142672] x29: 099037a0 x28: 0003 [ 181.142885] x27: x26: 294393bd8840 [ 181.143084] x25: a0defcc901b0 x24: fff5 [ 181.143287] x23: a0defd490b00 x22: 08a35878 [ 181.143480] x21: a0defcc90120 x20: 0002 [ 181.143679] x19: 294393aa9708 x18: 294393ac7220 [ 181.143878] x17: x16: 0006 [ 181.144080] x15: x14: a0defde99860 [ 181.144267] x13: a0defde996d0 x12: 0028 [ 181.144466] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f [ 181.144674] x9 : fefeff73686c686b x8 : 294317db3b7c [ 181.144876] x7 : fefefefefefefefe x6 : 00808080 [ 181.145075] x5 : x4 : 29431f6bb968 [ 181.145276] x3 : 0006 x2 : 0005 [ 181.145479] x1 : 0006 x0 : [ 181.145772] Call trace: [ 181.145966] nf_tables_newrule+0x4b4/0x718 [nf_tables] [ 181.146178] nfnetlink_rcv_batch+0x3ec/0x580 [nfnetlink] [ 181.146388] nfnetlink_rcv+0x138/0x188 [nfnetlink] [ 181.146810] netlink_unicast+0x1d0/0x260 [ 181.146968] netlink_sendmsg+0x1b0/0x358 [ 181.147128] sock_sendmsg+0x4c/0x68 [ 181.147273] ___sys_sendmsg+0x288/0x2c8 [ 181.147419] __sys_sendmsg+0x7c/0xd0 [ 181.147559] __arm64_sys_sendmsg+0x2c/0x38 [ 181.147726] el0_svc_common+0x94/0x108 [ 181.147881] el0_svc_handler+0x38/0x78 [ 181.148037] el0_svc+0x8/0xc [ 181.148314] Code: d503201f f94002a0 b480 f9402c00 (f9401400) [ 181.148838] ---[ end trace 04c9f90c72f843fa ]--- I can reproduce this problem on both QEMU and a real hardware, and as far as I can tell both aarch64 and armhf are affected. Sincerely yours, Reco -- Package-specific info: ** Version: Linux version 4.19.0-5-arm64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-arm64 root=/dev/mapper/stretch--arm64
Bug#933228: linux-image-4.19.0-5-arm64: Please enable CONFIG_VIDEO_BCM2835=m
Package: src:linux Version: 4.19.37-5 Severity: wishlist Dear Maintainer, Raspberry Pi3, from which I write this bugreport, is a popular SoC that finally got a proper support by Debian project. It would be nice to have a kernel module for the camera host interface, which is included into Debian's kernel source tree, but is currently disabled. Tainted status of the current kernel comes from self-built bcm2835_v4l2. Sincerely yours, Reco -- Package-specific info: ** Version: Linux version 4.19.0-5-arm64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-5 (2019-06-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-arm64 root=/dev/mapper/pi2-root ro quiet ** Tainted: COE (13312) * Module from drivers/staging has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Device Tree model: Raspberry Pi 3 Model B Plus Rev 1.3 ** Loaded modules: dm_snapshot dm_bufio cbc cts rpcsec_gss_krb5 nfsv4 dns_resolver nfs lockd grace fscache nls_ascii nls_cp437 vfat fat 8021q garp mrp stp llc ip6_tables ip6t_REJECT nf_reject_ipv6 xt_mac nft_counter ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_comment nft_compat nf_tables nfnetlink btsdio bluetooth drbg ansi_cprng microchip ecdh_generic brcmfmac lan78xx brcmutil of_mdio cfg80211 fixed_phy libphy rfkill bcm2835_thermal bcm2835_rng rng_core efi_pstore bcm2835_wdt leds_gpio efivars bcm2835_v4l2(OE) vchiq(C) v4l2_common videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common auth_rpcgss videodev sunrpc media efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb aes_arm64 dm_mod dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci usb_common bcm2835 phy_generic fixed ** PCI devices: not available ** USB devices: Bus 001 Device 004: ID 0424:7800 Standard Microsystems Corp. Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-5-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-5-arm64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-5-arm64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-5-arm64 suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-5-arm64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#922478: have yet to find an armhf board that works with 4.9.144-3
Hi. On Mon, Feb 18, 2019 at 05:09:12PM +0100, Cyril Brulebois wrote: > Checking this on real hardware would be great, trying to put everyone > involved in the loop through cc. Confirming that the patched kernel booted successfully on Armada385/Caiman. Reco
Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Hi. On Sun, Feb 17, 2019 at 08:27:34PM +0100, Cyril Brulebois wrote: > Hi, > > Reco (2019-02-17): > > Did this already in QEMU (virt board). > > 4.9.135-1 works. > > 4.9.144-1 (next one) is broken. > > Is there any chance you could share how to get such a VM set up in QEMU? > > I'd be happy to try a few kernel builds, but having a quick way to check > whether a given kernel build is OK/KO would be much appreciated. 1) Install qemu-system-arm. 2) Unpack kernel .deb, locate vmlinuz-4.9.0-8-armmp. Or search your just-built zImage. 3) Run qemu (no root required): qemu-system-arm -M virt -nographic -kernel vmlinuz-4.9.0-8-armmp If you see a kernel panic - the outcome is positive, the kernel is OK. If it just stays there eating 100% CPU - the outcome is negative. Reco
Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Hi. On Sun, Feb 17, 2019 at 07:38:18PM +0100, Cyril Brulebois wrote: > Hi folks, > > Jürgen Löb (2019-02-16): > > Package: linux-image-4.9.0-8-armmp-lpae > > Version: 4.9.144-3 > > Severity: serious > > > > Updated my Lamobo R1 board with apt update;apt upgrade > > > > After the update uboot is struck at "Starting kernel". There is no > > further output after "Starting kernel". Same happens on Bananapi 1 > > board. Unfortunately there is no more useful information. > […] > > Summing up, it looks like everybody in cc is confirming the regression > happens between 4.9.130-2 and 4.9.144-3, with and without lpae, on > various boards. Any chance you could check what happens with the > 4.9.135-1 intermediary version that can be found on snapshot.debian.org? Did this already in QEMU (virt board). 4.9.135-1 works. 4.9.144-1 (next one) is broken. The problem is - 4.9.144-1 introduced large amount of changes, including two Spectre mitigations. My attempts to build a kernel with CONFIG_SPECTRE=n yielded unbootable kernels, which may mean that: a) Spectre mitigations are not related to the problem. b) My kernel-rebuilding skill could use some improvement. Reco
Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Hi all. I'd like to add that plain armmp (non-lpae) is broken too. At least for Armada385/Caiman and QEMU's virt. Reco
Bug#918114: linux-image-armmp: please add CONFIG_SENSORS_LM75=m
Package: linux-image-armmp Version: 4.18+100~bpo9+1 Severity: wishlist Dear Maintainer, Please enable building lm75.ko as a module, there's a hardware (Helios4 NAS), which runs Debian kernel and userland without a hitch, but lm75 is required for monitoring CPU temperature. Sincerely yours, Reco -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.18.0-0.bpo.3-armmp (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-armmp depends on: ii linux-image-4.18.0-0.bpo.3-armmp 4.18.20-2~bpo9+1 linux-image-armmp recommends no packages. linux-image-armmp suggests no packages. -- no debconf information
Bug#908196: linux-image-4.9.0-8-armmp: Please set CONFIG_LEDS_PCA963X=m
Package: src:linux Version: 4.9.110-3+deb9u4 Severity: wishlist Dear Maintainer, I happen to have a piece of hardware (Linksys WRT1200 AC) which runs stock Debian kernel flawlessly. There's one small detail that mars that experience - the absence of I2C LED driver for PCA9634. Sincerely yours, Reco -- Package-specific info: ** Version: Linux version 4.9.0-8-armmp (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) ** Command line: console=ttyS0,115200 root=/dev/mapper/xx-root ro quiet apparmor=1 security=apparmor ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: Marvell Armada 380/385 (Device Tree) Revision: Device Tree model: Linksys WRT1200AC ** Loaded modules: tcp_diag inet_diag ctr ccm ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_nat_ipv6 xt_TCPMSS xfrm4_tunnel ipcomp ebt_ip ebt_arp ebtable_filter ebtables 8021q garp mrp ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_mac xt_limit xt_owner xt_multiport xt_hashlimit xt_comment xt_mark xt_conntrack iptable_filter cls_fw ipt_MASQUERADE nf_nat_masquerade_ipv4 em_meta xt_nat cls_basic xt_tcpudp sch_htb iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc sit af_key ah4 esp4 iptable_raw iptable_mangle ip_vti ip_tunnel echainiv authenc ansi_cprng drbg xfrm_ipcomp xfrm_user xfrm_algo tunnel4 xfrm4_mode_tunnel xfrm6_mode_tunnel arc4 sg ofpart pxa3xx_nand marvell_cesa tmp421 leds_gpio evdev orion_wdt des_generic mwlwifi(O) mac80211 cfg80211 auth_rpcgss oid_registry rfkill sunrpc ip_tables x_tables autofs4 crc32c_generic ext4 crc16 jbd2 fscrypto mbcache dm_mod sd_mod uas usb_storage ahci_mvebu libahci_platform libahci libata xhci_plat_hcd ehci_orion ehci_hcd phy_generic xhci_hcd usbcore scsi_mod mvmdio usb_common mvneta i2c_mv64xxx dsa_core ** PCI devices: 00:01.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device [11ab:6820] (rev 04) (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: 00:02.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device [11ab:6820] (rev 04) (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: 01:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88W8864 [Avastar] 802.11ac Wireless [11ab:2a55] Subsystem: Marvell Technology Group Ltd. 88W8864 [Avastar] 802.11ac Wireless [11ab:] 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: mwlwifi Kernel modules: mwlwifi 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88W8864 [Avastar] 802.11ac Wireless [11ab:2a55] Subsystem: Marvell Technology Group Ltd. 88W8864 [Avastar] 802.11ac Wireless [11ab:] 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: mwlwifi Kernel modules: mwlwifi ** USB devices: Bus 003 Device 002: ID 1058:25a2 Western Digital Technologies, Inc. Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.0-8-armmp (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.9.0-8-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.9.0-8-armmp recommends: pn firmware-linux-free ii irqbalance 1.1.0-2.3 Versions of packages linux-image-4.9.0-8-armmp suggests: pn debian-kernel-handbook pn l
Bug#758880: linux-image-3.14-0.bpo.2-powerpc64: [ppc64] Kernel panic on shutdown
Package: src:linux Version: 3.14.13-2~bpo70+1 Severity: normal Dear Maintainer, Current backported version of Linux kernel running in qemu-system-ppc64 panics on shutdown with: [ 567.737855] Oops: Exception in kernel mode, sig: 4 [#1] [ 567.738864] SMP NR_CPUS=32 NUMA pSeries [ 567.739615] Modules linked in: loop ext4 crc16 mbcache jbd2 virtio_blk virtio_net virtio_pci virtio_ring virtio [ 567.740337] CPU: 0 PID: 4106 Comm: echo Not tainted 3.14-0.bpo.2-powerpc64 #1 Debian 3.14.13-2~bpo70+1 [ 567.740611] task: c0003ab2a410 ti: c0003ffe4000 task.ti: c0003e6f8000 [ 567.740692] NIP: d01f5258 LR: d01f5610 CTR: d01f5570 [ 567.740762] REGS: c0003ffe7830 TRAP: 0700 Not tainted (3.14-0.bpo.2-powerpc64 Debian 3.14.13-2~bpo70+1) [ 567.740830] MSR: 80089032 SF,EE,ME,IR,DR,RI CR: 48422028 XER: [ 567.741096] CFAR: d01f51e4 SOFTE: 0 GPR00: c0003ffe7ab0 d01ff108 3b72a7c0 GPR04: 0002 0002 1b1e GPR08: 0001 c0003ac68020 c0003ac68000 24fe GPR12: d024f118 cfffa000 0001 c08354b8 GPR16: c09d5af0 c0003aa40430 0017 0001 GPR20: c09d25c8 c09d25c8 c0003aa40380 GPR24: c0987800 c0ac5c68 GPR28: c0003abc4690 c0003ab89800 0020 c0003ab89800 [ 567.742593] NIP [d01f5258] .detach_buf+0xb8/0xe0 [virtio_ring] [ 567.742652] LR [d01f5610] .virtqueue_get_buf+0xa0/0x180 [virtio_ring] [ 567.742732] Call Trace: [ 567.742894] [c0003ffe7ab0] [d01f5268] .detach_buf+0xc8/0xe0 [virtio_ring] (unreliable) [ 567.743019] [c0003ffe7b40] [d01f5610] .virtqueue_get_buf+0xa0/0x180 [virtio_ring] [ 567.743088] [c0003ffe7bc0] [d024d35c] .virtblk_done+0x7c/0x100 [virtio_blk] [ 567.743161] [c0003ffe7c70] [d01f594c] .vring_interrupt+0x7c/0x100 [virtio_ring] [ 567.743543] [c0003ffe7cf0] [c011b688] .handle_irq_event_percpu+0xc8/0x370 [ 567.743606] [c0003ffe7e00] [c011b988] .handle_irq_event+0x58/0xb0 [ 567.743686] [c0003ffe7e80] [c0120060] .handle_fasteoi_irq+0xd0/0x1d0 [ 567.743754] [c0003ffe7f00] [c0011104] .__do_irq+0xb4/0x200 [ 567.743820] [c0003ffe7f90] [c00229e8] .call_do_irq+0x14/0x24 [ 567.743886] [c0003e6fb720] [c00112dc] .do_IRQ+0x8c/0x100 [ 567.743953] [c0003e6fb7c0] [c0002268] hardware_interrupt_common+0x168/0x180 [ 567.744061] --- Exception: 501 at .arch_local_irq_restore+0x74/0x90 [ 567.744061] LR = .arch_local_irq_restore+0x74/0x90 [ 567.744152] [c0003e6fbab0] [c00108b8] .arch_local_irq_restore+0x38/0x90 (unreliable) [ 567.744241] [c0003e6fbb20] [c00e95e4] .finish_task_switch+0x74/0x190 [ 567.744316] [c0003e6fbbb0] [c06e792c] .__schedule+0x2dc/0x860 [ 567.744402] [c0003e6fbe30] [c000a788] .ret_from_except_lite+0x34/0x60 [ 567.744475] Instruction dump: [ 567.744731] 38090001 901f002c e8010010 ebc1fff0 ebe1fff8 7c0803a6 4e800020 6000 [ 567.744863] 6000 6000 7c6af02a 3800 0001 7844 [ 567.745331] ---[ end trace 3a346b1e72d4d1aa ]--- [ 567.761814] [ 569.762595] Kernel panic - not syncing: Fatal exception in interrupt Currently I don't have a spare LPAR to test this on a real hardware, but using latest qemu from the backports this issue reproduces 100%. Qemu commandline is (using libvirt, sorry for the length): /usr/bin/qemu-system-ppc64 -name wheezy-ppc -S -machine pseries,accel=tcg,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 2dfb78af-46ee-4540-8814-971d1797c910 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/wheezy-ppc.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -drive file=/var/lib/libvirt/images/wheezy_ppc.raw,if=none,id=drive-virtio-disk0,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:f1:db:16,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,reg=0x3000 -global spapr-nvram.reg=0x3000 -cpu POWER7 -- Package-specific info: ** Version: Linux version 3.14-0.bpo.2-powerpc64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-11) ) #1 SMP Debian 3.14.13-2~bpo70+1 (2014-07-31) ** Command line: root=UUID=e17a8c34-1eb6-4a70-a536-d215abcb84ae ro quiet ** Not tainted ** Kernel log: [0.023957] Yama: disabled by default; enable with sysctl kernel.yama.* [0.027287] Dentry cache hash table entries: 131072
