FAQ: [#7169] bonnie++ test may fail with atapi on bf548-ezkit(2012)

Document created by Aaronwu Employee on Sep 12, 2013
Version 1Show Document
  • View in full screen mode

[#7169] bonnie++ test may fail with atapi on bf548-ezkit

Submitted By: Vivi Li

Open Date

2012-06-26 03:57:56     Close Date

2012-09-04 05:37:18

Priority:

Medium     Assignee:

Sonic Zhang

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

Category:

N/A     Board:

EZKIT Lite

Processor:

BF548     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Rejected

Uboot version or rev.:

    Toolchain version or rev.:

gcc4.3-2012_Feb_15

App binary format:

N/A     

Summary: bonnie++ test may fail with atapi on bf548-ezkit

Details:

 

bonnie++ test may fail with atapi on bf548-ezkit.

 

Bellow is the log from regression machine:

--

mount /dev/sda2 /mnt/hd2

root:/> time bonnie++ -u root -d /mnt/hd2 -s 200M

Using uid:0, gid:0.

Writing a byte at a time...ata1: lost interrupt (Status 0x50)

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

ata1.00: failed command: WRITE DMA

ata1.00: cmd ca/00:08:fc:08:fa/00:00:00:00:00/e0 tag 0 dma 4096 out

         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ata1.00: status: { DRDY }

ata1: soft resetting link

ata1.00: configured for UDMA/66

ata1.00: device reported invalid CHS sector 0

ata1: EH complete

ata1: lost interrupt (Status 0x50)

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

ata1.00: failed command: WRITE DMA

ata1.00: cmd ca/00:08:fc:08:fa/00:00:00:00:00/e0 tag 0 dma 4096 out

         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ata1.00: status: { DRDY }

ata1: soft resetting link

ata1.00: configured for UDMA/66

ata1.00: device reported invalid CHS sector 0

ata1: EH complete

done

Writing intelligently...done

Rewriting...attempt to access beyond end of device

sda2: rw=0, want=134744080, limit=40965750

attempt to access beyond end of device

sda2: rw=0, want=134744080, limit=40965750

Boatite mpat itoI a ccres s eberyoende e)nd of device

: sndat2:u ruw=e0,o w

ant=134744080, limit=40965750

attempt to access beyond end of device

sda2: rw=0, want=134744080, limit=40965750

attempt to access beyond end of device

sda2: rw=0, want=134744080, limit=40965750

attempt to access beyond end of device

sda2: rw=0, want=134744080, limit=40965750

attempt to access beyond end of device

sda2: rw=0, want=134744080, limit=40965750

attempt to access beyond end of device

--

 

Bellow is my result by manul test:

--

root:/> time bonnie++ -u root -d /mnt/ -s 50M

Using uid:0, gid:0.

Writing a byte at a time...ata1: lost interrupt (Status 0x50)

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

ata1.00: failed command: WRITE DMA

ata1.00: cmd ca/00:08:fc:08:fa/00:00:00:00:00/e0 tag 0 dma 4096 out

         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ata1.00: status: { DRDY }

ata1: soft resetting link

ata1.00: configured for UDMA/66

ata1.00: device reported invalid CHS sector 0

ata1: EH complete

ata1: lost interrupt (Status 0x50)

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

ata1.00: failed command: WRITE DMA

ata1.00: cmd ca/00:08:fc:08:fa/00:00:00:00:00/e0 tag 0 dma 4096 out

         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

ata1.00: status: { DRDY }

ata1: soft resetting link

ata1.00: configured for UDMA/66

ata1.00: device reported invalid CHS sector 0

ata1: EH complete

done

Writing intelligently...done

Rewriting...done

Reading a byte at a time...done

Reading intelligently...done

start 'em...done...EXT2-fs (sda2): error: ext2_check_page: bad entry in directory #2: : rec_len is smaller than minimal - offset0

done...done...done...done...

Create files in sequential order...Can't make directory ./Bonnie.327

Cleaning up test directory after error.

Bonnie: drastic I/O error (rmdir): No such file or directory

Command exited with non-zero status 1

real    2m 26.02s

user    0m 15.29s

sys     1m 27.01s

root:/>

--

 

Follow-ups

 

--- Vivi Li                                                  2012-07-04 02:53:40

Add a patch in build script to change BFIN_MAX_SG_SEGMENTS to 1 in bf54x atapi

driver. Check later to see the result.

 

--- Vivi Li                                                  2012-07-27 03:01:49

This bug still exists after this patch is applied. So revert this patch as it's

not useful.

U-boot is updated to latest and this bug seems to disappear after 90 rounds of

test. Though bonnie++ failed 5 times with different error. It simply hangs in

the middle of bonnie++ and kernel reboots.

 

--- Vivi Li                                                  2012-09-04 06:35:21

This bug disappeared after I replaced the power supply of bf548-ezkit in

regression machine.

Power problem, not a bug. So close it.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

config.config.atapi_hd    application/octet-stream    51589    Vivi Li

config.linux.atapi_hd    application/octet-stream    45757    Vivi Li

Outcomes