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
Code: 89 01 81 3d 54 46 3e c0 ad de 74 0b 0f 0b 4a 00 a0 50
I'm attaching my kernel config (file called config)
I'm also attaching a boot log from my 2.4.19 boot so you can see my system setup. (file called x)
Please let me know if you need any more information.
Chris
On Sun, 29 Sep 2002 [email protected] 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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[email protected] 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
>
> Code: 89 01 81 3d 54 46 3e c0 ad de 74 0b 0f 0b 4a 00 a0 50
This has to do with isapnp. I have the same problem with isapnp
compiled in. In my case the kernel just detected the sound chip on the
motherboard. Not compiling isapnp makes the oops disappear.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9l6Lw2ijCOnn/RHQRAvFdAJ0ddM+2ozcQiFPLx+5J9J/9+qkIFACfW4Mf
RWA4yBXOf6znqgq9nUeryOk=
=OocT
-----END PGP SIGNATURE-----