This has happend to me atleast 12 times in the last 2 months. This oops comes from yesterday. Unable to handle kernel NULL pointer dereference at virtual address 0000010e printing eip: c01c1d02 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c01c1d02>] Tainted: P EFLAGS: 00010246 eax: 00000000 ebx: ffffffe8 ecx: c02e7324 edx: c02ebbc0 esi: cbe58d80 edi: cf770c00 ebp: 00000000 esp: c7083e70 ds: 0018 es: 0018 ss: 0018 Process python2.2 (pid: 28412, stackpage=c7083000) Stack: 00000000 cc463e50 000004ea 00000000 c01d792c cf770c00 00000000 048dd0a6 00000000 00000000 c7083ef8 00000000 00000000 cc463e68 00000008 cc463e50 cc464840 00000008 00000008 cc80c19c 00000000 00000008 c01dbc03 cc463e68 Call Trace: [<c01d792c>] [<c01dbc03>] [<c01e6a04>] [<c013b0c3>] [<c013b807>] [<c013ae1d>] [<c013baaa>] [<c013be65>] [<c0138e89>] [<c0131f83>] [<c010872b>] Code: 66 83 bb 26 01 00 00 00 75 10 80 a3 18 01 00 00 f7 53 e8 07 This one comes from 7 days ago: Unable to handle kernel NULL pointer dereference at virtual address 0000010e printing eip: c01c1d02 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c01c1d02>] Tainted: P EFLAGS: 00010246 eax: 00000000 ebx: ffffffe8 ecx: c02e7324 edx: c02ebbc0 esi: c23ae480 edi: cf777c00 ebp: 00000000 esp: c4123e70 ds: 0018 es: 0018 ss: 0018 Process python2.2 (pid: 16785, stackpage=c4123000) Stack: 00000000 cc3079a0 00000657 00000000 c01d792c cf777c00 00000000 048dd0a6 00000000 00000000 c4123ef8 00000000 00000000 cc3079b8 00000008 cc3079a0 cc2fe340 00000008 00000008 c369549c 00000000 00000008 c01dbc03 cc3079b8 Call Trace: [<c01d792c>] [<c01dbc03>] [<c01e6a04>] [<c013b0c3>] [<c013b807>] [<c013ae1d>] [<c013baaa>] [<c013be65>] [<c0138e89>] [<c0131f83>] [<c010872b>]
Code: 66 83 bb 26 01 00 00 00 75 10 80 a3 18 01 00 00 f7 53 e8 07 Both the Code and The "Unable to handle kernel NULL pointer dereference at virtual address 0000010e" are the same and this only happens when I am compiling some thing with portage.
what kernel version
2.4.19-xfs-r1
wow, that is weird as hell... do you have the time to test the new unmasked xfs-sources-2.4.19-r2? Much fixage over -r1 (including a new snapshot from teh XFS people)
All i've got is time...compiling now
Still an issue ?
I am now using the AA sources and this doesn't happen anymore....so no, it isn't an issue for me anymore.
Brandon, closing ...