Messages in this thread | | | Date | Wed, 3 May 2006 11:11:48 +0200 | From | "Benoit Boissinot" <> | Subject | Re: 2.6.17-rc3-mm1 |
| |
On 5/1/06, Andrew Morton <akpm@osdl.org> wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc3/2.6.17-rc3-mm1/ > > Hi Andrew,
Since a few -mm releases I am seeing processes stuck in a nanosleep({0, 0}, NULL) syscall. Sometimes, they unfreeze after several hours.
The processes are urxvtd (rxvt-unicode daemon) or urxvt (rxvt-unicode terminal). The backtrace from sysrq-t looks like: ... urxvtd S DD965F68 0 12171 1 12367 12598 12078 (NOTLB) dd965f38 326cc12f 00004abf dd965f68 dd965f38 631b6900 00000167 326c007b 003d0900 00000000 0000000a df51f144 df51f030 dfb81030 631b6900 00000167 003d0900 dd965000 dd965f68 00000001 dd965f50 c032703d 00000001 00000000 Call Trace: <c032703d> do_nanosleep+0x3d/0x80 <c012fc68> hrtimer_nanosleep+0x38/0xf0 <c012fd78> sys_nanosleep+0x58/0x60 <c032818b> sysenter_past_esp+0x54/0x75 ... Showing all blocking locks in the system: S urxvtd:12171 [df51f030, 115] (not blocked on mutex)
Was it already reported ? If not I'll test a vanilla kernel and start bisecting.
thanks,
Benoit - 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/
| |