linux-kernel - Re: Microblaze image hanging in qemu with 3.15-rc

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 23 Apr 2014 06:38:14 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	monstr@...str.eu
CC:	linux-kernel@...r.kernel.org
Subject: Re: Microblaze image hanging in qemu with 3.15-rc

On 04/22/2014 10:32 PM, Michal Simek wrote:
> Hi Guenter,
>
>
> On 04/22/2014 07:23 PM, Guenter Roeck wrote:
>> Hi all,
>>
>> when trying to run a microblaze image with 3.15-rc1 or 3.15-rc2 in qemu,
>> I get the following hangup. This used to work with earlier kernels
>> with the same configuration.
>>
>> Is this a known problem, or is something wrong with my configuration
>> or with my qemu command line ?
>
> Is this BE/LE version? Which qemu do you use?

BE.

file vmlinux:

vmlinux: ELF 32-bit MSB  executable, version 1 (SYSV), statically linked, BuildID[sha1]=5e1872c08df2956eddaed6fc1f6528a8540375b7, not stripped

qemu-system-microblaze --version:

QEMU emulator version 1.7.0, Copyright (c) 2003-2008 Fabrice Bellard

gcc --version:

microblaze-linux-gcc (GCC) 4.8.0
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

> There is endian autodetection in timer and intc driver
> which can caused this problem.
>
Is this new code ? I didn't see the problem in 3.13 (same compile options,
same configuration, same compiler, same qemu version).

Thanks,
Guenter

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