https://bugs.freedesktop.org/show_bug.cgi?id=98169
Christoph Haag changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #31 from Christoph Haag ---
Yes, your new patch works. No crashing, all panes are visible and show the
correct values.
--
You are receiving this mail because:
You are the QA Contact for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #30 from Steven Toth ---
Christoph, based on feedback from the mailing list, I made some changes to use
the MESA internal reference counting mechanisms which makes sensor and other
cleanup a little more robust.
The patch tests fine f
https://bugs.freedesktop.org/show_bug.cgi?id=98169
Steven Toth changed:
What|Removed |Added
Attachment #127222|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #28 from Christoph Haag ---
Sure.
--
You are receiving this mail because:
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesk
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #27 from Steven Toth ---
Thanks for reporting these issue. I'll wrap them up and get them on the ML for
review.
Care to give me your Tested-By sign-off?
--
You are receiving this mail because:
You are the QA Contact for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #26 from Christoph Haag ---
Created attachment 127250
--> https://bugs.freedesktop.org/attachment.cgi?id=127250&action=edit
success
With the patches
https://bugs.freedesktop.org/show_bug.cgi?id=98169#c19
https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #25 from Steven Toth ---
Christoph,
Please remove the prior sensor-cleanup.patch, apply the attached
sensor-cleanupv2.patch.
This should prevent freeing of an object while its being used by a second hud
element.
Let me know, thanks
https://bugs.freedesktop.org/show_bug.cgi?id=98169
Steven Toth changed:
What|Removed |Added
Attachment #127217|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=98169
Christoph Haag changed:
What|Removed |Added
Attachment #127224|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #22 from Steven Toth ---
That's odd, the reference patch had no sensor changes.
Can you back the reference count patch out and check that sensors is still
working from the last patch?
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #21 from Christoph Haag ---
Created attachment 127224
--> https://bugs.freedesktop.org/attachment.cgi?id=127224&action=edit
bt full
(In reply to Steven Toth from comment #20)
> Christoph,
>
> The attached referencecount.patch shou
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #20 from Steven Toth ---
Christoph,
The attached referencecount.patch should work very nicely for you.
Can you please test and report back.
I have unigine workere here now, I was able to reproduce the issue and I belive
this patch
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #19 from Steven Toth ---
Created attachment 127222
--> https://bugs.freedesktop.org/attachment.cgi?id=127222&action=edit
Bugfix: we're prematurely freeing a HUB object
Allow multiple open uses of the HUD objects, don't assuming we
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #18 from Ilia Mirkin ---
(In reply to Andy Furniss from comment #17)
> (In reply to Steven Toth from comment #16)
>
> > Can you please share your exact ./configure options for mesa? I still have
> > issues running unigine, it starts,
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #17 from Andy Furniss ---
(In reply to Steven Toth from comment #16)
> Can you please share your exact ./configure options for mesa? I still have
> issues running unigine, it starts, I see the render window appear and the
> app segfa
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #16 from Steven Toth ---
That's pretty bizarre, I don't see any of the cpu frequency, disk io or sensor
charts with any data.
This isn't the same bug as the sensor bug, it's something new.
Can you please share your exact ./configure
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #15 from Alex Deucher ---
(In reply to Christoph Haag from comment #14)
> I don't think there's another bug report needed for this as it's probably a
> similar issue:
> Attached is a screenshot that shows the hud with cpu frequency an
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #14 from Christoph Haag ---
Created attachment 127218
--> https://bugs.freedesktop.org/attachment.cgi?id=127218&action=edit
gallium hud showing 0 for cpu freq and sensors
Thanks for the patch. I can confirm that unigine-heaven star
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #13 from Steven Toth ---
Christoph,
I've been able to reproduce the problem. Your use case has been exercising a
code path that glxgears/heads/demo does not, with regards to HUD
free/destruction. glxgears termination never routes thr
https://bugs.freedesktop.org/show_bug.cgi?id=98169
Steven Toth changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |st...@kernellabs.com
|or
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #11 from Steven Toth ---
enable-texture-float=yes
^^^ This fixes the runtime issue, thanks.
I can now repro the original sensors related issue. Investigating.
--
You are receiving this mail because:
You are the QA Contact for the
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #10 from Ilia Mirkin ---
(In reply to Steven Toth from comment #8)
> + glxinfo
> + grep -i opengl
> libGL: pci id for fd 4: 10de:1402, driver nouveau
> libGL: OpenDriver: trying
> /home/stoth//mesa-tip/root/lib/dri/nouveau_dri.so
> li
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #9 from Steven Toth ---
Extended renderer info (GLX_MESA_query_renderer):
Vendor: nouveau (0x10de)
Device: NV126 (0x1402)
Version: 12.1.0
Accelerated: yes
Video memory: 2031MB
Unified memory: no
Preferred p
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #8 from Steven Toth ---
+ glxinfo
+ grep -i opengl
libGL: pci id for fd 4: 10de:1402, driver nouveau
libGL: OpenDriver: trying
/home/stoth//mesa-tip/root/lib/dri/nouveau_dri.so
libGL: Using DRI3 for screen 0
OpenGL vendor string: nouv
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #7 from Eero Tamminen ---
Does the crashing happen if you disable Heaven tessellation
(TESSELLATION_DISABLED option)?
One of the causes for FBConfig issues is X server using mismatching GL driver
than the application you're testing.
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #6 from Christoph Haag ---
Might be a nouveau issue on Maxwell, no idea.
A google search says that this means that the driver does not advertise
GLX_ARB_create_context as supported:
https://www.opengl.org/registry/specs/ARB/glx_crea
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #5 from Steven Toth ---
Grr. I still can't make it run against mesa tip.
+ ./heaven -project_name Heaven -data_path ../ -engine_config
../data/heaven_4.0.cfg -system_script heaven/unigine.cpp -sound_app openal
-video_app opengl -vide
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #4 from Christoph Haag ---
Only thing I can think of is that you may need LIBGL_DRIVERS_PATH.
Try
LIBGL_DRIVERS_PATH=$PWD/root/lib/xorg/modules/dri/
or something like that.
also LIBGL_DEBUG=verbose to check whether something goes wr
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #3 from Steven Toth ---
I'm not familiar with Unigine and I'm having issues trying to get it to run
with mesa tip. Your feedback is welcome.
Testing with a Heaven-Unigine 4.0 binary downloaded today.
Compiling/installing mesa tip to
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #2 from Steven Toth ---
Tests OK on glxgears, glxdemo and glxheads, on my platform (x86_64 Ubuntu
16.04), with NVIDIA GTX 950.
I'll look at installing unigine.
--
You are receiving this mail because:
You are the QA Contact for the
> Comment # 1 on bug 98169 from Christoph Haag
>
> I also noticed that the cpufrequency graphs (cpufreq-cur-cpu0) always show 0
> in
> unigine heaven.
>
> They work correctly in glxgears, so perhaps it's caused by the same thing
> unigine heaven does.
I'll open a bugzilla account tomorrow (monday)
https://bugs.freedesktop.org/show_bug.cgi?id=98169
--- Comment #1 from Christoph Haag ---
I also noticed that the cpufrequency graphs (cpufreq-cur-cpu0) always show 0 in
unigine heaven.
They work correctly in glxgears, so perhaps it's caused by the same thing
unigine heaven does.
--
You are re
https://bugs.freedesktop.org/show_bug.cgi?id=98169
Bug ID: 98169
Summary: lm_sensors hud option crashes unigine heaven
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
34 matches
Mail list logo
