lkml.org 
[lkml]   [2011]   [May]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: How to get backtrace? modprobe -r iwlagn; modprobe iwlagn kills kernel
    From
    On Wed, May 18, 2011 at 11:55 PM, Milton Miller <miltonm@bga.com> wrote:
    > On Wed May 18 2011 about 10:37:54 EST, Stevie Trujillo wrote:
    >> I'm having some problem getting a backtrace. When I do "modprobe -r
    >> iwlagn; modprobe iwlagn" (2.6.38.6 with Intel-1030N) the kernel crashes
    >> (sometimes I need to try 2 or 3 times, and sometimes the modprobe -r
    >> is the one that crashes).
    >>
    >> This spams my monitor with several oops/panics before it finally
    >> dies. I can only see bottom of the last one, which probably isn't
    >> very meaningful.  I tried loading netconsole, but I only get one or
    >> two lines before it stops sending/printing.
    >>
    >> I then tried kexec+crashkernel, but I only managed to get a backtrace
    >> for the last panic (which I think is just a result of memory corruption
    >> or something).  Finally I tried compiling ramoops into my kernel,
    >> but it didn't want to load because of "No such device".
    >
    > For the kexec+crashkernel, try to retrieve the kernel log buffer:
    >

    There is a utility in kexec-tools, named vmcore-dmesg, which
    is supposed to do this kind of thing.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2011-05-18 18:05    [W:0.021 / U:0.644 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site