[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20061205225126.d4118036.akpm@osdl.org>
Date: Tue, 5 Dec 2006 22:51:26 -0800
From: Andrew Morton <akpm@...l.org>
To: Oleg Mikheev <mihel@...box.ru>
Cc: linux-kernel@...r.kernel.org, "Brown, Len" <len.brown@...el.com>
Subject: Re: kernel 2.6.19 and RealTek RTL8139 interrupt
On Tue, 05 Dec 2006 21:36:37 +0300
Oleg Mikheev <mihel@...box.ru> wrote:
> Hi guys,
>
> I'm using FC5 with vanilla kernels.
> Everything worked great until 2.6.19 was released.
> Not each time I'm trying to up my eth0 kernel produces this:
>
>
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> irq 18: nobody cared (try booting with the "irqpoll" option)
> [<c01391aa>] __report_bad_irq+0x36/0x7d
> [<c0139379>] note_interrupt+0x188/0x1c3
> [<c0138a19>] handle_IRQ_event+0x1a/0x3f
> [<c01396ca>] handle_fasteoi_irq+0x61/0x73
> [<c0104e34>] do_IRQ+0x6b/0x83
> [<c0120c76>] sys_rt_sigprocmask+0x80/0x93
> [<c01034a2>] common_interrupt+0x1a/0x20
> =======================
> handlers:
> [<c0257416>] (rtl8139_interrupt+0x0/0x3aa)
> Disabling IRQ #18
>
>
> I'm posting it here b/c I don't think it's a normal behavior.
> Here is the diff of dmesg output between 2.6.18.3 and 2.6.19:
>
>
> 140,142c141,143
> < 8139too Fast Ethernet driver 0.9.27
> < ACPI: PCI Interrupt 0000:01:06.0[A] -> GSI 20 (level, low) -> IRQ 20
> < eth0: RealTek RTL8139 at 0xf8806c00, 00:40:45:28:2c:ae, IRQ 20
> ---
> > 8139too Fast Ethernet driver 0.9.28
> > ACPI: PCI Interrupt 0000:01:06.0[A] -> GSI 20 (level, low) -> IRQ 18
> > eth0: RealTek RTL8139 at 0xf8806c00, 00:40:45:28:2c:ae, IRQ 18
> 147c148
> < ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
> ---
> > ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 19
This looks like http://bugzilla.kernel.org/show_bug.cgi?id=7601
Please see http://bugzilla.kernel.org/show_bug.cgi?id=7601#c10 for a
possible fix.
That fix is in mainline now, so testing Linus's current tree would suit
too, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists