From: David Miller <davem@davemloft.net>
To: ben@decadent.org.uk
Cc: linux-ide@vger.kernel.org, 590327@bugs.debian.org, jan@goneko.de
Subject: Re: Bug#590327: linux-image-2.6.32-5-amd64: Unbalanced enable for IRQ 19
Date: Wed, 07 Sep 2011 01:16:13 -0400 (EDT) [thread overview]
Message-ID: <20110907.011613.391683420146319494.davem@davemloft.net> (raw)
In-Reply-To: <1315371519.3092.457.camel@deadeye>
From: Ben Hutchings <ben@decadent.org.uk>
Date: Wed, 07 Sep 2011 05:58:33 +0100
> Well, I'm concerned with what to do in distro configurations which
> aren't just for 'modern systems'. We already swapped over all the
> drivers not labelled as experimental. With the rest, I worry that we'd
> be exchanging obscure IDE drivers that mostly work for obscure libata
> drivers that have had little if any testing. That strikes me as being
> even more risky for the users with the old controllers.
>
> I suppose that for those controllers where the libata driver is
> experimental we could build both drivers, blacklist the IDE drivers and
> let people override that if necessary. (And hope that most of the bugs
> get shaken out of the libata drivers before we do a stable release,
> because that is too ugly to keep doing for long.)
But for the cases these bugs are hitting these are systems the old
drivers never could have worked on, because of the IRQ sharing issue
with things like USB controllers.
I think your blacklisting idea probably makes the most sense.
prev parent reply other threads:[~2011-09-07 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100725223004.5262.16774.reportbug@localhost>
[not found] ` <1280422961.13192.287.camel@localhost>
[not found] ` <20100730000715.GA6666@goneko.de>
[not found] ` <20110729151848.GA24689@pisco.westfalen.local>
[not found] ` <20110731184933.GA2442@goneko.de>
2011-09-07 4:16 ` Bug#590327: linux-image-2.6.32-5-amd64: Unbalanced enable for IRQ 19 Ben Hutchings
2011-09-07 4:39 ` David Miller
2011-09-07 4:58 ` Ben Hutchings
2011-09-07 5:16 ` David Miller [this message]
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=20110907.011613.391683420146319494.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=590327@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=jan@goneko.de \
--cc=linux-ide@vger.kernel.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