linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Mochel <mochel@osdl.org>
To: cwhmlist@bellsouth.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.39 oops
Date: Sun, 29 Sep 2002 18:07:16 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209291803090.18550-100000@cherise.pdx.osdl.net> (raw)
In-Reply-To: <20020930005203.GUNU26495.imf20bis.bellsouth.net@localhost>


On Sun, 29 Sep 2002 cwhmlist@bellsouth.net wrote:

> I am having a 2.5.39 oops on boot up.  Here is what I have been able to gleen from the bootstrap screen:
> 
> printing eip:
> c0218f17
> *pde = 00000000
> Oops: 0002
> 
> CPU: 1
> EIP: 0060:[<c0218f17>] Not tainted
> EFLAGS: 00010282
> EIP is at attach+0x63/0xb8
> eax: c13a409c ebx: c03e4650 ecx: 00000000 edx: c03f0b68
> esi: c13a4084 edi: c03e4650 ebp: 00000000 esp: c13dff84
> ds: 0068 es: 0068 ss 0068
> Process swapper (pid: 1, threadinfo=c13de000 task=c13e0080)
> Stack: 00000000 c13a408c c0219027 c13a4084 c13a4084 c02193ab c13a4084 c13a4084
>        c128aa4c c03f09c0 c128aa0c 00000001 c0416cb0 c13a4084 c04234e0 00000000
>        00000000 00000000 c128aa4c 00000000 c0402866 c13de000 c040288c c0105101
> Call Trace:
>  [<c0219027>device_attach+0x33/0x3c
>  [<c02193ab>device_register+0x173/0x260
>  [<c0105101>init+0x75/0x214
>  [<c010508c>init+0x0/0x214
>  [<c01055a1>kernel_thread_helper+ox5/0xc


There is a bug involving isapnp devices. A band-aid patch is available 
here:

http://marc.theaimsgroup.com/?l=linux-kernel&m=103331915631837&w=2

Please try that until I can look into a better solution..

Thanks,

	-pat


  parent reply	other threads:[~2002-09-30  1:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30  0:52 2.5.39 oops cwhmlist
2002-09-30  1:03 ` Ulrich Drepper
2002-09-30  1:07 ` Patrick Mochel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-29 16:40 Arador

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=Pine.LNX.4.44.0209291803090.18550-100000@cherise.pdx.osdl.net \
    --to=mochel@osdl.org \
    --cc=cwhmlist@bellsouth.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;
as well as URLs for NNTP newsgroup(s).