From: Jani Nikula <jani.nikula@linux.intel.com>
To: Colin Kincaid Williams <discord@uw.edu>, intel-gfx@lists.freedesktop.org
Subject: Re: i915 driver stack trace on laptop docking event
Date: Wed, 20 Apr 2016 13:06:00 +0300 [thread overview]
Message-ID: <87h9ewoarb.fsf@intel.com> (raw)
In-Reply-To: <CAB-gU_vxj_Eg9vyrLexeTm+8+EmXGYGCpeDNEsGgFELJLyQL8Q@mail.gmail.com>
On Wed, 20 Apr 2016, Colin Kincaid Williams <discord@uw.edu> wrote:
> bump
I'm not sure you properly appreciate the amount of email people here
handle.
> On Tue, Apr 19, 2016 at 4:05 AM, Colin Kincaid Williams <discord@uw.edu> wrote:
>> Hello,
>>
>> I tried to find the appropriate place to file a bug report. On my dell
>> latitude e5440 when I undock and redock I am unable to re-activate
>> both monitors using xrandr. I'm using linux kernel 4.4.5 and the i915
>> driver, and also could not find the appropriate section to file a bug
>> report.
>>
>> Can you appoint me to the appropriate section on the bug reporting
>> page to file the report against?
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-20 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 4:05 i915 driver stack trace on laptop docking event Colin Kincaid Williams
2016-04-20 1:07 ` Colin Kincaid Williams
2016-04-20 10:06 ` Jani Nikula [this message]
2016-04-20 19:16 ` Colin Kincaid Williams
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=87h9ewoarb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=discord@uw.edu \
--cc=intel-gfx@lists.freedesktop.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 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.