open two xterms, run glxgears from one and then 5 or so seconds after that
run an application which you can easily determine completion, such as
ifconfig. You will notice that the console app doesn't make much progress
and essentially get's starved.
ifconfig R 00000000 5738320 1213 1032 (NOTLB)
Call Trace:
[<c011ee20>] autoremove_wake_function+0x0/0x40
[<c02b6462>] generic_make_request+0x112/0x1b0
[<c011dc4d>] io_schedule+0x2d/0x40
[<c015851a>] __wait_on_buffer+0xba/0xc0
[<c011ee20>] autoremove_wake_function+0x0/0x40
glxgears S C010A1E8 4265977488 1209 1019 (NOTLB)
Call Trace:
[<c010a1e8>] common_interrupt+0x18/0x20
[<c01298d5>] schedule_timeout+0xb5/0xc0
[<c03e8490>] unix_poll+0x20/0x90
[<c0391e69>] sock_poll+0x19/0x20
[<c0169c22>] do_select+0x132/0x270
[<c0169960>] __pollwait+0x0/0xa0
Afflicted system was;
K6 500MHz laptop
128M RAM w/ 8M shared (Trident X11 Server)
This was not reproduceable with 2.4.18-3 nor with 2.5.66 and the
following patch applied;
-- function.linuxpower.ca - 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/