Bug 7582
| Summary: | Repeatable hang on boot with PCMCIA card present | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Steve Smith (tarka) |
| Component: | PCMCIA | Assignee: | linux-pcmcia |
| Status: | REJECTED UNREPRODUCIBLE | ||
| Severity: | high | CC: | daniel.ritz, protasnb |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.17+ | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
Photo of hung boot
dmesg output Output of lspcmcia -vvv |
||
Created attachment 9626 [details]
Photo of hung boot
please try using Dominik's tree: http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/brodo/pcmcia-fixes-new-2.6.git;a=summary or apply this one from -mm: http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc6/2.6.19-rc6-mm1/broken-out/git-pcmcia.patch I've tried the -mm patch with the same result unfortunately. Could you post the dmesg and the output of lspcmica -vvv when the card is inserted post-boot, please? Created attachment 9722 [details]
dmesg output
Created attachment 9723 [details]
Output of lspcmcia -vvv
Attached. Thanks guys. This appears to be an interaction with hostap/hostap_cs. Blacklisting them in favour of the orinoco driver works. Has this problem been resolved? Thanks. Steve, if you can confirm this problem with latest kernel please reopen. |
Most recent kernel where this bug did *NOT* occur: 2.6.16.23 Distribution: Ubuntu Edgy Hardware Environment: Dell Inspiron 8100 + Linksys WPC11 With recent kernel releases I have started seeing consistent hangs during boot when a PCMCIA card is present in the slot (the card in question is a Linksys WPC11). The symptoms are: If the card is present during boot an error of "Unknown interrupt or fault at EIP ..." appears. If the card is not present there is no error. The card can be plugged-in post-boot without problems. Using git-bisect I have narrowed down the error to one commit, namely "use bitfield instead of p_state and state". The commit# is e2d4096365e06b9a3799afbadc28b4519c0b3526 However I am still seeing this problem with the latest -RC releases, including 2.6.19-rc6.