Bug 7788
Summary: | System freeze as soon as PCMCIA card is inserted | ||
---|---|---|---|
Product: | Drivers | Reporter: | Gautam Iyer (gi1242) |
Component: | PCMCIA | Assignee: | linux-pcmcia |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | akpm, bjorn.helgaas, gi1242, linux, protasnb, serge |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.20 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Gautam Iyer
2007-01-08 01:12:56 UTC
I have the same problem with a wireless card (senao with prism chipset). Immediate system freeze upon insertion, no logs anywhere that I can find. I too am running Gentoo. pcmciautils-014-r1 udev-103 Sorry i forgot to add this in my previous post. When the card is inserted while the machine is off, at boot time the system hangs at the "Letting udev process events" step. Any updates on this probelms? Still present in latest kernels? Thanks. My system freezes when I am inserting any pcmcia card into slot and unfreezes after I remove it. I see it both on 2.6.18 and 2.6.20 kernels. # uname -a Linux localhost 2.6.20-gentoo #5 PREEMPT Sat Jul 14 12:20:35 MSD 2007 i686 Intel(R) Pentium(R) M processor 1.60GHz GenuineIntel GNU/Linux #dmesg ... pccard: card ejected from slot 0 MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0. Bank 0: b200004000000800 pccard: CardBus card inserted into slot 0 PCI: Error while updating region 0000:03:00.0/0 (6c000000 != ffffffff) PCI: Error while updating region 0000:03:00.1/0 (6c001000 != ffffffff) PCI: Error while updating region 0000:03:00.3/0 (6c002000 != ffffffff) ACPI: PCI Interrupt 0000:03:00.3[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 ehci_hcd 0000:03:00.3: EHCI Host Controller ehci_hcd 0000:03:00.3: new USB bus registered, assigned bus number 5 PCI: cache line size of 32 is not supported by device 0000:03:00.3 ehci_hcd 0000:03:00.3: irq 10, io mem 0x6c002000 ehci_hcd 0000:03:00.3: startup error -19 ehci_hcd 0000:03:00.3: USB bus 5 deregistered ACPI: PCI interrupt for device 0000:03:00.3 disabled ehci_hcd 0000:03:00.3: init 0000:03:00.3 fail, -19 pccard: card ejected from slot 0 ... Denis, Please try the latest-latest (2.6.22+) because there were fixes to register/unregister driver in USB area as well as device insertion/removal. Thanks. Bjorn, could you please take a look at this one? The theory is that the motherboard PNP resource management has claimed resources which the caddbus device wants to use. Probably it'd be helpful if the repprters could attach their full dmesg output and /proc/iomem and /proc/ioports output, thanks. Hi, Sorry for disappearing on you guys. I was traveling for a month, and had no access to a PC Card reader. But yes, I got back this week and plugged the same PC Card reader into my system. (I naturally braced my self for a complete system freeze). But surprisingly, it worked *perfectly*. It mounted my memory card as a IDE hard disk, after which I could happily copy pictures to my hearts content. I'm now using 2.6.21. I presume the original bug is now fixed in 2.6.21 :). Do you still see any issues in 2.6.21 Denis? Thanks, GI CardBus resource management is not well-integrated with the rest of the system, so I'm sure there are still problems lurking here. If somebody could (1) verify that there's still a problem, and (2) start collecting information like the dmesg log and /proc/{iomem,ioports} contents, we could start looking at it. Oops, I should have said PCMCIA resource management, not CardBus. I was thinking of the PCMCIA resource database, which tells the kernel which resources are available for use by PCMCIA. That information really ought to come from PNPBIOS or ACPI, not a user-supplied configuration file. The lspci says "CardBus bridge", so I guess this problem should be CardBus-related, and the PCMCIA resource database shouldn't be involved at all. Sorry for muddying the waters. If we think there's a PNP/CardBus conflict, the dmesg and /proc/iomem and ioports info still might shed some light. |