| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080620111553.GC21835@fluff.org.uk> Date: Fri, 20 Jun 2008 12:15:53 +0100 From: Ben Dooks <ben-linux@...ff.org> To: linux-kernel@...r.kernel.org, drzeus-mmc@...eus.cx Subject: MMC test driver - help with output I'm testing the s3c24xx sd/mmc driver and can't find any documentation for each of the tests the mmc_test driver is doing. The following is output from a recent linux-next+driver: [root@ ~]# echo > /sys/class/mmc_host/mmc0/mmc0\:0001/test mmc0: Starting tests of card mmc0:0001... mmc0: Test case 1. Basic write (no data verification)... mmc0: Result: OK mmc0: Test case 2. Basic read (no data verification)... mmc0: Result: OK mmc0: Test case 3. Basic write (with data verification)... mmc0: Result: OK mmc0: Test case 4. Basic read (with data verification)... mmc0: Result: OK mmc0: Test case 5. Multi-block write... mmc0: Warning: Host did not wait for busy state to end. mmc0: Result: OK mmc0: Test case 6. Multi-block read... mmc0: Result: OK mmc0: Test case 7. Power of two block writes... mmc0: Result: UNSUPPORTED (by card) mmc0: Test case 8. Power of two block reads... s3c2440-sdi s3c2440-sdi: unfinished read - pio_count:[0] pio_words:[0] mmc0: Result: UNSUPPORTED (by host) => probably the wrong error being returned, but what would be the general problem with this causing a finish before the driver has decided that there should have been data to read? mmc0: Test case 9. Weird sized block writes... mmc0: Result: UNSUPPORTED (by card) mmc0: Test case 10. Weird sized block reads... s3c2440-sdi s3c2440-sdi: unfinished read - pio_count:[0] pio_words:[0] mmc0: Result: UNSUPPORTED (by host) mmc0: Test case 11. Badly aligned write... mmc0: Result: OK mmc0: Test case 12. Badly aligned read... mmc0: Result: OK mmc0: Test case 13. Badly aligned multi-block write... mmc0: Warning: Host did not wait for busy state to end. mmc0: Warning: Host did not wait for busy state to end. mmc0: Warning: Host did not wait for busy state to end. mmc0: Result: OK mmc0: Test case 14. Badly aligned multi-block read... mmc0: Result: OK mmc0: Test case 15. Correct xfer_size at write (start failure)... s3c2440-sdi s3c2440-sdi: bad data crc (incoming) => is this sort of error what was exepected? mmc0: Result: ERROR (-84) mmc0: Test case 16. Correct xfer_size at read (start failure)... s3c2440-sdi s3c2440-sdi: data timeout mmc0: Result: OK => is this the expected response? mmc0: Test case 17. Correct xfer_size at write (midway failure)... s3c2440-sdi s3c2440-sdi: bad data crc (incoming) mmc0: Result: ERROR (-84) mmc0: Test case 18. Correct xfer_size at read (midway failure)... s3c2440-sdi s3c2440-sdi: data timeout mmc0: Result: OK mmc0: Tests completed. [root@ ~]# Also, any indications of how the "busy state" warnings could be debugged? -- Ben (ben@...ff.org, http://www.fluff.org/) 'a smiley only costs 4 bytes' -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists