I did some more testing with upstream kernel. The upstream kernel
similarly has the occasional freeze where the entire desktop stops
responding or updating (while the hardware mouse cursor is usually still
movable but clicking doesn't do anything), however unlike the Ubuntu
17.04 kernel it always r
** 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.
https://bugs.launchpad.net/bugs/1682402
Title:
Running I/O heavy operation (cp) inside terminal in X s
I just tested the latest upstream 4.11-rc7 which works fine. I didn't
test a previous version of Ubuntu, since I just switched to 17.04 from
Fedora 25.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Some additional info:
- a short self-test of the SSD has already completed without errors
- there was barely any memory usage while the bug occured, so it
shouldn't be an out of memory issue
- iotop shows always ~5 seconds of 99% I/O usage of the "cp" command at
the top with nothing notable else
Just to rule out hardware issues:
smartctl --all on the SSD shows no sector reallocations, barely any
media wearout, no uncorrectable error count and barely any CRC errors
(9). I am just running a long self-test and will report back whether it
shows any errors.
--
You received this bug notificat
Public bug reported:
Running I/O heavy operation (cp) inside terminal in X server session
will lock up entire system while running it in a TTY works fine.
I am filing this as a kernel bug because the following steps will still
hang the system:
1. Open up gnome-terminal
2. Start copying a really
I got the impression from my virtual server hoster (which runs the
hypervisor) that other customers don't have this issue.
I was also inquiried about my use of BTRFS as a filesystem, and I also
use Docker very heavily which makes heavy use of special BTRFS,
DeviceMapper and Cgroup features, which
I am now very confident that this bug is NOT present in 4.9-rc7,
therefore marking kernel-fixed-upstream.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
--
You
It appears as if the issue is NOT present in mainline 4.9-rc7. I will
wait a few more days to be sure before marking this 'kernel-fixed-
upstream', since the bug always appeared in a varying interval of 2-5
days, just to get a higher level of confidence.
--
You received this bug notification beca
For what it's worth, I am now running 4.9.0-040900rc7-generic since a
few minutes ago. The bug always hit me after 2-5 days but always under a
week, so I can tell you in at the earliest a week that the bug is or is
not in upstream with high certainty. (so around 9th of December)
--
You received t
The kernel panic itself locks up the system instantly and therefore no
logging to disk happens of that error. Therefore, see the attached
screenshot of the qemu screen after the crash.
** Attachment added: "Screenshot of VM in Qemu after crashing"
https://bugs.launchpad.net/ubuntu/+source/linu
Public bug reported:
With Ubuntu 16.04, I get frequent kernel panic crashes in my Linux KVM
guest. After notifying the hosting company the machine was migrated to a
different physical host which didn't fix the problem. A complete
reinstall of Ubuntu 16.04 also didn't fix anything. Therefore, I sus
(I don't have the bluetooth headphones long enough to know if this ever
not happened)
--
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/1469145
Title:
Bluetooth device sometimes instantly t
It doesn't happen *every* time when waking up from suspend, just
sometimes. I can try switching to the mainline kernel and run it for a
while, and hope it happens again.
However, I had exactly the same problem on Fedora 21 through multiple
kernel upgrades.
--
You received this bug notification b
** Summary changed:
- Bluetooth device sometimes instantly disconnects after turning it on
+ Bluetooth device sometimes instantly turns off again after turning it on
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Public bug reported:
Sometimes when turning on bluetooth in the gnome bluetooth panel, it is
shown as "On" for like a second and reverts back to "Off". This is what
I see in dmesg:
[1199362.625284] usb 1-1.4: Product: Broadcom Bluetooth Device
[1199362.625286] usb 1-1.4: Manufacturer: Broadcom Co
16 matches
Mail list logo
