Need advice on bad kernel 4.0 #5 but fine for 4.0 #4

Need advice on bad kernel 4.0 #5 but fine for 4.0 #4

Post by J Wuns » Tue, 23 May 2000 04:00:00




Quote:> Fatal trap 12: page fault while in kernel mode
> faul virtual address       = 0x0
> fault code         = supervisor read, page not present
> instruction pointer        = 0x8:0xc0f21dbb
> stack pointer              = 0x10:0xc8bdef10
> frame pointer              = 0x10:0xc8bdef2c
> Obviously ldconfig is trying to dereference a null pointer in kernel
> mode.

Well, ldconfig can't do this directly.  You could do a

nm /kernel | sort | more

...and try finding the symbol that precedes 0xc0f21dbb.  That'd be the
function the crash happens in.  Perhaps this gives us a clue.

Also, make sure your kernel modules are built from the same sources as
the kernel.  cd /sys/modules/; make all install ...

--
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

 
 
 

Need advice on bad kernel 4.0 #5 but fine for 4.0 #4

Post by James E. Qui » Wed, 24 May 2000 04:00:00





>> Fatal trap 12: page fault while in kernel mode
>> faul virtual address   = 0x0
>> fault code             = supervisor read, page not present
>> instruction pointer    = 0x8:0xc0f21dbb
>> stack pointer          = 0x10:0xc8bdef10
>> frame pointer          = 0x10:0xc8bdef2c

>> Obviously ldconfig is trying to dereference a null pointer in kernel
>> mode.

>Well, ldconfig can't do this directly.  You could do a

>nm /kernel | sort | more

>...and try finding the symbol that precedes 0xc0f21dbb.  That'd be the
>function the crash happens in.  Perhaps this gives us a clue.

>Also, make sure your kernel modules are built from the same sources as
>the kernel.  cd /sys/modules/; make all install ...

I already had done an nm and search but did not find anything reasonably near.
My first attempt to build just the modules failed with a missing include file
reference.  What did work was a make buildworld followed by installworld.
After that I decided to ease the debugging problem in the future by also
enabling dumpon/savecore and building a debug kernel as well.

Of course building the world before a new kernel cleared it up.

Thanks.

Now I just need a system that compiles much faster, so that I won't
get so lazy again in the future.  (Yeah, yeah, as if a buildworld
before going to bed the night before is that onerous.  I'm only
trying to justify another system purchase).
--
  ___ ___ | James E. Quick
   / /  / | Quick & Associates              NeXTMail O.K.
\_/ (_\/  | If only the HMO would cover my allergy to gravity.
       )  |

 
 
 

1. KStatusBar core dump - XFree86 4.0 + FreeBSD 4.0

Using kdevelop and a simple test application: clicking on File -> Close
results in a core dump.

The back trace looks as follows:

(gdb) bt
#0  0x283035a2 in QGList::first () from /usr/X11R6/lib/libqt.so
#1  0x281304f3 in KStatusBar::changeItem () from /usr/local/lib/libkdeui.so.3

    at ktest.cpp:596
#3  0x8052a8e in KtestApp::slotFileQuit (this=0x807db00) at ktest.cpp:528
#4  0x80533a9 in KtestApp::commandCallback (this=0x807db00, id_=10090)

Similar core dumps when exiting a KDE app happen at other places too.
Known problem ?

        -Arun

2. help with eth0

3. FreeBSD 4.0 moused vs XFree86 4.0

4. After Week 1 With Linux -- licking wounds.

5. Can't get XFree86 4.0 working on FBSD 4.0

6. LapTop

7. Linux 4.0 and NT 4.0

8. Announcing Splitvt 1.6.1

9. FreeBSD 4.0 : XFree86 4.0?

10. argh! mouse problem with freebsd 4.0/xfree 4.0

11. 4.0-20000430-STABLE vs. 4.0-STABLE

12. -= NT 4.0 Server for RedHat 4.0 =-

13. XFree86 4.0 and FreeBSD 4.0