Inserting an SD card disabled my ipw2200 and the SD slot

Bug #123129 reported by Rich on 2007-06-29
2
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

I inserted an SD card with a FAT32 filesystem into my laptop. I expected either pmount to notice and automount the card, or dmesg to notice and let me mount it manually.

Instead, dmesg printed this:
Jun 29 01:24:13 eris kernel: [467645.624000] mmc0: Problem switching card into high-speed mode!
Jun 29 01:24:14 eris kernel: [467645.624000] mmcblk0: mmc0:efa9 SU02G 1985024KiB

Annoyed, I used cfdisk to check the partition table of /dev/mmcblk0 - yes, it saw the partition there and even thought it should be mmcblk0p1, but nothing appeared in /dev/ or dmesg. hdparm -z /dev/mmcblk0 yielded no improvement.

I ejected the card (physically, not eject /dev/[etc]), and tried to remove the mmc modules - mmc_block and mmc_core were in use and wouldn't unload, but sdhci unloaded. I tried reinserting the card, and syslogd wrote the following to every terminal:
[13158.204000] Disabling IRQ #18

The following appeared in dmesg:
[13158.204000] irq 18: nobody cared (try booting with the "irqpoll" option)
[13158.204000] [<c01543a4>] __report_bad_irq+0x24/0x80
[13158.204000] [<c015465e>] note_interrupt+0x25e/0x290
[13158.204000] [<c01538d0>] handle_IRQ_event+0x30/0x60
[13158.204000] [<c0154f91>] handle_fasteoi_irq+0xc1/0xf0
[13158.204000] [<c0105b70>] do_IRQ+0x40/0x80
[13158.204000] [<c0104233>] common_interrupt+0x23/0x30
[13158.204000] [<c02100d8>] acpi_ds_load2_end_op+0xa4/0x2d1
[13158.204000] [<f88637e2>] acpi_processor_idle+0x225/0x3f7 [processor]
[13158.204000] [<c0101409>] cpu_idle+0x49/0xd0
[13158.204000] [<c03d97f5>] start_kernel+0x365/0x420
[13158.204000] [<c03d9230>] unknown_bootoption+0x0/0x260
[13158.204000] =======================
[13158.204000] handlers:
[13158.204000] [<f890ef10>] (usb_hcd_irq+0x0/0x60 [usbcore])
[13158.204000] [<f8b8c710>] (ipw_isr+0x0/0xc0 [ipw2200])
[13158.204000] Disabling IRQ #18
[13171.848000] ipw2200: Failed to send SCAN_REQUEST_EXT: Command timed out.
[13192.856000] ipw2200: Failed to send SCAN_REQUEST_EXT: Command timed out.
[13193.856000] ipw2200: Failed to send ASSOCIATE: Command timed out.
[13194.880000] ipw2200: Failed to send CARD_DISABLE: Command timed out.
[13194.944000] ACPI: PCI interrupt for device 0000:03:03.0 disabled

And my IPW card stopped functioning.

Needless to say, my MMC/SD reader was also not functioning, and removing/reinserting the card elicited no messages from dmesg.

I tried unloading and reloading the IPW driver, and received this for my troubles:
[13201.484000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
[13201.484000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[13201.484000] ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 17 (level, low) -> IRQ 18
[13201.484000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[13202.696000] ipw2200: Failed to send TX_POWER: Command timed out.
[13203.816000] ipw2200: Failed to send TX_POWER: Command timed out.
[13204.936000] ipw2200: Failed to send TX_POWER: Command timed out.
[13206.056000] ipw2200: Failed to send TX_POWER: Command timed out.
[13207.180000] ipw2200: Failed to send TX_POWER: Command timed out.
[13207.180000] ipw2200: Unable to initialize device after 5 attempts.
[13207.180000] ipw2200: failed to register network device
[13207.180000] ACPI: PCI interrupt for device 0000:03:03.0 disabled
[13207.180000] ipw2200: probe of 0000:03:03.0 failed with error -5

I tried a soft reboot of the machine, but the IPW card and SD reader were still inoperable afterward. Only after powering the machine off did they return to normal functionality.

Attached below will be the lspci -vvv output of these cards.

Rich (rincebrain) wrote :
Paul Dufresne (paulduf) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Paul Dufresne (paulduf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers