linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: PCI ACPI/IRQ-routing broken on H77 chipset + Ivy Bridge (kernel 3.5-rc7 and earlier)
Date: Sun, 15 Jul 2012 22:25:48 +0200	[thread overview]
Message-ID: <201207152225.49154.rjw@sisk.pl> (raw)
In-Reply-To: <5002BC55.3050107@gmx.de>

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

  reply	other threads:[~2012-07-15 20:20 UTC|newest]

Thread overview: 5+ 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 [this message]
2012-07-16 16:14   ` Bjorn Helgaas
2012-07-19 18:14     ` Malte Schröder
2012-07-30 17:12       ` [Bug 43238] " Bjorn Helgaas

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=201207152225.49154.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=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 \
    /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).