From: Andrew Morton <akpm@linux-foundation.org>
To: "Andev Debi" <andev.debi@gmail.com>
Cc: "debian developer" <debiandev@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
lenb@kernel.org, rl@hellgate.ch, Dave Airlie <airlied@linux.ie>
Subject: Re: Problem - disabling IRQ #20 and others
Date: Thu, 2 Aug 2007 11:31:46 -0700 [thread overview]
Message-ID: <20070802113146.30eb2139.akpm@linux-foundation.org> (raw)
In-Reply-To: <ef8c225f0708020427i6665d486he6a90f1f02823382@mail.gmail.com>
On Thu, 2 Aug 2007 16:57:42 +0530
"Andev Debi" <andev.debi@gmail.com> wrote:
> On 8/2/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> >> Please fix the wordwrapping before sending any more stuff - it's truly awful.
> >
> Sorry about that. Gmail automatically wraps the line. Will check in the future.
>
> > Could be a bug in the via driver, but it's more likely an
> > acpi/pci/platform/bios thing.
> >
> CC'ing VIA Rhine network driver maintainer. May be he has any idea.
Sorry, I meant the VIA DRM driver.
> CC'ing ACPI people too.
I suspect that's getting warmer.
> > Did any previous kernels work OK? If so, which?
> >
>
> I booted with the stock ubuntu kernel 2.6.15-28-386, and it is showing
> a different irq (irq #201)being disabled.
OK, that's bad.
> Im attaching the dmesg of both stock 2.6.15 and self compiled 2.6.22.1-cfs-v19
For long-term bugs like this one it's best to track it in
bugzilla.kernel.org. I'd suggest that you assign it to
acpi_config-interrupts@kernel-bugs.osdl.org and add airlied@linux.ie to the
cc.
It'll take a while, but these things often do end up fixed.
next prev parent reply other threads:[~2007-08-02 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 10:47 Problem - disabling IRQ #20 and others Andev Debi
2007-08-01 14:11 ` debian developer
2007-08-01 16:01 ` Andev Debi
2007-08-02 8:48 ` Andrew Morton
2007-08-02 11:27 ` Andev Debi
2007-08-02 18:31 ` Andrew Morton [this message]
2007-08-03 9:25 ` Andev Debi
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=20070802113146.30eb2139.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=andev.debi@gmail.com \
--cc=debiandev@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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