systemd[1]: ureadahead.service fails on vanilla kernels, needs Ubuntu kernel patch

Bug #1429098 reported by Cristian Aravena Romero
134
This bug affects 29 people
Affects Status Importance Assigned to Milestone
ureadahead (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

dmesg:
[ 4.717252] systemd[1]: ureadahead.service failed.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu3
Uname: Linux 4.0.0-040000rc2-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 6 08:55:40 2015
InstallationDate: Installed on 2014-09-25 (162 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-040000rc2-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Can you please show me the output of

   systemctl status -l ureadahead.service

?

affects: systemd (Ubuntu) → ureadahead (Ubuntu)
Changed in ureadahead (Ubuntu):
status: New → Incomplete
affects: systemd → null-and-void
Changed in null-and-void:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Ohhhhhhhhhhhhhhhhhh, one circle!

8<------------8<------------8<------------8<------------8<------------8<------------8<------------
caravena@caravena-530U3C-530U4C:~$ systemctl status -l ureadahead.service
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since vie 2015-03-06 08:54:44 CLST; 1h 53min ago
  Process: 296 ExecStart=/sbin/ureadahead (code=exited, status=5)
 Main PID: 296 (code=exited, status=5)

mar 06 08:54:44 caravena-530U3C-530U4C ureadahead[296]: ureadahead: Error al tracear: No existe el archivo o el directorio
mar 06 08:54:44 caravena-530U3C-530U4C ureadahead[296]: Counted 4 CPUs
mar 06 08:55:29 caravena-530U3C-530U4C systemd[1]: Stopped Read required files in advance.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Revision history for this message
Martin Pitt (pitti) wrote :

> ureadahead: Error al tracear: No existe el archivo o el directorio

Can you please give me the output of

  ls -l /var/lib/ureadahead

?

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

caravena@caravena-530U3C-530U4C:~$ ls -l /var/lib/ureadahead
total 0
drwxr-xr-x 1 root root 0 mar 25 2013 debugfs
caravena@caravena-530U3C-530U4C:~$

Revision history for this message
Martin Pitt (pitti) wrote :

OK, no *.pack files then, so the problem is on the initial data collection. Can you please run

  sudo ureadahead --verbose >/tmp/output 2>&1

in a terminal, then do some file system activity (e. g. cat /bin/bash >/dev/null), then press Control-C, let it finish, and attach /tmp/output?

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

All Right?

Revision history for this message
Martin Pitt (pitti) wrote :

Hm, that's veeery terse, there should have been multiple screenfuls of output. But still no error message. Is it possible to get ssh access to your system? I don't know what happens with ureadahead on that particular one.. :-/ This needs stracing, gdb'ing, etc., and that's really hard to do remotely if you aren't familiar with these tools.

Changed in ureadahead (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Hello Martin Pitt,

1) Sorry for delay
2) How to connecction for ssh?

Example of my private network. My [0]IP

[0]:
wlan0 Link encap:Ethernet direcciónHW c4:85:08:6c:01:06
          Direc. inet:10.243.197.120 Difus.:10.243.197.255 Másc:255.255.255.0

I have router Linksys with firmware update, router modern (2,4G and 5G). My netwrok is subnetwork of network XD. I'm life in an office XD. I'm not privilegios of administrator for admin configuration of equipaments. I'm only an person sympathetic :D

Help for Help

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Martin? :)

Revision history for this message
Martin Pitt (pitti) wrote :

Cristian, sorry I had been on vac for two weeks. For ssh you either need to be able to ssh to a public host where I can ssh to as well (a server of your's, a cloud instance, etc.) and forward your port 22, as you are behind a NATed network. Or open port 22 on your router; but I guess that isn't available to you.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Hello Martin,

My connection: [[Attach Image]]

Thanks for you work,
--
Cristian

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Problem with Network and NAT, is complicated.

Thank you in advance!
--
Cristian

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Hello Martin :)

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

[ 4.468374] systemd[1]: ureadahead.service: main process exited, code=exited, status=5/NOTINSSTALLED
[ 4.469097] systemd[1]: Unit ureadahead.service entered failed state.
[ 4.469149] systemd[1]: ureadahead.service failed.

Revision history for this message
aljosa (aljosa-p) wrote :

Asus optimus notebook N750JV-T4069H
Ubuntu 15.04, final Linux kernel 4.0

pastebinit /var/log/dmesg
http://paste.ubuntu.com/10849552/
(Nothing has been logged yet.)

terminal dmesg output:
[1.672332] systemd[1]: ureadahead.service: main process exited, code=exited, status=5/NOTINSSTALLED
[1.672612] systemd[1]: Unit ureadahead.service entered failed state.
[1.672643] systemd[1]: ureadahead.service failed.

