linux-kernel - Re: AMD 64 Box is not able to boot with latest -tip

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: <20090308095952.GA12298@elte.hu>
Date:	Sun, 8 Mar 2009 10:59:52 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...nel.org>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: AMD 64 Box is not able to boot with latest -tip


* Jaswinder Singh Rajput <jaswinder@...nel.org> wrote:

> Hello Peter,
> 
> On Sat, 2009-03-07 at 17:02 -0800, H. Peter Anvin wrote:
> > Jaswinder Singh Rajput wrote:
> > > My AMD 64 Box was not able to boot with latest -tip and kernel is
> > > dumping.
> > > 
> > > Because of hot weather and not proper cooling I cannot debug the problem
> > > so only thing I can tell is:
> > > 
> > > BAD : cb553adb4e83bc
> > > 
> > > Good : f0ef03985130287c6c
> > > 
> > 
> > You realize you left absolutely no usable information in that post, I
> > hope... not a single bit of detail about the system other than it having
> > an AMD CPU.
> 
> Oops, I have send my configs file and other related info 
> various times to LKML and Ingo.

You should attach such information to every separate new 
bugreport.

> Anyhow now I made a git tree for it ;)
> 
> http://git.kernel.org/?p=linux/kernel/git/jaswinder/kernel-cfgs.git;a=summary

that's not very useful for a quick review on lkml. Also, kernel 
configs change between kernel versions so that link can go 
stale. So it's always useful to attach the very config you saw a 
breakage with to the bugreport.

You say that the "kernel dumps" - does this mean you got a 
kernel oops during bootup? If possible you should try to capture 
the first oops/warning that triggers either via a serial console 
or via a digital camera. pause_on_oops=10000 can be useful too 
to make sure you capture the first oops in its entirety.

	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/