lkml.org 
[lkml]   [2007]   [Aug]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: CFS review

    * Rene Herman <rene.herman@gmail.com> wrote:

    > Realised the BUGs may mean the kernel DRM people could want to be in CC...

    and note that the schedule() call in there is not part of the crash
    backtrace:

    > >Call Trace:
    > > [<c10fa54b>] drm_lock+0x255/0x2de
    > > [<c10ff28d>] mga_dma_buffers+0x0/0x2e3
    > > [<c10f87fc>] drm_ioctl+0x142/0x18a
    > > [<c1005973>] do_IRQ+0x97/0xb0
    > > [<c10f86ba>] drm_ioctl+0x0/0x18a
    > > [<c10f86ba>] drm_ioctl+0x0/0x18a
    > > [<c105b0d7>] do_ioctl+0x87/0x9f
    > > [<c105b32c>] vfs_ioctl+0x23d/0x250
    > > [<c11b533e>] schedule+0x2d0/0x2e6
    > > [<c105b372>] sys_ioctl+0x33/0x4d
    > > [<c1003d1e>] syscall_call+0x7/0xb

    it just happened to be on the kernel stack. Nor is the do_IRQ() entry
    real. Both are frequent functions (and were executed recently) that's
    why they were still in the stackframe.

    Ingo
    -
    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: 2007-08-30 09:23    [W:0.021 / U:63.932 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site