Bug 10424 - filesystem I/O errors
Summary: filesystem I/O errors
Status: RESOLVED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: kernel (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Undecided critical
Target Milestone: ---
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-10-13 10:44 UTC by Jussi Kukkonen
Modified: 2016-10-13 11:12 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
dmesg (37.18 KB, application/octet-stream)
2016-10-13 10:44 UTC, Jussi Kukkonen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jussi Kukkonen 2016-10-13 10:44:51 UTC
Created attachment 3472 [details]
dmesg

Not sure if this is a kernel issue but Running genericx86-64 core-image-sato  on a NUC (booted from USB) I found I can't launch apps: desktop tries to start them but e.g. for gtk-play says:

    failed to execute child process "gtk-play" (Input/output error)

Starting matchbox-terminal from console:

    blk_update_request: I/O error, dev loop0, sector 142824
    segmentation fault

I also see this in message log:

WARNING: CPU: 1 PID: 374 at /mnt/extra-ssd/tmp/work-shared/genericx86-64/kernel-source/fs/fs-writeback.c:2154 __mark_inode_dirty+0x2fc/0x420failed 
bdi-block not registered
Modules linked in: bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core efivars snd_pcm x86_pkg_temp_thermal snd_timer
CPU: 1 PID: 374 Comm: loop0 Not tainted 4.8.0-yocto-standard #1
Hardware name:                  /D54250WYK, BIOS WYLPT10H.86A.0030.2014.0919.1139 09/19/2014
 0000000000000000 ffff88021438bb68 ffffffff813bbf7a ffff88021438bbb8
 0000000000000000 ffff88021438bba8 ffffffff8105814b 0000086a1438bbc0
 0000000000000001 ffff880213dd8088 ffff88021469cd68 0000000000000000
Call Trace:
 [<ffffffff813bbf7a>] dump_stack+0x4d/0x63
 [<ffffffff8105814b>] __warn+0xcb/0xf0
 [<ffffffff810581bf>] warn_slowpath_fmt+0x4f/0x60
 [<ffffffff811aac19>] ? locked_inode_to_wb_and_lock_list+0x69/0x160
 [<ffffffff811ac99c>] __mark_inode_dirty+0x2fc/0x420
 [<ffffffff8119a8b9>] generic_update_time+0x79/0xd0
 [<ffffffff8119c0d8>] touch_atime+0x88/0xa0
 [<ffffffff81125510>] generic_file_read_iter+0x600/0x6e0
 [<ffffffff8108484a>] ? update_curr+0x8a/0x130
 [<ffffffff8117eeef>] vfs_iter_read+0x7f/0xd0
 [<ffffffff815bf216>] loop_queue_work+0x3b6/0xa70
 [<ffffffff8108d753>] ? pick_next_task_fair+0xc3/0x450
 [<ffffffff8107be9e>] ? finish_task_switch+0x8e/0x1c0
 [<ffffffff81075582>] kthread_worker_fn+0xb2/0x170
 [<ffffffff810754d0>] ? kthread_create_on_node+0x180/0x180
 [<ffffffff81075709>] kthread+0xc9/0xe0
 [<ffffffff8191954f>] ret_from_fork+0x1f/0x40
 [<ffffffff81075640>] ? kthread_worker_fn+0x170/0x170
---[ end trace 9cc21ea4175e49c9 ]---
blk_update_request: I/O error, dev loop0, sector 142808
blk_update_request: I/O error, dev loop0, sector 142824
blk_update_request: I/O error, dev loop0, sector 142824
blk_update_request: I/O error, dev loop0, sector 165096
blk_update_request: I/O error, dev loop0, sector 165096
blk_update_request: I/O error, dev loop0, sector 142824



mount looks like this:

proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /dev type devtmpfs (rw,relatime,size=4040092k,nr_inodes=1010023,mode=755)
/dev/sda1 on /media/sda1 type ext4 (rw,relatime,data=ordered)
/dev/sdb on /media/realroot type vfat (rw,relatime,gid=6,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on / type ext4 (rw,noatime,nodiratime,data=ordered)
tmpfs on /mnt/.psplash type tmpfs (rw,relatime,size=40k)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sdc on /run/media/sdc type vfat (rw,relatime,gid=6,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Comment 1 Jussi Kukkonen 2016-10-13 11:12:50 UTC
I still think this is a kernel bug, just not in a yocto kernel: I rebooted my build machine and now the same images written to the same USB stick boot just fine...

Closing as NOTABUG for now, if this reappears and looks like a yocto issue I'll reopen.