lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikY23FxMVtqTNra05O3CxXZQ5=bvmppTiySHNq=@mail.gmail.com>
Date:	Thu, 24 Mar 2011 14:11:19 +0100
From:	Alessandro Suardi <alessandro.suardi@...il.com>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: regression: GM45 on Dell Latitude E6400 display from 1440x900 to
 1024x768 somewhere between 2.6.38-git2 and -git7

On Thu, Mar 24, 2011 at 1:27 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
> On Thu, 24 Mar 2011 13:03:55 +0100, Alessandro Suardi <alessandro.suardi@...il.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?

The WARNING is a separate issue which popped up later.

Summarizing in this respect,


2.6.38-git2: no WARNING, correct display

2.6.38-git3..6: no tests performed due to kernel build failure

2.6.38-git7..11: no WARNING, wrong display

2.6.38-git12-13: no tests performed due to no time

2.6.38-git14: WARNING present, wrong display


Here you go with the drm debug dmesg for -git14... thanks !

--alessandro

 "There's always a siren singing you to shipwreck"

   (Radiohead, "There There")

Download attachment "dmesg-2638git14-drmdebug.out" of type "application/octet-stream" (74751 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