Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Whoops, Intel SNB Is Borked At The Last Minute In Linux 2.6.39

  1. #1
    Join Date
    Jan 2007
    Posts
    14,812

    Default Whoops, Intel SNB Is Borked At The Last Minute In Linux 2.6.39

    Phoronix: Whoops, Intel SNB Is Borked At The Last Minute In Linux 2.6.39

    This morning after writing Intel Sandy Bridge On Ubuntu 11.04 Is Still Troubling, I proceeded to build the latest Mesa / Linux kernel / libdrm / DDX Git stack to see where the latest Intel SNB code is at and how it's running for the popular Core i5 2500K processor. Before leaving three weeks ago, everything was running great, but to much surprise, this morning it was a broken mess. Intel just regressed hard in their Sandy Bridge support for the about-to-be-released Linux 2.6.39 kernel. Whoops!

    http://www.phoronix.com/vr.php?view=16015

  2. #2
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    934

    Default


  3. #3
    Join Date
    Oct 2007
    Location
    Sweden
    Posts
    174

    Default

    If both configurations may cause lock-ups the driver is broken somewhere completely else. I guess it is good this happened so that the real problem will be fixed sooner.

  4. #4
    Join Date
    Aug 2009
    Posts
    2,264

    Default

    Intel is honouring it's acquired nickname: Sandy Bitch

    But bad support is not doing anyone good. It's terrible enough that I had no choice but to buy an i3 due to AMD's absence in the affordable quality 14 inch laptop 'sector'. Luckily that works (no shit).

  5. #5

    Default Ah, well ...

    ... nothing has ever put the "dead" in "deadline" quite like software development.

  6. #6
    Join Date
    Apr 2010
    Posts
    101

    Default

    Quote Originally Posted by misiu_mp View Post
    If both configurations may cause lock-ups the driver is broken somewhere completely else. I guess it is good this happened so that the real problem will be fixed sooner.
    this was what I was thinking, it breaks now with value of 0 on Phoronix test machine but it breaks with a value of 1 on the persons machine who submitted the patch....

  7. #7
    Join Date
    Mar 2011
    Posts
    3

    Default

    I was able to fix/prevent/work-a-round the Hangcheck error by:

    As root:

    echo 1 > /sys/module/i915/parameters/semaphores

    Please see this for more info.

  8. #8

    Default

    There's now a fix for the random SNB GPU hangs if you're able and willing to recompile a kernel. You need to apply the two patches attached here: https://bugzilla.redhat.com/show_bug.cgi?id=684097

    Note that if you're running the bleeding-edge 3.0rc4 kernel, you already have the first patch and only need to apply the second.

    Also note that after applying these patches semaphores should be turned on (put i915.semaphores=1 in your kernel boot parameters) Semaphores make the driver go faster. On my hardware, with semaphores enabled I get about 10% more frames in glxgears both with and without compositing; "real" workloads may vary.

  9. #9
    Join Date
    Aug 2007
    Posts
    6,631

    Default

    Why is that fix not even in mainline git? It should not require an option to activate for snb however too... Btw. that hang is not random, trine triggers it always.

  10. #10

    Default

    The first part of the fix is in mainline git. The second patch was only posted on the intel-gfx mailing list a couple days ago; I assume it'll make it into git any day now.

    You don't need any kernel option to "activate" the fixes. Without the patches, some people have fewer hangs with semaphores=0 and other people have fewer hangs with semaphores=1 (I suspect it depends mainly on what window manager they're running) With the patches, the hangs are gone, period; semaphores=1 is strictly a performance tweak. I'm guessing that once the kernel drm hackers are satisfied that the fix is working and correct, semaphores=1 will be made the default again, for good this time.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •