From: Bjorn Helgaas <bhelgaas@google.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Malte Schröder" <maltesch@gmx.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, "Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: PCI ACPI/IRQ-routing broken on H77 chipset + Ivy Bridge (kernel 3.5-rc7 and earlier)
Date: Mon, 16 Jul 2012 10:14:56 -0600 [thread overview]
Message-ID: <CAErSpo6Ka6XBakVZH7ge-==XY86FrOHP_dqGoa+zAFNgnnnFTA@mail.gmail.com> (raw)
In-Reply-To: <201207152225.49154.rjw@sisk.pl>
[CC +tglx]
On Sun, Jul 15, 2012 at 2:25 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> CC-ing linux-pci and Bjorn.
>
> On Sunday, July 15, 2012, Malte Schröder wrote:
>> Hello,
>> this is yet another try to get someone to look at this ;)
>>
>> I can't get PCI-devices to work on my DH77KC mainboard. I tested this
>> using an AVM B1 ISDN card, a Fritz!PCI card and an old 3Com 905c NIC.
>> I attached some dumps in case it helps. The CPU is a Core i7 3770.
>>
>> PCI hardware is detected by the kernel, but it gives IRQ errors. Using
>> irqpoll allows the PCI card to somewhat work, but it is unreliable.
>>
>> There are some reports in Intel's support forums that also report
>> PCI-problems with this mainboard, but Intel doesn't seem to be
>> interested. So I hope this is something that is fixable on the kernel side.
>>
>> If there is more information needed, please let me know.
>>
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-16 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 12:49 PCI ACPI/IRQ-routing broken on H77 chipset + Ivy Bridge (kernel 3.5-rc7 and earlier) Malte Schröder
2012-07-15 20:25 ` Rafael J. Wysocki
2012-07-15 20:25 ` Rafael J. Wysocki
2012-07-16 16:14 ` Bjorn Helgaas [this message]
2012-07-19 18:14 ` Malte Schröder
2012-07-30 17:12 ` [Bug 43238] " Bjorn Helgaas
2012-07-17 18:01 ` Galen Seitz
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='CAErSpo6Ka6XBakVZH7ge-==XY86FrOHP_dqGoa+zAFNgnnnFTA@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maltesch@gmx.de \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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.