linux-kernel - Re: linux-next: Tree for Dec 16

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:	Mon, 15 Dec 2014 22:55:02 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andy Lutomirski <luto@...capital.net>,
	James Hogan <james.hogan@...tec.com>,
	linux-metag@...r.kernel.org
Subject: Re: linux-next: Tree for Dec 16

On 12/15/2014 10:44 PM, Andrew Morton wrote:
> On Mon, 15 Dec 2014 22:35:49 -0800 Guenter Roeck <linux@...ck-us.net> wrote:
>
>> On Tue, Dec 16, 2014 at 03:46:22PM +1100, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any code destined for v3.20 to your linux-next included
>>> trees/branches until after v3.19-rc1 is released.
>>>
>>> Changes since 20141215:
>>>
>>> The infiniband tree gained a conflict against Linus' tree and a build
>>> failure so I used the version from next-20141215.
>>>
>>> The userns tree gained a conflict against the vfs tree.
>>>
>>> The clk tree gained a build failure so I used the version from
>>> next-20141215.
>>>
>>> Non-merge commits (relative to Linus' tree): 3588
>>>   2582 files changed, 123494 insertions(+), 135748 deletions(-)
>>>
>>
>> My metag buildbot test fails with this kernel.
>
> Thanks.  What are the error messages?
>
>
Nothing. It just hangs until killed.

qemu log:
char device redirected to /dev/pts/5
Unable to load ROM!
qemu: terminating on signal 15 from pid 17843

http://server.roeck-us.net:8010/builders/qemu-metag-next/builds/60/steps/qemubuildcommand/logs/stdio

Normally output would be similar to the following.

/opt/buildbot/bin/qemu-system-meta -display none -kernel vmlinux -device da,exit_threads=1 -chardev stdio,id=chan1 -chardev pty,id=chan2 -append "rdinit=/sbin/init"
char device redirected to /dev/pts/29
Unable to load ROM!
Linux version 3.18.0+ (groeck@...ver.roeck-us.net) (gcc version 4.2.4 (IMG-1.4.0.300)) #5 Mon Dec 15 22:50:31 PST 2014
LNKGET/SET go through cache but CONFIG_METAG_LNKGET_AROUND_CACHE=y
DA present
...

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/