Bug 89460 - wrong size in struct drm_mode_get_connector
Summary: wrong size in struct drm_mode_get_connector
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-06 09:02 UTC by Abraham Macias
Modified: 2015-03-09 11:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (8.08 KB, text/plain)
2015-03-06 09:42 UTC, Abraham Macias
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Abraham Macias 2015-03-06 09:02:18 UTC
Hi everybody,
 I'm trying to run a 32bits Linux distribution with a 64 bits Linux kernel and I have problems with Intel driver for xorg.

By tracing the problem and then searching in Google I found this conversation:
  http://comments.gmane.org/gmane.linux.kernel.stable/67503

It seems that due to differences in the size of struct drm_mode_get_connector is neccesary to add a "__u32 pad" at the end of the structure. And this was added to the kernel.

But if you look in libdrm-2.4.58/include/drm/drm_mode.h the "drm_mode_get_connector" struct haven't got any padding.

Is this a bug?
Is possible to run a 32 bits linux distribution with a 64 bits Linux kernel? or is it an impossible dream?

Best regards!
Comment 1 Chris Wilson 2015-03-06 09:06:41 UTC
What driver? 2.99.917 has it fixed.
Comment 2 Chris Wilson 2015-03-06 09:07:43 UTC
i.e. the failing Xorg.0.log would be useful to attach.
Comment 3 Chris Wilson 2015-03-06 09:13:46 UTC
fwiw, I just checked with my 32bit userspace, 64bit kernel build and it functions normally.
Comment 4 Abraham Macias 2015-03-06 09:42:49 UTC
Created attachment 114075 [details]
Xorg.0.log

I modified the source code by adding "error" messages to debug in what point the xorg is failing and freezing
Comment 5 Abraham Macias 2015-03-06 09:44:56 UTC
The driver is 2.99.917

What must I check to ensure that is taking the correct structure size?
Does it takes the struct from kernel headers? or ir takes it from another header?

Thanks
Comment 6 Chris Wilson 2015-03-06 09:46:08 UTC
uxa??? Then you have to update your kernel.
Comment 7 Abraham Macias 2015-03-06 09:50:26 UTC
What kernel must I use?
Comment 8 Chris Wilson 2015-03-07 10:18:45 UTC
v3.12 for the drm fixes. Why are you using the less tested UXA?
Comment 9 Abraham Macias 2015-03-09 10:24:15 UTC
I'm using UXA because I have some problems with SNA.
To make a long story short, I'm trying to run Linux in an Android tablet by adapting the Android kernel from its source code. (I've made this kind of things before)

If I use SNA it seems to detect properly all the interfaces (the screen and the HDMI), but after that Xorg shows the "failsafe" screen. But I can't see any error message in the Xorg.0.log

What can be the reason of that? What may I check to get the reason why Xorg shows the "failsafe" screen?

Also when in the past (with other tablet model) I used SNA, Xorg worked fine but I couldn't see any video with VLC or any other video player. (That's another reason to keep using UXA).

The kernel that I'm using is based on 3.10 version (it says to be a 3.10.20). 
Can you tell me what patches must I apply for the DRM fixes?

Also "Plymouth" is failing with a "sysmalloc: Assertion failed error", is there any bugfix for this?

Thank you and best regards
Comment 10 Chris Wilson 2015-03-09 11:52:42 UTC
(In reply to Abraham Macias from comment #9)
> I'm using UXA because I have some problems with SNA.
> To make a long story short, I'm trying to run Linux in an Android tablet by
> adapting the Android kernel from its source code. (I've made this kind of
> things before)
> 
> If I use SNA it seems to detect properly all the interfaces (the screen and
> the HDMI), but after that Xorg shows the "failsafe" screen. But I can't see
> any error message in the Xorg.0.log
> 
> What can be the reason of that? What may I check to get the reason why Xorg
> shows the "failsafe" screen?

Right, because that's not a bug in the ddx.
 
> Also when in the past (with other tablet model) I used SNA, Xorg worked fine
> but I couldn't see any video with VLC or any other video player. (That's
> another reason to keep using UXA).

Considering that SNA exposes kernel sprite planes, that is more likely to be a kernel bug. Considering you are byt, it is surprising that UXA even works...

> The kernel that I'm using is based on 3.10 version (it says to be a
> 3.10.20). 
> Can you tell me what patches must I apply for the DRM fixes?

http://comments.gmane.org/gmane.linux.kernel.stable/67503

> Also "Plymouth" is failing with a "sysmalloc: Assertion failed error", is
> there any bugfix for this?

No idea.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.