From: Oleg Mikheev <mihel@hotbox.ru>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.6.19 and RealTek RTL8139 interrupt
Date: Tue, 05 Dec 2006 21:36:37 +0300 [thread overview]
Message-ID: <4575BC35.7050008@hotbox.ru> (raw)
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
197,198c198,200
< TCP bic registered
< Initializing IPsec netlink socket
---
> input: AT Translated Set 2 keyboard as /class/input/input0
> TCP cubic registered
> Initializing XFRM netlink socket
294,306c305,310
< Non-volatile memory driver v1.2
< usb 4-2: new full speed USB device using uhci_hcd and address 2
< PM: Adding info for usb:4-2
< PM: Adding info for No Bus:usbdev4.2_ep00
< usb 4-2: configuration #1 chosen from 1 choice
< PM: Adding info for usb:4-2:1.0
< PM: Adding info for No Bus:usbdev4.2_ep81
< PM: Adding info for No Bus:usbdev4.2_ep02
< PM: Adding info for No Bus:usbdev4.2_ep82
< PM: Adding info for usb:4-2:1.1
< PM: Adding info for No Bus:usbdev4.2_ep03
< PM: Adding info for No Bus:usbdev4.2_ep83
< Bluetooth: Core ver 2.10
---
> PM: Adding info for No Bus:usbdev3.2_ep02
> PM: Adding info for No Bus:usbdev3.2_ep82
> PM: Adding info for usb:3-2:1.1
> PM: Adding info for No Bus:usbdev3.2_ep03
> PM: Adding info for No Bus:usbdev3.2_ep83
> Bluetooth: Core ver 2.11
312,315c316,319
< PM: Removing info for No Bus:usbdev4.2_ep03
< PM: Removing info for No Bus:usbdev4.2_ep83
< PM: Adding info for No Bus:usbdev4.2_ep03
< PM: Adding info for No Bus:usbdev4.2_ep83
---
> PM: Removing info for No Bus:usbdev3.2_ep03
> PM: Removing info for No Bus:usbdev3.2_ep83
> PM: Adding info for No Bus:usbdev3.2_ep03
> PM: Adding info for No Bus:usbdev3.2_ep83
317,320c321
< usbcore: registered new driver hci_usb
< PM: Adding info for ieee1394:00012f650000d9b3
< ieee1394: Host added: ID:BUS[0-00:1023] GUID[00012f650000d9b3]
< PM: Adding info for ieee1394:00012f650000d9b3-0
---
> usbcore: registered new interface driver hci_usb
322c323
< device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
dm-devel@redhat.com
---
> device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised:
dm-devel@redhat.com
next reply other threads:[~2006-12-05 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 18:36 Oleg Mikheev [this message]
2006-12-06 6:51 ` kernel 2.6.19 and RealTek RTL8139 interrupt Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 17:22 Oleg Mikheev
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=4575BC35.7050008@hotbox.ru \
--to=mihel@hotbox.ru \
--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