[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
+1 I have encountered the same bug (NMI watchdog: BUG: soft lockup - CPU#10 stuck for 23s!). Logs could be found in the attachment. ** Attachment added: "SecondHang.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4880124/+files/SecondHang.log -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31
[Kernel-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones
** Description changed: I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt). (If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.) Here is how I try to pair: $ bluetoothctl [NEW] Controller 54:27:1E:33:4B:85 impedance [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes [bluetooth]# scan on I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. - For example, my smartphone pairs with the headset in 5-15 seconds, my - laptop pairs with the headset in about 30 seconds. + For example, my smartphone pairs with the headset within 5-15 seconds, + my laptop pairs with the headset within about 30 seconds. = Here is info $ hciconfig -a hci0: Type: Primary Bus: USB - BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 - UP RUNNING PSCAN ISCAN - RX bytes:4475 acl:0 sco:0 events:565 errors:0 - TX bytes:7214 acl:0 sco:0 commands:487 errors:0 - Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 - Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 - Link policy: RSWITCH SNIFF - Link mode: SLAVE ACCEPT - Name: 'impedance' - Class: 0x1c0104 - Service Classes: Rendering, Capturing, Object Transfer - Device Class: Computer, Desktop workstation - HCI Version: 4.0 (0x6) Revision: 0x1000 - LMP Version: 4.0 (0x6) Subversion: 0x220e - Manufacturer: Broadcom Corporation (15) + BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 + UP RUNNING PSCAN ISCAN + RX bytes:4475 acl:0 sco:0 events:565 errors:0 + TX bytes:7214 acl:0 sco:0 commands:487 errors:0 + Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 + Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 + Link policy: RSWITCH SNIFF + Link mode: SLAVE ACCEPT + Name: 'impedance' + Class: 0x1c0104 + Service Classes: Rendering, Capturing, Object Transfer + Device Class: Computer, Desktop workstation + HCI Version: 4.0 (0x6) Revision: 0x1000 + LMP Version: 4.0 (0x6) Subversion: 0x220e + Manufacturer: Broadcom Corporation (15) = rfkill list 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no = Bluez packages installed: $ dpkg -l | grep bluez ii bluez ii bluez-btsco ii bluez-cups ii bluez-hcidump ii bluez-obexd ii bluez-tools ii libkf5bluezqt-data ii libkf5bluezqt6:amd64 ii qml-module-org-kde-bluezqt:amd64 = $ dmesg | grep -i blue [4.632406] Bluetooth: Core ver 2.21 [4.632414] Bluetooth: HCI device and connection manager initialized [4.632416] Bluetooth: HCI socket layer initialized [4.632417] Bluetooth: L2CAP socket layer initialized [4.632420] Bluetooth: SCO socket layer initialized [4.644619] Bluetooth: hci0: BCM: chip id 63 [4.660554] Bluetooth: hci0: impedance [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build [4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.061604] Bluetooth: BNEP filters: protocol multicast [ 15.061606] Bluetooth: BNEP socket layer initialized [ 48.001553] Bluetooth: RFCOMM TTY layer initialized [ 48.001558] Bluetooth: RFCOMM socket layer initialized [ 48.001562] Bluetooth: RFCOMM ver 1.11 [ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper
[Kernel-packages] [Bug 1654782] [NEW] Can not pair with bluetooth headphones
Public bug reported: I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt). (If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.) Here is how I try to pair: $ bluetoothctl [NEW] Controller 54:27:1E:33:4B:85 impedance [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes [bluetooth]# scan on I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. For example, my smartphone pairs with the headset in 5-15 seconds, my laptop pairs with the headset in about 30 seconds. = Here is info $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:4475 acl:0 sco:0 events:565 errors:0 TX bytes:7214 acl:0 sco:0 commands:487 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) = rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no = Bluez packages installed: $ dpkg -l | grep bluez ii bluez ii bluez-btsco ii bluez-cups ii bluez-hcidump ii bluez-obexd ii bluez-tools ii libkf5bluezqt-data ii libkf5bluezqt6:amd64 ii qml-module-org-kde-bluezqt:amd64 = $ dmesg | grep -i blue [4.632406] Bluetooth: Core ver 2.21 [4.632414] Bluetooth: HCI device and connection manager initialized [4.632416] Bluetooth: HCI socket layer initialized [4.632417] Bluetooth: L2CAP socket layer initialized [4.632420] Bluetooth: SCO socket layer initialized [4.644619] Bluetooth: hci0: BCM: chip id 63 [4.660554] Bluetooth: hci0: impedance [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build [4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.061604] Bluetooth: BNEP filters: protocol multicast [ 15.061606] Bluetooth: BNEP socket layer initialized [ 48.001553] Bluetooth: RFCOMM TTY layer initialized [ 48.001558] Bluetooth: RFCOMM socket layer initialized [ 48.001562] Bluetooth: RFCOMM ver 1.11 [ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jan 7 22:36:22 2017 InstallationDate: Installed on 2014-07-05 (917 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-10-09 (89 days ago) dmi.bios.date: 01/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be
[Kernel-packages] [Bug 1374595] [NEW] Emask 0x3 (HSM violation)
Public bug reported: I do not know how to reopen this bug https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/445852 so I decided to create new bug. After recent update of Kubuntu 14.10 (beta), and following reboot, I got these messages in dmesg [1.534737] ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [1.534758] ata14.00: irq_stat 0x4001 [1.534771] scsi 13:0:0:0: CDB: [1.534772] Inquiry: 12 01 00 00 ff 00 [1.534776] ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 3 dma 16640 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) [1.534816] ata14: hard resetting link Full dmesg: http://paste.ubuntu.com/8434914/ ** Affects: libatasmart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libatasmart in Ubuntu. https://bugs.launchpad.net/bugs/1374595 Title: Emask 0x3 (HSM violation) Status in “libatasmart” package in Ubuntu: New Bug description: I do not know how to reopen this bug https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/445852 so I decided to create new bug. After recent update of Kubuntu 14.10 (beta), and following reboot, I got these messages in dmesg [1.534737] ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [1.534758] ata14.00: irq_stat 0x4001 [1.534771] scsi 13:0:0:0: CDB: [1.534772] Inquiry: 12 01 00 00 ff 00 [1.534776] ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 3 dma 16640 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) [1.534816] ata14: hard resetting link Full dmesg: http://paste.ubuntu.com/8434914/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1374595/+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 1296887] Re: Boot-time vlan network setup fails
Thank you very much. Of course, it is very interesting why (and by what system update) it was removed, or how it was working before (in case if vlan package was not installed at all). But, after installing all start working! Thanks! ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- 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/1296887 Title: Boot-time vlan network setup fails Status in “linux” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Invalid Bug description: It seems that vlan network setup fails at boot-time (but all works well after boot). This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 iface eth0.10 inet dhcp auto eth0.20 iface eth0.20 inet manual auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dimanne2784 F pulseaudio /dev/snd/controlC0: dimanne2784 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 24 22:29:13 2014 HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596 InstallationDate: Installed on 2013-11-11 (133 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago) dmi.bios.date: 12/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+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 1296887] Re: Boot-time vlan network setup fails
Ping But still here -- 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/1296887 Title: Boot-time vlan network setup fails Status in “linux” package in Ubuntu: Confirmed Bug description: It seems that vlan network setup fails at boot-time (but all works well after boot). This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 iface eth0.10 inet dhcp auto eth0.20 iface eth0.20 inet manual auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dimanne2784 F pulseaudio /dev/snd/controlC0: dimanne2784 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 24 22:29:13 2014 HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596 InstallationDate: Installed on 2013-11-11 (133 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago) dmi.bios.date: 12/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+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 1296887] Re: Boot-time vlan network setup fails
I tried (already installed) 3.11.0-17-generic kernel (I thought it is not so important to test exactly the kernel version you pointed out), and issue also did NOT go away. It is still here. So it really seems that it is not kernel bug. But it is apparently 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/1296887 Title: Boot-time vlan network setup fails Status in “linux” package in Ubuntu: Confirmed Bug description: It seems that vlan network setup fails at boot-time (but all works well after boot). This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 iface eth0.10 inet dhcp auto eth0.20 iface eth0.20 inet manual auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dimanne2784 F pulseaudio /dev/snd/controlC0: dimanne2784 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 24 22:29:13 2014 HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596 InstallationDate: Installed on 2013-11-11 (133 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago) dmi.bios.date: 12/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+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 1296887] Re: Boot-time vlan network setup fails
I tried first available 3.13.* kernel (in my case it was 3.13.0-11-generic) and issue did NOT go away. Network configuration does not work. -- 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/1296887 Title: Boot-time vlan network setup fails Status in “linux” package in Ubuntu: Confirmed Bug description: It seems that vlan network setup fails at boot-time (but all works well after boot). This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 iface eth0.10 inet dhcp auto eth0.20 iface eth0.20 inet manual auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dimanne2784 F pulseaudio /dev/snd/controlC0: dimanne2784 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 24 22:29:13 2014 HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596 InstallationDate: Installed on 2013-11-11 (133 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago) dmi.bios.date: 12/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+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 1296887] [NEW] Boot-time vlan network setup fails
Public bug reported: It seems that vlan network setup fails at boot-time (but all works well after boot). This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 iface eth0.10 inet dhcp auto eth0.20 iface eth0.20 inet manual auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dimanne2784 F pulseaudio /dev/snd/controlC0: dimanne2784 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 24 22:29:13 2014 HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596 InstallationDate: Installed on 2013-11-11 (133 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago) dmi.bios.date: 12/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - vlan network set up fails on boot + Boot-time vlan network setup fails ** Description changed: + It seems that vlan network setup fails at boot-time (but all works well + after boot). + This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 - iface eth0.10 inet dhcp + iface eth0.10 inet dhcp auto eth0.20 - iface eth0.20 inet manual + iface eth0.20 inet manual auto dsl-provider - iface dsl-provider inet ppp - pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf + iface dsl-provider inet ppp + pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider - - During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. + During boot I see Waiting for network configuration..., after boot in + ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: dimanne2784 F pulseaudio - /dev/snd/controlC0: dimanne2784 F pulseaudio + USER
