From: Chris Wilson <chris@chris-wilson.co.uk>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: regression: GM45 on Dell Latitude E6400 display from 1440x900 to 1024x768 somewhere between 2.6.38-git2 and -git7
Date: Thu, 24 Mar 2011 12:27:52 +0000 [thread overview]
Message-ID: <b7da2f$qre4te@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <AANLkTinG5jvw7mYVxkhQ0RqpCyDmPTHHbiHxW8oHhwz0@mail.gmail.com>
On Thu, 24 Mar 2011 13:03:55 +0100, Alessandro Suardi <alessandro.suardi@gmail.com> wrote:
> OK - attaching in .tgz as they'd probably cross lkml size limits:
Ok, the clue to the bizarre sizing is:
[ 376.501] (WW) intel(0): No outputs definitely connected, trying again...
[ 376.501] (II) intel(0): Output LVDS1 connected
[ 376.501] (II) intel(0): Output VGA1 disconnected
[ 376.501] (II) intel(0): Output HDMI1 disconnected
[ 376.501] (II) intel(0): Output DP1 disconnected
[ 376.501] (II) intel(0): Output HDMI2 disconnected
[ 376.501] (II) intel(0): Output DP2 disconnected
[ 376.501] (II) intel(0): Output DP3 disconnected
[ 376.501] (II) intel(0): Output TV1 connected
[ 376.502] (II) intel(0): Using fuzzy aspect match for initial modes
[ 376.502] (II) intel(0): Output LVDS1 using initial mode 1024x768 +0+0
[ 376.502] (II) intel(0): Output TV1 using initial mode 1024x768 +0+0
Transient false TV detection rears its ugly head again. (It's detected
during the 'working' setup but then disappears upon reprobing.) So X
choose the intersection of the available modes, 1024x768. But that
doesn't explain why the LVDS exists (it prints the EDID for it) but it
thinks it is disconnected.
The difference in the dmesg is:
------------[ cut here ]------------
WARNING: at fs/sysfs/dir.c:455 sysfs_add_one+0x92/0xa6()
Hardware name: Latitude E6400
sysfs: cannot create duplicate filename
'/devices/pci0000:00/0000:00:02.0/backlight/acpi_video0/device'
Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit i2c_core video
Pid: 906, comm: modprobe Not tainted 2.6.38-git14 #1
Call Trace:
[<ffffffff8103319b>] warn_slowpath_common+0x80/0x98
[<ffffffff81033247>] warn_slowpath_fmt+0x41/0x43
[<ffffffff811253d0>] sysfs_add_one+0x92/0xa6
[<ffffffff81125ad6>] sysfs_do_create_link+0xf3/0x186
[<ffffffffa000175f>] acpi_video_bus_add+0x982/0xc87 [video]
which can be temporary fixed by reverting 9661e92c10a97752. But I don't
immediately see how that would cause the LVDS to be declared disconnected.
Can you add drm.debug=0xe to your grub kernel parameters and attach a
fresh dmesg?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-24 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:30 regression: GM45 on Dell Latitude E6400 display from 1440x900 to 1024x768 somewhere between 2.6.38-git2 and -git7 Alessandro Suardi
2011-03-24 11:45 ` Chris Wilson
2011-03-24 12:03 ` Alessandro Suardi
2011-03-24 12:27 ` Chris Wilson [this message]
2011-03-24 13:11 ` Alessandro Suardi
2011-03-24 13:30 ` [PATCH] drm/i915/lvds: Always return connected in the absence of better information Chris Wilson
2011-03-24 14:18 ` Alessandro Suardi
2011-03-24 18:12 ` [Intel-gfx] " Keith Packard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b7da2f$qre4te@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=alessandro.suardi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox