From: Andrew Morton <akpm@linux-foundation.org>
To: "Dave Milter" <davemilter@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: Re: linux-2.6.23-mm1 crashed
Date: Sun, 14 Oct 2007 12:31:01 -0700 [thread overview]
Message-ID: <20071014123101.208b102b.akpm@linux-foundation.org> (raw)
In-Reply-To: <2a382c6e0710141224n2b8a47c8v1346f1a9dedc7943@mail.gmail.com>
(please don't top-post! edited...)
On Sun, 14 Oct 2007 23:24:39 +0400 "Dave Milter" <davemilter@gmail.com> wrote:
> On 10/14/07, Dave Milter <davemilter@gmail.com> wrote:
> > I build linux-2.6.23-mm1 and try to boot it using qemu,
> > and it crashed with trace like this:
> > do_page_fault
> > error_code
> > lock_acquire
> > _spin_lock_irqsave
> > gdth_timeout
> > run_timer_softirq
> > __do_softirq
> > do_softirq
> >
> > I have screenshot, but have no idea, is it legal to include it, if I
> > sent copy to lkml.
> > config of kernel in attachment,
> > I apply all three patches from hot-fixes.
> >
>
> By the way, because of oops happens on early stage of boot,
> you not need any image to reproduce this bug:
> something like this will be enough:
> 1)cd /tmp/ && qemu-img create hda.img 10M
> 2)cd linux/mm/source/code
> 3)qemu -kernel arch/i386/boot/bzImage -hda /tmp/hda.img
>
> if you add "-s" to qemu options you can after that do:
> gdb vmlinux
> $target remote localhost:1234
> $br gth_timeout
> $continue
>
I didn't notice that qemu was involved. Does qemu have an emulator for the
gdth hardware?
next prev parent reply other threads:[~2007-10-14 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 18:45 linux-2.6.23-mm1 crashed Dave Milter
2007-10-14 19:21 ` Andrew Morton
2007-10-14 22:26 ` James Bottomley
2007-10-14 19:24 ` Dave Milter
2007-10-14 19:31 ` Andrew Morton [this message]
2007-10-16 5:44 ` Dave Milter
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=20071014123101.208b102b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davemilter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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