Here's the output of "systemctl status -l ureadahead.service":

● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2015-04-19 10:44:50 CEST; 28min ago
  Process: 262 ExecStart=/sbin/ureadahead (code=exited, status=5)
 Main PID: 262 (code=exited, status=5)

Apr 19 10:44:50 blabla ureadahead[262]: ureadahead: Error while tracing: No such file or directory
Apr 19 10:44:50 blabla ureadahead[262]: Counted 8 CPUs
Apr 19 10:45:44 blabla systemd[1]: Stopped Read required files in advance.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable

Revision history for this message
dino99 (9d9) wrote :

On that i386 vivid system, journalctl is flooded by such endless list:

.....
ureadahead[215]: ureadahead:ath10k: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:libertas_tf: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:hostap: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:p54: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:slip: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:bonding: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:caif: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:xen-netback: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:arcnet: Ignored relative path
ureadahead[215]: ureadahead:..: Ignored relative path
ureadahead[215]: ureadahead:ethernet: Ignored relative path
ureadahead[215]: ureadahead:broadcom: Ignored relative path
ureadahead[215]: ureadahead:genet: Ignored relative path
....

 systemctl status -l ureadahead.service
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since 2015-04-20 07:44:25 CEST; 30min ago
  Process: 225 ExecStart=/sbin/ureadahead (code=exited, status=0/SUCCESS)
 Main PID: 225 (code=exited, status=0/SUCCESS)

ureadahead[225]: ureadahead:samba: Ignored relative path
ureadahead[225]: ureadahead:.xsession-errors: Ignored relative path
ureadahead[225]: ureadahead:.: Ignored relative path
ureadahead[225]: ureadahead:session-c2.scope.d: Ignored relative path
ureadahead[225]: ureadahead:session-c1.scope.d: Ignored relative path
ureadahead[225]: ureadahead:sysinit.target.wants: Ignored relative path
ureadahead[225]: ureadahead:tracing_on: Ignored relative path
ureadahead[225]: ureadahead:events/fs/open_exec/enable: Ignored relative path
ureadahead[225]: ureadahead:events/fs/do_sys_open/enable: Ignored relative path
ureadahead[225]: Counted 4 CPUs

Revision history for this message
dino99 (9d9) wrote :

Looks like that other bug still exist, and should grab some more attention as tracing cant be done:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1176536

Revision history for this message
dino99 (9d9) wrote :

sudo /sbin/ureadahead --force-trace --debug
[sudo] password for oem:
Counted 4 CPUs

trace: Missing uselib tracing: No such file or directory

already reported: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1237042

Revision history for this message
dino99 (9d9) wrote :

sudo /sbin/ureadahead --force-trace --debug
[sudo] password for oem:
Counted 4 CPUs

trace: Missing uselib tracing: No such file or directory

already reported: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1237042

