LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-05-2018, 09:37 AM   #16
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,505

Rep: Reputation: Disabled

That sounds like it would work, but I'm not familiar with how get-mesa.sh works. My modified scripts will simply clone the git master with '--depth 1' as a temporary build directory and your manual clone where you are bisecting in is left untouched. If the build succeeds it will make a package of the latest git master or what commit you specified.
 
Old 06-05-2018, 09:48 AM   #17
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,505

Rep: Reputation: Disabled
My workflow would be like this.

1. Using the attached script above I would build and test the current master with: ./mesa.SlackBuild
2. Assuming the issue is still present: git clone git://anongit.freedesktop.org/mesa/mesa
3. cd mesa
4. git bisect start
5. git bisect good foo
6. git bisect bad bar
7. It gives a commit to test now and I build that commit and make a package with: COMMIT=3e27b37 ./mesa.SlackBuild (Using the script I attached above)
8. Use upgradepkg on the new package in /tmp/.
9. Test it and then in the original clone do 'git bisect good', 'git bisect bad' or 'git bisect skip' depending on if it works, fails, or can not be tested due to unrelated issues.
10. Repeat until git tells you what the first bad commit was.
11. Share the bisect result and the specific issue upstream on the mesa issue tracker or in irc, #dri-devel @ freenode is a good general graphics channel.

Again, assuming you are not using nouveau and do try my scripts, you should modify the configure arguments accordingly. You can look in Pat's script or './configure --help' for reference.
 
1 members found this post helpful.
Old 06-06-2018, 03:46 AM   #18
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 574

Original Poster
Rep: Reputation: 64
I have bisected the Mesa code base and opened a bug with our friends at Mesa

https://bugs.freedesktop.org/show_bug.cgi?id=106835
 
1 members found this post helpful.
Old 06-06-2018, 03:48 AM   #19
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 574

Original Poster
Rep: Reputation: 64
For reference

Quote:
d891f28df9a4efeda47ee307e7b13147597e8863 is the first bad commit
commit d891f28df9a4efeda47ee307e7b13147597e8863
Author: Lepton Wu <lepton@chromium.org>
Date: Mon Mar 19 15:01:30 2018 -0700

gallium/winsys/kms: Fix possible leak in map/unmap.

If user calls map twice for kms_sw_displaytarget, the first mapped
buffer could get leaked. Instead of calling mmap every time, just
reuse previous mapping. Since user could map same displaytarget with
different flags, we have to keep two different pointers, one for rw
mapping and one for ro mapping. Also introduce reference count for
mapped buffer so we can unmap them at right time.

v2:
- avoid duplicated mapping and leaked mapping (Tomasz)
v3:
- split from larger patch (Emil)
v4:
- remove munmap from dt_destory (Emil)
v5:
- introduce reference count for mapping (Tomasz)
- add back munmap in dt_destory
v6:
- remove change-id in commit message (Tomasz)
v7:
- remove munmap from dt_destory again (Emil)
- add revision history in commit message (Emil)

Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Lepton Wu <lepton@chromium.org>

:040000 040000 cabadd2837679d65c0ac787a51fb24593e32afb9 2f977691ffab0290cfda6a3ddb57ed108b02979c M src
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
screen is black after one move from x to virtual console, back to x, then to console Raul Claro Debian 13 02-22-2011 09:41 AM
[SOLVED] [startx problem] - startx goes to black/grey screen and comes back to command prompt! iNUKE Ubuntu 13 01-07-2011 01:32 PM
Help. Startx gives black screen! sl4ckw4r3 Slackware 23 01-29-2010 05:08 PM
Startx results in a black screen with VGA and screen errors kwosource Linux - Newbie 4 03-11-2005 02:58 PM
startx....black screen. bumjubeo Linux - Newbie 8 01-27-2005 10:13 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:08 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration