For older kernels, there are no such warnings:
update-initramfs: Generating /boot/initrd.img-5.3.0-62-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
cryptsetup: WARNING: could not determine root device from /etc/fstab
update-initramfs: Generating
uname -a
Linux lat61 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
sudo apt-get upgrade
reports:
update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
cryptsetup: WARNING: failed to detect canonical device of /dev/nvme0n1p2
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1701572
Title:
[regression] bluetooth headset not connecting after regular
I just reproduced the freeze again after switching off wireless devices
with a physical switch in my laptop. After reenabling wireless devices,
videos froze again. Worked around it by changing bluetooth profiles
(away from A2DP and back again).
So this issue is still not fixed.
--
You received
I think that one of the recent updates fixed it (and it also survives
S2RAM):
libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
Looks as if one of these updates improved it for S2RAM, but not for
hardware switch (I mean a real physical switch in my laptop for all
wireless hardware)
libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
I worked around it.
I had to remove --purge
bluetooth bluez blueman bluetooth pulseaudio pulseaudio-module-bluetooth
Then I removed all pairing information with devices, both in
~/.config/pulse and /var/lib/bluetooth
Then rebooted
Then paired my A2DP device again, this time with blueman.
Then
When I try to connect the headset (which still seems to pair), I see the
little lock next to the bluetooth device for ~0.5 seconds. Then the lock
disappears.
Syslog reports:
Jun 30 16:00:40 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for
00:1A:7D:70:08:7E: Protocol not available
Jun
Public bug reported:
Hi, my bluetooth headset Arctic P311 was connecting until I installed
these updates:
libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
As bluetooth headsets tend to deal with audio, I assume that the cause
of this issue is somewhere between pulseaudio and bluetooth.
Pulseaudio also deals with bluetooth directly, like in issue #508522. As
long as it is unclear where this issue really comes from, I'll add
pulseaudio package to
I've just seen this with 16.04, together with latest HES 4.8 kernel:
uname -a
Linux server 4.8.0-51-generic #54~16.04.1-Ubuntu SMP Wed Apr 26 16:00:28 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
That happened during a btrfs-scrub:
May 7 02:11:52 server kernel: [17884.471597] []
Tracked it further down (ubuntu 16.04).
On a fresh boot
- bluetooth device connects, with sound enabled (I configured bluetooth to
default to bluetooth sound device on connect)
- video playback does not stop
- Sound is played perfectly fine.
After a suspend to ram and suspend
- bluetooth
Replacing the SATA cable fixed this issue for me.
--
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/1385165
Title:
"Exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe frozen" when
I think my case is different: It's not about variable 231/duplicate
entries for temperature.
Instead, smartctl does something with the temperature's RAW_VALUE and
thereby falsifies it.
For my case, I filed a new bug report #1653560, respectively.
--
You received this bug notification because
Confirming this issue:
Using Ubuntu 16.04, Kernel 4.4.0-57-generic wrong temperatures also make
it into syslog:
Jan 2 20:22:27 server smartd[876]: Device: /dev/sda [SAT], SMART Usage
Attribute: 194 Temperature_Celsius changed from 110 to 112
Jan 2 20:22:27 server smartd[876]: Device: /dev/sdb
The bare metal system is a backup server (2x3 Terabytes of disk space),
holding a lot of subvolumes from incremental backups).
The report files I just sent are from the bare metal system. Note that
btrfs is on top of a Luks encrypted partition which is on top of a md
raid. That setup is a lot
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799044/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799043/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799041/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799040/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799042/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799034/+files/CRDA.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/1651435
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799036/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799035/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799037/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799038/+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/1651435
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1651435/+attachment/4799039/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I have a KVM guest system which was running for some time now (142 days
uptime).
Today, I logged in for the first time since months, and got an error
message in syslog (and console):
kernel: BTRFS error
I got the same error using a bare metal system on 16.04.. That system
got updated from 14.04 (and is much older). That system got installed
completely separate/independent, so there is not much to consider that
both systems somehow seem to be similar in terms of configuration.
The kernel of this
I'm faced with this issue using ubuntu 16.04, Kernel 4.4.0-53
--
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/1385165
Title:
"Exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe
Reboot worked without issues, now using kernel 4.4.0-53-generic x86_64.
I'll see how that works out.
--
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/1651435
Title:
BTRFS error: could not
Public bug reported:
I have a KVM guest system which was running for some time now (142 days
uptime).
Today, I logged in for the first time since months, and got an error
message in syslog (and console):
kernel: BTRFS error (device vda2): could not find root 8
The error happened together with
The 4.4.0-38, which got released via regular updates mitigated all the
flickering for me. It's all fine now. Thanks for the patch.
--
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/1553503
Here's some of the results (done by Josef Bacik) in an early stage of
the changes:
http://www.spinics.net/lists/linux-btrfs/msg53410.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
There are two btrfs related patches available for kernel 4.8 which
improve latency and solve problems with low free disk space:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ba929b6646c5b87c7bb15cd8d3e51617725c983b
I can confirm this is not fixed for 4.4.0-36 with an Ironlake GPU
(tested with Intel Core i5 520M CPU).
Let's wait for the Ironlake-specific bugfix in 4.4.0-37, I'll report
back after it is released.
--
You received this bug notification because you are a member of Kernel
Packages, which is
As documented in https://wiki.ubuntuusers.de/laptop-mode-
tools/#Eingabegeraete, one can configure laptop-mode-tools with
AUTOSUSPEND_USBTYPE_BLACKLIST=”usbhid”
IMO, this should be enabled by default.
** Also affects: laptop-mode-tools (Ubuntu)
Importance: Undecided
Status: New
**
No, /etc/rc.local was untouched. The file was empty besides of an "exit
0".
/etc$ sudo fgrep -ril powertop *
/etc$ sudo fgrep -ril autotune *
both give an empty result.
I installed TLP again, which automatially removed package
"laptop-mode-tools".
Using powertop, I've set back the two USB
I did not post the correct devices in my previous comment.
The two affected devices are:
Bus 002 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230
Bus 002 Device 003: ID 046d:c24c Logitech, Inc. G400s Optical Mouse
Mouse and keyboard, respectively. Both connected with
Public bug reported:
This issue is a regression after update to 16.04 (coming from 14.04). To
my knowledge, I was using TLP together with 14.04, which got removed
during the upgrade in favour of upower.
Two devices behave unexpected reproducably after a fresh reboot:
Bus 002 Device 005: ID
I have ubuntu 16.04, kernel 4.4.0-28-generic, up-to-date. I did not
experience the freezing video in 14.04.
However, in 14.04 (kernel 4.2) I sometimes did not have sound unless
toggling between A2DP and SCO. Freezing videos in 16.04 just come on-top
now.
--
You received this bug notification
I experience the same issue for device
Bus 002 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth
Module
together with an Arctic P311 head set.
For me, the problem does not occur reproducably, but about every 3-4
tries. Steps to reproduce
- Play video (e.g. youtube video in Firefox)
*** This bug is a duplicate of bug 1523088 ***
https://bugs.launchpad.net/bugs/1523088
** This bug has been marked a duplicate of bug 1523088
WARN_ON(!wm_changed) warning and stacktrace in kernel log
--
You received this bug notification because you are a member of Kernel
Packages, which
This issue also affects ubuntu 16.04 as can be seen in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503
--
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/1523088
Title:
https://cgit.freedesktop.org/drm-
intel/commit/?id=734fa01f3a17ac80d2d53cee0b05b246c03df0e4
This seems to be at least ONE of the patches done for
https://bugs.freedesktop.org/show_bug.cgi?id=89055#c62
I have no idea if it fixes this issue (=> not tested) nor do I really
understand the commit
For this symptomatic there is an upstream bug report with status RESOLVED FIXED:
- Dual monitor
- Flickering or black screen when mouse moved between screens
https://bugs.freedesktop.org/show_bug.cgi?id=89055#c62
Date: 2016-05-13
Upstream target kernel version: 4.8.
Maybe this can be backported?
After more testing I can say that also the same screen on which I am
scrolling with the scroll bars can go black.
When the mouse switches between screens, I get a flickering in ~50% of
tries.
Please note that I'm using Kernel 4.4.0-28, which is newer than 4.4.0-24
which contains a fix for a
Confirming this, using a Dell Latitude E5510 with Intel HD Graphics (on-
chip), together with a docking station PR02X and a two-monitor-setup (2x
BenQ GW2460, 1920x1080, DVI).
The problem occurs most of the time when scrolling in a full screen
application on the left screen using the scroll bar
As MikeB pointed out, the issue still exists with latest mainline
kernel. Therefore, I added Tag "kernel-bug-exists-upstream" and changed
status to "confirmed".
I know of another user with the same problem. He was also testing
against latest mainline kernel with no success.
** Tags added:
related: #1592948 originates from ubuntu's apport and was automatically
created after the first reboot (while cups was still unconfigured at
that time).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Workaround:
Step 1:
===
I killed the process with which I was stuck with (kill 20108):
root 20108 0.0 0.0 4508 1624 pts/18 S+ 18:42 0:00 /bin/sh
/var/lib/dpkg/info/cups-daemon.postinst configure 1.7.2-0ubuntu1.7
This had the result that the do-release-upgrade script continued to
configure
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684486/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684488/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684485/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684487/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684482/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684484/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684483/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684480/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684481/+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/1592917
apport information
** Tags added: apport-collected xenial
** Description changed:
On an up-to-date 14.04.x, I started do-release-upgrade -d to upgrade to
ubuntu 16.04.
At about 50% of the installation of packages, do-release-upgrade stucks
in the following manner:
- cpu runs at
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684479/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1592917/+attachment/4684478/+files/CRDA.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/1592917
After trying to stop or teardown apparmor, I still get
aa-status
apparmor module is loaded.
3 profiles are loaded.
3 profiles are in enforce mode.
/usr/lib/cups/backend/cups-pdf
/usr/sbin/cupsd
/usr/sbin/cupsd//third_party
0 profiles are in complain mode.
0 processes have profiles
Still in the middle of the (stucked) upgrade, I get:
apport-collect 1592917
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository
Public bug reported:
On an up-to-date 14.04.x, I started do-release-upgrade -d to upgrade to
ubuntu 16.04.
At about 50% of the installation of packages, do-release-upgrade stucks
in the following manner:
- cpu runs at 0%~ and there is no disk I/O for about 15 minutes now
- do-release-upgrade
In syslog, I get a lot of complaints from apparmor:
Jun 15 19:06:02 lat61 kernel: [10041.854940] audit: type=1400
audit(1466010362.719:539): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=24942
comm="apparmor_parser"
Jun 15 19:06:02
do-release-upgrade stucks at this place:
plymouth (0.9.2-3ubuntu13.1) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
update-rc.d: warning: start and stop actions are no
output of ps aux | grep dpkg is attached.
Note that there is a process with no progress (stucks)
root 20108 0.0 0.0 4508 1624 pts/18 S+ 18:42 0:00 /bin/sh
/var/lib/dpkg/info/cups-daemon.postinst configure 1.7.2-0ubuntu1.7
** Attachment added: "output of ps aux | grep dpkg"
related: #1370930
--
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/1592917
Title:
do-release-upgrade stuck when dealing with apparmor profile for cupsd
Status in linux package in Ubuntu:
Generally, the frozen desktop was very very rare/seldom. I'd have to
work weeks with the cdimage to reproduce this issue.
In the meantime I don't experience frozen desktops in Ubuntu 14.04.4 any
more. Maybe it's already fixed even in 14.04.4. Maybe I see it again in
a month or so.
For the
@penalvch no, /var/crash is empty:
/var/crash$ ls -la
insgesamt 0
drwxrwsrwt 1 root whoopsie 0 Jun 1 10:10 .
drwxr-xr-x 1 root root 130 Jul 26 2015 ..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674844/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674833/+files/CRDA.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/1551566
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674846/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674842/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674843/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674832/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674835/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674841/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674834/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674845/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674840/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674839/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674836/+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/1551566
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674837/+files/Lsusb.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/1551566
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1551566/+attachment/4674838/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
My desktop just froze and I could not press any keys.
When I tried CTRL+ALT+F1 I got logged out from my gnome session and the
graphical (!) login window appeared.
There's some messages in my syslog, e.g.
As described in my previous comment, the fs was available in read-write
mode again.
I added another disk to the btrfs and with the additional space I was
able to rerun and successfully finish the btrfs balance operation (as
described in https://www.slicewise.net/debian/balancierung-eines-vollen-
I rebooted the system in the meantime. It now had Kernel 4.2.0-30.36
from previous updates:
cat /proc/version_signature
Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
During the reboot, the system performed some disk I/O for several hours.
Before services like sshd became available. I guess this
@jsalisbury
What exactly should I test on a broken file system with a newer Kernel?
How could this help you? If btrfs balance corrupted my file system, how
should a newer kernel fix that?
If you can tell me test a scenario which will help you to see if the bug
is fixed upstream, I'd be happy to
Checking the underlying mdraid with
echo check > /sys/block/md0/md/sync_action
now has finished and it is just fine:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks super 1.2
Now, this one is funny after ~2 days:
# btrfs balance status x
Balance on 'x' is running
0 out of about 2797 chunks balanced (533 considered), 100% left
# btrfs balance cancel x
ERROR: balance cancel on 'x' failed - Read-only file system
So the balance is still running, consuming 100% of one
cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=8157548k,nr_inodes=2039387,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs
I found a few entries in kern.log, nothing special during btrfs balance:
Mar 19 03:47:03 server kernel: [2970569.341605] BTRFS info (device dm-0):
relocating block group 9553211031552 flags 36
Mar 19 04:01:08 server kernel: [2971415.588391] BTRFS info (device dm-0):
relocating block group
Error messages in dmesg |tail are still ongoing, presumably originating
from the btrfs command which still is eating 100% of the cpu,
I did not reboot yet nor kill the btrfs process (pid 27516).
Here's two lines from two of the latest error messages in dmesg:
[3111643.576434] []
Something noticable: The command btrfs is consuming 100% of the cpu for
a long time:
# top
[...]
PID BENUTZER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
27516 root 20 0 15476132 0 R 100,0 0,0 1348:33 btrfs
I assume that this process originates from my
Currently, I'm checking the md-raid (raid 1) with
echo check > /sys/block/md0/md/sync_action
I have 2 x 3.5TB hard drives, so this will take some while.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The underlying md-raid (mirroring) is fine. So according to md-raid
status, there's nothing wrong with the mirrored partitions:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks
Some relevant lines from /var/log/syslog:
Mar 19 19:15:10 server smartd[2251]: Device: /dev/sdb [SAT], SMART Usage
Attribute: 194 Temperature_Celsius changed from 107 to 106
Mar 19 07:59:21 server console-kit-daemon[2041]: GLib-CRITICAL: Source ID 376
was not found when attempting to remove it
1 - 100 of 114 matches
Mail list logo
