Disabling IRQ #4 (serial related)

Bug #70002 reported by Paul Sladen
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

$ dmesg | tail -15 | cut -c19-
irq 4: nobody cared (try booting with the "irqpoll" option)
 <c0139ed4> __report_bad_irq+0x24/0x80 <c0139fcf> note_interrupt+0x9f/0x1f0
 <c0139993> handle_IRQ_event+0x33/0x60 <c0139a75> __do_IRQ+0xb5/0xc0
 <c01056f9> do_IRQ+0x19/0x30 <c0103e8a> common_interrupt+0x1a/0x20
 <c02221a2> serial8250_startup+0x152/0x440 <c021df28> uart_startup+0x48/0x130
 <c021ed0f> uart_open+0xbf/0x410 <c01594cd> get_empty_filp+0x5d/0x110
 <c020de51> tty_open+0x161/0x310 <c016084e> chrdev_open+0x6e/0x140
 <c01607e0> chrdev_open+0x0/0x140 <c0156674> __dentry_open+0xb4/0x1e0
 <c0156855> nameidata_to_filp+0x35/0x40 <c01568b0> do_filp_open+0x50/0x60
 <c0115d10> default_wake_function+0x0/0x10 <c0156555> get_unused_fd+0x45/0xb0
 <c015690a> do_sys_open+0x4a/0xe0 <c01569dc> sys_open+0x1c/0x20
 <c0102dbb> sysenter_past_esp+0x54/0x79
handlers:
[<c0222520>] (serial8250_interrupt+0x0/0xf0)
Disabling IRQ #4

$ grep ' 4:' /proc/interrupts
  4: 200074 IO-APIC-edge serial

$ sudo setserial -g /dev/ttyS0
/dev/ttyS0, UART: undefined, Port: 0x03f8, IRQ: 4

This laptop (ThinkPad R52) does not have a physical serial port (there is IRDA) on the main body, although there could be one wired for the docking bay.

I've seen this issue once before.

description: updated
Revision history for this message
Paulo Pereira (pjpereira) wrote :

i also have this problem with a wireless card (Broadcom) and ndiswrapper. after a few minutes of perfect work the card just stops working with a console message of disabling irq #xxx (the irq number changes). I am working with edgy x86 but i got the same problem with amd64.

Revision history for this message
Raphaël Quinet (raphael-gimp) wrote :

For what it's worth, I have also seen the same issue on an old HP/Compaq x86 machine after upgrading it from kernel 2.4.x to 2.6.18. It looks like this could be related to a kernel bug, according to this short thread on the Linux kernel mailing list:
http://lkml.org/lkml/2006/12/29/30

Rolf Leggewie (r0lf)
Changed in linux-source-2.6.17:
status: New → Confirmed
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Markus Korn (thekorn) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,
Markus

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.