ureadahead (0.100.0-13) raring; urgency=low

  * src/trace.c: tracing_enabled is deprecated and gone, switch to tracing_on
    (LP: #1085766).

 -- Andy Whitcroft <email address hidden> Fri, 11 Jan 2013 12:05:17 +0000

.... then got that one (maybe related to actual 'Missing uselib tracing' above:

ureadahead (0.100.0-16) raring; urgency=low

  * src/trace.c: update to ignore symlinks when tracing + cleanup extra stat()
    (LP: #969926)

 -- Bryan Fullerton <email address hidden> Mon, 25 Mar 2013 10:09:18 +0100

Changed in ureadahead (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ferry Toth (ftoth) wrote :

Yes, I had the same.

I traced it back to the following:
Before and after the upgrade to 15.04 I was running kernel 4.0 (same as reporter). Apparently with this kernel something doesn't want to trace (whatever that means in this context). As a result no 'pack' file is generated in /var/lib/ureadahead. The missing pack file causes ureadahead again to try to trace on the next boot, which again fails.

Solution: boot one time as 15.04 default kernel (3.19.0) with systemd, not upstart. This will let ureadahead create the 'pack'. Lot's of uninteresting stuff fills syslog (about ignoring relative path blabla). On the next boot with kernel 4.0 ureadahead failure disappeared.

Revision history for this message
Ancoron Luciferis (ancoron-luciferis) wrote :

So, is this a problem of the 4.0 kernel itself or the kernel configuration?

Revision history for this message
Ancoron Luciferis (ancoron-luciferis) wrote :

In my case, I see the following:

ureadahead[275]: ureadahead: Error while tracing: No such device
systemd[1]: Stopped Read required files in advance.

Revision history for this message
Ferry Toth (ftoth) wrote :

Did you try a one time boot with the default kernel?

Revision history for this message
Martin Pitt (pitti) wrote : Re: systemd[1]: ureadahead.service failed on vanilla kernels

ureadahead needs an out-of-tree kernel patch to add trace events for open(), exec() and uselib() syscalls that take file paths, see bug 462111. This needs to be changed to use fanotify() which is available in the standard kernels. However, it needs to be checked whether it's also available on the Ubuntu touch kernels which often ship an ancient 3.4 kernel with Android changes.

summary: - systemd[1]: ureadahead.service failed.
+ systemd[1]: ureadahead.service failed on vanilla kernels
Changed in ureadahead (Ubuntu):
status: Confirmed → Triaged
summary: - systemd[1]: ureadahead.service failed on vanilla kernels
+ systemd[1]: ureadahead.service fails on vanilla kernels, needs Ubuntu
+ kernel patch
Revision history for this message
GuyR (guy-rouger) wrote :

Hello,
Same problem here when using
 guy@desktop:~$ uname --all
Linux desktop 3.19.8-031908ckt1-lowlatency #201505292219 SMP PREEMPT Fri May 29 22:30:32 UTC 2015 i686 i686 i686 GNU/Linux
So i boot one time in the official kernel 3.19.0-18-generic and reboot in the 3.19.8-031908ckt.
This time I found this
root@desktop:~# systemctl status ureadahead
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since jeu. 2015-06-04 14:49:40 CEST; 2min 12s ago
  Process: 202 ExecStart=/sbin/ureadahead (code=exited, status=0/SUCCESS)
 Main PID: 202 (code=exited, status=0/SUCCESS)

juin 04 14:49:36 desktop ureadahead[202]: ureadahead:/var/lib/NetworkManager/dhclient-eth0.conf: Aucun fichier ou dossier de ce type
juin 04 14:50:57 desktop systemd[1]: Stopped Read required files in advance.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

but this file exists
root@desktop:/var/lib/NetworkManager# ls -alrt /var/lib/NetworkManager/dhclient-eth0.conf
-rw-r--r-- 1 root root 2260 juin 4 14:50 /var/lib/NetworkManager/dhclient-eth0.conf

was it create too late??

Revision history for this message
GuyR (guy-rouger) wrote :

hello,
the next boot all seems ok
root@desktop:~# systemctl status ureadahead
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since jeu. 2015-06-04 15:08:50 CEST; 1min 22s ago
  Process: 201 ExecStart=/sbin/ureadahead (code=exited, status=0/SUCCESS)
 Main PID: 201 (code=exited, status=0/SUCCESS)

juin 04 15:09:56 desktop systemd[1]: Stopped Read required files in advance.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

root@desktop:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION="Ubuntu 15.04"

root@desktop:~# uname --all
Linux desktop 3.19.8-031908ckt1-lowlatency #201505292219 SMP PREEMPT Fri May 29 22:30:32 UTC 2015 i686 i686 i686 GNU/Linux
root@desktop:~#

Revision history for this message
GuyR (guy-rouger) wrote :

Hello,
There is still a problem with NetworkManager.
At the first boot this morning I get this errror missing file dhclient-eth0.conf despite the file exists but probably too late.
@desktop:/var/lib/NetworkManager$ systemctl status ureadahead.service -l
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since sam. 2015-06-06 08:45:55 CEST; 1min 53s ago
  Process: 205 ExecStart=/sbin/ureadahead (code=exited, status=0/SUCCESS)
 Main PID: 205 (code=exited, status=0/SUCCESS)

juin 06 08:45:49 desktop ureadahead[205]: ureadahead:/var/lib/NetworkManager/dhclient-eth0.conf: Aucun fichier ou dossier de ce type
juin 06 08:47:45 desktop systemd[1]: Stopped Read required files in advance.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
@desktop:/var/lib/NetworkManager$ ls -alrt dhclient-eth0.conf
-rw-r--r-- 1 root root 2260 juin 6 08:46 dhclient-eth0.conf
guy@desktop:/var/lib/NetworkManager$ uname --all
Linux desktop 3.19.8-031908ckt1-generic #201505292219 SMP Fri May 29 22:28:29 UTC 2015 i686 i686 i686 GNU/Linux
@desktop:/var/lib/NetworkManager$

dino99 (9d9)
tags: added: wily
Revision history for this message
cooloutac (cooloutac) wrote :

Hello, I have the same problem as din99 in post #17. My syslog is filled with endless "ignored relative path" messages.

Systemctl status for me also shows just a handful of processes with the same message.

Does this mean ureadahead is not working right? I disabled it just in case.

Revision history for this message
Jean-Baptiste Lièvremont (mithfindel) wrote :

Hi, I get the symptoms described in post #17 on x86_64 after upgrading to wily. I was using upstream kernel 4.0.9 without any issue before the upgrade, currently running 4.2.0-18-generic.

Changed in null-and-void:
status: Invalid → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Get the same garbage logged with xenial (gnome-shell session) (like #17 above)

tags: added: xenial
Revision history for this message
William Geiger (whgiii-q) wrote :

I am running Xubuntu Xenial and was getting the same "ignore relative path" statements in my log files. I ran the following to fix it for now:

sudo ureadahead --force-trace --verbose /

adding the "/" for the mount-point for uredahead rebuilt the pack file properly.

ran sudo ureadahead --dump afterwards and everything looks good.

hope this helps

Revision history for this message
dino99 (9d9) wrote :

@William

thanks for the command; after a reboot the error is gone.

note: from a terminal "sudo ureadahead --force-trace --verbose /" does nothing, but hitting ctrl+c has started the rebuilt.

Revision history for this message
whgiii (whgiii) wrote : Re: [Bug 1429098] Re: systemd[1]: ureadahead.service fails on vanilla kernels, needs Ubuntu kernel patch
Download full text (3.7 KiB)

My understanding is ureadahead collects data until you hit cntrl-c to
stop it, but I am not an expert on it, just what I gleaned with my
goolge-foo at 3 am. :) The key to this "fix" is adding the "/" I was
going through the config files and it looks like when ureadahead is
called from the system at boot time the command used does not have the
"/" mount option. I have a feeling that the error is going to return
without an edit of the configs next time ureadahead is called at boot. I
don't know if this is the correct way to do it as I have not studied the
source to see how ureadahead determines the mount point when one is not
presented on the command line when it is called (the man just says it
assumes root). before I edit the configs I want to make sure that there
is not a setting somewhere that should be changes or if it should be
hard coded in the source. I am working 80/hrs a week right now so I
don't know when I would have time to look at it.

Just my ramblings on the subject. I hope it is of some help.

--
William H. Geiger III
Furniture Superstore
2600 N T St
Pensacola,FL 32505
850-438-6881
http://www.furniture-pensacola.com
<email address hidden>

On Sat, Mar 26, 2016, at 08:45 AM, dino99 wrote:
> @William
>
> thanks for the command; after a reboot the error is gone.
>
> note: from a terminal "sudo ureadahead --force-trace --verbose /" does
> nothing, but hitting ctrl+c has started the rebuilt.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1429098
>
> Title:
> systemd[1]: ureadahead.service fails on vanilla kernels, needs Ubuntu
> kernel patch
>
> Status in NULL Project:
> Confirmed
> Status in ureadahead package in Ubuntu:
> Triaged
>
> Bug description:
> dmesg:
> [ 4.717252] systemd[1]: ureadahead.service failed.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: systemd 219-4ubuntu3
> Uname: Linux 4.0.0-040000rc2-generic x86_64
> ApportVersion: 2.16.2-0ubuntu1
> Architecture: amd64
> CurrentDesktop: GNOME
> Date: Fri Mar 6 08:55:40 2015
> InstallationDate: Installed on 2014-09-25 (162 days ago)
> InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64
> (20140923)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
> ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-040000rc2-generic
> root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@
> quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf
> nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf
> nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
> init=/lib/systemd/systemd
> SourcePackage: systemd
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 04/15/2013
> dmi.bios.vendor: Phoenix Technologies Ltd.
> dmi.bios.version: P14AAJ
> dmi.board.asset.tag: Base Board Asset Tag
> dmi.board.name: SAMSUNG_NP1234567890
> dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> dmi.board.version: FAB1
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 9
> dmi.chassis.vendor: SAMSUNG ELECTRONICS CO....

Read more...

Revision history for this message
dino99 (9d9) wrote :

@#34

you are right, that command only provide a temporary solution. With the next boot, the error reappear.

Colin Watson (cjwatson)
no longer affects: null-and-void
Revision history for this message
Lucas Magasweran (lucasrangit) wrote :

A non-Ubuntu kernel doesn't have the required tracepoints and will result in the following error.

ureadahead: Error while tracing: No such file or directory

If you're not running a stock Ubuntu kernel you will need a patch [1] (worked on my 4.14 Debian kernel) or [2] (original patch). Unfortunately, these trace events will never be upstreamed [3].

[1] http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe&id=7744c33fdad887074a481fd4d21ccb6670ac62e6
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/462111
[3] https://patchwork.kernel.org/patch/9254717/

Changed in ureadahead (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.