From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Cc: "Li,
Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.6.1 - IRQ routing regression on Abit VP6
Date: Wed, 14 Jan 2004 11:17:42 +0100 [thread overview]
Message-ID: <20040114101742.GQ14031@poupinou.org> (raw)
In-Reply-To: <4004D220.8010804-Wuw85uim5zDR7s880joybQ@public.gmane.org>
On Tue, Jan 13, 2004 at 11:22:40PM -0600, Ian Pilcher wrote:
> Li, Shaohua wrote:
> >Did you open CONFIG_PCI_USE_VECTOR? Please try close it or try the
> >attached patch.
>
> It sounds like you may not have read all the way to the bottom. I was
> able to get 2.6.1 working by updating the ACPI to version 20031203.
>
> So I wasn't asking for help, just reporting a bug. (And generally
> complaining about such an ugly regressing in a supposedly stable kernel
> series.)
>
It's just a stupid though, and I'm certainly wrong. Unless there is
a 2.7 tree, 2.6 can't be considered "stable".
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-14 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 5:09 2.6.1 - IRQ routing regression on Abit VP6 Li, Shaohua
[not found] ` <571ACEFD467F7749BC50E0A98C17CDD8D5FEB8-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-14 5:22 ` Ian Pilcher
[not found] ` <4004D220.8010804-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2004-01-14 10:17 ` Ducrot Bruno [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 4:42 Ian Pilcher
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=20040114101742.GQ14031@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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