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
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
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.
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
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:
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
** 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
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
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
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
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.
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:
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.
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:
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.
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
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
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.
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.
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:
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
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.
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.
** 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.
** 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.
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"
26 matches
Mail list logo
