<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226#c236">Comment # 236</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226">bug 54226</a> from <a class="email" href="mailto:jefbed@gmail.com" title="Jeffrey E. Bedard <jefbed@gmail.com>"> Jeffrey E. Bedard</a> <pre>I reported this bug from a system without an SSD. Recently, I have not seen the kernel messages appear however--currently on linux 4.2.5. On Sun, Nov 1, 2015 at 10:04 PM, <<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>> wrote: > *<a href="show_bug.cgi?id=54226#c235">Comment # 235</a> <<a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="show_bug.cgi?id=54226#c235">https://bugs.freedesktop.org/show_bug.cgi?id=54226#c235</a>> > on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="show_bug.cgi?id=54226">bug 54226</a> <<a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="show_bug.cgi?id=54226">https://bugs.freedesktop.org/show_bug.cgi?id=54226</a>> from > <a href="mailto:arrowsmith@pythian.com">arrowsmith@pythian.com</a> <<a href="mailto:arrowsmith@pythian.com">arrowsmith@pythian.com</a>> * > > FWIW, my issue (<a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="show_bug.cgi?id=54226#c191">https://bugs.freedesktop.org/show_bug.cgi?id=54226#c191</a>), was > resolved by uninstalling various components, re-installing and updating them. I > have a hunch (completely unproven) that it was a transparent bit-fail issue > from the SSD. By un-installing and re-installing, the files were likely > installed to a different location on the drive. It wasn't configuration, as I > tried erasing, and even rolling back to defaults, with the problem still > persisting. As it was almost daily, prior to uninstall, and hasn't happened > since the install, this is all I can attribute it to. > > HTH someone. > > ------------------------------ > You are receiving this mail because: > > - You are on the CC list for the bug. > ></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>