lkml.org 
[lkml]   [2005]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: Bug#328135: kernel-image-2.6.11-1-686-smp: nfs reading process stuck in disk wait
    Date
    Trond Myklebust <trond.myklebust@fys.uio.no> writes:

    >> on den 14.09.2005 Klokka 21:10 (-0400) skreiv Marc Horowitz:
    >> > Trond Myklebust <trond.myklebust@fys.uio.no> writes:
    >> >
    >> > >> on den 14.09.2005 Klokka 11:51 (+0900) skreiv Horms:
    >> > >> I doubt this has anything to do with NFS. We should no longer have a
    >> > >> sync_page VFS method in the 2.6 kernels. What other filesystems is the
    >> > >> user running?
    >> >
    >> > In the stack trace I sent, from a running 2.6.11 kernel, vfs_read
    >> > appears to be the vfs method, not sync_page. sync_page is called much
    >> > deeper in the stack trace.
    >>
    >> So? It is clearly the call to sync_page that is Oopsing.
    >>
    >> The NFS call is just trying to lock a page that appears to be owned by
    >> someone else. That triggers a call to that filesystem's sync_page, which
    >> then goes on to do a page allocation, which again Oopses.

    Ah, I understand now. I misinterpreted what you said to mean you
    didn't expect to see a sync_page call at all.

    That said, I'd like to clarify one thing: there is no oops in the
    dmesg output. That stack trace comes from dmesg after I do
    "echo t > /proc/sysrq_trigger".

    I'll give the 2.6.12 kernel a try today or tomorrow, and see what
    happens.

    Marc
    -
    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-09-15 16:32    [W:0.030 / U:4.572 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site