public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: bcorsello@usa.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM:  kernel oops on boot in 2.4.0 test10
Date: Sat, 04 Nov 2000 18:07:33 -0500	[thread overview]
Message-ID: <3A0496B5.3B298B6F@mandrakesoft.com> (raw)
In-Reply-To: <0d19638042204b0NYCSMTP1@nyc.rr.com>

Brad Corsello wrote:
> 
> [1.] One line summary of the problem:
>         kernel oops on boot in 2.4.0 test 10 (i386)
> 
> [2.] Full description of the problem/report:
>         On every boot of test 10, I get a kernel oops very early on.
>         Is reproducible (happens every boot).
>         I've successfully booted 2.3 kernels on this machine, but get this
>         kernel oops on boot every time with the later 2.4.0tests (from about
>         test5 on -- that's from memory, may not be accurate).
>         I am successfully running a late 2.2 kernel:  Linux version 2.2.15-4mdk
> (chmou@kenobi.mandrakesoft.com) (gcc version 2.95.3 19991030 (prerelease)) #1
> Wed May 10 15:31:30 CEST 2000

Can you play the kernel shuffle, and narrow down exactly which kernel
version breaks for you?  Read, from the linux source tree,
Documentation/BUG-HUNTING.


> [5.] Output of Oops.. message (if applicable) with symbolic information =
>      resolved (see Documentation/oops-tracing.txt)
> ksymoops 2.3.4 on i586 2.2.15-4mdk.  Options used
>      -v /usr/src/linux/vmlinux (specified)
>      -K (specified)
>      -L (specified)
>      -O (specified)
>      -m /usr/src/linux/System.map (specified)

Are you certain you used the correct vmlinux and System.map here?  Can
you present your .config for kernel building?

> Trace; c0194d36 <isapnp_proc_attach_device+36/94>

Do you have any ISAPNP cards in your system?

-- 
Jeff Garzik             | Dinner is ready when
Building 1024           | the smoke alarm goes off.
MandrakeSoft            |	-/usr/games/fortune
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-04 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-04 21:55 PROBLEM: kernel oops on boot in 2.4.0 test10 Brad Corsello
2000-11-04 23:07 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-06  4:31 Brad Corsello
2000-11-06 16:30 Brad Corsello

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=3A0496B5.3B298B6F@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=bcorsello@usa.net \
    --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