From: Edward Donovan <edward.donovan@numble.net>
To: Chris Palmer <chris.palmer@pobox.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: [PROBLEM] ASUS Sandybridge motherboards + PCI not working (IRQ n: nobody cared)
Date: Tue, 13 Dec 2011 19:12:21 -0500 [thread overview]
Message-ID: <20111214001221.GA2143@Brahman> (raw)
In-Reply-To: <4EE72C4D.9080207@pobox.com>
Hi Chris -
[Dammit, accidentally sent an html mail. Should have stepped out of gmail,
sorry.]
I will certainly take a look. I don't have the hardware, unfortunately. And
this is kinda my first rodeo, kernel-wise, so don't let me sound too expert. :)
Let me ask a couple questions, anyway.
- Later, I'll have time to look for Andrew's message, but do you know -- did he
mean an ACPI bug in the firmware, or in Linux?
- Does 2.6.38 behave the same as 3.1.5 or the other newest kernels? (If the
hardware doesn't require something newer than .38.) There was an IRQ overhaul
in 2.6.39, and the two bugs I fixed were regressions from that work. As of
now, the bad-irq handling seems equivalent to 2.6.38, but I should make sure
that goes for your problem, too.
I think I'll cc LKML, too, if you don't mind. I've seen this topic going by,
but don't know what's been said. And maybe tomorrow I can get some pondering
time -
Ed
next prev parent reply other threads:[~2011-12-14 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:04 [PROBLEM] ASUS Sandybridge motherboards + PCI not working (IRQ n: nobody cared) Chris Palmer
2011-10-15 0:29 ` Robert Hancock
2011-10-15 8:43 ` Chris Palmer
2011-10-15 16:23 ` Robert Hancock
[not found] ` <4EE72C4D.9080207@pobox.com>
2011-12-14 0:12 ` Edward Donovan [this message]
[not found] ` <CADdbW+E9=DKZ-839yPW_R4JM1omXEzqGqT=ae7Txu4Jikyw2=A@mail.gmail.com>
2011-12-14 10:49 ` Chris Palmer
2011-10-15 16:51 ` Thomas Backlund
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=20111214001221.GA2143@Brahman \
--to=edward.donovan@numble.net \
--cc=chris.palmer@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).