Bug 5017
| Summary: | pcmcia: trouble inserting network card and then network unstability | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Jean-Damien Durand (Jean-Damien.Durand) |
| Component: | PCMCIA | Assignee: | Dominik Brodowski (linux) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | Eugen.Dedu |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.13-rc5-git4 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
/var/log/syslog showing waproamd scanning again and again for an AP
my /proc/interrupts as of 2.6.13-rc5-git4 my /proc/pci as of 2.6.13-rc5-git4 my /proc/iomem as of 2.6.13-rc5-git4 my /proc/ioports as of 2.6.13-rc5-git4 my /proc/version as of 2.6.13-rc5-git4 |
||
|
Description
Jean-Damien Durand
2005-08-07 13:10:00 UTC
Created attachment 5535 [details]
/var/log/syslog showing waproamd scanning again and again for an AP
Strangely I do not see the "osl : wait for semaphore" error in my latest try.
Nevertheless network instability is still here.
Here is the /var/log/syslog of a kernel compiled with pci and pcmcia debug.
Search for "HERE" in this attachment.
Created attachment 5536 [details]
my /proc/interrupts as of 2.6.13-rc5-git4
Created attachment 5537 [details]
my /proc/pci as of 2.6.13-rc5-git4
Created attachment 5538 [details]
my /proc/iomem as of 2.6.13-rc5-git4
Created attachment 5539 [details]
my /proc/ioports as of 2.6.13-rc5-git4
Created attachment 5540 [details]
my /proc/version as of 2.6.13-rc5-git4
FYI, I tried with 2.6.13-rc6 - same thing: AP found, network available for few seconds, and then AP search again, etc. An update with 2.6.13-rc5-mm1. The network card is not seen at startup, and after few seconds there is: osl-0884 [139] os_wait_semaphore : Failed to acquire semaphore[ebf6e700|1| 0],AE_TIME When I get the card out there is: cs: pcmcia_socket0: parse_events: events 00000080 > An update with 2.6.13-rc5-mm1. The network card is not seen at startup, andI
I mean: is not seen when I insert it. Sorry.
I also see those semaphore errors: See Bug #5008 and the C program attached there to reliably generate those errors. From a fair amount of testing, I find that the errors correlate with running a pre-emptible kernel: the non-preemptible kernels don't show it, and the voluntary preempt or fully preemptible ones do. Which I suspect is also correlated with S3 sleep hanging on my thinkpad (Bug #5037). Dear Sanjoy, Did not thought to preemption, so thanks! Will give it a try. Before that, I am doing rc6-git5 with a lot of debug flags turned on; suspecting irq routing - personal printk()s in pci and pcmcia indicated they were not called. Thanks again for your update; hoping progress for your reports! Cheers, JD. > personal printk()s in pci and pcmcia indicated they were not called.
I meant: not called when I insert the card. Which the first thing that differ
compared to 2.6.12.4. Finding why might help resolve the rest - who knows.
Trying to isolate where is going the irq and/or if it seen is my first goal!
Not being a knowledgable person about kernel is not a plus - but that's ok -
time to learn.
Cheers! JD.
Played with preemption - no go - Not tried official 2.6.13 yet. In the meantime my enterasys card got broken by my daughter...! Will use a linksys wpc54g card from now on. Tried with linux-2.6.13.4 and pcmciautils 010 : still I have to insert the card twice _but_ network looks stable. I guess this bug report now resumes only to the fact that the card has to be inserted twice, which is a minor issue for me... You might want to close this bug, though. Thanks, Regards, Jean-Damien. The bug hit me a few days ago, when I upgraded from 2.6.12 to 2.6.14 (debian kernels). I use pcmcia-cs, since pcmciautils is not yet packaged. See http://lists.debian.org/debian-powerpc/2005/10/msg00548.html for more information. Additionnally, I cannot remove/reinsert the card (Cisco 350 series), because almost everytime the computer freezes. (The computer freezes generally also on resuming from sleeping, is this due to Cisco driver?!) Eugen I am happy with pcmciautils010 and linux 2.6.13.4. Packaging a minimal pcmciautils (i.e. no *cis file, no special setup - just the udev facts) is not that hard (this is what I did). Cheers, JD. Bug seems to be closed (cf. comment #16 ) -- if this impression is wrong, please re-open. |