Jukka Ruohonen wrote:
I was thinking about the VFS changes too. These panics appear to be related
to NFS somehow. Andreas, are you sure the time frame is correct?
Yes. Before rmind's changes of 2011.04.11.22.31.43, there hadn't been a
single uvm_fault crash in my test runs since January, and after those
changes, every single test run has failed that way, though not always
in the same test:
$ zgrep ' uvm_fault' 2011.0[2-4].*/test.log.gz
2011.04.11.22.31.43/test.log.gz: mountdhup: uvm_fault(0xc0b0f3c0, 0xc4ba1000,
1) -> 0xe
2011.04.11.22.37.10/test.log.gz: mountdhup: uvm_fault(0xc0b0f3c0, 0xc4bbf000,
1) -> 0xe
2011.04.12.00.21.10/test.log.gz: nfs_overwrite64k: uvm_fault(0xc0b0f3c0,
0xc4c10000, 1) -> 0xe
2011.04.12.07.54.16/test.log.gz: nfs_renamerace_dirs: uvm_fault(0xc0b0f3c0,
0xc40b5000, 1) -> 0xe
2011.04.12.08.39.26/test.log.gz: nfs_renamerace_dirs: uvm_fault(0xc0b0f3c0,
0xc4c04000, 1) -> 0xe
2011.04.12.08.40.34/test.log.gz: mountdhup: uvm_fault(0xc0b0f3c0, 0xc4b9f000,
1) -> 0xe
2011.04.13.12.40.54/test.log.gz: nfs_fillfs: uvm_fault(0xc0b0f3c0, 0xff29e000,
1) -> 0xe
2011.04.13.19.17.00/test.log.gz: nfs_fillfs: uvm_fault(0xc0b0f3c0, 0xc40b9000,
1) -> 0xe
2011.04.14.01.03.23/test.log.gz: mountdhup: uvm_fault(0xc0b0f3c0, 0xc4c05000,
1) -> 0xe
2011.04.14.07.06.52/test.log.gz: mountdhup: uvm_fault(0xc0b0f3c0, 0xc4b4d000,
1) -> 0xe
If you still doubt me, there's an easy way to prove me wrong: revert
the changes and see if the tests continue failing.
--
Andreas Gustafsson, gson%gson.org@localhost
!DSPAM:4da6ea0c2271863065636!