Re: has the i915 "black screen" boot issue returned?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 27 Jan 2011, Chris Wilson wrote:

> On Thu, 27 Jan 2011 08:55:24 -0500 (EST), "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx> wrote:
> > On Thu, 27 Jan 2011, Chris Wilson wrote:
> >
> > > On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx> wrote:
> > > >
> > > >   for me, this appears to be the offending commit:
> > > >
> > > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing)
> > > > Merge: ec30f34 abb72c8
> > > > Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> > > > Date:   Tue Jan 25 10:46:14 2011 +1000
> > > >
> > > >     Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai
> > >
> > > Let's just test the other parent ec30f343d to be sure it came in with the
> > > drm merge.
> >
> >   so that's something you want me to test?  checking out that commit
> > ec30f343d and trying it?
>
> Yes. If abb72c8 works and 5e82ea9 does not, then ec30f34 must be at fault
> (since the merge looks clean), verifying that the bug was introduced
> between abb72c828 and ec30f34.

  ok, i'm getting different results from this morning, not sure why,
but i'm fairly confident i've isolated it to this extent.  here's the
salient part of the git log i'm looking at:

===== git log =====

commit abb72c828878a2c69b2cfb33ac30007c8ecd735e
Merge: 58bbf01 8e934db
Author: Dave Airlie <airlied@xxxxxxxxx>
Date:   Tue Jan 25 08:41:58 2011 +1000

    Merge branch 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/g

    * 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/git/ickle/dr
      drm/i915: Prevent uninitialised reads during error state capture
      drm/i915: Use consistent mappings for OpRegion between ACPI and i915
      drm/i915: Handle the no-interrupts case for UMS by polling
      drm/i915: Disable high-precision vblank timestamping for UMS
      drm/i915: Increase the amount of defense before computing vblank timestamps
      drm/i915,agp/intel: Do not clear stolen entries
      Remove MAYBE_BUILD_BUG_ON
      BUILD_BUG_ON: make it handle more cases
      module: fix missing semicolons in MODULE macro usage
      param: add null statement to compiled-in module params
      module: fix linker error for MODULE_VERSION when !MODULE and CONFIG_SYSFS=n
      module: show version information for built-in modules in sysfs
      selinux: return -ENOMEM when memory allocation fails
      tpm: fix panic caused by "tpm: Autodetect itpm devices"
      TPM: Long default timeout fix
      trusted keys: Fix a memory leak in trusted_update().
      keys: add trusted and encrypted maintainers
      encrypted-keys: rename encrypted_defined files to encrypted
      trusted-keys: rename trusted_defined files to trusted
      drm/i915: Recognise non-VGA display devices
      ...

commit 58bbf018a70c562437eeae121a5d021ba7fe56a5
Author: Alex Deucher <alexdeucher@xxxxxxxxx>
Date:   Mon Jan 24 17:14:26 2011 -0500

    drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq

    Needed for timer queries in the 3D driver.

    Signed-off-by: Alex Deucher <alexdeucher@xxxxxxxxx>
    Signed-off-by: Dave Airlie <airlied@xxxxxxxxx>

===== git log =====

now:

  * commit 58bbf018 appears to be fine, boots reliably
  * commit 8e934dbf causes black screen issue

as you can see, rather than test the *merge* above, i decided to back
up one level and test the commit that was part of that merge, and it
failed.  is this helpful?  here's the log entry:

commit 8e934dbf264418afe4d1dff34ce074ecc14280db
Author: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
Date:   Mon Jan 24 12:34:00 2011 +0000

    drm/i915: Prevent uninitialised reads during error state capture

    error_bo and pinned_bo could be used uninitialised if there were no
    active buffers.

    Caught by kmemcheck.

    Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>


  i'm going to go on and test the merge itself, abb72c82, since i
thought that was working fine earlier today.  but you can see which
commit now seems to fail.  does this make any sense?

rday

-- 

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel


[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux