lkml.org 
[lkml]   [2009]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [Bugme-new] [Bug 13850] New: reading /proc/kcore causes oops
    From
    > What's layout of memory does your server have ?
    The log I gave was from my desktop, so I'll assume you wanted that
    instead of the server:
    [mike: mike in ~]$ grep "System RAM" /proc/iomem
    00010000-0009efff : System RAM
    00100000-1dedffff : System RAM

    > If so, can you please help work out where it crashed?
    I didn't compile the kernel myself; it's the stock Arch Linux kernel,
    which may explain the following useless output (this was the only file
    I could find called vmlinux):
    [mike: mike in /usr/src/linux-2.6.30-ARCH]$ addr2line -e vmlinux 0xc0224dd1
    kcore.c:0
    [mike: mike in /usr/src/linux-2.6.30-ARCH]$ gdb vmlinux
    GNU gdb 6.8
    Copyright (C) 2008 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "i686-pc-linux-gnu"...
    (no debugging symbols found)
    (gdb) l *0xc0224dd1
    No symbol table is loaded. Use the "file" command.


    I'll compile a minimal kernel later with debug symbols and see if I
    can reproduce it on that.


    \
     
     \ /
      Last update: 2009-07-29 04:49    [W:0.045 / U:95.864 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site