We may as well close this issue, I don't have that laptop any more, I
don't work for Canonical any more and the boot speed regressions seem to
have fallen off the CTO's "must do priority radar" otherwise this kind
of regression would have had more engineering time devoted to it.
--
You received
Thanks JJ, much appreciated :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2024599
Title:
linux-image-5.15.0-1032-realtime locks up under scheduler test load
Status
And also occurs in Ubuntu Mantic with 6.3.0-7-generic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2024599
Title:
linux-image-5.15.0-1032-realtime locks up under
5.15.0.75 works fine, no problem, 5.19.0-45 kernel crashes, so issue
introduced between 5.15 and 5.19
** Also affects: apparmor (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: apparmor
And with 5.19.0-45-generic:
sudo ./stress-ng --apparmor 1 --klog-check
[sudo] password for cking:
stress-ng: info: [1179] defaulting to a 86400 second (1 day, 0.00 secs) run
per stressor
stress-ng: info: [1179] dispatching hogs: 1 apparmor
stress-ng: info: [1180] klog-check: kernel cmdline:
On 6.2.0-21-generic I also get:
sudo ./stress-ng --apparmor 1 --klog-check
stress-ng: error: [1083] klog-check: alert: [66.442338] 'BUG: kernel NULL
pointer dereference, address: 0030'
stress-ng: error: [1083] klog-check: alert: [66.442538] '#PF: supervisor read
access in kernel
Why won't fix? It occurs on other releases too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992979
Title:
kinetic ppc64le reporting Failed to send WATCHDOG=1
systemd error is being emitted from dispatch_notify_event() in
src/journal/journald-server.c, which is called from
server_connect_notify(). This function contains a large hunk of comment
block describing a potential race condition. I wonder if this is some
kind of race condition that only occurs
This looks related:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754328
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992979
Title:
kinetic ppc64le
I can't install Kinetic server from the LiveCD because of this issue.
It's just broken.
** Also affects: systemd (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Critical
Status: Incomplete
--
You received this bug
Using power9 arch, attached is the xml config
ubuntu22.10-kinetic-ppc64le
e410f72a-6555-4b47-bb18-8bb61eb52de2
http://libosinfo.org/xmlns/libvirt/domain/1.0;>
http://ubuntu.com/ubuntu/22.04"/>
8388608
8388608
1
hvm
POWER9
destroy
restart
Getting the same issue on the kinetic server daily image during the
install phase, see attached
** Attachment added: "issue during install"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+attachment/5624145/+files/Screenshot%20from%202022-10-14%2018-01-37.png
--
You received
Public bug reported:
Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU, single
CPU, 1GB memory, rebooted, can NO longer login. Stuck in systems boot
phase.
Attached is an image of the hang
** Affects: systemd (Ubuntu)
Importance: Critical
Status: New
** Attachment
** Changed in: linux-azure (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Pa
Thanks Dimitri!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1931725
Title:
initramfs-tools: use zstd as the default compression method
Status in
Public bug reported:
Turns out that loading is always the slow part in loading initramfs into
memory and decompressing it since decompression is always the final
10-20% or so of the task. It therefore makes sense to use a good
compressor that shrinks the initramfs as much as possible with little
I tested this out with focal -proposed and don't see any issues. Looks
OK to me.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in
Public bug reported:
systemd is pegged at 100% after booting Groovy Desktop.
Seems like an apport-report.service issue:
Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when
automatic reporting is enabled.
Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service:
This is a useful workaround, the fundamental issue is a coreutils issue
with dd. I wonder if the coreutils maintainers can figure out why dd has
an executable stack.
** Also affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: coreutils (Ubuntu)
Importance:
Fix sent to mailing list for review: https://lists.ubuntu.com/archives
/kernel-team/2020-August/112820.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1885730
Title:
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
@xnox,
one can detect the machine type from the DMI data (iff it is available
and reliable).
e.g. on my laptop:
sudo dmidecode -s "chassis-type"
Notebook
on my desktop server:
sudo dmidecode -s "chassis-type"
There are quite a few chassis-type, see
The choice was made from running analysis on a wide range of Intel
machines, old and new. We are trying to select the optimal choice for a
wide range of CPUs for a wide range of use cases. Generally speaking,
the intel-pstate governor has deeper understanding of the processor
features and can
** Changed in: linux-signed (Ubuntu Groovy)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Ti
This appears not to be a kernel issue per-se, so any idea of an ETA for
a fix with udev for this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache
@Finom, that's a good observation, much appreciated.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Description changed:
- Description: In the event a particular Azure cloud
A fix has landed in lxd, I refer you to the following comment:
https://github.com/lxc/lxd/issues/4656#issuecomment-541266681
Please check if this addresses the issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
Public bug reported:
I've been trying to identify wakeup events that cause the CPU to wakeup
from idle on a "idle" laptop on Ubuntu Eoan. The good news is that
NetworkManager doesn't utilize much CPU when idle, however, it does seem
to wakeup from poll()/epool_wait() system calls once every 4-5
And for Standard_D2s_v3
IP addr Mac AddrKernel Reboots
104.42.252.54 00:0d:3a:32:df:92 5.0.0-1020-azure500
104.42.150.26 00:0d:3a:31:1b:50 5.0.0-1020-azure500
104.42.147.144 00:0d:3a:32:d8:2f 5.0.0-1020-azure500
40.112.129.232
@Joseph, so I can reproduce this hang/crash issue across a variety of
instances. I can't get any info back on a console, so debugging this is
not easy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Get more failures with Standard_B1ms
IP addr Mac AddrKernel Reboots
52.160.101.11 00:0d:3a:5b:a0:7c 5.0.0-1020-azure10
137.135.51.101 00:0d:3a:31:20:fc 5.0.0-1020-azure500
137.135.50.133 00:0d:3a:31:27:0f 5.0.0-1020-azure396 [hang]
See: https://github.com/lxc/lxd/issues/4656#issuecomment-535531229
In https://github.com/lxc/lxd/blob/master/lxd/storage_zfs_utils.go#L255
the umount is done by
err := unix.Unmount(mountpoint, unix.MNT_DETACH)
The umount2(2) manpage writes about MNT_DETACH:
Perform a lazy unmount: make
I kicked off another ~20K reboot tests with Standard_B2S instances and
hit hangs again:
IP addr Mac AddrKernel Reboots
104.42.3.16100:0d:3a:37:82:ee 5.0.0-1020-azure100
13.91.5.23 00:0d:3a:5a:74:23 5.0.0-1020-azure57
So the best way to reproduce this issue is to run ~500 reboots across
multiple instances rather than 5000-1 reboots on once instance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
See above, I ran several thousand reboot tests on a lot of Basic_A3
instances, ranging from 50, 250 to 500 reboots. Only one failed. So
this is *really* hard to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
IP addr Mac AddrKernel Reboots
13.64.67.18600:0d:3a:3a:dd:04 5.0.0-1016-azure50
104.42.152.115 00:0d:3a:35:b1:e6 5.0.0-1016-azure50
65.52.121.205 00:0d:3a:3b:0f:52 5.0.0-1016-azure50
13.88.28.42 00:0d:3a:3b:c7:da
Been digging into this a bit further with lxc 3.17 on Eoan.
lxc launch ubuntu:bionic zfs-bug-test
Creating zfs-bug-test
Starting zfs-bug-test
lxc delete zfs-bug-test --force
Error: Failed to destroy ZFS filesystem: Failed to run: zfs destroy -r
default/containers/z1: cannot destroy
@Robert, was there a specific class of virtual machine you were using
when this issue occurred?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic
** Changed in: linux-azure (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting
@Joseph, any ideas how we can progress on this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting cloud instance
Status in
The ZFS destroy checks the reference count on the dataset with
zfs_refcount_count(>ds_longholds) != expected_holds and returns
EBUSY in dsl_destroy_head_check_impl.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
Assignee: Colin Ian King (colin-king)
Status: Triaged
** Also affects: lxc (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Disco)
Importance: Undecided
Do we have any hunches on how to reproduce this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1779156
Title:
lxc 'delete' fails to destroy ZFS filesystem 'dataset is
Cosmic is now end-of-life. Does this still occur on Disco?
** Changed in: linux (Ubuntu)
Importance: High => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Touch
I agree with the analysis in comment #13 about stress-ng.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on
It is normally always preferable to use the intel-pstate driver compared
to pcc-cpufreq or acpi-cpufreq on modern Intel hardware.
Some HP ProLiant platforms implement the PCC interface [1] which can be
disabled by a BIOS setting in which case the PCC driver will not load
and the acpi-cpufreq
Public bug reported:
I installed the Cosmic s390x server on an x86-64 Cosmic host using virt
manager and get a SIGILL when using libptread.
For example: I built stress-ng from the upstream git repo using:
sudo apt-get build-dep stress-ng
git clone git://kernel.ubuntu.com/cking/stress-ng
cd
Hrm, softlockups that break the journal aren't particularly rare on
highly loaded servers. I'm a little concerned that a potential user
space DoS attack could cause the log to discard important information
that the system admin may use to help track down misbehaving system
behaviour.
--
You
Public bug reported:
I was running the new stress-ng softlockup stressor and observed that
systemd-journald gets killed with an abort and this corrupts the systemd
journal.
How to reproduce:
git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make clean; make
sudo ./stress-ng
tested and verified it is fixed on Ubuntu Xenial with -proposed kernel
4.4.0-64 #86
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor
tested and verified it is fixed on Ubuntu Yakkety with -proposed kernel
4.8.0-39-generic #42
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
4.9.0-12_4.9.0-12.13 + jj latest fixes that landed on the kernel-team
mailing list in the last 24 hours.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1661030
Title:
Public bug reported:
from source, I'm running the tests and the makefile fails at the end
with:
running stackprofile
Makefile:303: recipe for target 'tests' failed
make: *** [tests] Error 1
No idea why that is happening. It's breaking on our kernel team
regression tests runs, so can this be
OK, a bit more data:
Xenial with 4.4 and 4.8 kernels - works fine (so not a 4.8 kernel regression)
Yakkety with 4.4 and 4.8 kernels - shows the slow behavior (so not a kernel
issue)
So I think this is a problem in the plumbing layer.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned)
I think this is a systemd/udevd kinda bug isn't it?
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
I've instrumented a kernel so I can clearly see when processes start and
exit, this allows me to see when exactly the kernel has handed off
control to userspace. The time the kernel actually takes to initialize
compared to the time systemd-analyze reports are different.
$
Public bug reported:
I've noticed that boots on Ubuntu Yakkety have slowed down recently. I
added some debug into my kernel to see where delays are occurring and I
can observe 5 seconds being consumed in /scripts/local-premount/resume
:
Aug 22 14:34:36 lenovo kernel: [6.823263] _do_fork: 1
Some data to take into consideration. I've tested 4 difference configs
(3 laptops, 1 server) of mixed Intel and AMD hardware, comparing the
default powersave/ondemand [1] vs performance
[1] depends on CPU and if intel-pstate is supported
For faster modern Intel CPUs where intel-pstate is
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1584124
Title:
revisit /etc/ini
Public bug reported:
I can't boot from a PCIe NVME device on Xenial because the nvme.ko is
missing from the initramfs. Can this please be added.
** Affects: initramfs-tools (Ubuntu)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: New
** Changed in: initramfs-tools
>From the syslog in comment #2,
Suspend blocking wakelocks:
None
Resume wakeup causes:
EINT, 553 97.88%
CLDMA_MD6 1.06%
CLDMA_MD, 6 1.06%
Suspend failure causes:
tasks freezer abort
Commit a87938b2e was included in 3.19.0-20.20 (see commit
b51621abbcb4694b8d2842ce3a66006a60bba6e5), so perhaps trying this would
be the first step to see if that commit fixes things. As it stands,
I've checked the heap and stack on a VM image using this kernel and
there is now plenty of space
OK, I guess that is the cost of a high level API that doesn't use
statfs().
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1471906
Title:
camera app is polling the
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It may be that the process is swapped out, so the delivery of the
SIGKILL takes a while for it to be swapped back in and to hence get the
signal.
To test this hypothesis:
a) one could disable swap and see if the process can be delivered the
SIGKILL and how quickly it responds to that.
Public bug reported:
I noticed that systemd on my idle Wily desktop is creating very short
lived threads at 1Hz. While these aren't doing much, it still consumes
power doing wakeups to create these periodic threads.
Showing thread creation with forkstat:
$ sudo forkstat
Time Event PID
journalctl -f -b -u systemd-logind
-- Logs begin at Tue 2015-03-31 09:36:25 BST. --
Mar 31 09:36:26 skylake systemd[1]: Starting Login Service...
Mar 31 09:36:26 skylake systemd-logind[671]: New seat seat0.
Mar 31 09:36:26 skylake systemd-logind[671]: Watching system buttons on
/dev/input/event3
The HandleLidSwitch=ignore stops the box from suspending:
$ uptime
09:50:25 up 5 min, 2 users, load average: 0.00, 0.00, 0.00
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm actually running vivid server on this box, so I don't have a unity
session running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301
Title:
desktop machine
Public bug reported:
For reasons I cannot fathom, my development server goes into deep
suspend after ~3 minutes after startup with systemd, however, if I boot
with upstart it does not. This happens everytime I boot with systemd,
the machine just goes into a deep suspend without me requesting
** Changed in: systemd (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301
Title:
desktop machine suspends with systemd
Public bug reported:
I believe this is a change in shutdown tied somehow to systemd, but I am
guessing.
How to reproduce the bug:
sudo shutdown -h now
[ wait a couple of minutes, don't enter in one's password ]
authentication times out and one is left with non-echo on one's tty.
This has to be
Any chance of getting that syslog to see what's going on?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1372413
Title:
Extensive battery drain on RTM
Status in the base
FYI, For my tests, I am reading the battery capacity directly, just to
keep it as light weight as possible:
#!/bin/sh
rm -f battery.log
while true
do
c=$(cat /sys/devices/platform/battery/power_supply/battery/capacity)
d=$(date +%d/%m/%Y %H:%M:%S)
echo $d $c battery.log
I've correlated each processes against the spike in activity for upowerd
and also see that mpdecision and systemd-udevd also change their
behaviors at that transition. See attached spreadsheet.
** Attachment added: upowerd-procs.ods
I noticed that at this point, the syslog shows and incoming call
occurred. After that, the phone does NOT deep suspend at all.
Eventually, the phone drains at 03:55:33 on the 7th of Feb. So I think
somebody needs to look at the way incoming calls seem to block deep
suspend.
Feb 6 17:12:05
So there is a rise of activity with systemd-udev at the same time that
upowerd gets busy too
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1372413
Title:
Extensive
Pat, do you mind attaching the entire cpustat.log so I spot any specific
trends? Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1372413
Title:
Extensive battery
Pat, I use something such like the following awk script to parse the
data:
{
if ((NF == 5) ($4 != PID)) {
total[$4] += $1
usr[$4] += $2
sys[$4] += $3
cmd[$4] = $5
}
if ((NF == 5) ($4 == PID))
We could possibly attach health-check to powerd to see what activity is
going.
E.g.
health-check -r -w -W -f -c -p upowerd -d 3600 health-check.log
..that will attach health-check for 1 hour and dump the results into
health-check.log.
Colin
--
You received this bug notification because you
With wifi associated to a fairly busy AP that produces regular beacon
intervals with CTS protection mode enabled and also phone data enabled
I'm seeing ~24+ hours on deep sleep idle.
With wifi enabled, I'm seeing ~7.5 wifi related wakeups per minute. I
then disabled wifi and these wakeups
I've written a bash script to periodically grab battery capacity levels
over some of this afternoon and projected the expected duration (making
an assumption the battery drain is linear, which it is not, i know
that). Anyhow, I predict 30+ hours of idle on a default clean install
on deep sleep.
I also compared 10 minutes of file process wakeup activity (old pre-
Christmas image vs lastest RTM image) and I'm seeing little different
between old vs new, so no obvious regressions there.
See attached files (spreadsheet and old vs new file activity logs).
** Attachment added:
I compared 10 minutes of file access activity (old pre-Christmas image
vs lastest RTM image) and I'm seeing a lot more udevd activity on
/lib/udev/rules.d, /etc/modprobe.d and /etc/group.
See attached files (spreadsheet and old vs new file activity logs).
** Attachment added: tar of old vs new
I compared a 10 minute sleep from an image from pre-Christmas to the
latest RTM image and I see better deep suspend stats with the latest
image (see attached).
If Thomas can attach all the syslog files from /var/log/syslog we can
parse this with suspend-blocker and get an idea of what's been
I compared a 10 minute sleep from an image from pre-Christmas to the
latest RTM image and I see better deep suspend stats with the latest
image (see attached).
If Thomas can attach all the syslog files from /var/log/syslog we can
parse this with suspend-blocker and get an idea of what's been
Also, it would be useful to capture activity of the system using the
following over a 10 minute period
Still using ppa:colin-king/white:
sudo apt-get install eventstat cpustat fnotifystat forkstat
sudo eventstat 10 60 eventstat.log
(10 seconds of sampling, 60 x a second)
And see if the CPU
I think also we need to consider security of data is the ultimate goal.
Quite frankly, unpredictable things happen users can do all kinds of
things like yank out the battery and trip kernel panics. Nobody has
formally verified that the kernel is perfect so there is always the
possibility of the
@Ricardo,
I'm added copious amounts of debug into the kernel and a shim on umount
too and I can't see /dev/mmcblk023 being unmounted anywhere. Can you
inform me where to expect this umount is actioned on shutdown. I just
can't see it.
With full journaling on I'd expect this to cope with a
So just to re-iterate:
1. I believe the file system is not being cleanly umounted.
2. data=journal saved us from disaster because it works so well.
My recommendation is to keep data=journal because a user can power off
the device (battery death, pulling out battery, random kernel reboot,
etc)
I don't thing we're seeing many writes to that partition, most of it's
probably data pages being flushed out in the background so it's not
going to bite too hard. We do have tools to figure out how much is
being written if it needs some analysis.
--
You received this bug notification because
We've been exercising the rtm images that include the latest workaround
now for a considerable amount of time repeating the test that originally
triggered the issue.
On mako, 2 devices running:
device #1, 329 iterations - no corruption observed
device #2, 251 iterations - no
** Changed in: linux-mako (Ubuntu)
Assignee: Colin Ian King (colin-king) = Paolo Pisati (p-pisati)
** Changed in: linux-mako (Ubuntu RTM)
Assignee: Colin Ian King (colin-king) = Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Touch
** Summary changed:
- thermald prevents unmounting /dev/sda1 in recovery mode
+ dbus invoked while in recovery mode
** Changed in: thermald (Ubuntu)
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Did we conclude this is more of a misconfiguration rather than a
thermald issue pe se, if so, I may remove thermald from the bug and
rename it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
Public bug reported:
While trying to figure out what's keeping the phone busy when idle
(trying to save power), I noticed that unity8 is performing a lot of
frequent poll() system calls with timeouts of 85-195 ms and it times out
on these the majority of times.Wakeups keep a phone busy, so
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from (to try to reduce flash writes and hence reduce power
consumption) and I spotted that /home/phablet/.cache/upstart/indicator-
network.log is being written to rather often (every minute or so) (tail
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from (to try to reduce flash writes and hence reduce power
consumption) and I spotted that the dbus log on my phone is being hit by
messages from process 2046:
root@ubuntu-phablet:~# ps -ef | grep 2046
Yep, still polling at the same rate doing inotify add watches:
root@ubuntu-phablet:~# strace -f -p 2078
Process 2078 attached with 4 threads
[pid 2091] restart_syscall(... resuming interrupted call ... unfinished ...
[pid 2081] restart_syscall(... resuming interrupted call ... unfinished ...
Public bug reported:
I was trying to figure out where excessive file system writes were
coming from on the ubuntu phone (to try to reduce flash writes and hence reduce
power
consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the
same debug message written to every every 300
1 - 100 of 120 matches
Mail list logo
