From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chuck Ebbert <cebbert@redhat.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Rodrigo Luiz <troops.of.doom@gmail.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@suse.cz>,
Ben Collins <bcollins@ubuntu.com>,
reiserfs-devel@vger.kernel.org,
"Vladimir V. Saveliev" <vs@namesys.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-ide@vger.kernel.org, David Chinner <dgc@sgi.com>,
Tejun Heo <htejun@gmail.com>,
Rodney Gordon II <meff@spherevision.org>
Subject: Re: [1/2] 2.6.22-rc6: known regressions v2
Date: Fri, 29 Jun 2007 14:10:49 -0400 [thread overview]
Message-ID: <46854B29.80906@garzik.org> (raw)
In-Reply-To: <20070629190602.4ef6a0cb@the-village.bc.nu>
Alan Cox wrote:
>>> I'm not even sure this report is IT8212 related rather than just an IRQ
>>> storm
>> Why does the driver report "irq 0"?
>>
>> ata7: PATA max UDMA/133 cmd <blah> ctl <blah> bmdma <blah> irq 0 <====
>>
>> Above that, the ACPI layer says it assigned IRQ 20
>
> Because the libata core code in 2.6.22rc6 reports all the ports and IRQ
> values wrongly ?
AFAIK that was fixed, for IRQ. Please point out examples where it
remains broken...
Jeff
next prev parent reply other threads:[~2007-06-29 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 15:13 [1/2] 2.6.22-rc6: known regressions v2 Michal Piotrowski
2007-06-29 16:59 ` Alan Cox
2007-06-29 17:39 ` Chuck Ebbert
2007-06-29 18:06 ` Alan Cox
2007-06-29 18:10 ` Jeff Garzik [this message]
2007-06-29 18:24 ` Alan Cox
2007-06-29 21:01 ` Jeff Garzik
2007-06-29 17:55 ` Michal Piotrowski
2007-06-29 17:09 ` Sergei Shtylyov
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=46854B29.80906@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bcollins@ubuntu.com \
--cc=cebbert@redhat.com \
--cc=dgc@sgi.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meff@spherevision.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=perex@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=troops.of.doom@gmail.com \
--cc=vs@namesys.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 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.