[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
** Attachment added: "Dmesg output after general protection fault" https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1771075/+attachment/5139125/+files/protection_fault.log ** Package changed: linux-gcp (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] [NEW] General Protection fault in inotify (fixed upstream)
Public bug reported: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug uec-images xenial ** Attachment added: "Dmesg output during soft lockup" https://bugs.launchpad.net/bugs/1771075/+attachment/5139122/+files/soft_lockup.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
I've upload the apport information from a host that had the issue but note that I had to downgrade the kernel back to 4.10 due to this issue, so that's what is included in the apport information. ** 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/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139137/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
apport information ** Tags added: apport-collected ** Description changed: We've run into some issues where upgrading the kernel from a 4.10 series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of inotify causes panics and lockups in the kernel in inotify-related code. Our particular use case seemed to hit these at a rate of one every 30 minutes or so when serving up production traffic. Unfortunately, I have been unable to replicate the issue so far with a simulated load-testing environment. When the issue occurs, we get dmesg entries like "BUG: soft lockup - CPU#0 stuck for 22s!" or "General protection fault: [#1] SMP PTI". In the soft lockup case, the host is still up but all I/O operations stall indefinitely (e.g. typing "sync" into the console will hang forever). In the protection fault case, the system reboots. I've attached dmesg output from the two cases to this bugreport. We have noticed the issue with the following kernels: - linux-image-4.13.0-1013-gcp - linux-image-4.13.0-1015-gcp - linux-image-4.13.0-36-generic We did _not_ have the issue with - linux-image-4.10.0-32-generic I've submitted this bug report from a system which should be configured identically to our production hosts that were having issue (the affected hosts were immediately rolled back to 4.10). This bug appears to have been fixed upstream as of 4.17-rc3 in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5 I would guess that perhaps this patch should be backported into both the 4.13 HWE and GCP Ubuntu kernel series? Thanks, KJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17 ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16 Uname: Linux 4.13.0-1013-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 14 07:58:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 10 07:57 seq + crw-rw 1 root audio 116, 33 May 10 07:57 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Google Google Compute Engine + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y console=ttyS0 + ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-32-generic N/A + linux-backports-modules-4.10.0-32-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images xenial uec-images + Uname: Linux 4.10.0-32-generic x86_64 + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + _MarkForUpload: False + dmi.bios.date: 01/01/2011 + dmi.bios.vendor: Google + dmi.bios.version: Google + dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB + dmi.board.name: Google Compute Engine + dmi.board.vendor: Google + dmi.chassis.type: 1 + dmi.chassis.vendor: Google + dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: + dmi.product.name: Google Compute Engine + dmi.sys.vendor: Google ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139132/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139133/+files/HookError_generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139138/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139135/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139134/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1771075/+attachment/5139136/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Awesome, thanks for getting back to me so quickly! Unfortunately we're in a change freeze at the moment - I'll try and get an exemption approved to test this but I may have to wait until Monday to try it out. Is there anything special I have to do to boot your test kernels on Xenial other than installing the debs with dpkg, set GRUB_DEFAULT to point to it, running update-grub, and rebooting? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Good news - I got the chance to test this in our production environment today for about 7 hours and no issues whatsoever. Given that this workload was triggering the issue pretty reliably within about half an hour before, I think this fix has done the trick. Thanks a bunch for your help! What are the next steps here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Cool! I noticed you've marked the bug as affecting Artful, Bionic and Cosmic but it also affects Xenial with the 4.13 HWE kernels; should that be marked here 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/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Yup, I think this is a dupe of that. I noticed that bug was filed against linux-azure; do I need to file a corresponding bug against linux-gcp to get the patch sent there 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/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771075] Re: General Protection fault in inotify (fixed upstream)
Thanks, much appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771075 Title: General Protection fault in inotify (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327242] [NEW] x86_64-w64-mingw32-pkg-config ignores PKG_CONFIG_PATH
Public bug reported:
The x86_64-w64-mingw32-pkg-config program (i.e. the mingw toolchain's
pkg-config) ignores the PKG_CONFIG_PATH environment variable. This
program is a simple shell script wrapper, and the offending line is as
follows:
PKG_CONFIG_PATH=/usr/lib/${triplet}/pkgconfig:/usr/${triplet}/lib/pkgconfig
pkg-config $@
This of course discards whatever PKG_CONFIG_PATH was set in the
environment. This causes the cross compilation of VLC to fail, because
it expects to be alble to link to libraries it provides by setting
PKG_CONFIG_PATH. The solution is to change the x86_64-w64-mingw32-pkg-
config script to do something like the following
if [ -n "$PKG_CONFIG_PATH" ]; then
EXISTING=":$PKG_CONFIG_PATH"
fi
PKG_CONFIG_PATH=/usr/lib/${triplet}/pkgconfig:/usr/${triplet}/lib/pkgconfig${EXISTING}
pkg-config $@
I'd submit a patch but i'm not entirely sure where and how to do it! If
anyone has a few pointers on this that'd be great.
Environment:
Ubuntu 14.04 LTS
Package: mingw-w64-tools
Package version: 3.1.0-1
** Affects: mingw-w64 (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/1327242
Title:
x86_64-w64-mingw32-pkg-config ignores PKG_CONFIG_PATH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mingw-w64/+bug/1327242/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327242] Re: x86_64-w64-mingw32-pkg-config ignores PKG_CONFIG_PATH
Oh cool :) Is there a better way to get this fix into my Trusty install other than just manually changing the file to use PKG_CONFIG_LIBDIR? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327242 Title: x86_64-w64-mingw32-pkg-config ignores PKG_CONFIG_PATH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mingw-w64/+bug/1327242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414724] Re: wl driver (Broadcom) does not receive ARP packets (broadcasts)
I did a dist-upgrade of server 12.04 today, and am now experiencing exactly this problem. I also have the same driver (wl) using a BCM4313 wireless card. Is this a regression? ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/414724 Title: wl driver (Broadcom) does not receive ARP packets (broadcasts) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111956] [NEW] BCM4313 ignores ARP broadcast packets
Public bug reported: I'm running ubuntu server 12.04 on a netbook with a Broadcom BCM4313 wireless chip. I had the wl.ko driver installed by compiling the bcmwl- kernel-source package, and everything was good in the world. Then, yesterday, I did a dist-upgrade, and the machine now no longer responds to ARP broadcast packets. Consider two machines- the affected netbook A, and my other windows machines B and C. If I try and ping A from B, I get "destination host unreachable". Wireshark on B shows ARP broadcast packets going out, but tcpdump on A does not see these packets. If I then ping B from A, I see an ARP broadcast from A asking "Who has B? Tell A", which B responds to. B then sends a "Who has A? Tell B" message, but directs this specifically to A's MAC address and not the broadcast MAC. A responds to this message, and the pings succeed. Because B's ARP table has been filled in this process, pings from B to A now work too- but pings from C to A still fail. The inability to do inbound connections seems like a pretty big showstopper for a server! This is possibly related to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414724 ** Affects: bcmwl (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/956 Title: BCM4313 ignores ARP broadcast packets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111956] Re: BCM4313 ignores ARP broadcast packets
I tried to run apport-collect but the machine doesn't have a GUI, and the OAuth process fails in links. Let me know what other information is needed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956 Title: BCM4313 ignores ARP broadcast packets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1107109] Re: the last upgrade broke WiFi
I'm running 12.04 too, with kernel Linux 3.2.0-37 and the same version of bcmwl. I was having issues with ARP multicast- possibly related. See my bugreport here: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/956 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1107109 Title: the last upgrade broke WiFi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1107109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] [NEW] Transaction ID collisions cause slow DNS lookups in getaddrinfo
Public bug reported: When resolving DNS names with getaddrinfo(), I have seen this hang for 5 seconds and then retry and succeed. The issue is that glibc will issue a both an A and query on the same socket, and in some circumstances they can be sent with the same DNS transaction ID as well. I verified this with a packet capture; in the packet capture, I saw the A and queries for a name be made with the same DNS transaction ID, get responses, do nothing for five seconds, and then send the same DNS query again. On the glibc side, I confirmed that it's blocked waiting for the DNS response by interrupting it with gdb, even though the packet capture shows the response has well and truly arrived. I've attached a packet capture & a backtrace of the glibc hang. I believe this is the same issue reported in these places: * In RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1904153 * Also RHEL: https://bugzilla.redhat.com/show_bug.cgi?id=1903880 * Upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=26600 The environment I noticed this bug in was: * Docker for Mac on an arm64 m1 Macbook * Docker for Mac Linux kernel version is 5.10.76-linuxkit * Linux is also arm64, not emulated * Container with the buggy DNS environment is Ubuntu bionic (also arm64, not emulated) * Glibc 2.27-3ubuntu1.4 However one of the redhat reporters noticed this issue in m6 series EC2 instances in AWS. A patch has been provided upstream for this issue: https://sourceware.org/pipermail/libc-alpha/2020-September/117547.html I applied the upstream patch to glibc 2.27-3ubuntu1.4 and rebuilt the package, and the problem went away. I've attached the exact patch I applied, since I had to work through some conflicts. So, I think that patch just needs to be backported to Bionic and (I think) Focal as well. Is that reasonable? Thanks! ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Patch added: "upstream patch with conflicts resolved for 2.27" https://bugs.launchpad.net/bugs/1961697/+attachment/5562611/+files/resolv-txnid-collision.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
** Attachment added: "Packet capture showing DNS queries with same txnid" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+attachment/5562612/+files/dns_same_txid.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
** Attachment added: "glibc backtrace from hang" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+attachment/5562613/+files/glibc_backtrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
Just wondering if there's a plan or desire to (correct me if I use the wrong terminology here..) SRU this into bionic/focal? The criteria for SRU, from what I read, seem to be related to "critical bugs" (of which maybe this is not), "regressions" (which this isn't), and "hardware enablement" (which I think does apply here - this bug seems to be triggered much more often on new hardware like M1 macbooks and m6 EC2 instances) Let me know if I can help with this at all by providing a merge proposal (although I don't think there's much more to it than applying the attached patch & writing up the changelog?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961697] Re: Transaction ID collisions cause slow DNS lookups in getaddrinfo
It's definitely non-deterministic, unfortunately. I do have a reliable reproduction for Bionic and Focal I can trigger on my laptop, but it's a huge pile of proprietary Ruby code that just happens to hit all the right timings on my machine. I can validate a -proposed package if you need though. The reproduction instructions basically boil down to "Have IPv6, call getaddrinfo(), and if you're unlucky, it will take > 5 seconds and make 4 DNS queries instead of two". There is also a test case provided in the upstream glibc patch that could also be applied. https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/tst-resolv- txnid- collision.c;h=611d37362f3e5e89b92766f0790459340cc071b3;hb=2dfa659a66f20facc4082207884c20e986ddecee -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961697 Title: Transaction ID collisions cause slow DNS lookups in getaddrinfo To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1961697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
