From: Daniel Ritz <daniel.ritz@gmx.ch>
To: Kitt Tientanopajai <kitt@gear.kku.ac.th>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5 yenta_socket irq 10: nobody cared!
Date: Wed, 7 Apr 2004 17:41:47 +0200 [thread overview]
Message-ID: <200404071741.47624.daniel.ritz@gmx.ch> (raw)
In-Reply-To: <20040406093510.33c937e3.kitt@gear.kku.ac.th>
On Tuesday 06 April 2004 04:35, Kitt Tientanopajai wrote:
> Hi,
>
> > this is a known problem with the acer travelmate 361. it reports IRQ 11 for
> > the O2Micro cardbus bridge when it is in reality IRQ 10.
> >
> > see:
> > http://www.naos.co.nz/hardware/laptop/acer-361evi/x94.html#AEN138
> > and
> > http://sourceforge.net/tracker/index.php?func=detail&aid=533863&group_id=2405&atid=102405
>
> Thanks for info. I'll try that.
>
> > please give a full dmesg and a lspci -vvvn.
> > are you using ACPI?
>
> My boot param is "acpi=on pci=noacpi", below is output from dmesg and lspci.
>
>
> kitt
>
> --
>
> $ dmesg
looks like you need a little workaround in the interuput routing code...please
apply the attached patch, send dmesg output plus output of dmidecode
( http://www.nongnu.org/demidecode/ ).
on the other side it could be that the o2micro bridge is wrongly programmed.
what looks a bit weired is that both functions of the o2micro show Pin A
routed to IRQ 11. this could be wrong. i'm reading the spec now.
do you happen to have the redmond OS on this machine? it would be nice to see
which interrupt windoze assignes to the o2micro bridge.
and one more question: any change in the interrupt assignment if you use full ACPI?
--- 1.36/arch/i386/pci/irq.c Fri Feb 27 06:48:13 2004
+++ edited/arch/i386/pci/irq.c Wed Apr 7 13:57:44 2004
@@ -542,8 +542,6 @@
r->name = "SIS";
r->get = pirq_sis_get;
r->set = pirq_sis_set;
- DBG("PCI: Detecting SiS router at %02x:%02x\n",
- rt->rtr_bus, rt->rtr_devfn);
return 1;
}
--- 1.17/arch/i386/pci/pci.h Mon Mar 1 07:20:00 2004
+++ edited/arch/i386/pci/pci.h Wed Apr 7 13:56:51 2004
@@ -4,7 +4,7 @@
* (c) 1999 Martin Mares <mj@ucw.cz>
*/
-#undef DEBUG
+#define DEBUG
#ifdef DEBUG
#define DBG(x...) printk(x)
next prev parent reply other threads:[~2004-04-07 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 0:27 2.6.5 yenta_socket irq 10: nobody cared! Daniel Ritz
2004-04-06 2:35 ` Kitt Tientanopajai
2004-04-07 15:41 ` Daniel Ritz [this message]
2004-04-07 19:24 ` Kitt Tientanopajai
2004-04-07 20:25 ` Daniel Ritz
2004-04-08 7:37 ` Kitt Tientanopajai
2004-04-08 15:17 ` Daniel Ritz
2004-04-09 2:30 ` Kitt Tientanopajai
2004-04-09 17:41 ` Daniel Ritz
2004-04-10 3:18 ` Kitt Tientanopajai
2004-04-10 16:14 ` Daniel Ritz
2004-04-10 19:40 ` Kitt Tientanopajai
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 2:06 Kitt Tientanopajai
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=200404071741.47624.daniel.ritz@gmx.ch \
--to=daniel.ritz@gmx.ch \
--cc=kitt@gear.kku.ac.th \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).