While inserting any Prism2/2.5 PCMICIA card in a running system (kernel 2.6.27-r10) works perfectly with hostap_cs.ko, leaving the card inserted during a reboot will crash hard, leaving the machine locked up with all LEDs flashing. I've not yet written down all the goobledigook it leaves on the screen. (Not sure its the same every time.) Regards, Wim.
It would be nice to see some of the gobbledigook, please. A digital photo of the screen is a convenient way.
On Tue, Jun 02, 2009 at 05:53:12AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > > Andrew Morton <akpm@linux-foundation.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |akpm@linux-foundation.org > > > > > --- Comment #1 from Andrew Morton <akpm@linux-foundation.org> 2009-06-02 > 05:53:12 --- > It would be nice to see some of the gobbledigook, please. A digital photo of > the screen is a convenient way. Here it is. Wim.
> > --- Comment #1 from Andrew Morton <akpm@linux-foundation.org> 2009-06-02 > 05:53:12 --- > > It would be nice to see some of the gobbledigook, please. A digital photo > of > > the screen is a convenient way. > > Here it is. > Wim. Hmm, the attachment doesn't show up in your mail copy, nor do I see any sign of it on bugzilla.kernel.org. How am I supposed to deliver a jpeg? Wim.
Go to http://bugzilla.kernel.org/show_bug.cgi?id=13426 and click on "Add an attachment".
Created attachment 21717 [details] screenshot of hard crash Photo of crashed boot of kernel-2.6.27-r10 + hostap_cs + prism2.5 PCMCIA card.
argh, the important info scrolled off. Can you boot with a 50-row screen? IIRC that involves adding "vga=extended" or perhaps "vga=80x50" to the boot command line. Thanks.
Created attachment 21719 [details] 80x60 screenshot of hard crash (vga=ask) I choosed the longest one, 80x60.
OK, thanks. It is indeed a PCMCIA bug. Looks like we died in pcmcia_request_configuration().
Could you post the output of "lspcmcia -vvv" with the card inserted post-boot, please?
bugzilla-daemon@bugzilla.kernel.org zei ooit: >Date: Tue, 2 Jun 2009 01:21:36 GMT >From: bugzilla-daemon@bugzilla.kernel.org >Subject: [Bug 13426] New: booting with Prism2/2.5 PCMCIA card inserted crashes >hard > http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > Summary: booting with Prism2/2.5 PCMCIA card inserted crashes > hard > Product: Drivers > Version: 2.5 > Kernel Version: 2.6.27-r10 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: PCMCIA > AssignedTo: linux-pcmcia@lists.infradead.org > ReportedBy: wim@djo.tudelft.nl > CC: wim@djo.tudelft.nl > Regression: No > > > While inserting any Prism2/2.5 PCMICIA card in a running system (kernel > 2.6.27-r10) works perfectly with hostap_cs.ko, leaving the card inserted > during > a reboot will crash hard, leaving the machine locked up with all LEDs > flashing. > I've not yet written down all the goobledigook it leaves on the screen. > (Not sure its the same every time.) > > Regards, Wim. Thanks for the progress. Up until kernel 2.6.33.-rc3 this behaviour remains the same. The errors before lockup are none, process pcmcia, process modprobe, divide error, and presumably the important one: do_IRQ No irq handler for vector (irq -1). The amazing thing is that hostap _works_ at insertion after the login prompt. Moving the kernel and modules to another laptop (Dell Inspiron 4100) shows _always_ a lockup at insertion of the card. The error then is always: do_IRQ:0176 No irq handler for vector (irq -1) Since I found a kernel 2.6.30-r8 (gentoo) that worked fine on the Dell with that card, it must be that there is a configurational bug involved. The Dell is much faster in compiling kernels. Eliminating the different configure options one by one I came to the point where the Dell would always work when I have the option CONFIG_DEBUG_SHIRQ unset. The explanation of this option has no big fat warning, so a layman like me would turn it on because I have a problem to debug. This is one configurational kernel bug to begin with. The description holds only a faint hint that the driver should handle the problem. So, there's also clearly a bug in hostap! Now I've another problem. The option CONFIG_DEBUG_SHIRQ is not set in all the kernels on my Thinkpad. So there must be more of these dangerous configure options. :-( The 'good' kernel 2.6.30-r8 has not yet been tried on the thinkpad. (must be recompiled for the lower CPU of the thinkpad). Regards, Wim. ----- wim@djo.tudelft.nl -----
bugzilla-daemon@bugzilla.kernel.org zei ooit: >Date: Wed, 3 Jun 2009 03:42:47 GMT >Subject: [Bug 13426] booting with Prism2/2.5 PCMCIA card inserted crashes hard >In-Reply-To: <bug-13426-4844@http.bugzilla.kernel.org/> > > http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > > Andrew Morton <akpm@linux-foundation.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |daniel.ritz@gmx.ch > > > > > --- Comment #8 from Andrew Morton <akpm@linux-foundation.org> 2009-06-03 > 03:42:45 --- > > OK, thanks. It is indeed a PCMCIA bug. Looks like we died in > pcmcia_request_configuration(). > I'd say more specificly it's a hostap bug. Two bugs actually, because I don't see their relationship. The second bug, as recently reported, causes always a system crash when inserting a PCMCIA card that loads hostap_cs, only if CONFIG_DEBUG_SHIRQ is set. (It does not happen when inserting other cards.) The first bug, as reported earlier, causes a system crash when a hostap_cs loading card is present at boot time. Inserting the card after that point in the boot stage will also cause a hard crash. Apparently there are several places in the boot sequence where it is dangerous to have the card inserted. Inserting at the login prompt always seems to be safe. This bug now appears present as soon as CONFIG_ISA is set! Unfortunately I must have ISA selected on my Thinkpad because the sound chip is ISA based. (My Dell is 'ISA free'.) Regards, Wim Osterholt. ----- wim@djo.tudelft.nl -----
> http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > > John W. Linville <linville@tuxdriver.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |j@w1.fi, > | |linville@tuxdriver.com > > Up to kernel 2.6.33-rc8 the crashes are still there. It doesn't look like it's taken serious. Jouni, do you still have an external hostap package that is suitable for kernel 2.6 ? The in-kernel driver is dysfunctional (you can't even boot when the hardware is present). Regards, Wim. ----- wim@djo.tudelft.nl -----
So the card works fine if it is inserted post-boot? I fear this bug might be one of the cases where we are the PCMCIA subsystem turned out not to do proper locking. Could you try whether the extensive patchset to be found at git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git helps?
bugzilla-daemon@bugzilla.kernel.org zei ooit: >Date: Fri, 19 Feb 2010 18:07:34 GMT >From: bugzilla-daemon@bugzilla.kernel.org >Subject: [Bug 13426] booting with Prism2/2.5 PCMCIA card inserted crashes hard > http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > --- Comment #13 from Dominik Brodowski <linux@brodo.de> 2010-02-19 18:07:08 > --- > > So the card works fine if it is inserted post-boot? I fear this bug might be > one of the cases where we are the PCMCIA subsystem turned out not to do > proper > locking. Could you try whether the extensive patchset to be found at > git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git helps? > As I said, 'a hostap loading card'. It does not occur with other PCMCIA cards (3com network, Fujitsu modem, New Media SCSI, Future Domain SCSI) or cardbus cards (Xircom network, 3com and others). It does occur with any brand of prism2.5 card (Senao, Belkin, BenQ, chinese clones). It did not happen with an old Belkin prism2.0 card. However, hostap wasn't loaded automatically for that card because there was no entry for it in the compiled-in table. Once I added that, it behaved the same as the other prism cards. All these cards work fine when inserted at the login prompt. I'll try the patchset later.. Regards, Wim. ----- wim@djo.tudelft.nl -----
> --- Comment #13 from Dominik Brodowski <linux@brodo.de> 2010-02-19 18:07:08 > --- > > So the card works fine if it is inserted post-boot? I fear this bug might be > one of the cases where we are the PCMCIA subsystem turned out not to do > proper > locking. Could you try whether the extensive patchset to be found at > git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git helps? Unfamiliar with git, it didn't give me an 'extensive patchset' but I managed to get an entire source tree from there. After compiling it gave me a kernel calling itself 2.6.33-r4. Booting this kernel with a prism card inserted ran up to the login prompt without any problem. So you seem to have found the cuprit. Regards, Wim. ----- wim@djo.tudelft.nl -----
Glad to see that it helps. Will close the bug accordingly.
bugzilla-daemon@bugzilla.kernel.org zei ooit: >Subject: [Bug 13426] booting with Prism2/2.5 PCMCIA card inserted crashes hard >X-Bugzilla-Status: RESOLVED > http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > > Dominik Brodowski <linux@brodo.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |RESOLVED > Resolution| |CODE_FIX Sorry to spoil the fun, but there's nothing resolved. It has even worsened because the card can't even be used now! Anxiously waiting for the bugfixes to appear I found that the new release of 2.6.34-rc2 held the changes. Improved is that the machine didn't crash while the PCMCIA card was inserted. However, at a given moment it says 'starting wlan0' and 'starting dhcp' (where I hadn't even configured these things to happen) and from then on regularly call traces fill the screen from 'process swapper'. Killing dhcpcd didn't change anything. rmmod hostap_cs cannot be done because it is 'in use'. ifconfig wlan0 down hangs permanently. A power cycle is needed to get control back. 'Normal' use isn't possible either. After booting, inserting the card at the prompt immediately results in the same kind of call traces. Removing the card doesn't change a thing. A reboot/shutdown hangs at the point where the interfaces are brought down. Call traces are now from 'pccardd'. A power cycle is needed to get control back. Regards, Wim. ----- wim@djo.tudelft.nl -----
Uh, that's bad news. However, the locking patches on their own worked, right? (see comment #15). Could you test 2.6.34-rc1, please?
> --- Comment #19 from Dominik Brodowski <linux@brodo.de> 2010-03-25 16:56:50 > --- > > Uh, that's bad news. However, the locking patches on their own worked, right? > (see comment #15). I'm trying to check that again.. (can't find that kernel here..)-: >Could you test 2.6.34-rc1, please? Where could I get that? I don't find it at www.kernel.org anymore. (text mode browser) Regards, Wim Osterholt. ----- wim@djo.tudelft.nl -----
That's available at http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.34-rc1.tar.bz2 (full source) or http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.34-rc1.bz2 (patch). In the meantime, a "dmesg", "/proc/iomem", "/proc/ioports" and "lspcmcia -vvv" of -rc2 before inserting the card would already help a bit in trying to track the bug down.
(In reply to comment #21) > ... In the meantime, a "dmesg", "/proc/iomem", "/proc/ioports" and > "lspcmcia -vvv" of -rc2 before inserting the card would already help a bit in > trying to track the bug down. See attached file. Wim.
Created attachment 25727 [details] output files as requested in #21 as requested in #21 lcpci -vvv dmesg /proc/iomem /proc/ioports
Hm, nothing obvious to see here -- it'd be really helpful if you could try to bisect the issue -- or, at first, determine whether indeed the PCMCIA locking patches are at fault (which I doubt, actually), or whether -rc2-git3 (http://www.kernel.org/pub/linux/kernel//v2.6/snapshots/patch-2.6.34-rc2-git3.bz2) works?
> https://bugzilla.kernel.org/show_bug.cgi?id=13426 > > > Dominik Brodowski <linux@brodo.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|RESOLVED |REOPENED > Resolution|CODE_FIX | > > > --- Comment #21 from Dominik Brodowski <linux@brodo.de> 2010-03-26 08:24:10 > --- > That's available at > http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.34-rc1.tar.bz2 -rc1 behaves equally bad as -rc2 I'll try to find back the original test case. (deleted for space problems. That will take some time. The laptop is slow and I don't have regular internet access.) Regards, Wim Osterholt. ----- wim@djo.tudelft.nl -----
Created attachment 25740 [details] pcmcia patches (first pull for 2.6.34-rc1, complete patch) Attached is a patch with all relevant PCMCIA changes for -rc1. It applies on top of a plain 2.6.33 kernel. If this works fine, we are many steps further in determining the cause of the trouble.
> --- Comment #24 from Dominik Brodowski <linux@brodo.de> 2010-03-27 13:17:26 > --- > Hm, nothing obvious to see here -- it'd be really helpful if you could try to > bisect the issue -- or, at first, determine whether indeed the PCMCIA locking > patches are at fault (which I doubt, actually), or whether -rc2-git3 > > (http://www.kernel.org/pub/linux/kernel//v2.6/snapshots/patch-2.6.34-rc2-git3.bz2) > works? Kernel source 2.6.34-rc2. patch-2.6.34-rc2-git3 ran successfully. Booting this kernel displayed the same problems as earlier. Regards, Wim. Osterholt ----- wim@djo.tudelft.nl -----
> http://bugzilla.kernel.org/show_bug.cgi?id=13426 > > --- Comment #15 from Wim Osterholt <wim@djo.tudelft.nl> 2010-02-21 23:34:50 > --- > > --- Comment #13 from Dominik Brodowski <linux@brodo.de> 2010-02-19 > 18:07:08 --- > > > > So the card works fine if it is inserted post-boot? I fear this bug might > be > > one of the cases where we are the PCMCIA subsystem turned out not to do > proper > > locking. Could you try whether the extensive patchset to be found at > > git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git helps? > > Unfamiliar with git, it didn't give me an 'extensive patchset' but I managed > to get an entire source tree from there. > After compiling it gave me a kernel calling itself 2.6.33-r4. > Booting this kernel with a prism card inserted ran up to the login prompt > without any problem. So you seem to have found the cuprit. Can't remember what exactly I did before my hastily conclusions. Or something indeed has changed again. Anyway, this is what I did yesterday: git clone git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git A huge kernel tree appeared. I took my .config that I use with 2.6.3*-rc*. I did not apply a few private tweaks that I normally do. I ran make oldconfig and confirmed the defaults (that usually are drivers for new hardware that I don't have). Then make, make modules_install and install the kernel. Upon rebooting that new kernel, I was expecting normal behaviour. It showed up differently, even like I've not seen before. - Booting runs up to the prompt, without much signs of weirdness. (Oh whell, except for the fact that gentoo now tries to do dhcp which I never configured. That might be caused by recent updates.) Sometimes the cards led is off, sometimes it is flashing. (Too little attempts for a useful conclusion. I do have one card that is a bit buggy, which might or might not be of any influence. Here I used a good card.) Ifconfig wlan0 up gives an error and does not switch the cards led on (or off in case of -down.) Iwconfig wlan0 shows far too little lines. It tells 'mode master' (which I hate) and 'essid 'test' (which I dislike. There are too many 'test's to be found in the source.)-: Iwconfig gives an error when I try to change anything. Unknown is wether the card sends out beacons or not when the led is on. Rmmod hostap_cs fails because it is 'in use'. Removing the card triggers a call trace avalanche. Reboot hangs at the spot where the driver is to be unloaded. - Booting and inserting the card at the prompt does not lead to a working situation. After some time the call traces appear. Ifconfig says 'Error while getting interface flags.' Iwconfig just hangs uninterruptible. Removing the card triggers call traces. You might want to see this: Mar 30 10:22:25 tp600 login[4408]: ROOT LOGIN on 'tty1' Mar 30 10:22:34 tp600 kernel: pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 Mar 30 10:22:34 tp600 kernel: pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. Mar 30 10:22:34 tp600 kernel: pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 3) Mar 30 10:22:34 tp600 kernel: lib80211: common routines for IEEE802.11 drivers Mar 30 10:22:34 tp600 kernel: lib80211_crypt: registered algorithm 'NULL' Mar 30 10:22:34 tp600 kernel: hostap_cs: setting Vcc=33 (constant) Mar 30 10:22:34 tp600 kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01) Mar 30 10:22:34 tp600 kernel: IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 Mar 30 10:22:34 tp600 kernel: io->flags = 0x0046, io.base=0x0000, len=64 Mar 30 10:22:34 tp600 kernel: hostap_cs: Registered netdevice wifi0 Mar 30 10:22:34 tp600 kernel: hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f Mar 30 10:22:34 tp600 kernel: prism2_hw_init: initialized in 192 ms Mar 30 10:22:36 tp600 kernel: wifi0: hfa384x_cmd: entry still in list? (entry=c82f1340, type=0, res=0) Mar 30 10:22:36 tp600 kernel: wifi0: hfa384x_cmd: command was not completed (res=0, entry=c82f1340, type=0, cmd=0x0021, param0=0xfd0b, EVSTAT=8010 INTEN=0010) Mar 30 10:22:36 tp600 kernel: wifi0: interrupt delivery does not seem to work Mar 30 10:22:36 tp600 kernel: wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd0b, len=8) Mar 30 10:22:36 tp600 kernel: Could not get RID for component NIC Mar 30 10:22:36 tp600 kernel: hostap_cs: Initialization failed Mar 30 10:22:36 tp600 kernel: prism2_config() failed Mar 30 10:22:36 tp600 kernel: hostap_cs: probe of 0.0 failed with error 1 Mar 30 10:22:36 tp600 kernel: hostap_cs: setting Vcc=33 (constant) Mar 30 10:22:36 tp600 kernel: Checking CFTABLE_ENTRY 0x01 (default 0x01) Mar 30 10:22:36 tp600 kernel: IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 Mar 30 10:22:36 tp600 kernel: io->flags = 0x0046, io.base=0x0000, len=64 Mar 30 10:22:36 tp600 kernel: GetNextTuple(): No matching CIS configuration. Maybe you need the ignore_cis_vcc=1 parameter. Mar 30 10:22:38 tp600 kernel: wifi0: hfa384x_cmd: entry still in list? (entry=c82f1440, type=0, res=0) Mar 30 10:22:38 tp600 kernel: wifi0: hfa384x_cmd: command was not completed (res=0, entry=c82f1440, type=0, cmd=0x0002, param0=0x0000, EVSTAT=8010 INTEN=0010) Mar 30 10:22:38 tp600 kernel: wifi0: interrupt delivery does not seem to work Mar 30 10:22:38 tp600 kernel: hostap_cs: Shutdown failed Mar 30 10:22:38 tp600 kernel: BUG: scheduling while atomic: pccardd/1061/0x00010000 Mar 30 10:22:38 tp600 kernel: Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb snd_opl3_lib fb snd_hwdep cfbcopyarea snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore snd_timer cfbfillrect battery parport snd_page_alloc thermal processor Mar 30 10:22:38 tp600 kernel: Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb snd_opl3_lib fb snd_hwdep cfbcopyarea snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore snd_timer cfbfillrect battery parport snd_page_alloc thermal processor Mar 30 10:22:38 tp600 kernel: Mar 30 10:22:38 tp600 kernel: Pid: 1061, comm: pccardd Not tainted 2.6.34-rc2 #1 2645310/2645310 Mar 30 10:22:38 tp600 kernel: EIP: 0060:[<c0478f74>] EFLAGS: 00000282 CPU: 0 Mar 30 10:22:38 tp600 kernel: EIP is at yenta_set_socket+0x174/0x280 Mar 30 10:22:38 tp600 kernel: EAX: ca7fa898 EBX: 80001050 ECX: 00000000 EDX: 00000200 Mar 30 10:22:38 tp600 kernel: ESI: c9a00000 EDI: c9a00044 EBP: c9a03d98 ESP: c9a03d78 Mar 30 10:22:38 tp600 kernel: DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Mar 30 10:22:38 tp600 kernel: Process pccardd (pid: 1061, ti=c9a02000 task=c9964de0 task.ti=c9a02000) Mar 30 10:22:38 tp600 kernel: Stack: Mar 30 10:22:38 tp600 kernel: c9a03d8a c81c0000 c9a00040 05800296 05c00000 c9a7ee00 c9a00040 c8154d40 Mar 30 10:22:38 tp600 kernel: <0> c9a03dbc c0472845 c9a00148 00000000 00000000 00000001 c9a7ee00 c9a7ee00 Mar 30 10:22:38 tp600 kernel: <0> ffffffe4 c9a03dd0 c0472b48 c81c0000 c9a7ee00 ffffffe4 c9a03de0 cb07a409 Mar 30 10:22:38 tp600 kernel: Call Trace: Mar 30 10:22:38 tp600 kernel: [<c0472845>] ? pcmcia_release_configuration+0xd5/0x110 Mar 30 10:22:38 tp600 kernel: [<c0472b48>] ? pcmcia_disable_device+0x18/0xc0 Mar 30 10:22:38 tp600 kernel: [<cb07a409>] ? prism2_release+0x39/0x50 [hostap_cs] Mar 30 10:22:38 tp600 kernel: [<cb07d3a9>] ? hostap_cs_probe+0xb9/0x968 [hostap_cs] Mar 30 10:22:38 tp600 kernel: [<c0470fdc>] ? pcmcia_device_probe+0xfc/0x1d0 Mar 30 10:22:38 tp600 kernel: [<c0426500>] ? driver_detach+0x50/0x80 Mar 30 10:22:38 tp600 kernel: [<c04266d2>] ? driver_probe_device+0x62/0x160 Mar 30 10:22:38 tp600 kernel: [<c04714ed>] ? pcmcia_bus_match+0x6d/0x470 Mar 30 10:22:38 tp600 kernel: [<c0426891>] ? __device_attach+0x41/0x50 Mar 30 10:22:38 tp600 kernel: [<c0425cb3>] ? bus_for_each_drv+0x53/0x80 Mar 30 10:22:38 tp600 kernel: [<c042693b>] ? device_attach+0x6b/0x70 Mar 30 10:22:38 tp600 kernel: [<c0426850>] ? __device_attach+0x0/0x50 Mar 30 10:22:38 tp600 kernel: [<c042559d>] ? bus_rescan_devices_helper+0x3d/0x70 Mar 30 10:22:38 tp600 kernel: [<c0425f73>] ? bus_for_each_dev+0x53/0x80 Mar 30 10:22:38 tp600 kernel: [<c0425fb6>] ? bus_rescan_devices+0x16/0x20 Mar 30 10:22:38 tp600 kernel: [<c0425560>] ? bus_rescan_devices_helper+0x0/0x70 Mar 30 10:22:38 tp600 kernel: [<c0471fa7>] ? pcmcia_requery+0xb7/0x150 Mar 30 10:22:38 tp600 kernel: [<c0470b40>] ? pcmcia_requery_callback+0x0/0x30 Mar 30 10:22:38 tp600 kernel: [<c022852f>] ? finish_task_switch+0x2f/0x80 Mar 30 10:22:38 tp600 kernel: [<c05600d2>] ? schedule+0x352/0x460 Mar 30 10:22:38 tp600 kernel: [<c046fbf2>] ? pccardd+0x1d2/0x460 Mar 30 10:22:38 tp600 kernel: [<c046fa20>] ? pccardd+0x0/0x460 Mar 30 10:22:38 tp600 kernel: [<c024403c>] ? kthread+0x6c/0x80 Mar 30 10:22:38 tp600 kernel: [<c0243fd0>] ? kthread+0x0/0x80 Mar 30 10:22:38 tp600 kernel: [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Mar 30 10:22:38 tp600 kernel: Code: 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 <83> e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 Mar 30 10:22:38 tp600 kernel: Call Trace: Mar 30 10:22:38 tp600 kernel: [<c0472845>] pcmcia_release_configuration+0xd5/0x110 Mar 30 10:22:38 tp600 kernel: [<c0472b48>] pcmcia_disable_device+0x18/0xc0 Mar 30 10:22:38 tp600 kernel: [<cb07a409>] prism2_release+0x39/0x50 [hostap_cs] Mar 30 10:22:38 tp600 kernel: [<cb07d3a9>] hostap_cs_probe+0xb9/0x968 [hostap_cs] Mar 30 10:22:38 tp600 kernel: [<c0470fdc>] pcmcia_device_probe+0xfc/0x1d0 Mar 30 10:22:38 tp600 kernel: [<c0426500>] ? driver_detach+0x50/0x80 Mar 30 10:22:38 tp600 kernel: [<c04266d2>] driver_probe_device+0x62/0x160 Mar 30 10:22:38 tp600 kernel: [<c04714ed>] ? pcmcia_bus_match+0x6d/0x470 Mar 30 10:22:38 tp600 kernel: [<c0426891>] __device_attach+0x41/0x50 Mar 30 10:22:38 tp600 kernel: [<c0425cb3>] bus_for_each_drv+0x53/0x80 Mar 30 10:22:38 tp600 kernel: [<c042693b>] device_attach+0x6b/0x70 Mar 30 10:22:38 tp600 kernel: [<c0426850>] ? __device_attach+0x0/0x50 Mar 30 10:22:38 tp600 kernel: [<c042559d>] bus_rescan_devices_helper+0x3d/0x70 Mar 30 10:22:38 tp600 kernel: [<c0425f73>] bus_for_each_dev+0x53/0x80 Mar 30 10:22:38 tp600 kernel: [<c0425fb6>] bus_rescan_devices+0x16/0x20 Mar 30 10:22:38 tp600 kernel: [<c0425560>] ? bus_rescan_devices_helper+0x0/0x70 Mar 30 10:22:38 tp600 kernel: [<c0471fa7>] pcmcia_requery+0xb7/0x150 Mar 30 10:22:38 tp600 kernel: [<c0470b40>] ? pcmcia_requery_callback+0x0/0x30 Mar 30 10:22:38 tp600 kernel: [<c022852f>] ? finish_task_switch+0x2f/0x80 Mar 30 10:22:38 tp600 kernel: [<c05600d2>] ? schedule+0x352/0x460 Mar 30 10:22:38 tp600 kernel: [<c046fbf2>] pccardd+0x1d2/0x460 Mar 30 10:22:38 tp600 kernel: [<c046fa20>] ? pccardd+0x0/0x460 Mar 30 10:22:38 tp600 kernel: [<c024403c>] kthread+0x6c/0x80 Mar 30 10:22:38 tp600 kernel: [<c0243fd0>] ? kthread+0x0/0x80 Mar 30 10:22:38 tp600 kernel: [<c0202ef6>] kernel_thread_helper+0x6/0x10 (Note that after this the card works like a charm on a unpatched kernel.) Regards, Wim Osterholt. ----- wim@djo.tudelft.nl -----
Really interesting results. Thanks! Now that you have full git sources available, could you test the following, please? Create a branch which contains the PCMCIA locking patches, which seemed to solve the issues (see comment #14), and check it out: # git branch pcmcia-locking 7b4884ca8853a638df0eb5d251d80d67777b8b1a # git checkout pcmcia-locking now, compile this kernel, re-boot and test.
> https://bugzilla.kernel.org/show_bug.cgi?id=13426 > > --- Comment #29 from Dominik Brodowski <linux@brodo.de> 2010-03-30 12:55:18 > --- > Really interesting results. Thanks! > > Now that you have full git sources available, could you test the following, > please? Create a branch which contains the PCMCIA locking patches, which > seemed > to solve the issues (see comment #14), and check it out: As I decribed, I'm not really sure wether comment 14 would be valid, because when I repeated it all it didn't work out as expected. > # git branch pcmcia-locking 7b4884ca8853a638df0eb5d251d80d67777b8b1a > # git checkout pcmcia-locking I'll try that.. Regards, Wim. ----- wim@djo.tudelft.nl -----
> https://bugzilla.kernel.org/show_bug.cgi?id=13426 > --- Comment #29 from Dominik Brodowski <linux@brodo.de> 2010-03-30 12:55:18 > --- > Now that you have full git sources available, could you test the following, > please? Create a branch which contains the PCMCIA locking patches, which > seemed > to solve the issues (see comment #14), and check it out: > > # git branch pcmcia-locking 7b4884ca8853a638df0eb5d251d80d67777b8b1a > # git checkout pcmcia-locking > > now, compile this kernel, re-boot and test. Booting the kernel without card runs ok up to the prompt. Inserting the card causes one call trace (process modprobe). Lsmod says hostap_cs is used by 1. Iwconfig looks like it's working, that is I may succesfully say 'iwconfig wlan0 mode managed' for example. However when I start kismet a call trace avalanche starts. Kismet never appears. lsmod says hostap_cs is used by 3. Booting with the card inserted runs up to the moment hostap_cs gets loaded, then one call trace occurs (process swapper) which then keeps waiting indefinitely. When I press Ctrl-C it continues up to the prompt. Lsmod says hostap_cs is used by 2. A shutdown hangs because the module cannot be unloaded. Regards, Wim Osterholt. ----- wim@djo.tudelft.nl -----
This is getting _really_ confusing. The best thing now would be to handle the case "insert after boot" first, and address the "inserted during boot" bug next. We do know that 2.6.33-rc8 works fine for the "insert after boot" case (see comment #12), we do also know that the most recent kernel (2.6.34-rc3-git...) does not work. Could you attempt to "bisect" it to the relevant commit which breaks things for the "insert after boot" case? See "man git-bisect" and some websites for details on how to bisect a kernel issue using git. Thanks!
> https://bugzilla.kernel.org/show_bug.cgi?id=13426 > > --- Comment #32 from Dominik Brodowski <linux@brodo.de> 2010-04-01 19:40:25 > --- > This is getting _really_ confusing. The best thing now would be to > handle the case "insert after boot" first, and address the "inserted during > boot" bug next. We do know that 2.6.33-rc8 works fine for the "insert after > boot" case (see comment #12), we do also know that the most recent kernel > (2.6.34-rc3-git...) does not work. Could you attempt to "bisect" it to the > relevant commit which breaks things for the "insert after boot" case? See > "man > git-bisect" and some websites for details on how to bisect a kernel issue > using > git. Thanks! > After the struggle I stumbled on this: 'git bisect log' after 0 revisions left. git bisect start # good: [724e6d3fe8003c3f60bf404bf22e4e331327c596] Linux 2.6.33-rc8 git bisect good 724e6d3fe8003c3f60bf404bf22e4e331327c596 # bad: [7b4884ca8853a638df0eb5d251d80d67777b8b1a] pcmcia: validate late-added resources git bisect bad 7b4884ca8853a638df0eb5d251d80d67777b8b1a # good: [9ddabb6700f82a033a76bcf7a547204fa12aaa17] Merge branch 'for-linus/samsung' of git://git.fluff.org/bjdooks/linux git bisect good 9ddabb6700f82a033a76bcf7a547204fa12aaa17 # good: [7432a5b6c7e38f5d89e890c6fcc00990006ab997] pcmcia/at91_cf: don't redefine SZ_2K git bisect good 7432a5b6c7e38f5d89e890c6fcc00990006ab997 # bad: [94a819f80297e1f635a7cde4ed5317612e512ba7] pcmcia: assert locking to struct pcmcia_device git bisect bad 94a819f80297e1f635a7cde4ed5317612e512ba7 # good: [9e86749cff70fca505c7c1a9dc760d193f27a059] pcmcia: lock ops->set_socket git bisect good 9e86749cff70fca505c7c1a9dc760d193f27a059 # good: [3d3de32fad19e37695e6649136e4cb17f9d46329] pcmcia: add locking to struct pcmcia_socket->pcmcia_state() git bisect good 3d3de32fad19e37695e6649136e4cb17f9d46329 Groeten, Wim. ----- wim@djo.tudelft.nl -----
Created attachment 25885 [details] patch to fix io resource issues Many many thanks for this valuable bisect log. I think I now got a clearer picture of what goes wrong: 1) Inserting the card probably got broken in 94a819f80297e1f635a7cde4ed5317612e512ba7 and fixed by 4e06e240dcbb803433ee31bfe89a3e785a77cd3b. 2) Between 2.6.33 and 2.6.34-rc1, mainline got another problem relating to the io resource setting. This will be fixed really soon by attached patch. 3) The code you pulled in comment #28 contained both bug 2 and another one, which broke IRQ routing. This was fixed in the meantime. I'll tell you once the fix for 2) enters mainline. Would be great if you could test the next -rc by Linus then, and if insert-after-boot or boot-with-card-inserted still fails, please also post a dmesg of any call traces you see. Although I really hope we've now tracked down all issues...
> --- Comment #34 from Dominik Brodowski <linux@brodo.de> 2010-04-06 19:47:57 > --- > Created an attachment (id=25885) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25885) > patch to fix io resource issues > > Many many thanks for this valuable bisect log. I think I now got a clearer > picture of what goes wrong: > > 1) Inserting the card probably got broken in > 94a819f80297e1f635a7cde4ed5317612e512ba7 and fixed by > 4e06e240dcbb803433ee31bfe89a3e785a77cd3b. > > 2) Between 2.6.33 and 2.6.34-rc1, mainline got another problem relating to > the > io resource setting. This will be fixed really soon by attached patch. > > 3) The code you pulled in comment #28 contained both bug 2 and another one, > which broke IRQ routing. This was fixed in the meantime. > > I'll tell you once the fix for 2) enters mainline. Would be great if you > could > test the next -rc by Linus then, and if insert-after-boot or > boot-with-card-inserted still fails, please also post a dmesg of any call > traces you see. Although I really hope we've now tracked down all issues... Plain 2.6.34-rc3 (without any patch) results in call traces when booting with the card inserted. New is that it continues booting up to the prompt. It even looks like the card is working. The avalanche of call traces make it hardly useable, but for example kismet with Ctrl-L (screen redraw) show APs appearing in the list. Regards, Wim. ----- wim@djo.tudelft.nl -----
> https://bugzilla.kernel.org/show_bug.cgi?id=13426 > --- Comment #34 from Dominik Brodowski <linux@brodo.de> 2010-04-06 19:47:57 > --- > Created an attachment (id=25885) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25885) > patch to fix io resource issues Hmmm. Plain 2.6.34-rc3 with this patch succesfully applied behaved exactly the same as without patch. It doesn't hang, but call traces as soon as the card is accessed. (process swapper mostly). Regards, Wim. ----- wim@djo.tudelft.nl -----
> --- Comment #34 from Dominik Brodowski <linux@brodo.de> 2010-04-06 19:47:57 > --- > Created an attachment (id=25885) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25885) > patch to fix io resource issues >.... > I'll tell you once the fix for 2) enters mainline. Would be great if you > could > test the next -rc by Linus then, and if insert-after-boot or > boot-with-card-inserted still fails, please also post a dmesg of any call > traces you see. Although I really hope we've now tracked down all issues... Latest call traces log in /var/log/messages. kernel 2.6.34-rc3 with patch: Apr 8 06:55:15 tp600 init: Switching to runlevel: 6 Apr 8 06:55:42 tp600 sshd[4794]: Received signal 15; terminating. Apr 8 06:55:52 tp600 kernel: BUG: scheduling while atomic: dhcpcd/3067/0x00000200 Apr 8 06:55:52 tp600 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss sd_mod neofb snd_cs4236 hostap_cs fb snd_wss_lib hostap snd_opl3_lib cfbcopyarea snd_hwdep uhci_hcd vgastate snd_mpu401_uart lib80211 snd_rawmidi cfbimgblt snd_pcm usbcore battery cfbfillrect parport snd_timer snd_page_alloc thermal processor Apr 8 06:55:52 tp600 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss sd_mod neofb snd_cs4236 hostap_cs fb snd_wss_lib hostap snd_opl3_lib cfbcopyarea snd_hwdep uhci_hcd vgastate snd_mpu401_uart lib80211 snd_rawmidi cfbimgblt snd_pcm usbcore battery cfbfillrect parport snd_timer snd_page_alloc thermal processor Apr 8 06:55:52 tp600 kernel: Apr 8 06:55:52 tp600 kernel: Pid: 3067, comm: dhcpcd Not tainted 2.6.34-rc3 #2 2645310/2645310 Apr 8 06:55:52 tp600 kernel: EIP: 0060:[<c0479151>] EFLAGS: 00000286 CPU: 0 Apr 8 06:55:52 tp600 kernel: EIP is at yenta_set_socket+0x191/0x280 Apr 8 06:55:52 tp600 kernel: EAX: ca7fa000 EBX: 80001050 ECX: ffffffd8 EDX: 00000200 Apr 8 06:55:52 tp600 kernel: ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 Apr 8 06:55:52 tp600 kernel: DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 Apr 8 06:55:52 tp600 kernel: Process dhcpcd (pid: 3067, ti=c8cc4000 task=c80269a0 task.ti=c8cc4000) Apr 8 06:55:52 tp600 kernel: Stack: Apr 8 06:55:52 tp600 kernel: c9a03dda c8d8e290 c9a00040 05808692 05c00000 c8d8e200 c9a00040 c8f13200 Apr 8 06:55:52 tp600 kernel: <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c8d8e200 c8d8e200 Apr 8 06:55:52 tp600 kernel: <0> c06f3200 c9a03e20 c04731c8 c820c000 c8d8e200 c06f3200 c9a03e30 cab39409 Apr 8 06:55:52 tp600 kernel: Call Trace: Apr 8 06:55:52 tp600 kernel: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 Apr 8 06:55:52 tp600 kernel: [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 Apr 8 06:55:52 tp600 kernel: [<cab39409>] ? prism2_release+0x39/0x50 [hostap_cs] Apr 8 06:55:52 tp600 kernel: [<cab39430>] ? prism2_detach+0x10/0x220 [hostap_cs] Apr 8 06:55:52 tp600 kernel: [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 Apr 8 06:55:52 tp600 kernel: [<c04264b1>] ? __device_release_driver+0x51/0xa0 Apr 8 06:55:52 tp600 kernel: [<c04265a0>] ? device_release_driver+0x20/0x40 Apr 8 06:55:52 tp600 kernel: [<c0425ab1>] ? bus_remove_device+0x81/0xb0 Apr 8 06:55:52 tp600 kernel: [<c0423f6a>] ? device_del+0xfa/0x180 Apr 8 06:55:52 tp600 kernel: [<c0423ffb>] ? device_unregister+0xb/0x20 Apr 8 06:55:52 tp600 kernel: [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 Apr 8 06:55:52 tp600 kernel: [<c0471f45>] ? ds_event+0x115/0x170 Apr 8 06:55:52 tp600 kernel: [<c046f11a>] ? send_event+0xaa/0xe0 Apr 8 06:55:52 tp600 kernel: [<c046f809>] ? socket_shutdown+0x19/0x100 Apr 8 06:55:52 tp600 kernel: [<c055ff9b>] ? printk+0x18/0x1d Apr 8 06:55:52 tp600 kernel: [<c046fa37>] ? socket_remove+0x47/0x60 Apr 8 06:55:52 tp600 kernel: [<c046fccf>] ? pccardd+0x27f/0x460 Apr 8 06:55:52 tp600 kernel: [<c046fa50>] ? pccardd+0x0/0x460 Apr 8 06:55:52 tp600 kernel: [<c024406c>] ? kthread+0x6c/0x80 Apr 8 06:55:52 tp600 kernel: [<c0244000>] ? kthread+0x0/0x80 Apr 8 06:55:52 tp600 kernel: [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Apr 8 06:55:52 tp600 kernel: Code: 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 83 e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 74 03 83 c9 80 8b 46 0c <05> 02 08 00 00 8a 00 38 c1 74 14 8b 46 0c 05 02 08 00 00 88 08 Apr 8 06:55:52 tp600 kernel: Call Trace: Apr 8 06:55:52 tp600 kernel: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 Apr 8 06:55:52 tp600 kernel: [<c04731c8>] pcmcia_disable_device+0x18/0x140 Apr 8 06:55:52 tp600 kernel: [<cab39409>] prism2_release+0x39/0x50 [hostap_cs] Apr 8 06:55:52 tp600 kernel: [<cab39430>] prism2_detach+0x10/0x220 [hostap_cs] Apr 8 06:55:52 tp600 kernel: [<c04711a7>] pcmcia_device_remove+0x47/0x110 Apr 8 06:55:52 tp600 kernel: [<c04264b1>] __device_release_driver+0x51/0xa0 Apr 8 06:55:52 tp600 kernel: [<c04265a0>] device_release_driver+0x20/0x40 Apr 8 06:55:52 tp600 kernel: [<c0425ab1>] bus_remove_device+0x81/0xb0 Apr 8 06:55:52 tp600 kernel: [<c0423f6a>] device_del+0xfa/0x180 Apr 8 06:55:52 tp600 kernel: [<c0423ffb>] device_unregister+0xb/0x20 Apr 8 06:55:52 tp600 kernel: [<c04707d0>] pcmcia_card_remove+0x90/0xb0 Apr 8 06:55:52 tp600 kernel: [<c0471f45>] ds_event+0x115/0x170 Apr 8 06:55:52 tp600 kernel: [<c046f11a>] send_event+0xaa/0xe0 Apr 8 06:55:52 tp600 kernel: [<c046f809>] socket_shutdown+0x19/0x100 Apr 8 06:55:52 tp600 kernel: [<c055ff9b>] ? printk+0x18/0x1d Apr 8 06:55:52 tp600 kernel: [<c046fa37>] socket_remove+0x47/0x60 Apr 8 06:55:52 tp600 kernel: [<c046fccf>] pccardd+0x27f/0x460 Apr 8 06:55:52 tp600 kernel: [<c046fa50>] ? pccardd+0x0/0x460 Apr 8 06:55:52 tp600 kernel: [<c024406c>] kthread+0x6c/0x80 Apr 8 06:55:52 tp600 kernel: [<c0244000>] ? kthread+0x0/0x80 Apr 8 06:55:52 tp600 kernel: [<c0202ef6>] kernel_thread_helper+0x6/0x10 Apr 8 06:56:30 tp600 syslog-ng[3934]: Termination requested via signal, terminating; Apr 8 06:56:30 tp600 syslog-ng[3934]: syslog-ng shutting down; version='3.0.4' Regards, Wim. ----- wim@djo.tudelft.nl -----
> --- Comment #34 from Dominik Brodowski <linux@brodo.de> 2010-04-06 19:47:57 > --- > Created an attachment (id=25885) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25885) > patch to fix io resource issues >... > I'll tell you once the fix for 2) enters mainline. Would be great if you > could > test the next -rc by Linus then, and if insert-after-boot or > boot-with-card-inserted still fails, please also post a dmesg of any call > traces you see. Although I really hope we've now tracked down all issues... The dmesg outputs are included here. (I cannot easily manage the webinterface remotely). What you can recognise her is: Card inserted. Call traces after ifconfig wlan0 up. Call trace after card ejected (without ifconfig wlan0 down). Call trace after insertion of network card (xircom_cb). lsmod shows hostap_cs stays in use by 3 xircom_cb modules gets loaded, but stays disfunctional (until a reboot). Regards, Wim. ----- wim@djo.tudelft.nl ----- pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' hostap_cs: setting Vcc=33 (constant) Checking CFTABLE_ENTRY 0x01 (default 0x01) IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 io->flags = 0x0046, io.base=0x0000, len=64 hostap_cs: Registered netdevice wifi0 wifi0: Interrupt, but dev not configured hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f prism2_hw_init: initialized in 196 ms wifi0: NIC: id=0x800c v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.7.4 BUG: scheduling while atomic: runscript.sh/5885/0x10010000 Modules linked in: hostap_cs(+) hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs(+) hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 5885, comm: runscript.sh Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0073:[<08091116>] EFLAGS: 00000202 CPU: 0 EIP is at 0x8091116 EAX: 08102298 EBX: 081104e0 ECX: 080de89b EDX: 00000088 ESI: ca797762 EDI: 00000050 EBP: bfdb67c8 ESP: bfdb67b0 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b Process runscript.sh (pid: 5885, ti=c8f56000 task=c80c8940 task.ti=c8f56000) Call Trace: wifi0: registered netdevice wlan0 prism2: wlan0: operating mode changed 3 -> 6 Enabling monitor mode BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<ca8027f8>] EFLAGS: 00000246 CPU: 0 EIP is at acpi_idle_enter_bm+0x215/0x23e [processor] EAX: c06bff7c EBX: 0000287a ECX: 00000000 EDX: 000001ac ESI: 00000000 EDI: c9a19cbc EBP: c06bffa0 ESP: c06bff7c DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: 000f4240 00000000 c9a19800 00000b4f 00000000 00000000 c9a1981c c9a19934 <0> c06c0000 c06bffb0 c0494b35 c0740c40 00099d00 c06bffb8 c0201af4 c06bffc0 <0> c05588ed c06bffdc c070a7bf 000000ba c070a334 00100000 c0740c40 00000000 Call Trace: [<c0494b35>] ? cpuidle_idle_call+0x75/0xf0 [<c0201af4>] ? cpu_idle+0x34/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 36 00 f7 65 e8 8d 14 11 e8 46 d8 bb f5 89 c3 b8 17 01 00 00 69 ca 17 01 00 00 89 d6 f7 e3 8d 14 11 e8 ed 74 a4 f5 fb 89 e0 31 c9 <25> 00 e0 ff ff 89 fa 83 48 0c 04 ff 47 18 8b 45 e4 e8 c6 fa ff Call Trace: [<c0494b35>] cpuidle_idle_call+0x75/0xf0 [<c0201af4>] cpu_idle+0x34/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 wifi0: card already removed or not configured during shutdown BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0479134>] EFLAGS: 00000282 CPU: 0 EIP is at yenta_set_socket+0x174/0x280 EAX: ca7fa898 EBX: 80001050 ECX: 00000000 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c995c940 task.ti=c9a02000) Stack: c9a03dda c80df090 c9a00040 05808692 05c00000 c80df000 c9a00040 c809d600 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c80df000 c80df000 <0> c06f3200 c9a03e20 c04731c8 c81e3000 c80df000 c06f3200 c9a03e30 cb014409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cb014409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 <83> e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cb014409>] prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10 BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0479134>] EFLAGS: 00000282 CPU: 0 EIP is at yenta_set_socket+0x174/0x280 EAX: ca7fa898 EBX: 80001050 ECX: 00000000 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c995c940 task.ti=c9a02000) Stack: c9a03dda c80df090 c9a00040 05808692 05c00000 c80df000 c9a00040 c809d600 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c80df000 c80df000 <0> c06f3200 c9a03e20 c04731c8 c81e3000 c80df000 c06f3200 c9a03e30 cb014409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cb014409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 <83> e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cb014409>] prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10 BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0479134>] EFLAGS: 00000282 CPU: 0 EIP is at yenta_set_socket+0x174/0x280 EAX: ca7fa898 EBX: 80001050 ECX: 00000000 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c995c940 task.ti=c9a02000) Stack: c9a03dda c80df090 c9a00040 05808692 05c00000 c80df000 c9a00040 c809d600 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c80df000 c80df000 <0> c06f3200 c9a03e20 c04731c8 c81e3000 c80df000 c06f3200 c9a03e30 cb014409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cb014409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 <83> e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cb014409>] prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10 BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0479134>] EFLAGS: 00000282 CPU: 0 EIP is at yenta_set_socket+0x174/0x280 EAX: ca7fa898 EBX: 80001050 ECX: 00000000 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c995c940 task.ti=c9a02000) Stack: c9a03dda c80df090 c9a00040 05808692 05c00000 c80df000 c9a00040 c809d600 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c80df000 c80df000 <0> c06f3200 c9a03e20 c04731c8 c81e3000 c80df000 c06f3200 c9a03e30 cb014409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cb014409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 <83> e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cb014409>] prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10 BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb fb snd_wss_lib snd_opl3_lib cfbcopyarea snd_hwdep vgastate snd_mpu401_uart uhci_hcd snd_rawmidi cfbimgblt snd_pcm cfbfillrect xircom_cb usbcore battery snd_timer parport snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0479134>] EFLAGS: 00000282 CPU: 0 EIP is at yenta_set_socket+0x174/0x280 EAX: ca7fa898 EBX: 80001050 ECX: 00000000 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c995c940 task.ti=c9a02000) Stack: c9a03dda c80df090 c9a00040 05808692 05c00000 c80df000 c9a00040 c809d600 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c80df000 c80df000 <0> c06f3200 c9a03e20 c04731c8 c81e3000 c80df000 c06f3200 c9a03e30 cb014409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cb014409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 <83> e0 1b 89 c1 83 c9 40 f6 c2 10 74 05 89 c1 83 c9 60 80 e6 02 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cb014409>] prism2_release+0x39/0x50 [hostap_cs] [<cb014430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10
Created attachment 25918 [details] patch to fix io probe issue Thanks! Such calltraces -- and dmesg output -- is probably the most valuable debugging tool (next to git bisect). For comparison, I'd now be interested in the lines like pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' hostap_cs: setting Vcc=33 (constant) Checking CFTABLE_ENTRY 0x01 (default 0x01) IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 io->flags = 0x0046, io.base=0x0000, len=64 hostap_cs: Registered netdevice wifi0 wifi0: Interrupt, but dev not configured hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f prism2_hw_init: initialized in 196 ms wifi0: NIC: id=0x800c v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.7.4 from a _working_ kernel (2.6.33, card insert after boot). Also, there's yet another bugfix patch I'll attach here; possibly it helps...
> --- Comment #39 from Dominik Brodowski <linux@brodo.de> 2010-04-08 18:30:27 > --- > Created an attachment (id=25918) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25918) > patch to fix io probe issue > > Thanks! Such calltraces -- and dmesg output -- is probably the most valuable > debugging tool (next to git bisect). For comparison, I'd now be interested in > the lines like > > pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 > pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. > pcmcia 0.0: pcmcia: registering new device pcmcia0.0 > lib80211: common routines for IEEE802.11 drivers > lib80211_crypt: registered algorithm 'NULL' > hostap_cs: setting Vcc=33 (constant) > Checking CFTABLE_ENTRY 0x01 (default 0x01) > IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 > io->flags = 0x0046, io.base=0x0000, len=64 > hostap_cs: Registered netdevice wifi0 > wifi0: Interrupt, but dev not configured > hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f > prism2_hw_init: initialized in 196 ms > wifi0: NIC: id=0x800c v1.0.0 > wifi0: PRI: id=0x15 v1.1.1 > wifi0: STA: id=0x1f v1.7.4 > > from a _working_ kernel (2.6.33, card insert after boot). Also, there's yet > another bugfix patch I'll attach here; possibly it helps... Not much different. Inserting and ejecting a card. dmesg in kernel 2.6.33-rc8 pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' hostap_cs: setting Vcc=33 (constant) Checking CFTABLE_ENTRY 0x01 (default 0x01) IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 io->flags = 0x0046, io.base=0x0000, len=64 hostap_cs: Registered netdevice wifi0 hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f prism2_hw_init: initialized in 196 ms wifi0: NIC: id=0x800c v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.7.4 wifi0: registered netdevice wlan0 pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 wifi0: card already removed or not configured during shutdown wifi0: Interrupt, but dev not OK Regards, Wim. ----- wim@djo.tudelft.nl -----
> --- Comment #39 from Dominik Brodowski <linux@brodo.de> 2010-04-08 18:30:27 > --- > Created an attachment (id=25918) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25918) > patch to fix io probe issue >... > from a _working_ kernel (2.6.33, card insert after boot). Also, there's yet > another bugfix patch I'll attach here; possibly it helps... You don't state what to patch. So I assumed the latest (2.6.34-rc3) with the previous patch. This patch applied fine. The resulting kernel generates call traces after ifconfig wlan0 up: pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' hostap_cs: setting Vcc=33 (constant) Checking CFTABLE_ENTRY 0x01 (default 0x01) IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 io->flags = 0x0046, io.base=0x0000, len=64 hostap_cs: Registered netdevice wifi0 wifi0: Interrupt, but dev not configured hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f prism2_hw_init: initialized in 192 ms wifi0: NIC: id=0x800c v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.7.4 wifi0: registered netdevice wlan0 prism2: wlan0: operating mode changed 3 -> 6 Enabling monitor mode BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639ba4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 wifi0: card already removed or not configured during shutdown BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c047913f>] EFLAGS: 00000246 CPU: 0 EIP is at yenta_set_socket+0x17f/0x280 EAX: 00000018 EBX: 80001050 ECX: 00000058 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c9965720 task.ti=c9a02000) Stack: c9a03dda c8e9ce90 c9a00040 05808692 05c00000 c8e9ce00 c9a00040 c8d93ac0 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c8e9ce00 c8e9ce00 <0> c06f3200 c9a03e20 c04731c8 c80c9000 c8e9ce00 c06f3200 c9a03e30 cafb8409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cafb8409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cafb8430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 83 e0 1b 89 c1 83 c9 40 f6 c2 10 <74> 05 89 c1 83 c9 60 80 e6 02 74 03 83 c9 80 8b 46 0c 05 02 08 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cafb8409>] prism2_release+0x39/0x50 [hostap_cs] [<cafb8430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10 BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c047913f>] EFLAGS: 00000246 CPU: 0 EIP is at yenta_set_socket+0x17f/0x280 EAX: 00000018 EBX: 80001050 ECX: 00000058 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c9965720 task.ti=c9a02000) Stack: c9a03dda c8e9ce90 c9a00040 05808692 05c00000 c8e9ce00 c9a00040 c8d93ac0 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c8e9ce00 c8e9ce00 <0> c06f3200 c9a03e20 c04731c8 c80c9000 c8e9ce00 c06f3200 c9a03e30 cafb8409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cafb8409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cafb8430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 83 e0 1b 89 c1 83 c9 40 f6 c2 10 <74> 05 89 c1 83 c9 60 80 e6 02 74 03 83 c9 80 8b 46 0c 05 02 08 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cafb8409>] prism2_release+0x39/0x50 [hostap_cs] [<cafb8430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10 BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 neofb snd_wss_lib fb snd_opl3_lib cfbcopyarea snd_hwdep snd_mpu401_uart uhci_hcd vgastate snd_rawmidi cfbimgblt snd_pcm usbcore parport xircom_cb cfbfillrect battery snd_timer snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #2 2645310/2645310 EIP: 0060:[<c047913f>] EFLAGS: 00000246 CPU: 0 EIP is at yenta_set_socket+0x17f/0x280 EAX: 00000018 EBX: 80001050 ECX: 00000058 EDX: 00000200 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c9965720 task.ti=c9a02000) Stack: c9a03dda c8e9ce90 c9a00040 05808692 05c00000 c8e9ce00 c9a00040 c8d93ac0 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c8e9ce00 c8e9ce00 <0> c06f3200 c9a03e20 c04731c8 c80c9000 c8e9ce00 c06f3200 c9a03e30 cafb8409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cafb8409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cafb8430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 8b 46 0c 05 02 08 00 00 8a 00 8b 17 83 e0 1b 89 c1 83 c9 40 f6 c2 10 <74> 05 89 c1 83 c9 60 80 e6 02 74 03 83 c9 80 8b 46 0c 05 02 08 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cafb8409>] prism2_release+0x39/0x50 [hostap_cs] [<cafb8430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10
Created attachment 25924 [details] wireless: hostap, fix oops due to early probing interrupt It seems the device is set up the same by PCMCIA both times, then... Only for the non-working case, the device mode is re-configured: prism2: wlan0: operating mode changed 3 -> 6 Enabling monitor mode immediately before things fall apart. Now, to exclude the possibility that this is a hostap bug, could you use the doubly-patched 2.6.34-rc3 kernel and revert this patch? It contains the only real code change hostap got between 2.6.33-rc8 and now.
> --- Comment #42 from Dominik Brodowski <linux@brodo.de> 2010-04-09 04:45:48 > --- > Created an attachment (id=25924) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25924) > wireless: hostap, fix oops due to early probing interrupt > > It seems the device is set up the same by PCMCIA both times, then... Only for > the non-working case, the device mode is re-configured: > > prism2: wlan0: operating mode changed 3 -> 6 > Enabling monitor mode > > immediately before things fall apart. > > Now, to exclude the possibility that this is a hostap bug, could you use the > doubly-patched 2.6.34-rc3 kernel and revert this patch? It contains the only > real code change hostap got between 2.6.33-rc8 and now. Good that you notice this. This is intended behaviour (in my 'normal' kernel). Time to mention the security bug in hostap. It's really bad that someone choose this to be the default behaviour. A long time before you get to the prompt and may configure things otherwise, the card is already advertising itself to the world. Not even as a client, but as an open AP. So I changed it to be in monitor mode as a default. The default ESSID is 'test' which doesn't really help you in finding where that is actually done. To help myself I changed that into '_hw.c', referring to hostap_hw.c . (line 67 and 71 in that file.) I'd suggest you change that in the sources. There's a peculiarity to mention, a behaviour that I don't understand and wouldn't expect. The default ESSID is 'test' and the card is in master mode. That is what iwconfig tells me. Now, when I change it to monitor mode, then iwconfig tells me that the ESSID is ' '. I don't get where that single space comes from, but it should remain the same. What do I see wrong? Regards, Wim Osterholt. ----- wim@djo.tudelft.nl -----
> --- Comment #42 from Dominik Brodowski <linux@brodo.de> 2010-04-09 04:45:48 > --- > Created an attachment (id=25924) > --> (https://bugzilla.kernel.org/attachment.cgi?id=25924) > wireless: hostap, fix oops due to early probing interrupt > > It seems the device is set up the same by PCMCIA both times, then... Only for > the non-working case, the device mode is re-configured: > > prism2: wlan0: operating mode changed 3 -> 6 > Enabling monitor mode > > immediately before things fall apart. > > Now, to exclude the possibility that this is a hostap bug, could you use the > doubly-patched 2.6.34-rc3 kernel and revert this patch? It contains the only > real code change hostap got between 2.6.33-rc8 and now. kernel 2.6.34-rc3 with 1 patch (second patch reverted) ---card inserted here: pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' hostap_cs: setting Vcc=33 (constant) Checking CFTABLE_ENTRY 0x01 (default 0x01) IO window settings: cfg->io.nwin=1 dflt->io.nwin=1 io->flags = 0x0046, io.base=0x0000, len=64 hostap_cs: Registered netdevice wifi0 wifi0: Interrupt, but dev not configured hostap_cs: index 0x01: , irq 3, io 0x0100-0x013f prism2_hw_init: initialized in 192 ms wifi0: NIC: id=0x800c v1.0.0 wifi0: PRI: id=0x15 v1.1.1 wifi0: STA: id=0x1f v1.7.4 wifi0: registered netdevice wlan0 ---nothing happens until 'ifconfig wlan0 up': BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #4 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639be4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #4 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639be4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #4 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639be4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10020000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #4 2645310/2645310 EIP: 0060:[<c047add7>] EFLAGS: 00000246 CPU: 0 EIP is at serio_interrupt+0x17/0x40 EAX: 00000001 EBX: c06f4360 ECX: c06cb8a0 EDX: c9a09830 ESI: 00000246 EDI: 00000000 EBP: c06bfe54 ESP: c06bfe4c DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: 00000000 00000015 c06bfea0 c047be60 c99e1a20 c99aba00 c06bfe94 c042ee7b <0> c06faa80 c06bfe7c a48e97db 00000001 c07dc2a0 c9984a00 00000296 9c6cfce0 <0> 0000000e 0000009c c06cf8d0 00000001 c99f5580 c06bfed0 c026ea38 0000000e Call Trace: [<c047be60>] ? i8042_interrupt+0x1c0/0x300 [<c042ee7b>] ? ide_intr+0x7b/0x1d0 [<c026ea38>] ? handle_IRQ_event+0x58/0x130 [<c02702a1>] ? handle_level_irq+0x51/0xb0 [<c0204654>] ? handle_irq+0x34/0x60 [<c0204199>] ? do_IRQ+0x39/0xb0 [<c02518a3>] ? tick_dev_program_event+0x33/0x160 [<c0202ee9>] ? common_interrupt+0x29/0x30 [<c0228570>] ? finish_task_switch+0x40/0x80 [<c0560432>] ? schedule+0x352/0x460 [<c0248431>] ? hrtimer_start_range_ns+0x21/0x30 [<c0252228>] ? tick_nohz_restart_sched_tick+0x198/0x1c0 [<c0201b0b>] ? cpu_idle+0x4b/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 90 90 90 90 55 31 c9 89 e5 31 d2 e8 f4 fd ff ff 5d c3 66 90 55 89 e5 56 53 9c 5e fa 8b 58 6c 85 db 74 0c 0f b6 d2 ff 53 14 56 9d <5b> 5e 5d c3 85 c9 8d 76 00 75 09 f6 80 a4 00 00 00 02 75 04 31 Call Trace: [<c047be60>] i8042_interrupt+0x1c0/0x300 [<c042ee7b>] ? ide_intr+0x7b/0x1d0 [<c026ea38>] handle_IRQ_event+0x58/0x130 [<c02702a1>] handle_level_irq+0x51/0xb0 [<c0204654>] handle_irq+0x34/0x60 [<c0204199>] do_IRQ+0x39/0xb0 [<c02518a3>] ? tick_dev_program_event+0x33/0x160 [<c0202ee9>] common_interrupt+0x29/0x30 [<c0228570>] ? finish_task_switch+0x40/0x80 [<c0560432>] schedule+0x352/0x460 [<c0248431>] ? hrtimer_start_range_ns+0x21/0x30 [<c0252228>] ? tick_nohz_restart_sched_tick+0x198/0x1c0 [<c0201b0b>] cpu_idle+0x4b/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 BUG: scheduling while atomic: swapper/0/0x10010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Pid: 0, comm: swapper Not tainted 2.6.34-rc3 #4 2645310/2645310 EIP: 0060:[<c0252236>] EFLAGS: 00000282 CPU: 0 EIP is at tick_nohz_restart_sched_tick+0x1a6/0x1c0 EAX: 00000000 EBX: 00000000 ECX: 00000020 EDX: c06c8a40 ESI: 00000001 EDI: c06c0000 EBP: c06bffb0 ESP: c06bffa8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c06be000 task=c06c4f00 task.ti=c06be000) Stack: c0740c40 00099d00 c06bffb8 c0201b06 c06bffc0 c05588ed c06bffdc c070a7bf <0> 000000ba c070a334 00100000 c0740c40 00000000 c06bfff8 c070a07a 007e51d8 <0> 00000000 c0639be4 00000000 00099d00 00986003 00000000 Call Trace: [<c0201b06>] ? cpu_idle+0x46/0x60 [<c05588ed>] ? rest_init+0x4d/0x60 [<c070a7bf>] ? start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] ? i386_start_kernel+0x7a/0xb6 Code: 1d cc e7 6c c0 8b 0d d8 e7 6c c0 c7 44 24 04 02 00 00 00 29 d3 89 1c 24 e8 e8 61 ff ff 8b 35 e4 e7 6c c0 85 f6 74 8c fb 83 c4 10 <5b> 5e 5d c3 8d b6 00 00 00 00 89 d0 e8 79 00 fd ff e9 13 ff ff Call Trace: [<c0201b06>] cpu_idle+0x46/0x60 [<c05588ed>] rest_init+0x4d/0x60 [<c070a7bf>] start_kernel+0x26a/0x2c7 [<c070a334>] ? unknown_bootoption+0x0/0x1d0 [<c070a07a>] i386_start_kernel+0x7a/0xb6 ---the above keeps repeating until 'iwconfig wlan0 down': wifi0: Deauthenticate all stations ---nothing more happens until ejecting the card manually: mv used greatest stack depth: 5300 bytes left sh used greatest stack depth: 5272 bytes left pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 wifi0: card already removed or not configured during shutdown BUG: scheduling while atomic: pccardd/1061/0x00010000 Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Modules linked in: hostap_cs hostap lib80211 snd_mixer_oss sd_mod snd_cs4236 snd_wss_lib neofb fb snd_opl3_lib snd_hwdep cfbcopyarea snd_mpu401_uart vgastate snd_rawmidi uhci_hcd cfbimgblt snd_pcm cfbfillrect snd_timer usbcore battery parport snd_page_alloc thermal processor Pid: 1061, comm: pccardd Not tainted 2.6.34-rc3 #4 2645310/2645310 EIP: 0060:[<c0479128>] EFLAGS: 00000286 CPU: 0 EIP is at yenta_set_socket+0x168/0x280 EAX: ca7fa850 EBX: 80001050 ECX: 00000000 EDX: 00000000 ESI: c9a00000 EDI: c9a00044 EBP: c9a03de8 ESP: c9a03dc8 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process pccardd (pid: 1061, ti=c9a02000 task=c9966500 task.ti=c9a02000) Stack: c9a03dda c8fc1090 c9a00040 05808692 05c00000 c8fc1000 c9a00040 c8176c00 <0> c9a03e0c c0472e25 c9a00150 00000000 00000000 00000001 c8fc1000 c8fc1000 <0> c06f3200 c9a03e20 c04731c8 c827c000 c8fc1000 c06f3200 c9a03e30 cb026409 Call Trace: [<c0472e25>] ? pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] ? pcmcia_disable_device+0x18/0x140 [<cb026409>] ? prism2_release+0x39/0x50 [hostap_cs] [<cb026430>] ? prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] ? pcmcia_device_remove+0x47/0x110 [<c04264b1>] ? __device_release_driver+0x51/0xa0 [<c04265a0>] ? device_release_driver+0x20/0x40 [<c0425ab1>] ? bus_remove_device+0x81/0xb0 [<c0423f6a>] ? device_del+0xfa/0x180 [<c0423ffb>] ? device_unregister+0xb/0x20 [<c04707d0>] ? pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ? ds_event+0x115/0x170 [<c046f11a>] ? send_event+0xaa/0xe0 [<c046f809>] ? socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] ? socket_remove+0x47/0x60 [<c046fccf>] ? pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] ? kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] ? kernel_thread_helper+0x6/0x10 Code: e8 0f b6 d1 8b 40 c0 3b 90 00 01 00 00 74 08 66 81 4d ee 80 00 09 cb 8b 46 0c 05 03 08 00 00 88 18 8b 46 0c 05 03 08 00 00 8a 00 <8b> 46 0c 05 02 08 00 00 8a 00 8b 17 83 e0 1b 89 c1 83 c9 40 f6 Call Trace: [<c0472e25>] pcmcia_release_configuration+0xd5/0x110 [<c04731c8>] pcmcia_disable_device+0x18/0x140 [<cb026409>] prism2_release+0x39/0x50 [hostap_cs] [<cb026430>] prism2_detach+0x10/0x220 [hostap_cs] [<c04711a7>] pcmcia_device_remove+0x47/0x110 [<c04264b1>] __device_release_driver+0x51/0xa0 [<c04265a0>] device_release_driver+0x20/0x40 [<c0425ab1>] bus_remove_device+0x81/0xb0 [<c0423f6a>] device_del+0xfa/0x180 [<c0423ffb>] device_unregister+0xb/0x20 [<c04707d0>] pcmcia_card_remove+0x90/0xb0 [<c0471f45>] ds_event+0x115/0x170 [<c046f11a>] send_event+0xaa/0xe0 [<c046f809>] socket_shutdown+0x19/0x100 [<c055ff9b>] ? printk+0x18/0x1d [<c046fa37>] socket_remove+0x47/0x60 [<c046fccf>] pccardd+0x27f/0x460 [<c046fa50>] ? pccardd+0x0/0x460 [<c024406c>] kthread+0x6c/0x80 [<c0244000>] ? kthread+0x0/0x80 [<c0202ef6>] kernel_thread_helper+0x6/0x10
Hm. Just strange. Could you enable "dynamic debug" for PCMCIA by issued echo "module pcmcia +p" > /sys/kernel/debug/dynamic_debug/control echo "module pcmcia_core +p" > /sys/kernel/debug/dynamic_debug/control before inserting the card and post the resulting dmesg (possibly as an attachment, for it will be looong). THanks for your countinous testing!
Created attachment 26013 [details] dmesg output with dynamic debugging as requested in #45 dmesg output with dynamic debugging as requested in #45 split in these parts: dmesg.ejectxircom. After reboot, ejecting the usual xircom card that sits in the way. dmesg.insertprism. Inserting the prism2 card. dmesg.ifup. After ifconfig wlan0 up. dmesg.ifdown After ifconfig wlan0 down. dmesg.xircominsert. The otherwise normally working xircom card now also gets call traces and won't work anymore until after a reboot.
Created attachment 26014 [details] dmesg output with dynamic debugging as requested in #45
Created attachment 26015 [details] dmesg output 3 with dynamic debugging as requested in #45
Created attachment 26016 [details] dmesg output 4 with dynamic debugging as requested in #45
Created attachment 26017 [details] dmesg output 5 with dynamic debugging as requested in #45 manually eject prism card
Created attachment 26018 [details] dmesg output 6 with dynamic debugging as requested in #45 insert xircom card back. After this exercise thsi also generates call traces and the card wo'nt work anymore until a reboot.
Do you have 4K stacks enabled?
Also, for comparison: what is the output (with dynamic debug enabled) in a working kernel? dmesg up to and including "dmesg.ifup" sufficces.
> --- Comment #52 from Dominik Brodowski <linux@brodo.de> 2010-04-15 17:12:56 > --- > Do you have 4K stacks enabled? > No. Regards, Wim. ----- wim@djo.tudelft.nl -----
Created attachment 26034 [details] dmesg 2.6.33-rc8 as requested in #53 as requested in #53 This one goes much longer..
Created attachment 26035 [details] avoid and report late calls to pccard_validate_cis Thanks for this helpful debug output. The only pcmcia_read_cis_mem/pcmcia_write_cis_mem related difference seems to be related to extra pccard_validate_cis calls, which might be the cause of the issue you're seeing. Could you test attached patch, with the dynamic debug enabled, and post the dmesg output up to and including the call to "ifup"? Many thanks!
Created attachment 26059 [details] dmesg as requested in #56 dmesg as requested in #56. includes ifconfig wlan0 up. Still call traces.
Created attachment 26061 [details] patch on top of 2.6.34-rc5 -- pcmcia urgent patches, debug and test patch I think I've tracked down what happens: the "card_present" callback in hostap_cs calls pcmcia_card_present() in IRQ context. This function then attempts to grab a mutex, which is a bad thing to do in IRQ context... To verify this is indeed the cause, it'd be great if you could test the attached patched on top of 2.6.34-rc5.
Created attachment 26110 [details] patch on top of 2.6.34-rc5 -- pcmcia urgent patches and specific bugfix Here's now a proper bugfix for the issue I suspect to be present. Could you test this patch, please, and also enable CONFIG_DEBUG_SPINLOCK_SLEEP in the kernel configuration? Possibly, this patch solves both the post-boot and the during-boot issue. Many thanks!
> Attachment #26061 [details]|0 |1 > is obsolete| | > > --- Comment #59 from Dominik Brodowski <linux@brodo.de> 2010-04-23 10:26:07 > --- > Created an attachment (id=26110) > --> (https://bugzilla.kernel.org/attachment.cgi?id=26110) > patch on top of 2.6.34-rc5 -- pcmcia urgent patches and specific bugfix > > Here's now a proper bugfix for the issue I suspect to be present. Could you > test this patch, please, and also enable CONFIG_DEBUG_SPINLOCK_SLEEP in the > kernel configuration? Possibly, this patch solves both the post-boot and the > during-boot issue. Many thanks! Just a short report. Patched a virgin 2.6.34-rc5. Booting with a card inserted ran up to the prompt without errors. Unfortunately hostap_hc.c was not patched and I forgot to check that first. So the card was in master mode for minutes before I could get to it. Besides that, I didn't have an antenna at hand, so the transmitter output was at risk all that time. It isn't stated anywhere that there would be a protection circuit, and it's not obvious that there would be such a feature in the long range / high power cards. Once again, please change the default state to a safe mode, which means monitor mode only will do. Actual testing wether the card works hasn't been done yet. I assume you don't need any output logs now. Regards, Wim. ----- wim@djo.tudelft.nl -----
Wim, regarding comment #60 -- could you open up a separate bug for this issue, please, as this seems to be unrelated to the issue we're investigating here. Logs will only be needed if the "call trace" problem persists in any way. Many thanks! Dominik
Wim, re-parsing your comment #60 -- does this mean that even "ifup" works without creating lots of call traces?
> --- Comment #62 from Dominik Brodowski <linux@brodo.de> 2010-04-27 16:56:36 > --- > Wim, re-parsing your comment #60 -- does this mean that even "ifup" works > without creating lots of call traces? > That's what it means actually. A double check just shows that everything is working again as before, so no peculiarities are to be reported. Thank you. Reagards, Wim. ----- wim@djo.tudelft.nl -----