2.6.17-mm4
In-Reply-To: <[email protected]>
Quoted 16 lines · Ingo Molnar
Quoted 1 line
+profile-likely-unlikely-macros.patch
CONFIG_PROFILE_LIKELYdoesnt quite work:Low memory ends at vaddr
f7e00000
node 0 will remap to vaddrf7e00000-f8000000High memory starts at vaddrf7e00000
found SMP MP-table at000f5680
NX (Execute Disable) protection: active
Unknown interrupt or fault at EIP 00000060c1d9f26400000002 Unknown interrupt or fault at EIP 00000060c01002950000f264Unknown interrupt or fault at EIP 00000060c010029500000294 Unknown interrupt or fault at EIP 00000060c010029500000294 Unknown interrupt or fault at EIP 00000060c010029500000294 Unknown interrupt or fault at EIP 00000060c010029500000294
Quoted 1 line
disabling it makes these go away.
Can you find out what source line belongs to c1d9f264?
arch/i386/kernel/head.S::ignore_int(), which produced those messages, is horribly broken. The first fault was likely a page fault attempting to write to some unmapped area. Since page fault pushes an error code onto the stack and ignore_int() doesn't pop it because it has no idea whether one is there, it attempts to return to cs:eip f264:00000002 which causes segment-not-present for segment index f264 in the GDT. Same thing then happens when _that_ tries to return to 0295:0000f264; now we are into infinite recursion. Eventually the stack will overflow and more fun errors will occur...
Is this worth fixing? We could get nice diagnostics for page fault here by writing a handler for early init code.
Signature · 2 lines
Chuck "You can't read a newspaper if you can't read." --George W. Bush
Quoted 34 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
Quoted 16 lines · Ingo Molnar
Quoted 1 line
+profile-likely-unlikely-macros.patch
CONFIG_PROFILE_LIKELYdoesnt quite work:Low memory ends at vaddr
f7e00000
node 0 will remap to vaddrf7e00000-f8000000High memory starts at vaddrf7e00000
found SMP MP-table at000f5680
NX (Execute Disable) protection: active
Unknown interrupt or fault at EIP 00000060c1d9f26400000002 Unknown interrupt or fault at EIP 00000060c01002950000f264Unknown interrupt or fault at EIP 00000060c010029500000294 Unknown interrupt or fault at EIP 00000060c010029500000294 Unknown interrupt or fault at EIP 00000060c010029500000294 Unknown interrupt or fault at EIP 00000060c010029500000294Quoted 1 line
disabling it makes these go away.
Can you find out what source line belongs to
c1d9f264?arch/i386/kernel/head.S::ignore_int(), which produced those messages, is horribly broken. The first fault was likely a page fault attempting to write to some unmapped area. Since page fault pushes an error code onto the stack and
ignore_int()doesn't pop it because it has no idea whether one is there, it attempts to return to cs:eip f264:00000002 which causes segment-not-present for segment index f264 in the GDT. Same thing then happens when _that_ tries to return to 0295:0000f264; now we are into infinite recursion. Eventually the stack will overflow and more fun errors will occur...
Quoted 2 lines
Is this worth fixing? We could get nice diagnostics for page fault here by writing a handler for early init code.
yes, it's worth fixing if it doesnt complicate that code too much - i run across such early init faults every couple of weeks when hacking various code. (Maybe just some generic 'dump 64 bytes of the top of the stack' would be enough too. Early-bootup is fragile enough already.)
Ingo