From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: "H. Peter Anvin" <hpa@kernel.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: AMD 64 Box is not able to boot with latest -tip
Date: Sun, 8 Mar 2009 10:59:52 +0100 [thread overview]
Message-ID: <20090308095952.GA12298@elte.hu> (raw)
In-Reply-To: <1236498137.2807.5.camel@ht.satnam>
* Jaswinder Singh Rajput <jaswinder@kernel.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
prev parent reply other threads:[~2009-03-08 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 15:51 AMD 64 Box is not able to boot with latest -tip Jaswinder Singh Rajput
2009-03-08 1:02 ` H. Peter Anvin
2009-03-08 7:42 ` Jaswinder Singh Rajput
2009-03-08 9:59 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090308095952.GA12298@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@kernel.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox