linux-kernel - Re: linux-next: Apr 27

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] [day] [month] [year] [list]

Message-ID: <20100428151838.GA2772@osiris.boeblingen.de.ibm.com>
Date:	Wed, 28 Apr 2010 17:18:38 +0200
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Sachin Sant <sachinp@...ibm.com>
Cc:	linux-s390@...r.kernel.org,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Apr 27 - S390 boot failure.

On Wed, Apr 28, 2010 at 11:50:09AM +0530, Sachin Sant wrote:
> Yesterday's -next (20100427) fails to boot on a s390.
> Here is the boot log.
> [...]
> 01: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial C
> PU reset from CPU 00.
> 02: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial C
> PU reset from CPU 00.
> 03: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial C
> PU reset from CPU 00.
> 
> At this point the boot process just hangs. Previous -next build
> (20100415) worked fine.
> Have attached the .config

Yes, I got several reports about this. The patch "improve irq tracing code
in entry[64].S" was broken for !CONFIG_PREEMPT. I fixed it and pushed out
a new version.
Should be fixed with tomorrow's linux-next.

Thanks for reporting!
--
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/