[Kernel-packages] [Bug 1895789] [NEW] rfkill hangs when turn on/off bluetooth
Public bug reported: Turn on/off leads to a kernel panic related to rfkill Hardware ID: 201712-26024 OS: 20.04 Desktop Kernel: 5.4.0-48-generic Step to reproduce: 1. Click on/off in the bluetooth settings for a few time 2. Oberserve kernel message as following [ 126.914032] [ cut here ] [ 126.914034] kernel BUG at mm/slub.c:306! [ 126.914041] invalid opcode: [#1] SMP PTI [ 126.914044] CPU: 6 PID: 4741 Comm: gsd-rfkill Tainted: P OE 5.4.0-48-generic #52-Ubuntu [ 126.914045] Hardware name: Dell Inc. XPS 13 9370/0173S1, BIOS 1.13.1 07/08/2020 [ 126.914050] RIP: 0010:__slab_free+0x189/0x330 [ 126.914052] Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 65 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c 24 28 75 e8 48 8b 44 24 28 49 89 4c 24 28 49 89 44 [ 126.914054] RSP: 0018:b46f42d73c90 EFLAGS: 00010246 [ 126.914056] RAX: 9c6931960a00 RBX: 80200015 RCX: 9c6931960a00 [ 126.914057] RDX: 9c6931960a00 RSI: e19511c65800 RDI: 9c695bff9340 [ 126.914058] RBP: b46f42d73d28 R08: 0001 R09: a4d1b6be [ 126.914059] R10: 9c6931960a00 R11: 0001 R12: e19511c65800 [ 126.914060] R13: 9c6931960a00 R14: 9c695bff9340 R15: 9c695bff9340 [ 126.914062] FS: 7fbd905bf840() GS:9c695e58() knlGS: [ 126.914063] CS: 0010 DS: ES: CR0: 80050033 [ 126.914064] CR2: 7fc51ed2 CR3: 0003e6012002 CR4: 003606e0 [ 126.914066] DR0: DR1: DR2: [ 126.914067] DR3: DR6: fffe0ff0 DR7: 0400 [ 126.914068] Call Trace: [ 126.914072] ? finish_wait+0x59/0x70 [ 126.914075] ? wait_woken+0x80/0x80 [ 126.914078] ? kfree_skbmem+0x4e/0x60 [ 126.914080] kmem_cache_free+0x288/0x2b0 [ 126.914085] ? btusb_shutdown_intel_new+0x36/0x60 [btusb] [ 126.914087] kfree_skbmem+0x4e/0x60 [ 126.914089] kfree_skb+0x3a/0xa0 [ 126.914092] btusb_shutdown_intel_new+0x36/0x60 [btusb] [ 126.914108] hci_dev_do_close+0x40c/0x520 [bluetooth] [ 126.914121] hci_rfkill_set_block+0x56/0xa0 [bluetooth] [ 126.914124] rfkill_set_block+0x9b/0x150 [ 126.914127] rfkill_fop_write+0x136/0x1e0 [ 126.914130] __vfs_write+0x1b/0x40 [ 126.914131] vfs_write+0xb9/0x1a0 [ 126.914134] ksys_write+0xb1/0xe0 [ 126.914136] __x64_sys_write+0x1a/0x20 [ 126.914139] do_syscall_64+0x57/0x190 [ 126.914142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 126.914144] RIP: 0033:0x7fbd9097021f [ 126.914146] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 59 65 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 8c 65 f8 ff 48 [ 126.914147] RSP: 002b:7fffd6047f00 EFLAGS: 0293 ORIG_RAX: 0001 [ 126.914149] RAX: ffda RBX: 7fbd905bf7c0 RCX: 7fbd9097021f [ 126.914150] RDX: 0008 RSI: 5581c4fe4dd0 RDI: 0008 [ 126.914151] RBP: 7fffd6047f50 R08: R09: 000b [ 126.914152] R10: 5581c4fd3dc8 R11: 0293 R12: 0001 [ 126.914153] R13: 7fffd6047fb0 R14: R15: 5581c4fd6020 [ 126.914155] Modules linked in: thunderbolt veth nft_masq nft_chain_nat uhid rfcomm vboxnetadp(OE) xt_CHECKSUM vboxnetflt(OE) xt_MASQUERADE xt_tcpudp vboxdrv(OE) bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter nf_tables nfnetlink ccm aufs cmac algif_hash algif_skcipher af_alg overlay bnep hid_logitech_hidpp typec_displayport hid_logitech_dj hid_apple binfmt_misc ftdi_sio usbserial snd_usb_audio snd_usbmidi_lib mei_hdcp intel_rapl_msr snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_hda_codec x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_core dell_laptop ledtrig_audio snd_hwdep kvm_intel joydev snd_pcm snd_seq_midi snd_seq_midi_event dell_wmi kvm crct10dif_pclmul dell_smbios [ 126.914188] dcdbas snd_rawmidi nls_iso8859_1 cdc_ether ghash_clmulni_intel usbnet aesni_intel r8152 crypto_simd mii snd_seq iwlmvm cryptd glue_helper snd_seq_device intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor rapl snd_timer intel_cstate mac80211 btusb btrtl btbcm uvcvideo input_leds btintel libarc4 videobuf2_vmalloc bluetooth serio_raw videobuf2_memops videobuf2_v4l2 videobuf2_common videodev iwlwifi ecdh_generic cdc_acm mc ecc i915 snd cfg80211 soundcore rtsx_pci_ms mei_me memstick drm_kms_helper hid_multitouch mei ucsi_acpi typec_ucsi i2c_algo_bit fb_sys_fops processor_thermal_device intel_xhci_usb_role_switch syscopyarea
[Kernel-packages] [Bug 1891598] Re: Broken build dep in snapcraft.yaml
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891598 Title: Broken build dep in snapcraft.yaml Status in linux package in Ubuntu: Confirmed Bug description: Current snapcraft.yaml is broken for building kernel snaps with ubuntu kernel tree from a clean ubuntu environment. Please see the patch in attached to fix the problem This is effecting Ubuntu Core developers to build a custom kernel base on Ubuntu stable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891598] [NEW] Broken build dep in snapcraft.yaml
Public bug reported: Current snapcraft.yaml is broken for building kernel snaps with ubuntu kernel tree from a clean ubuntu environment. Please see the patch in attached to fix the problem This is effecting Ubuntu Core developers to build a custom kernel base on Ubuntu stable kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891598 Title: Broken build dep in snapcraft.yaml Status in linux package in Ubuntu: New Bug description: Current snapcraft.yaml is broken for building kernel snaps with ubuntu kernel tree from a clean ubuntu environment. Please see the patch in attached to fix the problem This is effecting Ubuntu Core developers to build a custom kernel base on Ubuntu stable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
No, it doesn't effect functionality AFAIK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
The wifi looks functional after the fix but ath10k driver starts complaining ** Attachment added: "dmesg.tar.xz" https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+attachment/5263930/+files/dmesg.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
confirmed #35 build fix same issue on XPS13 9360 with wifi module QCA6174. Tested 10 suspends on power pluged and unpluged Thanks Kai-Heng for the fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
@Kai-Heng is there a patched kernel package I can test with? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662754] Re: Calling docker command from a snap leads a kernel panic
Hi Seth, What's the right way to try your kernel? I created a test snap to reproduce the issue: https://github.com/pliu6/docker-kernel-panic-test With the test snap, I can reproduce the issue with official linux- image-4.4.0-59-generic, but after I tried to install the kernel image from the link you gave, I am not able to boot the machine. The issue can not be reproduced with an old version kernel on my machine (official 4.2.0-42-generic). Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662754 Title: Calling docker command from a snap leads a kernel panic Status in linux package in Ubuntu: Triaged Bug description: On the latest version of all-snap image, when I call docker command from a snap, the kernel will panic. The "uname -a" result is below: Linux localhost.localdomain 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662754] Re: Calling docker command from a snap leads a kernel panic
Kernel log is below: [ 3629.712878] BUG: unable to handle kernel paging request at fff3 [ 3629.796735] IP: [] strlen+0x0/0x20 [ 3629.856430] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 3629.906140] Oops: [#4] SMP [ 3629.945243] Modules linked in: xt_nat xt_tcpudp veth xt_comment ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay aufs arc4 ath10k_pci ath9k ath10k_core ath9k_common ath9k_hw ath mac80211 kvm_amd kvm uas irqbypass cfg80211 k10temp sp5100_tco r8169 i2c_piix4 mii shpchp mac_hid iptable_filter ip_tables ip6table_filter ip6_tables x_tables autofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 3630.543640] CPU: 0 PID: 2479 Comm: snap-confine Tainted: G D 4.4.0-59-generic #80-Ubuntu [ 3630.654077] Hardware name: PC Engines APU/APU, BIOS 4.0 09/08/2014 [ 3630.728123] task: 88007a338000 ti: 88007a388000 task.ti: 88007a388000 [ 3630.817768] RIP: 0010:[] [] strlen+0x0/0x20 [ 3630.906581] RSP: 0018:88007a38ba20 EFLAGS: 00010246 [ 3630.970226] RAX: 88007a38bb20 RBX: fff3 RCX: [ 3631.055710] RDX: 0151 RSI: fff3 RDI: fff3 [ 3631.141195] RBP: 88007a38ba38 R08: 880060a4c93b R09: 88007a38ba94 [ 3631.226679] R10: 000e R11: 880060a4c934 R12: 88007a701240 [ 3631.312163] R13: 88007a338000 R14: 8139b3d0 R15: fff3 [ 3631.397650] FS: 7f0e8d98b740() GS:88007de0() knlGS: [ 3631.494574] CS: 0010 DS: ES: CR0: 80050033 [ 3631.563417] CR2: fff3 CR3: 6719a000 CR4: 06f0 [ 3631.648901] Stack: [ 3631.673030] 8112333a 88007a701240 88007a38bb00 88007a38ba60 [ 3631.762464] 8139b438 88007a701240 88007a38bb00 88007a338000 [ 3631.851901] 88007a38bad8 81370498 81229680 88007a38baf0 [ 3631.941337] Call Trace: [ 3631.970675] [] ? audit_log_untrustedstring+0x1a/0x30 [ 3632.049919] [] audit_cb+0x68/0x3f0 [ 3632.110444] [] common_lsm_audit+0x1b8/0x740 [ 3632.180330] [] ? alloc_inode+0x50/0x90 [ 3632.245011] [] ? prepend_path+0xc6/0x2a0 [ 3632.311779] [] aa_audit+0x5f/0x170 [ 3632.372300] [] audit_mount+0x152/0x160 [ 3632.436988] [] match_mnt_path_str+0x1dd/0x490 [ 3632.508951] [] ? dentry_path+0x18/0x70 [ 3632.573638] [] match_mnt+0xda/0x150 [ 3632.635203] [] aa_bind_mount+0x100/0x180 [ 3632.701969] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 3632.778095] [] security_sb_mount+0x57/0x80 [ 3632.846939] [] do_mount+0xab/0xda0 [ 3632.907468] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 3632.985668] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 3633.061798] [] ? memdup_user+0x42/0x70 [ 3633.126479] [] SyS_mount+0x9f/0x100 [ 3633.188050] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 3633.265205] Code: 89 f8 48 89 e5 f6 82 e0 0d a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 e0 0d a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <80> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 3633.504601] RIP [] strlen+0x0/0x20 [ 3633.565335] RSP [ 3633.607143] CR2: fff3 [ 3633.646880] ---[ end trace 23ca1e52db270fbd ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662754 Title: Calling docker command from a snap leads a kernel panic Status in linux package in Ubuntu: New Bug description: On the latest version of all-snap image, when I call docker command from a snap, the kernel will panic. The "uname -a" result is below: Linux localhost.localdomain 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662754] Re: Calling docker command from a snap leads a kernel panic
This bug is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651944, even though the steps to reproduce are different. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662754 Title: Calling docker command from a snap leads a kernel panic Status in linux package in Ubuntu: New Bug description: On the latest version of all-snap image, when I call docker command from a snap, the kernel will panic. The "uname -a" result is below: Linux localhost.localdomain 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662754] [NEW] Calling docker command from a snap leads a kernel panic
Public bug reported: On the latest version of all-snap image, when I call docker command from a snap, the kernel will panic. The "uname -a" result is below: Linux localhost.localdomain 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662754 Title: Calling docker command from a snap leads a kernel panic Status in linux package in Ubuntu: New Bug description: On the latest version of all-snap image, when I call docker command from a snap, the kernel will panic. The "uname -a" result is below: Linux localhost.localdomain 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Actually, this bug was found with Ubuntu all-snap version. So I am not able to try the kernel.deb. Could you tell me how to get the latest version of the kernel snap for 16.04? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Changed the target to be apparmor because the kernel panic is triggered by apparmor. ** Package changed: linux (Ubuntu) => apparmor (Ubuntu) ** Also affects: apparmor Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
The bug was found on the all-snap image. Therefore I was not able to run apport-collect command. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in linux package in Ubuntu: Confirmed Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1651944] [NEW] Kernel panic when we call pipework to setup virtual network for docker containers
Public bug reported: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in linux package in Ubuntu: New Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev
[Kernel-packages] [Bug 1394368] Re: Bluetooth with AR9462 doesn't work (New ID /Firmware)
Looks like the module is built for 3.16.0-24-generic, which is earlier than the
status quo 3.16.0-27-generic.
Is there a way to get the module file built against latest kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1394368
Title:
Bluetooth with AR9462 doesn't work (New ID /Firmware)
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Fix Released
Status in linux-firmware source package in Vivid:
Confirmed
Bug description:
This is (kind of) a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884
(please read)
I can't use Bluetooth with my AR9462 WLAN/BT-Combo.
In the link above, it has been fixed, but not for my Adapter ID/Firmware:
System:
Ubuntu 14.10 utopic 64bit - 3.16.0-24-generic x86_64
lspci -nnk
02:00.0 Network controller [0280]: Qualcomm Atheros AR9462
Wireless Network Adapter [168c:0034] (rev 01)
Subsystem: Lite-On Communications Inc Device [11ad:0802]
Kernel driver in use: ath9k
lsusb (identified Bluetooth Device)
Bus 002 Device 003: ID 04ca:300d Lite-On Technology Corp.
ath9k.conf
options ath9k btcoex_enable=1
The "04ca:300d" ID is not in the Kernel, so i added it via dkms.
I took ath3k.c and btusb.c out of the 3.16.0-24-generic source files
and changed them:
diff -urN ./linux-3.16.0/drivers/bluetooth/ath3k.c
/usr/src/ar9462-1.5.1/ath3k.c
--- ./linux-3.16.0/drivers/bluetooth/ath3k.c 2014-08-04 00:25:02.0
+0200
+++ /usr/src/ar9462-1.5.1/ath3k.c 2014-11-19 21:12:46.646265890 +0100
@@ -85,6 +85,7 @@
{ USB_DEVICE(0x04CA, 0x3007) },
{ USB_DEVICE(0x04CA, 0x3008) },
{ USB_DEVICE(0x04CA, 0x300b) },
+ { USB_DEVICE(0x04CA, 0x300d) },
{ USB_DEVICE(0x0930, 0x0219) },
{ USB_DEVICE(0x0930, 0x0220) },
{ USB_DEVICE(0x0b05, 0x17d0) },
@@ -134,6 +135,7 @@
{ USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
diff -urN ./linux-3.16.0/drivers/bluetooth/btusb.c
/usr/src/ar9462-1.5.1/btusb.c
--- ./linux-3.16.0/drivers/bluetooth/btusb.c 2014-08-04 00:25:02.0
+0200
+++ /usr/src/ar9462-1.5.1/btusb.c 2014-11-19 21:12:46.646265890 +0100
@@ -157,6 +157,7 @@
{ USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
sudo dkms add -m ar9462 -v 1.5.1
sudo dkms build -m ar9462 -v 1.5.1
sudo dkms install -m ar9462 -v 1.5.1
(DKMS package in the same style/versioning as in the bug report above)
dkms status
ar9462, 1.5.1, 3.16.0-24-generic, x86_64: installed
Now the new output:
dmesg | egrep 'ath3|ar3|Bluet'
[2.787819] Bluetooth: Core ver 2.19
[2.787833] Bluetooth: HCI device and connection manager initialized
[2.787839] Bluetooth: HCI socket layer initialized
[2.787842] Bluetooth: L2CAP socket layer initialized
[2.787848] Bluetooth: SCO socket layer initialized
[2.793551] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[2.793554] Bluetooth: BNEP filters: protocol multicast
[2.793561] Bluetooth: BNEP socket layer initialized
[3.130779] Bluetooth: Patch file not found ar3k/AthrBT_0x11020100.dfu
[3.130783] Bluetooth: Loading patch file failed
[3.130788] ath3k: probe of 2-5:1.0 failed with error -12
[3.130823] usbcore: registered new interface driver ath3k
[9.776503] Bluetooth: RFCOMM TTY layer initialized
[9.776512] Bluetooth: RFCOMM socket layer initialized
[9.776517] Bluetooth: RFCOMM ver 1.11
My patch works, but just like in the bug report above, a Firmware file is
missing:
AthrBT_0x11020100.dfu
I found it neither in linux-firmware
(http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ar3k)
nor elsewhere.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1394368/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1394368] Re: Bluetooth with AR9462 doesn't work (New ID /Firmware)
This command doesn't work for me:
:~$ sudo dpkg -i ar9462-dkms_1.5.1_all.deb
(Reading database ... 235336 files and directories currently installed.)
Preparing to unpack ar9462-dkms_1.5.1_all.deb ...
Uninstall Beginning
Module: ar9462
Version: 1.5.1
Kernel: 3.16.0-24-generic (x86_64)
-
Status: This module version was INACTIVE for this kernel.
depmod(bad exit status: 1)
DKMS: uninstall completed.
--
Deleting module version: 1.5.1
completely from the DKMS tree.
--
Done.
Unpacking ar9462-dkms (1.5.1) over (1.5.1) ...
Setting up ar9462-dkms (1.5.1) ...
Loading tarball for ar9462-1.5.1
Loading /var/lib/dkms/ar9462/1.5.1/3.16.0-24-generic/x86_64...
DKMS: ldtarball completed.
Creating symlink /var/lib/dkms/ar9462/1.5.1/source ->
/usr/src/ar9462-1.5.1
DKMS: add completed.
First Installation: checking all kernels...
Building only for 4.2.0-27-generic
Building for architecture x86_64
Building initial module for 4.2.0-27-generic
Error! Bad return status for module build on kernel: 4.2.0-27-generic (x86_64)
Consult /var/lib/dkms/ar9462/1.5.1/build/make.log for more information.
FILE CONTENT IN: /var/lib/dkms/ar9462/1.5.1/build/make.log:
DKMS make.log for ar9462-1.5.1 for kernel 4.2.0-27-generic (x86_64)
Wed Feb 10 19:01:56 EST 2016
make: Entering directory '/usr/src/linux-headers-4.2.0-27-generic'
LD /var/lib/dkms/ar9462/1.5.1/build/built-in.o
CC [M] /var/lib/dkms/ar9462/1.5.1/build/btusb.o
/var/lib/dkms/ar9462/1.5.1/build/btusb.c: In function ‘btusb_intr_complete’:
/var/lib/dkms/ar9462/1.5.1/build/btusb.c:315:7: error: implicit declaration of
function ‘hci_recv_fragment’ [-Werror=implicit-function-declaration]
if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
^
cc1: some warnings being treated as errors
scripts/Makefile.build:264: recipe for target
'/var/lib/dkms/ar9462/1.5.1/build/btusb.o' failed
make[1]: *** [/var/lib/dkms/ar9462/1.5.1/build/btusb.o] Error 1
Makefile:1398: recipe for target '_module_/var/lib/dkms/ar9462/1.5.1/build'
failed
make: *** [_module_/var/lib/dkms/ar9462/1.5.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.2.0-27-generic'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1394368
Title:
Bluetooth with AR9462 doesn't work (New ID /Firmware)
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Fix Released
Status in linux-firmware source package in Vivid:
Confirmed
Bug description:
This is (kind of) a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884
(please read)
I can't use Bluetooth with my AR9462 WLAN/BT-Combo.
In the link above, it has been fixed, but not for my Adapter ID/Firmware:
System:
Ubuntu 14.10 utopic 64bit - 3.16.0-24-generic x86_64
lspci -nnk
02:00.0 Network controller [0280]: Qualcomm Atheros AR9462
Wireless Network Adapter [168c:0034] (rev 01)
Subsystem: Lite-On Communications Inc Device [11ad:0802]
Kernel driver in use: ath9k
lsusb (identified Bluetooth Device)
Bus 002 Device 003: ID 04ca:300d Lite-On Technology Corp.
ath9k.conf
options ath9k btcoex_enable=1
The "04ca:300d" ID is not in the Kernel, so i added it via dkms.
I took ath3k.c and btusb.c out of the 3.16.0-24-generic source files
and changed them:
diff -urN ./linux-3.16.0/drivers/bluetooth/ath3k.c
/usr/src/ar9462-1.5.1/ath3k.c
--- ./linux-3.16.0/drivers/bluetooth/ath3k.c 2014-08-04 00:25:02.0
+0200
+++ /usr/src/ar9462-1.5.1/ath3k.c 2014-11-19 21:12:46.646265890 +0100
@@ -85,6 +85,7 @@
{ USB_DEVICE(0x04CA, 0x3007) },
{ USB_DEVICE(0x04CA, 0x3008) },
{ USB_DEVICE(0x04CA, 0x300b) },
+ { USB_DEVICE(0x04CA, 0x300d) },
{ USB_DEVICE(0x0930, 0x0219) },
{ USB_DEVICE(0x0930, 0x0220) },
{ USB_DEVICE(0x0b05, 0x17d0) },
@@ -134,6 +135,7 @@
{ USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
diff -urN ./linux-3.16.0/drivers/bluetooth/btusb.c
/usr/src/ar9462-1.5.1/btusb.c
--- ./linux-3.16.0/drivers/bluetooth/btusb.c 2014-08-04 00:25:02.0
+0200
+++ /usr/src/ar9462-1.5.1/btusb.c 2014-11-19 21:12:46.646265890 +0100
@@ -157,6 +157,7 @@
{ USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{
[Kernel-packages] [Bug 872652] Re: screensaver backlight stuck off, system looks hung
** Changed in: linux (Ubuntu) Assignee: Kamal Mostafa (kamalmostafa) = (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/872652 Title: screensaver backlight stuck off, system looks hung Status in Gnome Settings Daemon: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Oneiric: Fix Released Bug description: After the screensaver fades the screen to black and turns off the backlight, tapping a keyboard key does NOT turn the backlight back on again. The backlight is stuck off making the system appear to be hung. This a regression in Ubuntu 11.10. - (original problem description) - [The original problem description is below, however it has been determined that the problem occurs with the the stock 11.10 release kernel and does not actually relate to acpi_backlight=vendor.] I have been using Kamal Mostafa's kernels for my Dell Studio 15 for a few releases. Now, in oneiric, the brightness can not be changed unless I add acpi_backlight=vendor to the kernel command line. The brightness adjustment works fine when I make this change. However, when I add this command line option, it introduces another issue where when the display goes to sleep, it does not resume. Somtimes I get the screen back by switching to a console tty and then back to the X tty. But, the only reliable way I can get a screen to come back on is to close the laptop lid (so the system suspends) and then open it. The display will turn on for resume. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jrubin 3145 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf0a0 irq 45' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:111d7675,10280413,00100103 HDA:80862804,80860101,0010' Controls : 20 Simple ctrls : 11 Date: Tue Oct 11 22:09:44 2011 HibernationDevice: RESUME=UUID=ffe5b171-a88d-44b8-9f4e-bca222ce60bd InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: Dell Inc. Studio 1558 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to oneiric on 2011-10-03 (8 days ago) dmi.bios.date: 03/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0G939P dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd03/30/2011:svnDellInc.:pnStudio1558:pvrA12:rvnDellInc.:rn0G939P:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Studio 1558 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/872652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1027202] Re: Does not connect (to wired network) after suspend
*** This bug is a duplicate of bug 1184262 *** https://bugs.launchpad.net/bugs/1184262 ** This bug has been marked a duplicate of bug 1184262 [logind] times out too early, stuck in PrepareForSleep, causing network and other services to not resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1027202 Title: Does not connect (to wired network) after suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I work with Xubuntu 12.04 on a MacBook Air 4,1. I can easily connect to the internet (wired network / auto ethernet), but after I put the laptop to sleep/suspend, nm-applet is gray and I can't connect to the internet anymore. Rebooting solves the problem. This seemed to be related up to the fact that it was a wireless connection (which always worked fine for me): https://bugs.launchpad.net/ubuntu/+source /network-manager-applet/+bug/704756 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Fri Jul 20 20:33:05 2012 EcryptfsInUse: Yes InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 178.83.94.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 178.83.94.0/23 dev eth1 proto kernel scope link src 178.83.94.48 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 eth2 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1027202] Re: Does not connect (to wired network) after suspend
Just for some input I have tested the mainline 3.8 kernel under saucy and the problem still occurs. Since I didn't have this problem in raring so maybe it's not kernel bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1027202 Title: Does not connect (to wired network) after suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I work with Xubuntu 12.04 on a MacBook Air 4,1. I can easily connect to the internet (wired network / auto ethernet), but after I put the laptop to sleep/suspend, nm-applet is gray and I can't connect to the internet anymore. Rebooting solves the problem. This seemed to be related up to the fact that it was a wireless connection (which always worked fine for me): https://bugs.launchpad.net/ubuntu/+source /network-manager-applet/+bug/704756 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Fri Jul 20 20:33:05 2012 EcryptfsInUse: Yes InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 178.83.94.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 178.83.94.0/23 dev eth1 proto kernel scope link src 178.83.94.48 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 eth2 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 771857] Re: Realtek 8168B (r8169) interface not working following suspend
I have the same problem once upgraded to 13.10. I have never had this problem before. It's a gigabyte motherboard. lspci | grep -i ethernet 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/771857 Title: Realtek 8168B (r8169) interface not working following suspend Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Invalid Status in “linux” package in Fedora: Unknown Bug description: After suspending and resuming, the network adapter appears to be active (Link UP) however it is not able to properly communicate data and appears in network-manager as disconnected due to the inability to negotiate DHCP successfully. The workaround, in my case, is to execute this fixnet script following the resume to unload an reload the r8169 module. In 11.04 the network manager automatically reconnects at this point. imac@repo:/usr/local/bin$ cat fixnet #!/bin/sh rmmod r8169 modprobe r8169 imac@repo:/usr/local/bin$ lspci -v | grep -i realtek 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Here is a typical dmesg, showing the link up after resume (@5958) followed by my script execution (starting @ 6105). [ 5956.140651] r8169 :0a:00.0: eth0: link down [ 5958.247724] r8169 :0a:00.0: eth0: link up [ 6105.570173] r8169 :0a:00.0: PCI INT A disabled [ 6105.604106] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 6105.604141] r8169 :0a:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 6105.604191] r8169 :0a:00.0: setting latency timer to 64 [ 6105.604248] r8169 :0a:00.0: irq 45 for MSI/MSI-X [ 6105.610321] r8169 :0a:00.0: eth0: RTL8168c/8111c at 0xc90002098000, 00:1e:ec:f2:0f:f3, XID 1c4000c0 IRQ 45 [ 6105.624882] r8169 :0a:00.0: eth0: link down [ 6105.624896] r8169 :0a:00.0: eth0: link down [ 6105.636108] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6108.331777] r8169 :0a:00.0: eth0: link up [ 6108.332388] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 6118.770054] eth0: no IPv6 routers present Upstream we see this here: https://bugzilla.kernel.org/show_bug.cgi?id=12296 This problem also affects Maverick ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imac 2744 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xd240 irq 16' Mixer name : 'IDT 92HD71B7X' Components : 'HDA:111d76b2,103c30fd,00100302 HDA:11c11040,103c137e,00100200' Controls : 22 Simple ctrls : 14 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd231 irq 46' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Apr 27 10:16:01 2011 HibernationDevice: RESUME=UUID=5828f841-5250-4229-bfc5-af24c6f41811 MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: LANGUAGE=en_US:en LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=52543d1c-6080-4cdf-80e0-30b9af3748f7 ro crashkernel=384M-2G:64M,2G-:128M splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: Upgraded to natty on 2011-04-06 (21 days ago) WpaSupplicantLog: dmi.bios.date: 08/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30FD dmi.board.vendor: Compal dmi.board.version: 01.99 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.49:bd08/17/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr1:rvnCompal:rn30FD:rvr01.99:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 1 dmi.sys.vendor:
[Kernel-packages] [Bug 771857] Re: Realtek 8168B (r8169) interface not working following suspend
It appears my problem is related to the network-manager bug other than the kernel. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1027202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/771857 Title: Realtek 8168B (r8169) interface not working following suspend Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Invalid Status in “linux” package in Fedora: Unknown Bug description: After suspending and resuming, the network adapter appears to be active (Link UP) however it is not able to properly communicate data and appears in network-manager as disconnected due to the inability to negotiate DHCP successfully. The workaround, in my case, is to execute this fixnet script following the resume to unload an reload the r8169 module. In 11.04 the network manager automatically reconnects at this point. imac@repo:/usr/local/bin$ cat fixnet #!/bin/sh rmmod r8169 modprobe r8169 imac@repo:/usr/local/bin$ lspci -v | grep -i realtek 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Here is a typical dmesg, showing the link up after resume (@5958) followed by my script execution (starting @ 6105). [ 5956.140651] r8169 :0a:00.0: eth0: link down [ 5958.247724] r8169 :0a:00.0: eth0: link up [ 6105.570173] r8169 :0a:00.0: PCI INT A disabled [ 6105.604106] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 6105.604141] r8169 :0a:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 6105.604191] r8169 :0a:00.0: setting latency timer to 64 [ 6105.604248] r8169 :0a:00.0: irq 45 for MSI/MSI-X [ 6105.610321] r8169 :0a:00.0: eth0: RTL8168c/8111c at 0xc90002098000, 00:1e:ec:f2:0f:f3, XID 1c4000c0 IRQ 45 [ 6105.624882] r8169 :0a:00.0: eth0: link down [ 6105.624896] r8169 :0a:00.0: eth0: link down [ 6105.636108] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6108.331777] r8169 :0a:00.0: eth0: link up [ 6108.332388] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 6118.770054] eth0: no IPv6 routers present Upstream we see this here: https://bugzilla.kernel.org/show_bug.cgi?id=12296 This problem also affects Maverick ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imac 2744 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xd240 irq 16' Mixer name : 'IDT 92HD71B7X' Components : 'HDA:111d76b2,103c30fd,00100302 HDA:11c11040,103c137e,00100200' Controls : 22 Simple ctrls : 14 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd231 irq 46' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Apr 27 10:16:01 2011 HibernationDevice: RESUME=UUID=5828f841-5250-4229-bfc5-af24c6f41811 MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: LANGUAGE=en_US:en LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=52543d1c-6080-4cdf-80e0-30b9af3748f7 ro crashkernel=384M-2G:64M,2G-:128M splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: Upgraded to natty on 2011-04-06 (21 days ago) WpaSupplicantLog: dmi.bios.date: 08/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30FD dmi.board.vendor: Compal dmi.board.version: 01.99 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.49:bd08/17/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr1:rvnCompal:rn30FD:rvr01.99:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
