I'm coming back to this topic just to add what worked for me.
I had to disable Wayland in order to get audio up and running through
HDMI again, following the instructions at
https://linuxconfig.org/how-to-enable-disable-wayland-on-
ubuntu-22-04-desktop
I'm not sure why this helped, but at the mo
@koba - I am not sure how to downgrade. I know that the kernel you are
asking about is not in my /boot folder so I could not load it from the
grub menu, however, I'm not sure where to get it from.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
@koba
Sorry, I did not try with that version. Based on comments above, I
switched the config of software updater to use pre-released updates and
ended up with
5.19.0-42-generic #43~22.04.1-Ubuntu
This gave me the option to select HDMI audio in my sound settings again
(it was previously missing).
Bit of an odd one here in that I can now select HDMI output again, but
not actually getting anything coming through.
This was working a long time ago before this issue, was broken by the
kernel bug, and now still doesn't work despite the HDMI option being
available again.
Any tips or advice?
--
Public bug reported:
Affects linux kernels 5.13+ (21.10 uses 5.13).
See: https://github.com/openzfs/zfs/issues/12712
Patch to backport into linux-modules that should fix issue:
https://github.com/openzfs/zfs/pull/12759
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-modules-5.13.0-2
> I'll file a ticket with IS for their input...
Canonical staff can see this at rt #130839
--
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/1926955
Title:
[VMs on] arm64 eMAG system often
pgrading the virt stack alone *may* be possible, we
can check that (the cloud archive doesn't contain edk2 though). It's
also running Launchpad buildds though. I would expect reluctance to do
this from their side due to the risks and, annoying as it is, think we
should plan on identifying
I've just noticed a few failing with "Synchronous Exception at
0x984FA4A8" instead of the IRQ Exception seen earlier.
--
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/1926955
Title:
FTR, I just checked with Canonical IS and the affected host systems are
running Xenial.
(We also have some different hardware which is running the same versions
too and doesn't suffer from this bug, so I do suspect it is somehow hw
specific.)
--
You received this bug notification because you are
** Summary changed:
- arm64 eMAG system often failng to reboot with "IRQ Exception at
0x9BC11F38"
+ [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at
0x9BC11F38"
--
You received this bug notification because you are a member of Kernel
Packages, which is
I captured the console log when the bug happens, was hoping there would
be something interesting just before the exception starts spamming the
console, but sadly not.
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 17.856242] reboot: Restarting system
IRQ Exception at 0xBBC
** Description changed:
We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.
Guests (currently impish VMs on OpenStack) which we spawn often fail to
reboot, repeating this over and over:
- IRQ Exception at 0x
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494399/+files/UdevDb.txt
--
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/1926955
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494400/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494398/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494397/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494396/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494395/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494394/+files/Lspci.txt
--
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/1926955
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1926955/+attachment/5494393/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected ec2-images impish
** Description changed:
We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.
Guests (currently impish VMs on OpenStack) which we spawn often fail to
r
Public bug reported:
We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.
Guests (currently impish VMs on OpenStack) which we spawn often fail to
reboot, repeating this over and over:
IRQ Exception at 0x9BC11F38
(stand
** Tags removed: block-proposed block-proposed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv pack
Would have preferred this to come much earlier, but sounds like
something we need to do ...
Please make sure to keep an eye out for bugs.
I'll accept, thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Tags removed: rls-ff-incoming
--
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/1873052
Title:
Showing two cursors after login
Status in gnome-shell package in Ubuntu:
Confirmed
Statu
Are you saying that the live session worked and then the installed
system did not?
If that's right, we need the contents of /var/log/installer, please, to
see what the installer did.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
laney@dev> ./change-override -S -c main -s hirsute libbpf
Override component to main
libbpf 0.3-2 in hirsute: universe/misc -> main
libbpf-dev 1:0.3-2 in hirsute amd64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute arm64: universe/libdevel/optional/100% -> main
libbpf-dev 1:
The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent situati
ah I see, OK - I will upload, thanks!
can you update the test case to say that this version of alsa-utils is
needed please? maybe provide a PPA link for people to install it with,
until that is accepted into focal?
** Changed in: alsa-lib (Ubuntu Focal)
Status: Incomplete => Fix Committed
I don't see the same problem on the Focal ISO - do we need to fix this
in Focal?
** Changed in: alsa-lib (Ubuntu Focal)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://b
Removing 455 from groovy to groovy-proposed to fix (2).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh groovy
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh
New shim-signed is now on the latest images (20201021).
I'm still not clear what happened when enabling Broadcom from the
installer since it all looks fine to me. Perhaps you could try and let
us know what doesn't work with detailed steps to reproduce? (but
hopefully it does work)
--
You receive
I think the second part (apt install not showing the prompt on next
boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8.
But I'm not quite sure about your initial part where the installer
didn't do the same. I can make that happen if I tick to install
proprietary drivers and th
Yeah, fossfreedom, can you tell us what you ticked on the 'install third
party drivers' page?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - d
w
** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu Focal)
Status: New => In Progress
** Changed in: gdm3 (Ubuntu Focal)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: gnome-session (Ubu
there's an updated kernel in that bug, jibel can you test it please to
confirm if this is a dupe or not?
** Tags removed: rls-gg-incoming
--
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/188
please re-add the tag if it's not
--
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/1881699
Title:
No analog output
Status in linux package in Ubuntu:
Confirmed
Status in pulseaudio pack
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-440 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Groovy)
Importance: Undecided
** Also affects: gnome-control-center (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affe
Public bug reported:
We are in the process of switching ubuntu-drivers to installing linux-
restricted-modules versions of NVidia drivers when it can, but this
fails when Ubiquity invokes ubuntu-drivers, like:
Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
/var/lib/dpkg/i
I don't think there's anything to fix in udisks2 here, since it's just
using the filesystems that are available; invalidating the task.
Perhaps you're arguing for exfat-fuse to be removed from the archive?
See comment #3.
** Changed in: udisks2 (Ubuntu)
Status: Incomplete => Invalid
--
Y
ee why you would. I think we just need the dependency. Thanks for
handling this!
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
awesome, thanks for following up!
--
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/1852122
Title:
ocfs2-tools is causing kernel panics in Ubuntu Focal
(Ubuntu-5.4.0-9.12)
Status in OCFS
Actually, I'm not certain it is a duplicate of that one - this bug I
think is a regression in eoan due to some change in the kernel between
disco and eoan. Perhaps they are related though.
When I'm back from travelling I'll try to do a little bit of
investigation (but I don't know anything about t
blem as if you revert to kernel
5.0 it goes away. So I'll reassign this bug to linux - maybe we can find
out when it was introduced if the kernel team can help us to bisect.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer
** No longer affects: ubuntu
--
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/1833916
Title:
USB-C to HDMI converter is not working with thunderbolt port
Status in linux package in Ubuntu
I was getting random freezes on a Dell Latitude E7450 with Intel HD
Graphics 5500, with no hints as to the cause in logs that I could find.
Freezes could happen multiple times a day when in heavy use, but often
more like once a week. I followed the advice in #42 a month ago and have
had no freezes
** Tags removed: rls-bb-incoming
--
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/1817738
Title:
Can't change virtual terminal when auto-login is enabled
Status in gdm3 package in Ubuntu:
** Also affects: gnome-control-center (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: upower (U
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1714178
Title:
Triple 4K monitor display failed
** Changed in: mesa (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1770271
Title:
VegaM support
Status in amd:
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification b
I've been following this for a while. 16.04 isn't going to get the 4.15
kernel until August (https://wiki.ubuntu.com/Kernel/Support) but 18.04
is going to ship with it
(https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes) and that gets a
stable release on 26 April.
I think everyone has the option of
** Tags added: kernel-fixed-upstream
--
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/1666260
Title:
"Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
Status in linux package in
Servers are now running on 4.10 kernels, so I guess no one cares about
4.8 anymore.
--
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/1666260
Title:
"Out of memory" errors after upgrade to
As original poster, if I didn't continue to post oom dumps, perhaps
things started to peter out on 4.8.0-39 or later.
What was particular about the load that triggered this bug was heavy IO
putting cache pressure on ext4 on a system where there's zero locality
of reference in anything read from or
Thanks.
By the way, also confirming that the patch works here (have been running
the patched kernel for 3 days now). Running on hardware Super Micro
X9SCL with an Intel 82574L NIC.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi, will these patches also land in the HWE kernel?
--
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/1730550
Title:
e1000e in 4.4.0-97-generic breaks 82574L under heavy load.
Status in li
Just a heads up - this apparently became much harder for me to reproduce
at will. We're still seeing it in actual workloads but I'm having
trouble recreating manually.
My current strategy is to start stress-ng on a number of machines and
then constantly reboot them, with the idea that this will st
OK a few days ago apw pointed me at http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13.8/ which is the mainline kernel that the artful-
proposed one I identified as bad is based on.
I ran 35 instances and rebooted them 30 times - all successful. So I
think that says this kernel is good.
Will tr
d is okay to check candidate kernels. Feel free to
throw some more at me if you want to bisect.
(I think IS took some of the slower machines out of rotation so the
problem might become slightly harder to reproduce - definitely is still
happening though.)
--
Iain Lane
mainline/v4.13.12/
20 instances, all good.
Maybe I should try one that we think is 'bad' to confirm that the way
I'm doing this is actually capable of reproducing the issue? If you
think that's sensible, could you recommend me a kernel to try
24294bd2f343fd5e7a625) packages, on lcy01 (the busy
cloud that exhibits this problem).
I started 34 (17 × 2 in two runs - that's all I could squeeze in before
I hit my quota) instances, and they were all good. This isn't definitive
proof, but it looks like that kernel mig
l host but didn't
reproduce the problem - it probably wasn't under enough stress anyway.
> Crossing fingers for jsalisbury's hope that 4.14 might already have a
> fix.
Right now I'm trying to build a new cloud image with this kernel that I
can try.
--
Iain Lane
I tried 28 (then my quota ran out) xenial guests BTW and none of those
failed.
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG:
** Attachment added: "bad run console-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+attachment/5005464/+files/laney-test25.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Oh also see https://bugs.launchpad.net/ubuntu/+source/linux-
hwe/+bug/1713751 which has some superficially similar symptoms (cpu
stuck on shutdown).
** Description changed:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by th
** Attachment added: "good run console-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+attachment/5005465/+files/laney-test14.log
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
Public bug reported:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn and
backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the foll
** Tags added: rls-aa-incoming
--
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/1711358
Title:
20170817 - ISO hangs on boot on qemu with splash screen enabled and
qxl graphics driver
St
(ah, it was already closed)
--
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/1706283
Title:
ADT tests fail since 4.11.0-11.16
Status in linux package in Ubuntu:
Fix Released
Bug descri
ok, the test completes without hanging. It fails though:
ubuntu-regression-suite FAIL non-zero exit status 253
but that's not what this bug was about, so closing & unblacklisting.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
ist if it doesn't hang.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because you a
Public bug reported:
The ADT tests started failing with 4.11.0-11.16 on amd64, i386 and
ppc64el: all the arches we run using qemu over OpenStack. The virtual
machines hang completely.
The last lines in the log are:
12:11:18 DEBUG| [stdout] Test icebp [Ok]
12:11:18 DEBUG| [stdout] Test int 3 trap
Public bug reported:
First traceback looks to be the cause. The second traceback is the
effect that followed (repeatedly).
Don't think it's specific to system76.
Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here
]
Apr 30 09:56:10 galago kernel: [97085.090137] ke
Maybe IS happens to have a box that's not provisioned yet and you can
borrow? Or you can borrow that one for a bit if lgw01 has some spare
capacity? Or they'll upgrade to the current lts-xenial kernel so we
maybe get lucky. :)
--
You received this bug notification because you are a member of Kern
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Invalid
** Also affects: virtualbox (Ubuntu Zesty)
Importance: Undecided
Status: Invalid
** Also affects: dkms (Ubuntu Zesty)
Import
With my patch, tested like so
- boot a yakkety cloud vm
- install bcmwl-kernel-source virtualbox-dkms ubuntu-release-upgrader-core
from yakkety
- install dkms from comment #19
- do-release-upgrade -d
- [...]
- dkms status
ubuntu@autopkgtest:~$ sudo dkms status
bcmwl, 6.30.223.271+bdc
Here's my take 2, which was forwarded upstream. Could someone
review/test please?
** Patch added: "lp1661843-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1681566/+attachment/4861224/+files/lp1661843-v2.debdiff
--
You received this bug notification becaus
Also this appears to not reproduce every time :(
ubuntu@autopkgtest:/lib/modules$ find -name wl.ko
./4.10.0-19-generic/updates/dkms/wl.ko
./4.8.0-46-generic/updates/dkms/wl.ko
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu
The function says above it
"# Get the most recent kernel on Debian based systems. This keeps
# into account both the version and the ABI. If the current kernel
# is the most recent kernel then the function will print a null string."
so I think that my previous patch is wrong.
--
You received th
For me it's enough to boot an instance on an affected lgw01 compute
node, install qemu-system-x86, download a cloud image and run "/usr/bin
/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -drive
format=raw,cache=unsafe,file=zesty-server-cloudimg-amd64.img -machine
accel=kvm -enable-kvm -cpu
Public bug reported:
Hello,
We just noticed that systemd's autopkgtests have started failing often
on amd64 for all releases, when run in Canonical's scalingstack cloud.
This is nested KVM I think.
TEST RUN: Basic systemd setup
+ /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -
** Attachment added: "linux-48036.oom6.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827640/+files/linux-48036.oom6.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Attachment added: "linux-48036.oom7.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827641/+files/linux-48036.oom7.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Attachment added: "linux-48036.oom5.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827639/+files/linux-48036.oom5.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Another 4 servers OOM'd on 4.8.0-36 over the weekend. Upgraded to
4.8.0-39
** Attachment added: "linux-48036.oom4.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4827637/+files/linux-48036.oom4.txt
--
You received this bug notification because you are a member
And again on 4.8.0-36. Upgraded server to 4.8.0-39. (How many times must
I keep on doing this?)
** Attachment added: "linux-48036.oom3.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4825946/+files/linux-48036.oom3.txt
--
You received this bug notification becau
And again on 4.8.0-36. Upgraded server to 4.8.0-39.
** Attachment added: "linux-48036.oom2.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4825131/+files/linux-48036.oom2.txt
--
You received this bug notification because you are a member of Kernel
Packages, whi
** Description changed:
Same as #1655842 - Started seeing oom-killer on multiple servers
upgraded to 4.4.0-59.
Unlike #1655842, also seeing the same oom-killer on multiple servers
updated to 4.8.0-34.
First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
4.4.0-63
No OOM on servers running 4.4.0-63 just yet, but the memory usage on
them is weird to say the least. The Buffer/SLAB ratio is completely
different from 4.4.0-57.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
And 4.8.0-36 is affected by bug also.
** Attachment added: "linux-48036.oom.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4823499/+files/linux-48036.oom.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Attaching current slabtop
---
# cat /proc/meminfo
MemTotal: 32856000 kB
MemFree: 381632 kB
MemAvailable: 30990804 kB
Buffers:28709688 kB
Cached: 221664 kB
SwapCached: 184 kB
Active: 24854232 kB
Inactive:5393552 kB
Active(anon): 78378
SLAB is still dropping.
--
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/1666260
Title:
"Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
Status in linux package in Ubuntu:
Co
I think this is currently in the middle of happening right now on one of
the servers running 4.4.0-63.
SReclaimable is down from 15GB to 5GB, and Buffers is has been slowly
rising over the last hour from 12GB to approaching 25GB.
---
# cat /proc/meminfo
MemTotal: 32856000 kB
MemFree:
Attaching the call trace for 4.8.0-34, this is from Feb 19th.
** Attachment added: "linux-48034.oom.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822834/+files/linux-48034.oom.txt
--
You received this bug notification because you are a member of Kernel
Packag
Attaching the call trace for 4.4.0-59, this is from Jan 16th.
** Attachment added: "linux-44059.oom.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822833/+files/linux-44059.oom.txt
--
You received this bug notification because you are a member of Kernel
Packag
Public bug reported:
Same as #1655842 - Started seeing oom-killer on multiple servers
upgraded to 4.4.0-59.
Unlike #1655842, also seeing the same oom-killer on multiple servers
updated to 4.8.0-34.
First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
4.4.0-63. I am seeing no c
The OOM fixes were introduced in 4.4.0-58 according to the changelog,
but sure.
--
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/1655842
Title:
"Out of memory" errors after upgrade to 4.4.
1 - 100 of 133 matches
Mail list logo
