lkml.org 
[lkml]   [2005]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.12-rc3-mm1
    Alexander Nyberg <alexn@dsv.su.se> wrote:
    >
    > > - We're still miles away from 2.6.12. Lots of patches here, plus my
    > > collection of bugs-post-2.6.11 is vast. I'll start working through them
    > > again after 2.6.12-rc4 is available to testers.
    > >
    >
    > Something is bad with my init process, so with debug patch below I'm
    > getting:
    > do_page_fault: force_sig_info SIGSEV to 1, addr ffffe018, eip b7fe576a
    > do_page_fault: force_sig_info SIGSEV to 1, addr ffffe018, eip b7fe576a
    > do_page_fault: force_sig_info SIGSEV to 1, addr ffffe018, eip b7fe576a
    > do_page_fault: force_sig_info SIGSEV to 1, addr ffffe018, eip b7fe576a
    >
    > continuing forever. 0xffffe018 is inside the vsyscall page so could be
    > related but the eip should be there too in that case I think...
    > You have any candidates? I've failed to find any.

    Nope. The easiest way to identify this is to grab broken-out.tar.gz, the
    series file and use quilt to do a bisection search. Ten compiles max.

    If you're not interested in that, please share the .config.

    > Index: mm/arch/i386/mm/fault.c
    > ===================================================================
    > --- mm.orig/arch/i386/mm/fault.c 2005-04-30 12:49:17.000000000 +0200
    > +++ mm/arch/i386/mm/fault.c 2005-04-30 12:56:31.000000000 +0200
    > @@ -391,6 +391,8 @@
    > info.si_errno = 0;
    > /* info.si_code has been set above */
    > info.si_addr = (void __user *)address;
    > + printk("%s: force_sig_info SIGSEV to %d, addr %lx, eip %lx\n",
    > + __FUNCTION__, tsk->pid, address, regs->eip);
    > force_sig_info(SIGSEGV, &info, tsk);
    > return;
    > }
    >
    >
    > Also, this brought me to trying to find what has changed between the
    > versions which appears a little tricky.

    Well announce.txt tells you what was added and what was removed.

    > Do you think it would be
    > possible to set up your scripts that currently notify the author of a
    > patch about the inclusion to CC something like mm-commits list.

    Certainly could. I'll ask davem about getting a list set up.

    > That way people can audit patches that have got in before the tarball is
    > released, it is easy to see what has gone in and when.
    -
    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: 2005-04-30 13:30    [W:0.028 / U:0.556 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site