Your message dated Fri, 11 Jan 2019 00:46:42 +0000 with message-id <0d5b88076134c0fb738c38434cbae0a23fcbda7d.camel@decadent.org.uk> and subject line Re: Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start has caused the Debian Bug report #908192, regarding linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 908192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908192 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start
- From: John Wong <johnw.mail@gmail.com>
- Date: Fri, 07 Sep 2018 16:06:58 +0800
- Message-id: <153630761841.3845.3054759475313484066.reportbug@kvm102>
Package: src:linux Version: 4.18.6-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As title, after upgrade to linux-image-4.18.0-1-amd64, lxc can not start, If boot to old kernel (4.17-3..), lxc can start again. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 4.18.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.6-1 (2018-09-06) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-amd64 root=UUID=5cb16262-d214-4feb-9369-81a291a2388b ro apparmor=1 security=apparmor quiet ** Not tainted ** Kernel log: ** Model information [ 50.617580] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 50.617598] lxcbr0: port 2(veth471YAX) entered blocking state [ 50.617599] lxcbr0: port 2(veth471YAX) entered forwarding state [ 50.633435] lxcbr0: port 2(veth471YAX) entered disabled state [ 50.633527] device veth471YAX left promiscuous mode [ 50.633528] lxcbr0: port 2(veth471YAX) entered disabled state [ 111.648345] lxcbr0: port 2(vethMT2FWQ) entered blocking state [ 111.648347] lxcbr0: port 2(vethMT2FWQ) entered disabled state [ 111.648372] device vethMT2FWQ entered promiscuous mode [ 111.651743] lxcbr0: port 2(vethMT2FWQ) entered disabled state [ 111.651866] device vethMT2FWQ left promiscuous mode [ 111.651867] lxcbr0: port 2(vethMT2FWQ) entered disabled state [ 221.679794] lxcbr0: port 2(vethYPTVY4) entered blocking state [ 221.679795] lxcbr0: port 2(vethYPTVY4) entered disabled state [ 221.679821] device vethYPTVY4 entered promiscuous mode [ 221.701044] eth0: renamed from vethHEA5JH [ 221.724082] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 221.725177] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 221.725196] lxcbr0: port 2(vethYPTVY4) entered blocking state [ 221.725197] lxcbr0: port 2(vethYPTVY4) entered forwarding state [ 221.740431] lxcbr0: port 2(vethYPTVY4) entered disabled state [ 221.740526] device vethYPTVY4 left promiscuous mode [ 221.740527] lxcbr0: port 2(vethYPTVY4) entered disabled state [ 229.743698] lxcbr0: port 2(vethG6VBDH) entered blocking state [ 229.743699] lxcbr0: port 2(vethG6VBDH) entered disabled state [ 229.743727] device vethG6VBDH entered promiscuous mode [ 229.769070] eth0: renamed from vethESL89I [ 229.791893] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 229.792987] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 229.793003] lxcbr0: port 2(vethG6VBDH) entered blocking state [ 229.793004] lxcbr0: port 2(vethG6VBDH) entered forwarding state [ 229.804473] lxcbr0: port 2(vethG6VBDH) entered disabled state [ 229.804572] device vethG6VBDH left promiscuous mode [ 229.804573] lxcbr0: port 2(vethG6VBDH) entered disabled state [ 252.543415] lxcbr0: port 2(vethQTK7VL) entered blocking state [ 252.543416] lxcbr0: port 2(vethQTK7VL) entered disabled state [ 252.543442] device vethQTK7VL entered promiscuous mode [ 252.573029] eth0: renamed from veth8J8RJX [ 252.587882] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 252.589098] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 252.589115] lxcbr0: port 2(vethQTK7VL) entered blocking state [ 252.589116] lxcbr0: port 2(vethQTK7VL) entered forwarding state [ 252.600700] lxcbr0: port 2(vethQTK7VL) entered disabled state [ 252.600801] device vethQTK7VL left promiscuous mode [ 252.600802] lxcbr0: port 2(vethQTK7VL) entered disabled state [ 1270.152712] lxcbr0: port 2(veth83ORBG) entered blocking state [ 1270.152713] lxcbr0: port 2(veth83ORBG) entered disabled state [ 1270.152741] device veth83ORBG entered promiscuous mode [ 1270.175792] eth0: renamed from vethXLKI4X [ 1270.199037] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1270.200115] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1270.200133] lxcbr0: port 2(veth83ORBG) entered blocking state [ 1270.200134] lxcbr0: port 2(veth83ORBG) entered forwarding state [ 1270.215342] lxcbr0: port 2(veth83ORBG) entered disabled state [ 1270.215431] device veth83ORBG left promiscuous mode [ 1270.215432] lxcbr0: port 2(veth83ORBG) entered disabled state [ 1281.911374] lxcbr0: port 2(vethWLL3H7) entered blocking state [ 1281.911375] lxcbr0: port 2(vethWLL3H7) entered disabled state [ 1281.911402] device vethWLL3H7 entered promiscuous mode [ 1281.935451] eth0: renamed from vethDVX7T8 [ 1281.946282] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1281.947522] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1281.947540] lxcbr0: port 2(vethWLL3H7) entered blocking state [ 1281.947541] lxcbr0: port 2(vethWLL3H7) entered forwarding state [ 1281.968923] lxcbr0: port 2(vethWLL3H7) entered disabled state [ 1281.969039] device vethWLL3H7 left promiscuous mode [ 1281.969040] lxcbr0: port 2(vethWLL3H7) entered disabled state [ 1418.839495] lxcbr0: port 2(vethEH6D5X) entered blocking state [ 1418.839496] lxcbr0: port 2(vethEH6D5X) entered disabled state [ 1418.839524] device vethEH6D5X entered promiscuous mode [ 1418.872072] eth0: renamed from vethJJ83AV [ 1418.886803] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1418.887976] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1418.887997] lxcbr0: port 2(vethEH6D5X) entered blocking state [ 1418.887998] lxcbr0: port 2(vethEH6D5X) entered forwarding state [ 1418.911752] lxcbr0: port 2(vethEH6D5X) entered disabled state [ 1418.911846] device vethEH6D5X left promiscuous mode [ 1418.911847] lxcbr0: port 2(vethEH6D5X) entered disabled state [ 1424.773581] lxcbr0: port 2(vethXY4AJT) entered blocking state [ 1424.773582] lxcbr0: port 2(vethXY4AJT) entered disabled state [ 1424.773609] device vethXY4AJT entered promiscuous mode [ 1424.799757] eth0: renamed from vethSATD6O [ 1424.815852] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1424.816926] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1424.816947] lxcbr0: port 2(vethXY4AJT) entered blocking state [ 1424.816948] lxcbr0: port 2(vethXY4AJT) entered forwarding state [ 1424.831505] lxcbr0: port 2(vethXY4AJT) entered disabled state [ 1424.831594] device vethXY4AJT left promiscuous mode [ 1424.831595] lxcbr0: port 2(vethXY4AJT) entered disabled state [ 1529.333864] lxcbr0: port 2(veth03FHO8) entered blocking state [ 1529.333865] lxcbr0: port 2(veth03FHO8) entered disabled state [ 1529.333892] device veth03FHO8 entered promiscuous mode [ 1529.358331] eth0: renamed from vethMJ9C11 [ 1529.376607] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1529.377975] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1529.377997] lxcbr0: port 2(veth03FHO8) entered blocking state [ 1529.377998] lxcbr0: port 2(veth03FHO8) entered forwarding state [ 1529.385125] lxcbr0: port 2(veth03FHO8) entered disabled state [ 1529.385210] device veth03FHO8 left promiscuous mode [ 1529.385212] lxcbr0: port 2(veth03FHO8) entered disabled state sys_vendor: QEMU product_name: Standard PC (i440FX + PIIX, 1996) product_version: pc-i440fx-2.12 chassis_vendor: QEMU chassis_version: pc-i440fx-2.12 bios_vendor: SeaBIOS bios_version: 1.11.1-1 ** Loaded modules: veth squashfs snd_rawmidi snd_seq_device snd_hwdep rpcsec_gss_krb5 ppdev overlay nls_utf8 nls_iso8859_1 snd_intel8x0 nfsv4 nfsv3 nfs_acl nfs snd_ac97_codec md4 loop lockd isofs iptable_filter hid_generic hid grace snd_pcm snd_timer ghash_clmulni_intel fuse joydev ext4 virtio_gpu mbcache jbd2 sg serio_raw ttm pcspkr snd soundcore fscrypto parport_pc parport evdev ecb drm_kms_helper drm crct10dif_pclmul crc32_pclmul crc16 cmac cifs dns_resolver fscache ccm button bridge stp llc auth_rpcgss arc4 ac97_bus sunrpc ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c crc32c_generic sr_mod cdrom ata_generic virtio_net net_failover failover virtio_blk crc32c_intel ata_piix aesni_intel aes_x86_64 crypto_simd cryptd glue_helper libata i2c_piix4 scsi_mod psmouse virtio_pci virtio_ring virtio ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering]) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8] Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8] Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) Region 4: I/O ports at c560 [size=16] Kernel driver in use: ata_piix Kernel modules: ata_piix, ata_generic 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 9 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:02.0 VGA compatible controller [0300]: Red Hat, Inc Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Virtio GPU [1af4:1100] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 10 Region 0: Memory at fe000000 (32-bit, prefetchable) [size=8M] Region 2: Memory at fe800000 (64-bit, prefetchable) [size=16K] Region 4: Memory at febd0000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] Subsystem: Red Hat, Inc Virtio network device [1af4:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at c540 [size=32] Region 1: Memory at febd1000 (32-bit, non-prefetchable) [size=4K] Region 4: Memory at fe804000 (64-bit, prefetchable) [size=16K] Expansion ROM at feb80000 [disabled] [size=256K] Capabilities: <access denied> Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:04.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Physical Slot: 4 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at c000 [size=1K] Region 1: I/O ports at c400 [size=256] Kernel driver in use: snd_intel8x0 Kernel modules: snd_intel8x0 00:05.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001] Subsystem: Red Hat, Inc Virtio block device [1af4:0002] Physical Slot: 5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at c500 [size=64] Region 1: Memory at febd2000 (32-bit, non-prefetchable) [size=4K] Region 4: Memory at fe808000 (64-bit, prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: virtio-pci Kernel modules: virtio_pci ** USB devices: not available -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (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) LSM: AppArmor: enabled Versions of packages linux-image-4.18.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.132 ii kmod 25-1 ii linux-base 4.5 Versions of packages linux-image-4.18.0-1-amd64 recommends: ii apparmor 2.13-8 pn firmware-linux-free <none> pn irqbalance <none> Versions of packages linux-image-4.18.0-1-amd64 suggests: pn debian-kernel-handbook <none> ii grub-pc 2.02+dfsg1-6 pn linux-doc-4.18 <none> Versions of packages linux-image-4.18.0-1-amd64 is related to: pn firmware-amd-graphics <none> pn firmware-atheros <none> pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-cavium <none> pn firmware-intel-sound <none> pn firmware-intelwimax <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> pn firmware-iwlwifi <none> pn firmware-libertas <none> pn firmware-linux-nonfree <none> pn firmware-misc-nonfree <none> pn firmware-myricom <none> pn firmware-netxen <none> pn firmware-qlogic <none> pn firmware-realtek <none> pn firmware-samsung <none> pn firmware-siano <none> pn firmware-ti-connectivity <none> pn xen-hypervisor <none> -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Pierre-Elliott Bécue <peb@debian.org>, 908192-done@bugs.debian.org, John Wong <johnw.mail@gmail.com>, Salvatore Bonaccorso <carnil@debian.org>, Christian Brauner <christian@brauner.io>
- Subject: Re: Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Fri, 11 Jan 2019 00:46:42 +0000
- Message-id: <0d5b88076134c0fb738c38434cbae0a23fcbda7d.camel@decadent.org.uk>
- In-reply-to: <[🔎] 20190110225736.5cpvd2cgb4z32tci@crans.org>
- References: <153630761841.3845.3054759475313484066.reportbug@kvm102> <[🔎] 20190110225736.5cpvd2cgb4z32tci@crans.org>
Version: 4.19.13-1 On Thu, 2019-01-10 at 23:57 +0100, Pierre-Elliott Bécue wrote: > Hi, > > Do any of the three of you see an issue with me closing this bug? > > As the problem was deemed not to be in linux, and got fixed in LXC, I see no > benefit from having it stay open. > > Without response, I'll close it the next time I triage bugs regarding LXC > (~1 month I think) It is a kernel bug, and has been fixed in Linux 4.20 and 4.19.13. Thanks for the reminder. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---