lkml.org 
[lkml]   [2002]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [OOPS] Problem Booting 2.5.50 / ext3_reserve_inode_write
    On Fri, 6 Dec 2002, Andy Pfiffer wrote:

    > On Fri, 2002-11-29 at 06:11, Alex Goddard wrote:
    > > 2.5.45-49 worked fine. Here's the output, I can provide .config and
    > > anything else at request.
    > >
    > > Oops: 0000
    > > CPU: 0
    > > EIP: 0060:[<c017c04d>] Not Tainted
    > > EFLAGS: 00010202
    > > EIP: is at ext3_get_inode_loc+0x2d/0x1a0
    > > eax: e7237610 ebx: 00000000 ecx: 00000000 edx: 5a5a5a5a
    > > esi: 5a5a5a5a edi: e721dec0 edp: e721de78 esp: e721de4c
    > > ds: 0068 es: 0068 ss: 0068
    > > Process mount (pid: 248, threadinfo=e721c000, task=e7708700)
    > > Stack:
    > >
    > > e7f9c9a4 e7237590 e7c65c80 e7dcde00 e7f9c9a4 e7234594 e7249e84 00000296
    > > 00000000 e75c2584 e7249ec0 e7249eac c017cd4a e7234610 e7249ec0 c01823bd
    > > e7f9c9a4 e7237594 e7249ea8 c015ace6 e7234610 e7249ec0 e75c2584 e7234610
    > >
    > > Call Trace:
    > > [<c017cd4a>] ext3_reserve_inode_write+0x2a/0xe0
    > > [<c01823bd>] ext3_destroy_inode+0x1d/0x20
    > > [<c015ace6>] destory_inode+0x36/0x50
    > > [<c017ce28>] ext3_mark_inode_dirty+0x28/0x50
    > > [<c017fe12>] ext3_add_nondir+0x52/0x60
    > > [<c0151601>] vfs_create+0x61/0xb0
    > > [<c0151b63>] open_namei+0x363/0x3c0
    > > [<c0142fe1>] filp_open+0x41/0x70
    > > [<c0143413>] sys_open+0x53/0x90
    > > [<c010940b>] sys_call+0x7/0xb
    > >
    > > Code: 8b 86 24 01 00 00 3b 50 50 72 0d 8b 9e 24 01 00 00 8b 43 2c
    > >
    > > I can't tell if this affects performance or anything one way or another
    > > because my machine dies after the above oops, but I also get another trace
    > > earlier in the boot, during the initialization of my framebuffer console:
    >
    > Alex,
    >
    > Did you get any response on this OOPS? I can't find any, and I'm
    > curious because it is happening on one of my systems during bootup as
    > well.

    No, I haven't. I've successfully reproduced it several times though.
    Sometime on Monday I'll have time to see if it's been fixed in the latest
    bk tree.

    [Snip]

    > Mounting local file systems...
    > /etc/init.d/boot.d/S05boot.localfs: line 179: 76 Segmentation fault

    What is that script doing on that line?

    --
    Alex Goddard
    agoddard@purdue.edu
    -
    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-03-22 13:31    [W:0.024 / U:29.704 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site