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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 15 Apr 2014 14:12:52 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Ulf Hansson <ulf.hansson@...aro.org>
CC:	Peter Maydell <peter.maydell@...aro.org>,
	Chris Ball <chris@...ntf.net>,
	Johan Rudholm <jrudholm@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Regression?] qemu-system-arm flooding "sd_write_data: not in
 Receiving-Data state"

On 04/15/2014 12:26 AM, Ulf Hansson wrote:
> On 15 April 2014 02:28, John Stultz <john.stultz@...aro.org> wrote:
>> $ qemu-system-arm -version
>> QEMU emulator version 1.5.0 (Debian 1.5.0+dfsg-3ubuntu5.3), Copyright
>> (c) 2003-2008 Fabrice Bellard
>>
>> Booting w/:
>> qemu-system-arm -kernel zImage-arm -M vexpress-a9 -cpu cortex-a9
>> -nographic -m 1024  -append 'root=/dev/mmcblk0p2 rw mem=1024M
>> raid=noautodetect console=ttyAMA0,38400n8 rootwait vmalloc=256MB
>> devtmpfs.mount=0' -sd test-arm.img -redir tcp:4300::22
>>
>> Let me know if you have any other questions or need any other info to
>> help trouble-shoot this.
> I am quite new to the qemu-system-arm model, I will need to spend some
> time with it to be able to help out more.
>
> Though, maybe you can provide me with some information about the qemu
> environment you are using?
>
> 1. Especially, what variant of the ARM primcell pl180 is being
> modelled/used here? The mmci driver handles a handful of different
> variants.

Not totally sure, honestly.

>From dmesg, the mmc related messages are:
mmci-pl18x mb:mmci: mmc0: PL181 manf 41 rev0 at 0x10005000 irq 41,42 (pio)
mmc0: new SDHC card at address 4567
mmcblk0: mmc0:4567 QEMU! 2.00 GiB
mmcblk0: p1 p2 p3 p4 < p5 p6 >


> 2. What type of mmc/sd card is being modelled/used here?

Not sure, other then if the SDHC bit above is enlightening. Is there
some other debug info (from sysfs or something) I can get to you to
answer these better?

I can also provide a .config and point you to similar disk images as I'm
using so you can reproduce if you'd like.

thanks
-john


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