PCMCIA modem gives IRQ error

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested from https://help.ubuntu.com/community/DebuggingIRQProblems as separate attachments.

Christian, please stop using generic bug messages.

Jonathan, what I need you to attach to this bug is the following:

cat /proc/interrupts
lspci -vv
lspci -vvn

Attach these separately (do not paste into comment)

Thanks

Bug still in feisty's default kernel (with Novatel Wireless Merlin U630).

You can add Shared IRQ in the kernel (I think that was not necessary in 2.6.19) :

Character Device
  -> Serial Driver
    -> Extended 8250/16550 serial driver options
          [x] Support for sharing serial interrupts

I have that bug also with Novatel Wireless Merlin U530 on Ubuntu feisty.

I have same problem with Merlin U530 on (k)ubuntu feisty.

"Support for sharing serial interrupts" added, but nothing...

dmesg:

[ 625.500000] pccard: PCMCIA card inserted into slot 0
[ 625.500000] pcmcia: registering new device pcmcia0.0
[ 625.500000] kobject 0.0: registering. parent: 0000:03:05.0, set: devices
[ 625.500000] PM: Adding info for pcmcia:0.0
[ 625.500000] kobject_uevent_env
[ 625.500000] fill_kobj_path: path = '/devices/pci0000:00/0000:00:1e.0/0000:03:05.0/0.0'
[ 625.500000] pcmcia: registering new device pcmcia0.1
[ 625.500000] kobject 0.1: registering. parent: 0000:03:05.0, set: devices
[ 625.500000] PM: Adding info for pcmcia:0.1
[ 625.500000] kobject_uevent_env
[ 625.500000] fill_kobj_path: path = '/devices/pci0000:00/0000:00:1e.0/0000:03:05.0/0.1'
[ 625.516000] pcmcia: request for exclusive IRQ could not be fulfilled.
[ 625.516000] pcmcia: the driver needs updating to supported shared IRQ lines.
[ 625.560000] PM: Removing info for No Bus:ttyS0
[ 625.560000] kobject_uevent_env
[ 625.560000] fill_kobj_path: path = '/class/tty/ttyS0'
[ 625.560000] fill_kobj_path: path = '/devices/platform/serial8250'
[ 625.560000] kobject ttyS0: cleaning up
[ 625.564000] kobject ttyS0: registering. parent: tty, set: devices
[ 625.564000] PM: Adding info for No Bus:ttyS0
[ 625.564000] kobject_uevent_env
[ 625.564000] fill_kobj_path: path = '/class/tty/ttyS0'
[ 625.564000] fill_kobj_path: path = '/devices/pci0000:00/0000:00:1e.0/0000:03:05.0/0.0'

Option Globetrotter EDGE works correctly but this is a PCMCIA card, U530 is a newer cardbus type.

MSI L720 notebook, Intel 915GM/ICH6, O2 Micro cardbus controller

I can confirm this behaviour:

Aug 11 09:37:54 bnibws02 kernel: [55397.324000] pccard: PCMCIA card inserted into slot 0
Aug 11 09:37:54 bnibws02 kernel: [55397.324000] cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
Aug 11 09:37:54 bnibws02 kernel: [55397.324000] cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
Aug 11 09:37:54 bnibws02 kernel: [55397.340000] pcmcia: registering new device pcmcia0.0
Aug 11 09:37:54 bnibws02 kernel: [55397.340000] pcmcia: registering new device pcmcia0.1
Aug 11 09:37:54 bnibws02 kernel: [55397.432000] pcmcia: request for exclusive IRQ could not be fulfilled.
Aug 11 09:37:54 bnibws02 kernel: [55397.432000] pcmcia: the driver needs updating to supported shared IRQ lines.
Aug 11 09:37:54 bnibws02 kernel: [55397.476000] 0.0: ttyS2 at I/O 0x3e8 (irq = 3) is a 16550A

OS is Ubuntu 7.04, Kernel 2.6.20-16-generic, Card Merlin U530

I have a Merlin U630 and get the same sort of thing about shared interrupts on Gutsy (2.6.22)

To get the card to work on my Laptop (HP dv1448ea) (915 chipset) I have to exclude the serial port ranges that the PCMCIA modem wants to use:

/etc/pcmcia/config.opts:

exclude port 0x2f8-0x2ff
exclude port 0x3f8-0x3ff

I still get the warnings from pcmcia but the the card works:

[ 16.812000] pcmcia: request for exclusive IRQ could not be fulfilled.
[ 16.812000] pcmcia: the driver needs updating to supported shared IRQ lines.
[ 16.856000] 0.0: ttyS2 at I/O 0x3e8 (irq = 3) is a 16550A
[ 16.856000] pcmcia: request for exclusive IRQ could not be fulfilled.
[ 16.856000] pcmcia: the driver needs updating to supported shared IRQ lines.
[ 16.896000] 0.1: ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A

Interestingly, on Windows XP there is a 'patch' that you have to install to make the card work that I expect does the same thing. Therefore, I think there is a hardware problem (i.e. a bug in the HP laptop hardware) with the PCI bridge to the PCMCIA slot which is preventing the serial ports on ISA 0x2f8, etc. from reaching the CPU and therefore, the PCMCIA code falls back to the other ports as specified by the CIS on the U630 card. Hope this helps somebody.

Cheers
Alex.

I can confirm this on gutsy and cannot seem to get the vodafone mobile connect utility for linux to work because of that. This happens both on an older Samsung P30 and on a newer Samsung Q35 laptop (entirely different hardware).

Unfortunately Alex's config.opts fix does not work in my case, I still cannot access the card.

Seems to work on the same machine (see https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/79398/comments/9) an 8.04:

Jul 6 11:27:20 bnibws02 kernel: [12297.914651] pccard: PCMCIA card inserted into slot 0
Jul 6 11:27:20 bnibws02 kernel: [12297.914666] cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
Jul 6 11:27:20 bnibws02 kernel: [12297.914707] cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
Jul 6 11:27:20 bnibws02 kernel: [12297.936827] pcmcia: registering new device pcmcia0.0
Jul 6 11:27:20 bnibws02 kernel: [12297.938987] pcmcia: registering new device pcmcia0.1
Jul 6 11:27:20 bnibws02 kernel: [ 4610.700408] 0.0: ttyS2 at I/O 0x3e8 (irq = 3) is a 16550A

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.