Bug 23089 - bad fd access when drm module is missing
Summary: bad fd access when drm module is missing
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Wang Zhenyu
QA Contact: Xorg Project Team
Depends on:
Reported: 2009-08-02 05:28 UTC by Oswald Buddenhagen
Modified: 2009-08-19 15:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

log file (91.24 KB, text/plain)
2009-08-02 05:31 UTC, Oswald Buddenhagen
no flags Details

Description Oswald Buddenhagen 2009-08-02 05:28:03 UTC
this shows up in the log on vt switches:
(WW) intel(0): drmDropMaster failed: Bad file descriptor
Comment 1 Oswald Buddenhagen 2009-08-02 05:31:09 UTC
Created attachment 28260 [details]
log file
Comment 2 Wang Zhenyu 2009-08-06 00:59:34 UTC
Please try patches on #23082, I haven't seen this error yet.
Comment 3 Oswald Buddenhagen 2009-08-06 13:48:33 UTC
still getting it.
maybe it is related to the fact that the agp driver is loaded, but the dri one isn't?
Comment 4 Wang Zhenyu 2009-08-18 22:00:13 UTC
oh, you haven't mentioned you have no dri modules installed? I think we simply not support that any more.
Comment 5 Oswald Buddenhagen 2009-08-19 00:23:38 UTC
i think the bug title mentions is sufficiently clearly. ;)

anyway, just like i say in bug 23090, it should work cleanly or not at all. having it in this state is confusing for the user and certainly doesn't help maintaining the code (see, duh, this report). oh, well.
Comment 6 Gordon Jin 2009-08-19 02:27:42 UTC
no-drm should still be supported now, but with limit support (means it should _basically_ works).

Oswald, do you see any real impact when doing vt switch, other than the warning?
Comment 7 Oswald Buddenhagen 2009-08-19 15:40:23 UTC
no ... much it's more stable than with drm, after all. :D
whatever, it's not usable anyway (see the rejected report about slowness), so i don't really mind.

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.