linux-kernel - Re: linux-next: Tree for May 30

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]

Message-ID: <20080601150710.GB27843@elte.hu>
Date:	Sun, 1 Jun 2008 17:07:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: linux-next: Tree for May 30


* Thomas Meyer <thomas@...3r.de> wrote:

> Am Freitag, den 30.05.2008, 18:19 +1000 schrieb Stephen Rothwell:
> > Hi all,
> > 
> > Changes since next-20080529:
> 
> Last next kernel booting for me is next-20080527. I didn't try 
> next-20080528, but next-20080529 and next-20080530 fail to boot.
> 
> Git told me to revert a63ef28f149c113740c7e429072351078a8821c6 (x86: 
> fix bootmem crash).
> 
> After reverting above commit, next-20080530 boots again.
> 
> Basicly I'm running Fedora 9 with the linux-next kernel.
> 
> See attached screenshot of boot error.

hm, that commit is gone in latest tip - does tip/master boot fine for 
you? It's:

   http://people.redhat.com/mingo/tip.git/README

that commit was an interim fix that got removed meanwhile and replaced 
with the real fixes.

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