On Fri, Oct 17, 2008 at 08:54:35PM +0400, Alexander Beregalov wrote: > Workload is not specific, many i/o commands trigger the message. > > dmesg|grep comm: > [ 4.419605] Pid: 1396, comm: mkdir Not tainted 2.6.27-next-20081017 #2 > [ 6.056443] Pid: 1782, comm: dhcpcd Not tainted 2.6.27-next-20081017 #2 > [ 17.899905] Pid: 1791, comm: dhcpcd-run-hook Not tainted > 2.6.27-next-20081017 #2 > [ 3846.588549] Pid: 2005, comm: screen Not tainted 2.6.27-next-20081017 #2 > [ 4416.242723] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 > [ 4430.618037] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 > [ 4431.641578] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 > [ 4432.944265] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 > [ 4590.330706] Pid: 2026, comm: git-merge Not tainted 2.6.27-next-20081017 #2 > [14882.802479] Pid: 2058, comm: git-merge Not tainted 2.6.27-next-20081017 #2 > [16955.026436] Pid: 2091, comm: git-merge Not tainted 2.6.27-next-20081017 #2 > [18466.645935] Pid: 2119, comm: git-merge Not tainted 2.6.27-next-20081017 #2 > [19165.813049] Pid: 2150, comm: git-merge Not tainted 2.6.27-next-20081017 #2 Very strange. Can you retry with tomorrow Linux-next which should have a large XFS update? If it still happens I'll investigate it in more detail. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
