linux-kernel - Regression: boot failure on AMD Elan TS-5500

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

Message-ID: <20080616121138.GA51097@atlantis.8hz.com>
Date:	Mon, 16 Jun 2008 12:11:39 +0000
From:	Sean Young <sean@...s.org>
To:	linux-kernel@...r.kernel.org
Cc:	Rusty Russell <rusty@...tcorp.com.au>
Subject: Regression: boot failure on AMD Elan TS-5500

The symptons are either a crash or reboot on booting the kernel. No printk's
have occurred yet -- even with early printk on.

2.6.15 worked on this board however current does not. I've bisected it to:

	commit a24e785111a32ccb7cebafd24b1b1cb474ea8e5d
	Author: Rusty Russell <rusty@...tcorp.com.au>
	Date:   Sun Oct 21 16:41:35 2007 -0700

	    i386: paravirt boot sequence
	    
	    This patch uses the updated boot protocol to do paravirtualized boot.
	    If the boot version is >= 2.07, then it will do two things:
	    
	     1. Check the bootparams loadflags to see if we should reload the
		segment registers and clear interrupts.  This is appropriate
		for normal native boot and some paravirtualized environments, but
		inapproprate for others.
	    
	     2. Check the hardware architecture, and dispatch to the appropriate
		kernel entrypoint.  If the bootloader doesn't set this, then we
		simply do the normal boot sequence.

Unfortunately this patch can't be reverse-applied onto mainline, so I've
tried it on 2.6.24-rc1. 2.6.24-rc1 as-is fails, but with this patch
reverted it does work.

This is the board: 

http://www.embeddedarm.com/products/board-detail.php?product=TS-5500

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