linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Matthew Garrett <mjg59@coreos.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, andre@lianse.eu
Subject: [REGRESSION, bisected] [Bug 102311] New: ASMEDA asm1062 not working
Date: Mon, 10 Aug 2015 10:34:11 -0500	[thread overview]
Message-ID: <CAErSpo7D51x=D4fuPuk0PyzrxqvnVTq684fKBR3J-CGeqUWTLQ@mail.gmail.com> (raw)

On Wed, Aug 5, 2015 at 1:36 AM,  <bugzilla-daemon@bugzilla.kernel.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=102311
>
>             Bug ID: 102311
>            Summary: ASMEDA asm1062 not working
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 4.1
>           Hardware: x86-64
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: PCI
>           Assignee: drivers_pci@kernel-bugs.osdl.org
>           Reporter: andre@lianse.eu
>         Regression: No
>
> Created attachment 184311
>   --> https://bugzilla.kernel.org/attachment.cgi?id=184311&action=edit
> git_bisect_4.0_4.1.log
>
> I'm running Arch Linux on a ASRock Z87 Extreme 6. After switching from 4.0
> kernel to 4.1. All drives attached to the ASMedia Chipset stopped working.
>
> To inspect this further I switched over to vanilla kernel and did a git bisect
> to mirror it down to the following commit:
> [387d37577fdd05e9472c20885464c2a53b3c945f] PCI: Don't clear ASPM bits when the
> FADT declares it's unsupported
>
> --
> You are receiving this mail because:
> You are watching the assignee of the bug.

                 reply	other threads:[~2015-08-10 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAErSpo7D51x=D4fuPuk0PyzrxqvnVTq684fKBR3J-CGeqUWTLQ@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=andre@lianse.eu \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg59@coreos.com \
    /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;
as well as URLs for NNTP newsgroup(s).