[lkml]   [2003]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] O16.2int
    Hi Con,

    I've been unable to test many of your patches lately, but I recently
    upgraded to 2.6.0-test3-mm2 and included the O16.2 patches and I'm
    having some very bad behaviour. I'll try to describe it the best way I

    The worst case scenario involves wine applications (a program that seems
    to be causing a significant amount of trouble) but I think I've seen the
    issue in several other applications as well.

    1. -- Wine running Windows Media Player 6.4 works great when running in
    a window but if you make the program open to full screen it gets so much
    attention that it almost completely starves the entire system, you can't
    even manage to get switched back to the standard screen. If you get
    very lucky you can switch the system to a VT and manage, painfully
    slowly to kill the wine process off, then the system will turn to
    normal. This issue actually seems to affect almost any wine
    applications that's doing a lot of screen updates, for example small
    flash animations work OK, but complex animations can cause many seconds
    of starvation to the rest of the system. Renicing the X server and wine
    server to much lower numbers seems to make this issue go away.

    2. -- Adobe Acrobat 5.07 for Linux seems to have a very similar issue, a
    large complex document seems to starve out the whole system making the
    system feel locked up for several seconds.

    3. -- It seems I can trigger the same kind of starvation by simply doing
    large selects in a Konsole window. Selecting a large section of text
    which causes the window to scroll can sometime make the system almost
    totally non-responsive in every other window.

    The wine issue is the easiest to trigger, the others seem to require
    that some other things are also using CPU. In other words, if the
    system is otherwise totally idle I have been unable to trigger the
    Konsole issue, however, if another application is using a reasonable
    amount of CPU, say a video playing in Wine using ~50% CPU, then it seems
    easy to make this happen. Once it happens it's very hard to recover,
    the systems almost completely fails to respond to mouse button clicks
    and keyboard functions (although the mouse usually continues to move
    smoothly) if I get lucky I can get to a VT and eventually login and kill
    something off, but this sometimes takes minutes (it took 90 seconds
    earlier today just to get the password prompt after type in my username
    at the VT prompt and another minute to get to a shell).


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:47    [W:0.023 / U:29.436 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site