Public bug reported:
I installed Trusty beta 2, and since then have had maximum uptime of about 12
hours.
System hangs frequently, sometimes with mouse still active, sometimes not.
The clock in the upper right of the screen shows the time of the hang.
I have not yet established whether the
The log error messages are not new; I forgot, but I've been having this problem
for a while, see bug 671979
(which was with proprietary nvidia drivers).
The hang may be unrelated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I switched to the recommended proprietary nvidia driver, and since then there
have been no hangs.
So either some update may have fixed it, or it's in the Nouveau driver, or I'm
just lucky.
I should try switching back to Nouveau to see if it comes back, and if
it does, I could then try the
The affected system is dirty. Its ASUS VW266H LCD monitor itself has
been locking up lately, making it seem like the system is crashed. This
bug report is tainted and should probably be closed as invalid.
--
You received this bug notification because you are a member of Kernel
Packages, which
No, I guess I got distracted. I'm pretty busy; if someone else wants to
pick this up, that'd be fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to eject in Ubuntu.
https://bugs.launchpad.net/bugs/678419
Title:
volname does not work
Public bug reported:
I tried pm-hibernate, and turned the computer back on after it shut
down. My apps weren't there after startup.
ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-12-generic 3.19.0-12.12
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
I updated the BIOS as described. No change -- it still fails to resume
from hibernate; I get a fresh boot and an apport problem report prompt
as before.
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
now outputs
FBKT99AUS
09/19/2014
** Changed in: linux (Ubuntu)
Installed
linux-headers-4.0.0-04_4.0.0-04.201504121935_all.deb
linux-headers-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb
linux-image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb
uname -a reports
Linux library 4.0.0-04-generic #201504121935 SMP Sun Apr 12
Please advise on how you suspended, and resumed specifically.
- Executing at a terminal pm-hibernate
While booted into the latest non-daily mainline kernel, please attach to your
report:
cat /proc/acpi/wakeup wakeup
- Attached
While booted into the latest non-daily mainline kernel, please
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443762/+attachment/4378033/+files/dmesg.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/1443762
I have not tested on this computer with a release prior to Vivid, but in
general, I have never found hibernate or suspend to be useful or stable
on any computer I've tested with any version of Ubuntu. Windows 7 does
suspend ok on the two similar computers I've tested it on.
** Changed in: linux
Since this is a hibernate failure, adding info from
https://wiki.ubuntu.com/DebuggingKernelHibernate
dank@library:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.0.0-04-generic
root=UUID=ddf8fcf8-5870-4a32-afc2-b54de9d66128 ro quiet splash vt.handoff=7
dank@library:~$ cat
Tried this:
echo core /sys/power/pm_test
echo reboot /sys/power/disk
echo disk /sys/power/state
dmesg /tmp/dmesg-core-reboot.txt
Result attached.
** Attachment added: dmesg-core-reboot.txt
** Attachment added: lsmod.output.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443762/+attachment/4378037/+files/lsmod.output.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The Thinkserver TS140 by design does not support suspend. Should still
support hibernate, though.
I'll try 14.04.1.
--
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/1443762
Title:
14.04.1 hibernates and resumes like a champ on this machine. On first
try, it resumed a hibernated session with two terminals, an xclock,
firefox, and amoeba. Did not test resume of wireless, but wired
ethernet was fine.
So this appears to be a regression in ubuntu 15.04 beta 2 relative to
Tested kernel 4.0 on 14.04.1. Hibernated fine. Thus problem not in
kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I installed 14.10 and used btrfs for /home. Later, I did a clean install of
15.04, using the same /home partition.
Ever since then, boots have been agonizingly slow; all the delay appears to be
while the message
scanning for btrfs filesystems is diplayed early in boot.
** Attachment added: bootchart-20150531-0837.svg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+attachment/4407664/+files/bootchart-20150531-0837.svg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm willing to test, too, but the procedure is hard to extract from that
email thread.
--
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/1436940
Title:
Atheros wifi 168c:0041(QCA6164) is
acer aspire e15 e5-573g-59c3 suffers from similar problem, but with
lspci reporting 168c:0042 (rev 30),not 0041 (rev 20).
--
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/1436940
Title:
Upgrading to ubuntu 15.10 magically improved things.
It's possible it was running fsck, or something.
I would like to close this as fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hibernate worked fine on this computer with ubuntu 14.04.
I agree suspend is intentionally disabled by hardware/BIOS.
--
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/1443762
Title:
This is back with 16.04, and affects multiple systems.
--
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/1460447
Title:
Boot slow, "scanning for btrfs filesystems" takes 100 seconds
This happened to me, too. I uninstalled xserver-xorg-video-intel to work around
awful, nasty flashing, as suggested by
https://bugs.chromium.org/p/chromium/issues/detail?id=606152#c73
So evidently that workaround isn't stable enough yet.
--
You received this bug notification because you are a
https://askubuntu.com/questions/836105/ubuntu-16-04-takes-long-time-to-
boot-using-btrfs-and-persistent-logs suggests disabling COW on the
systemd journal directory may help.
Avoiding / as btrfs, and using it just for e.g. /var/lib/lxd, may be an
option for some people.
--
You received this bug
https://lkml.org/lkml/2017/12/7/201 tries to raise the limit, but according to
https://bugs.freedesktop.org/show_bug.cgi?id=102508#c11 it does not work.
Also, Skull Canyon is 6th generation, is it not? See
https://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc6i7kyk-features-
See also similar bugs
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178
Those were treated as if the 8kx8k limit was ok, and the bug was in the
compositor
which failed to work around that limit. Perhaps this bug
Public bug reported:
This is on a fresh Dell 8930 with an i7-8700 (and a gtx1050) running ubuntu
18.04.
Linux rbb-ubu1804-1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Oddly this only happens on one of the two such boxes I have.
Here's the main
This just changed for me... but the hardware may matter, as I'm on Hades
Canyon, using the amd gpu, not HD graphics.
A few days ago I updated to the then-latest 4.19-rc2
(and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting
exactly what I did).
Using plain old X (no desktop) on
I should have mentioned, my Hades has 32GB of RAM.
With 8GB or less of RAM, the problem might persist (if I understand the mailing
list posts).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
FWIW, I ran into this after updating to 19.04 from 18.04.
Audio working fine with HDMI (yay) but not with back panel audio (boo)
unless I ran aplay as root, e.g.
sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav
ps showed timidity running. 'sudo apt remove timidity; sudo
(The zero size problem mentioned above also occurs occasionally on
ubuntu 18.04, and the workaround is to add a sleep in the user script
after modprobe nbd, so that's really a separate problem.)
--
You received this bug notification because you are a member of Kernel
Packages, which is
FWIW, running same script on ubuntu 16.04 seems to work better.
--
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/1896350
Title:
nbd locks system?
Status in linux package in Ubuntu:
On today's groovy snapshot (with the default kernel, 5.8.0-generic), the
original problem is still present; didn't seem to show up until 2nd run
of the bug script.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I'm trying to use nbd on ubuntu 20.04 like so:
qemu-img create -f qcow2 foo.img 500M
sudo modprobe nbd
sudo qemu-nbd --disconnect /dev/nbd15 || true
sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img
sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard
Here's the apport file from the VM (which is a very recent clean install);
for some reason I couldn't upload it with ubuntu-bug.
** Attachment added: "apport.linux-image-5.4.0-47-generic.0beq9kz0.apport"
Also seems to work fine on ubuntu 18.04 (fresh, fully updated).
--
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/1896350
Title:
nbd locks system?
Status in linux package in Ubuntu:
38 matches
Mail list logo
