From: "Mirko Caserta" <mirko@mcaserta.com>
To: "OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>
Cc: "Linux Kernel ML" <linux-kernel@vger.kernel.org>
Subject: Re: 8139too not working in 2.6 (works now)
Date: Mon, 26 Apr 2004 17:37:24 +0200 [thread overview]
Message-ID: <opr62lomnxpsnffn@mail.mcaserta.com> (raw)
In-Reply-To: <878ygirctm.fsf@devron.myhome.or.jp>
I tried "acpi=off" and it worked like a charm. He's the new
/proc/interrupts:
carbon:~# cat /proc/interrupts
CPU0 CPU1
0: 857627 12 IO-APIC-edge timer
1: 1073 0 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
8: 1 1 IO-APIC-edge rtc
12: 87 0 IO-APIC-edge i8042
14: 4103 2 IO-APIC-edge ide0
15: 4900 2 IO-APIC-edge ide1
21: 4505 1 IO-APIC-level eth0
27: 1484 0 IO-APIC-level i91u, uhci_hcd, uhci_hcd,
uhci_hcd
NMI: 0 0
LOC: 857482 857455
ERR: 0
MIS: 0
Hope this helps someone else too.
Thanks a lot, Mirko.
On Tue, 27 Apr 2004 00:14:29 +0900, OGAWA Hirofumi
<hirofumi@mail.parknet.co.jp> wrote:
> "Mirko Caserta" <mirko@mcaserta.com> writes:
>
>> Anyway, it doesn't look like an irq problem to me. It looks more like
>> a wrong detection of the TX triggering level in the driver.
>
> In interrupts-2.6.6-rc2-mm2-broken-out,
>
> CPU0 CPU1
> 0: 103394 48 IO-APIC-edge timer
> 1: 157 0 IO-APIC-edge i8042
> 5: 2 1 IO-APIC-edge eth0
> ^^^^^^^^^^^^-- wrong
> 8: 2 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-level acpi
> 11: 3 1 IO-APIC-edge i91u
> 12: 87 0 IO-APIC-edge i8042
> 14: 1068 2 IO-APIC-edge ide0
> 15: 953 1 IO-APIC-edge ide1
>
> The above must be IO-APIC-level.
> And the following is interesting one.
>
> ACPI: ACPI tables contain no PCI IRQ routing entries
> PCI: Invalid ACPI-PCI IRQ routing table
> PCI: Probing PCI hardware
> PCI: Using IRQ router default [1106/3091] at 0000:00:00.0
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 1!
> PCI BIOS passed nonexistent PCI bus 0!
>
> Um.. can you try "pci=noacpi" or "acpi=off"?
next prev parent reply other threads:[~2004-04-26 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 11:35 8139too not working in 2.6 Mirko Caserta
2004-04-26 11:41 ` David Johnson
2004-04-26 12:14 ` MNH
2004-04-26 13:29 ` Gene Heskett
2004-04-26 14:26 ` David Johnson
2004-04-26 15:53 ` OGAWA Hirofumi
2004-04-26 12:05 ` Jorge Bernal (Koke)
2004-04-26 12:13 ` David Johnson
2004-04-26 16:01 ` Jorge Bernal
2004-04-26 12:41 ` Derek Chen-Becker
2004-04-26 12:58 ` OGAWA Hirofumi
2004-04-26 14:46 ` Mirko Caserta
2004-04-26 15:14 ` OGAWA Hirofumi
2004-04-26 15:37 ` Mirko Caserta [this message]
2004-04-26 16:11 ` 8139too not working in 2.6 (works now) OGAWA Hirofumi
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=opr62lomnxpsnffn@mail.mcaserta.com \
--to=mirko@mcaserta.com \
--cc=hirofumi@mail.parknet.co.jp \
--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 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.