Bug 8985

Summary:	Parselogs error: FAT-fs (sdb1): Directory bread failed on NUC
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Cristina Agurida <cristina-danielax.agurida>
Component:	bsps-runtime	Assignee:	Cristina Agurida <cristina-danielax.agurida>
Status:	VERIFIED NOTABUG	QA Contact:	Cristina Agurida <cristina-danielax.agurida>
Severity:	normal
Priority:	Medium	CC:	alexandru.c.georgescu, costin.c.constantin, jianxun.zhang, sgw, yp.kernel.watcher, yp.watcher
Version:	2.0.1
Target Milestone:	2.1 M3
Hardware:	NUC
OS:	x86_64
Whiteboard:	Possible backport 2.0.2
OS type for building Yocto:	---	Type of Regression:	Regression (Used to work)
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Cristina Agurida 2016-01-22 12:53:34 UTC

STATUS: FAILED
BUILD: 2.0.1_RC2:dd0ba9ea4a11ab15348d4fe3574e4b28784db82f
ENVIRONMENT: genericx86-64 on NUC
STEPS TO REPRODUCE: 
  
 Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc.
Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.



EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:

This error appears:

Central error: [ 1852.760822] FAT-fs (sdb1): Directory bread(block 29786) failed
| ***********************
| [ 1852.736934] usb 1-2: USB disconnect, device number 5
| [ 1852.758172] FAT-fs (sdb1): FAT read failed (blocknr 32)
| [ 1852.760799] FAT-fs (sdb1): Directory bread(block 29778) failed
| [ 1852.760812] FAT-fs (sdb1): Directory bread(block 29779) failed
| [ 1852.760814] FAT-fs (sdb1): Directory bread(block 29780) failed
| [ 1852.760816] FAT-fs (sdb1): Directory bread(block 29781) failed
| [ 1852.760817] FAT-fs (sdb1): Directory bread(block 29782) failed
| [ 1852.760818] FAT-fs (sdb1): Directory bread(block 29783) failed
| [ 1852.760820] FAT-fs (sdb1): Directory bread(block 29784) failed
| [ 1852.760821] FAT-fs (sdb1): Directory bread(block 29785) failed
| [ 1852.760822] FAT-fs (sdb1): Directory bread(block 29786) failed
| [ 1852.760824] FAT-fs (sdb1): Directory bread(block 29787) failed
| [ 1852.773097] FAT-fs (sdb1): FAT read failed (blocknr 32)
| [ 3359.315011] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
| [ 7021.846779] Hello world!
| [ 7022.162533] Cleaning up hellomod.

Comment 1 Cristina Agurida 2016-01-25 10:03:02 UTC

The image used or testing was core-image-sato-sdk and can be found at the following link: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc2/machines/genericx86-64/core-image-sato-sdk-genericx86-64.hddimg

Comment 2 Saul Wold 2016-01-25 17:44:37 UTC

This looks like bad USB stick, can you reproduce this regularly?  Did you try a different USB device?

Comment 3 Jianxun Zhang 2016-01-26 00:15:34 UTC

Investigated this issue a little bit today. I downloaded and flashed image to a USB stick and use it to live-boot Minnow Max (I don't have NUC). Assuming this test involves another external USB stick (we don't have sdb in live boot session or a real installation for "internal" drives), I insert another USB stick and it can be mounted successfully although kernel detects that disk was not amounted correctly before which should be a specific case not related to this bug. I don't see the failed message in kernel log either.

I have to assign this back to reporter. Please feel free to assign this back to me with the below info necessary to process this bug:

() The detailed test procedure to reproduce this issue. Please also confirm you can see this issue consistently with another working USB drive.

() Please provide full kernel log for the failure. There is a USB disconnection happened right before the error messages but we don't know if this is from same USB device.

Thanks

Comment 4 Jianxun Zhang 2016-01-28 17:13:51 UTC

Change status to "Need info" based on my previous comment.

Comment 5 Costin 2016-02-15 15:29:31 UTC

Hello,

The issue described in the first comment is the result of a local hardware glitch. Never happened before.

Will just close the issue as invalid

Comment 6 Costin 2016-02-15 15:30:06 UTC

marking as resolved

Comment 7 Cristina Agurida 2016-02-15 15:31:46 UTC

On behalf of the discussion with Costin set is as verified.