[Bug 1859649] Re: networking disruption on upgrade from 14.0.0 to 14.0.3
Subscribing field medium to represent the issue this now causes with landscape per-AZ upgrades -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859649 Title: networking disruption on upgrade from 14.0.0 to 14.0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1859649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849126] [NEW] Thunderbolt dock dropping offline
Public bug reported: I've filed with ubuntu-bug so additional logging should be available. Starting with 19.10 there has been a regression in my CalDigit thunderbolt 3 dock. With Bionic and Disco the dock has been stable across two laptops. After upgrading to Eaon and running 5.3.0-18-generic I'm getting periodic (every few minutes) resets of the dock. This presents as a loss of ethernet, microphone, audio, and video all of which are provided by the dock. Dmesg during the event: https://pastebin.canonical.com/p/VyrT4PDXW7/ I haven't changed the firmware on my bios or dock just the eaon upgrade. If there's more data I can provide please let me know. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: i3 Date: Mon Oct 21 09:05:02 2019 InstallationDate: Installed on 2019-09-13 (38 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QDCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=UUID=f6e80d0e-f384-4ffc-8212-9346884a3fff ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-18 (3 days ago) dmi.bios.date: 08/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET35W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET35W(1.18):bd08/20/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849126 Title: Thunderbolt dock dropping offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
** Changed in: charm-neutron-openvswitch Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782922] Re: LDAP: changing user_id_attribute bricks group mapping
Subscribing field-high which wasn't carried over from the other duplicate bug https://bugs.launchpad.net/keystone/+bug/1832766 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782922 Title: LDAP: changing user_id_attribute bricks group mapping To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1782922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
requested logging during the month of the error ** Attachment added: "unattended-upgrades.log.1" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261355/+files/unattended-upgrades.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
dpk logging from the same time period ** Attachment added: "unattended-upgrades-dpkg.log.1" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261356/+files/unattended-upgrades-dpkg.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
@rbalint I've included the logs but I don't see any Traces as mentioned in LP: #1824341 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
I've reinstalled with: sudo apt install maas -o debug::pkgproblemresolver=true 2>&1 | tee install.log As the attached log shows there were no errors, clean install. After following the restore and restarting the services juju returned the following error: ERROR opening environment: unexpected: ServerError: 409 Conflict (http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> Error: Conflict Error Conflict error. Try your request again, as it will most likely succeed. ) Restarting the machine has restored normal operation. ** Attachment added: "install.log" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260208/+files/install.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
That's all relevant logs I could think of, when I am able to do a reinstall I'll include the above recommended debug option as well. If there's something I didn't think of let me know and I'll provide that as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
attached apt history.log ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260156/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
Attached dpkg.log ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260154/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
attached apt term.log ** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260155/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826916 Title: MAAS uninstalls itself on unattended upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826916] [NEW] MAAS uninstalls itself on unattended upgrade
Public bug reported: Having recently found my MAAS unresponsive I was surprised to find out it's because it uninstalled itself. First, how on earth does this happen, and second how do I go about recovering this I have several critical juju services deployed on a nodes that this MAAS runs and juju is unusable with MAAS down. I've just done the backup as per https://docs.maas.io/2.5/en/manage- backup do I just do a fresh install now and do the restore steps? Will this simply get removed on the next upgrade? Start-Date: 2019-04-24 06:02:09 Commandline: /usr/bin/unattended-upgrade Remove: libjs-yui3-full:amd64 (3.5.1-1ubuntu3), python3-pexpect:amd64 (4.0.1-1), python3-distro-info:amd64 (0.14build1), libwebp5:amd64 (0.4.4-1), python3-roman:amd64 (2.0.0-2), python3-html5lib:amd64 (0.999-4), squid-langpack:amd64 (20150704-1), python3-ecdsa:amd64 (0.13-2), python3-dnspython:amd64 (1.12.0-0ubuntu3), python3-mimeparse:amd64 (0.1.4-1build1), libirs-export141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), fonts-font-awesome:amd64 (4.5.0~dfsg-1), python3-zope.interface:amd64 (4.1.3-1build1), python3-djorm-ext-pgarray:amd64 (1.2-0ubuntu2), javascript-common:amd64 (11), python3-formencode:amd64 (1.3.0-0ubuntu5), dbconfig-pgsql:amd64 (2.0.4ubuntu1), os-prober:amd64 (1.70ubuntu3.3), python3-seamicroclient:amd64 (0.4.0-1ubuntu1), python3-babel:amd64 (1.3+dfsg.1-6), docutils-common:amd64 (0.12+dfsg-1), python3-maas-provisioningserver:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libibverbs1:amd64 (1.1.8-1.1ubuntu2), python3-sphinx:amd64 (1.3.6-2ubuntu1.1), libfreeipmi16:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1:amd64 (1.5.4-1build1), libipmidetect0:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-netaddr:amd64 (0.7.18-1), grub-common:amd64 (2.02~beta2-36ubuntu3.17), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), squid-common:amd64 (3.5.12-1ubuntu7.5), authbind:amd64 (2.1.1+nmu1), freeipmi-common:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-pam:amd64 (0.4.2-13.2ubuntu2), python3-pbr:amd64 (1.8.0-4ubuntu1), python3-pil:amd64 (3.1.2-0ubuntu1.1), python3-simplestreams:amd64 (0.1.0~bzr426-0ubuntu1.2), libaprutil1-dbd-sqlite3:amd64 (1.5.4-1build1), python3-netifaces:amd64 (0.10.4-0.1build2), python3-django-maas:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libjs-jquery:amd64 (1.11.3+dfsg-4), libjs-underscore:amd64 (1.7.0~dfsg-1ubuntu1), libjs-yui3-min:amd64 (3.5.1-1ubuntu3), python3-curtin:amd64 (17.1-11-ga4c9636b-0ubuntu1~16.04.1), python-django-common:amd64 (1.8.7-1ubuntu5.8), python3-service-identity:amd64 (16.0.0-2), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), librdmacm1:amd64 (1.0.21-1), libconfig-general-perl:amd64 (2.60-1), python3-jsonschema:amd64 (2.5.1-4), maas-common:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-txtftp:amd64 (0.1~bzr42-0ubuntu2), apache2-data:amd64 (2.4.18-2ubuntu3.10), python3-crochet:amd64 (1.4.0-0ubuntu2), python3-httplib2:amd64 (0.9.1+dfsg-1), python3-iso8601:amd64 (0.1.11-1), pxelinux:amd64 (3:6.03+dfsg-11ubuntu1), python3-sphinx-rtd-theme:amd64 (0.1.9-1), python3-pyparsing:amd64 (2.0.3+dfsg1-1ubuntu0.1), libpaper1:amd64 (1.1.24+nmu4ubuntu1), libjs-yui3-common:amd64 (3.5.1-1ubuntu3), python3-twisted:amd64 (16.0.0-1ubuntu0.2), python3-simplejson:amd64 (3.8.1-1ubuntu2), ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5.9), libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.2), libapr1:amd64 (1.5.2-3), maas-rack-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libipmiconsole2:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1-ldap:amd64 (1.5.4-1build1), maas-cli:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), distro-info:amd64 (0.14build1), maas-dns:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libisccfg-export140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), python3-pyvmomi:amd64 (5.5.0-2014.1.1-3), sphinx-rtd-theme-common:amd64 (0.1.9-1), python3-petname:amd64 (2.0-0ubuntu1~16.04), python3-alabaster:amd64 (0.7.7-1), python3-maas-client:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), tgt:amd64 (1:1.0.63-1ubuntu1.1), python3-docutils:amd64 (0.12+dfsg-1), postgresql:amd64 (9.5+173ubuntu0.1), python3-tempita:amd64 (0.5.2-1build1), python3-bson-ext:amd64 (3.2-1build1), python3-convoy:amd64 (0.2.1+bzr39-1), maas-region-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libpaper-utils:amd64 (1.1.24+nmu4ubuntu1), ieee-data:amd64 (20150531.1), maas-dhcp:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-django-piston3:amd64 (0.3~rc2-3ubuntu1), liblua5.1-0:amd64 (5.1.5-8ubuntu1), python-babel-localedata:amd64 (1.3+dfsg.1-6), python3-bson:amd64 (3.2-1build1), dbconfig-common:amd64 (2.0.4ubuntu1), libwebpmux1:amd64 (0.4.4-1), python3-django:amd64 (1.8.7-1ubuntu5.8), formencode-i18n:amd64 (1.3.0-0ubuntu5), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), maas-region-api:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-psycopg2:amd64 (2.6.1-1build2), fonts-lato:amd64 (2.0-1), squid:amd64 (3.5.12-1ubuntu7.5), python3-paramiko:amd64 (1.16.0-1ubuntu0.2), python3-tz:amd64 (
[Bug 1787245] [NEW] Auto-hosts do not include fqdn
Public bug reported: The --H, --auto-hosts option does not currently include fqdn and in fact removes the fqdn entries. This is blocking the use of sshuttle for things like accessing a Graylog server which links back to itself via fqdn. This has been fixed with pull request #173 [0] in Oct of 2017 adds this functionality and works for the Graylog forwarding which I've been trying to use it for. [0]: https://github.com/sshuttle/sshuttle/pull/173 ** Affects: sshuttle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787245 Title: Auto-hosts do not include fqdn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1787245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749425] Re: Neutron integrated with OpenVSwitch drops packets and fails to plug/unplug interfaces from OVS on router interfaces at scale
I've subscribed Canonical Field Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749425 Title: Neutron integrated with OpenVSwitch drops packets and fails to plug/unplug interfaces from OVS on router interfaces at scale To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1749425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
The machine I was using has been redeployed without LVM. If I get a chance to redeploy I'll grab the requested logs. It's fairly trivial to trigger if you have a machine available to deploy with lvm boot as described above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1573982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
** Package changed: maas (Ubuntu) => maas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1573982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
I've run across this today and it affects MAAS. MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) Configuring an LVM based drive with a raid on top of it for the root partition will trigger this. Deploying the default kernel / OS will fail due to inactive volume groups. The fix as expected: lvm vgchange -ay mdadm --assemble --scan exit Then apply the above mentioned script to make it stick. ** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
** Also affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-meta-hwe (Ubuntu) ** No longer affects: linux-meta-hwe (Ubuntu Yakkety) ** No longer affects: linux-meta-hwe (Ubuntu Zesty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Great, this should fix it for you then. I ran between 40 min and 3 hours between crashes. I've been running daily (this is my daily use laptop for work) and after the above fix it's completely stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Javi, see comment 25 above I'm booting with a work around on the 9550 with PM951. However, also note that this bug shouldn't crash "on boot". I had a seperate issue with the 9550 with tlp and external usb devices causing an on boot crash which is not related to this. I recommend you run w/o any external devices to see if your boot problem is this, and add the above work around to keep you from crashing randomly when this bug triggers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Nils, from above use 'nvme-core.nvme_core.default_ps_max_latency_us=0' to turn APST off. That as my first step to confirm this is indeed related to APST and the same bug. If that doesn't do it, I'm afraid you might have another issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I can now confirm that I've had a stable machine for more than 7 hours using 6k for latency. I think the longest I had with out the option was ~3 hours and generally it was ~45 minutes to crash. Nils, I'm setting the parameter in /etc/default/grub by appending it to the "GRUB_CMDLINE_LINUX_DEFAULT" options then running `update-grub`. That has worked for me, although I'm not sure how to confirm it took. That is a permanent method, I started by just adding the 250 during boot so it was for a single boot while testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I have an xps15 9550 same as above, same controller, same issue. I set nvme_core.default_ps_max_latency_us=6000 this morning and have ~1 hour right now with no crash. I'll continue to run it today and report back. The only issue I have seen with the 6k setting which I didn't not see with a setting of 250 was a black screen on boot with an external display connected. I can't imagine how that's affected by this setting. I was able to boot by turning off the display until the laptop was booted and then turning it on which seems to be working. This reliably repeats with the 6k kernel setting with no problem on the 250 setting, at least on the 3-4 reboots I've done in the last two days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel
I've just noticed this has resolved for me. See below, the errors do not repeat and I connect to the network. However, I have recently updated my router firmware to my knowledge it's still configured like it was (40/80 Mhz channels). I'm running the same nvidia-375 that was causing errors before. Description:Ubuntu 16.10 Release:16.10 4.8.0-46-generic dmesg | grep brcm [6.101044] usbcore: registered new interface driver brcmfmac [6.101082] brcmfmac :02:00.0: enabling device ( -> 0002) [6.245598] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [6.754207] brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c [6.786602] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [6.794712] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 [ 520.395510] brcmf_inetaddr_changed: fail to get arp ip table err:-23 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630324 Title: Broadcom wifi dies in 60s cycles with 4.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel
This appears to be a conflict with the Nvidia driver (at least for me). I've tried: nvidia-378 (open source) nvidia-370 (open source) nvidia-375 (proprietary) All three give the exact same results as above on both 2.4 and 5 Ghz. Switching to the intel graphics driver completely clears this up. It's not a great work around for me as the Intel in the XPS-15 (9550) chokes on an external 4k display with chrome. But it's functional when I need to switch to wifi (which I'm generally not connected to an external display with) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630324 Title: Broadcom wifi dies in 60s cycles with 4.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630324] Re: Broadcom wifi dies in 60s cycles with 4.8 kernel
XPS-15 (9550), Yakkety, 4.8.0-41-generic, 40Mhz channels also unable to connect to Wifi any longer. Happy to provide testing or any additional information. dmesg | grep brcm [5.481593] usbcore: registered new interface driver brcmfmac [5.481639] brcmfmac :02:00.0: enabling device ( -> 0002) [5.599437] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [6.112535] brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c [6.167629] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [6.177287] brcmfmac :02:00.0 wlp2s0: renamed from wlan0 [ 34.475342] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 38.568678] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 43.673001] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 242.690117] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 246.670201] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 248.314205] brcmf_cfg80211_escan: Connecting: status (3) [ 248.314223] brcmf_cfg80211_scan: scan error (-11) [ 251.619740] brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 251.675201] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 292.410333] brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 344.298222] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 396.312220] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 448.332129] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 482.471888] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 523.156863] brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 523.502468] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 527.549349] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 531.589616] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630324 Title: Broadcom wifi dies in 60s cycles with 4.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
