public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Drynoff <pauldrynoff@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.18-rc1-mm1: as usual can not boot
Date: Wed, 12 Jul 2006 11:37:18 +0400	[thread overview]
Message-ID: <20060712113718.8e5e3af7.pauldrynoff@gmail.com> (raw)
In-Reply-To: <20060712001232.a31285e3.akpm@osdl.org>

On Wed, 12 Jul 2006 00:12:32 -0700
Andrew Morton <akpm@osdl.org> wrote:

> On Wed, 12 Jul 2006 09:59:33 +0400
> Paul Drynoff <pauldrynoff@gmail.com> wrote:
> 
> > I try boot 2.6.18-rc1-mm1,
> > here is result:
> > 
> > show_stack_log_lve
> > show_registers
> > die
> > do_trap
> > do_invalid_op
> > error_code
> > buffered_rmqueue
> > get_page_from_freelist
> > __alloc_pages
> > get_zeroed_page
> > sysenter_setup
> > identify_cpu
> > check_bugs
> > start_kernel
> > 
> > EIP:... prep_new_page
> 
> Don't know, sorry.  Your config works ok here (well, gets a lot further).
> 
> It's dying quite late in boot there - the page allocator has already been
> used a bit, but then it falls over in a heap.
> 
> I notice you're set up for an i386.  Is the target CPU really an i386?  If
> not, and if you change this, does it affect anything?

My CPU is:
$ cat /proc/cpuinfo 
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 10
model name      : AMD Athlon(tm) XP 2600+
stepping        : 0
cpu MHz         : 1913.456
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow ts
bogomips        : 3833.86


First of all I booted with Athlon/Duron/K7 option,
and get this error.
After that I rebuild it as i386,
nothing changed.
I rebuild it with gcc-4.1.1 instead of gcc-3.3.6.
Nothing changed.

But the more interesting thing, that when I try this kernel with qemu (0.8.1),
I got the same error. Sorry, I can not sent it image, it is too big: 3 GB.

But I can sent screenshots or gdb output if somebody interesting.

  reply	other threads:[~2006-07-12  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  5:59 [BUG] 2.6.18-rc1-mm1: as usual can not boot Paul Drynoff
2006-07-12  7:12 ` Andrew Morton
2006-07-12  7:37   ` Paul Drynoff [this message]
     [not found]     ` <1152690358.3217.20.camel@laptopd505.fenrus.org>
2006-07-12  8:17       ` Paul Drynoff
2006-07-12 12:46         ` Arjan van de Ven
2006-07-12 14:28           ` Paul Drynoff
2006-07-12  9:27   ` [BUG] 2.6.18-rc1-mm1: the simple way to reproduce it Paul Drynoff
2006-07-13  3:49     ` Andrew Morton

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=20060712113718.8e5e3af7.pauldrynoff@gmail.com \
    --to=pauldrynoff@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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