All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16581] New: 2.6.35 regression bisected : System hang when starting X with VGA/DVI monitor connected.
Date: Fri, 13 Aug 2010 14:19:10 GMT	[thread overview]
Message-ID: <bug-16581-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=16581

           Summary: 2.6.35 regression bisected : System hang when starting
                    X with VGA/DVI monitor connected.
           Product: Drivers
           Version: 2.5
    Kernel Version: 2.6.35
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: Roel.Teuwen@gmail.com
                CC: alexdeucher@gmail.com
        Regression: Yes


Created an attachment (id=27432)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=27432)
kernel .config file

After upgrading from 2.6.34 to 2.6.35.1 on my laptop, I'm seeing a hang and
blank screen when X is started if a VGA or DVI monitor is connected to the
docking station before boot. If I boot without the VGA or DVI monitor
connected, and hotplug them after X is started, all is fine. Interestingly,
there is no problem when both the VGA and DVI monitors are connected.
Console on radeondrmfb works all the time.

Attached you can find the kernel .config, dmesg with and without the panel
attached on boot and the Xorg log on success and failure.

I've bisected the problem to the following change :

ce8f53709bf440100cb9d31b1303291551cf517f is the first bad commit
commit ce8f53709bf440100cb9d31b1303291551cf517f
Author: Alex Deucher <alexdeucher@gmail.com>
Date:   Fri May 7 15:10:16 2010 -0400

    drm/radeon/kms/pm: rework power management

    - Separate dynpm and profile based power management methods.  You can
select the pm method
      by echoing the selected method ("dynpm" or "profile") to power_method in
sysfs.
    - Expose basic 4 profile in profile method
      "default" - default clocks
      "auto" - select between low and high based on ac/dc state
      "low" - DC, low power mode
      "high" - AC, performance mode
      The current base profile is "default", but it should switched to "auto"
once we've tested
      on more systems.  Switching the state is a matter of echoing the
requested profile to
      power_profile in sysfs.  The lowest power states are selected
automatically when dpms turns
      the monitors off in all states but default.
    - Remove dynamic fence-based reclocking for the moment.  We can revisit
this later once we
      have basic pm in.
    - Move pm init/fini to modesetting path.  pm is tightly coupled with
display state.  Make sure
      display side is initialized before pm.
    - Add pm suspend/resume functions to make sure pm state is properly
reinitialized on resume.
    - Remove dynpm module option.  It's now selectable via sysfs.

    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>

:040000 040000 fa3acba12b9886453c2de619577ae633abfc97bc
faf940f2c2791f1382ed1abbfa54e22df7e1c936 M    drivers

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
--

             reply	other threads:[~2010-08-13 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 14:19 bugzilla-daemon [this message]
2010-08-13 14:20 ` [Bug 16581] 2.6.35 regression bisected : System hang when starting X with VGA/DVI monitor connected bugzilla-daemon
2010-08-13 14:21 ` bugzilla-daemon
2010-08-13 14:45 ` bugzilla-daemon
2010-08-16  8:36 ` bugzilla-daemon
2012-08-13 15:48 ` bugzilla-daemon

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=bug-16581-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.