linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Dowideit <svenud@ozemail.com.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Russell King <rmk@arm.linux.org.uk>, Jean Tourrilhes <jt@hpl.hp.com>
Subject: mis-identified cisco aironet pccard (and Re: hang with pcmcia wlan card)
Date: 13 Jul 2003 22:57:58 +1000	[thread overview]
Message-ID: <1058100731.778.5.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 4381 bytes --]

Hi,
i just noticed with 2.5.75 that if I boot with the cisco airo 340 wifi
card in, this kernel thinks it is a memory card. when i remove it and
re-insert it after boot, it then works .... see the following log :) I
am running debian unstable, on an ibm t21 pIII-850 notebook

the cisco card works at boot time using 2.5.70.

as for the two patches for the pcmcia hang, this time i am running the
one Russell posted, but the result is the same for the other.

as i shutdown i get a number of kernel stack dumps related to airo_stat,
but the machine reboots before i can do anything about them..(what do i
need to log them?)

if i replace the cisco card with a dlink orinoco card, it get recognised
correctly at boot. 

to make this story more interesting, i put the thinkpad into the docking
station and the cisco card into the dock's pccard (something that has
locked up 2.5 every time that i tried it), and the card is recogised
correctly at boot, and runs fine (there was a kernel stack dump during
boot - *what do i need to do to get them logged?*)

thanks for the great work!

sven
--

Jul 13 21:36:43 [kernel] Linux Kernel Card Services 3.1.22
Jul 13 21:36:43 [kernel]   options:  [pci] [cardbus] [pm]
Jul 13 21:36:43 [kernel] PCI: Found IRQ 9 for device 0000:00:02.0
Jul 13 21:36:43 [kernel] PCI: Sharing IRQ 9 with 0000:00:05.0
Jul 13 21:36:43 [kernel] PCI: Sharing IRQ 9 with 0000:01:00.0
Jul 13 21:36:43 [kernel] Yenta IRQ list 00b8, PCI irq9
Jul 13 21:36:43 [kernel] Socket status: 30000010
Jul 13 21:36:43 [kernel] PCI: Found IRQ 9 for device 0000:00:02.1
Jul 13 21:36:43 [kernel] Yenta IRQ list 00b8, PCI irq9
Jul 13 21:36:43 [kernel] Socket status: 30000006
Jul 13 21:36:44 [cardmgr] watching 2 sockets
Jul 13 21:36:44 [kernel] cs: IO port probe 0x0c00-0x0cff: clean.
Jul 13 21:36:44 [kernel] cs: IO port probe 0x0800-0x08ff: clean.
Jul 13 21:36:44 [kernel] cs: IO port probe 0x0100-0x04ff: excluding
0x3c0-0x3df 0x4d0-0x4d7
Jul 13 21:36:44 [kernel] cs: IO port probe 0x0a00-0x0aff: clean.
Jul 13 21:36:44 [cardmgr] starting, version is 3.2.2
Jul 13 21:36:44 [kernel] cs: memory probe 0xa0000000-0xa0ffffff: clean.
Jul 13 21:36:44 [cardmgr] socket 0: Anonymous Memory
Jul 13 21:36:44 [cardmgr] executing: 'modprobe memory_cs'
Jul 13 21:36:44 [cardmgr] + FATAL: Module memory_cs not found.
Jul 13 21:36:44 [cardmgr] modprobe exited with status 1
Jul 13 21:36:44 [cardmgr] module /lib/modules/2.5.75/pcmcia/memory_cs.o
not available
Jul 13 21:36:44 [cardmgr] bind 'memory_cs' to socket 0 failed: Invalid
argument
Jul 13 21:36:44 [cardmgr] socket 0: Anonymous Memory

......


Jul 13 21:53:01 [cardmgr] executing: 'modprobe -r memory_cs'
Jul 13 21:53:01 [cardmgr] + FATAL: Module memory_cs not found.
Jul 13 21:53:01 [cardmgr] modprobe exited with status 1

.......

Jul 13 21:56:11 [cardmgr] socket 0: Aironet PC4800
Jul 13 21:56:12 [cardmgr] executing: 'modprobe airo_cs'
Jul 13 21:56:12 [kernel] airo:  Probing for PCI adapters
Jul 13 21:56:12 [kernel] airo:  Finished probing for PCI adapters
Jul 13 21:56:12 [kernel] airo: MAC enabled eth1 0:40:96:33:e:a4
Jul 13 21:56:12 [cardmgr] executing: './network start eth1'
Jul 13 21:56:12 [kernel] bad: scheduling while atomic!
Jul 13 21:56:12 [kernel] bad: scheduling while atomic!
Jul 13 21:56:12 [dhclient] Internet Software Consortium DHCP Client
2.0pl5
Jul 13 21:56:12 [dhclient] Copyright 1995, 1996, 1997, 1998, 1999 The
Internet Software Consortium.
Jul 13 21:56:12 [dhclient] All rights reserved.
Jul 13 21:56:12 [dhclient] 
Jul 13 21:56:12 [dhclient] Please contribute if you find this software
useful.
Jul 13 21:56:12 [kernel] bad: scheduling while atomic!
Jul 13 21:56:12 [dhclient] For info, please visit
http://www.isc.org/dhcp-contrib.html
Jul 13 21:56:12 [dhclient] 
Jul 13 21:56:12 [dhclient] wifi0: unknown hardware address type 801
Jul 13 21:56:14 [dhclient] wifi0: unknown hardware address type 801
Jul 13 21:56:14 [dhclient] Listening on LPF/eth1/00:40:96:33:0e:a4
Jul 13 21:56:14 [dhclient] Sending on   LPF/eth1/00:40:96:33:0e:a4
Jul 13 21:56:14 [dhclient] Sending on   Socket/fallback/fallback-net
Jul 13 21:56:14 [dhclient] DHCPREQUEST on eth1 to 255.255.255.255 port
67
Jul 13 21:56:14 [dhclient] DHCPACK from 10.11.11.1
Jul 13 21:56:14 [dhclient] bound to 10.11.11.34 -- renewal in 21600
seconds.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-07-13 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13 12:57 Sven Dowideit [this message]
2003-07-14 16:48 ` mis-identified cisco aironet pccard (and Re: hang with pcmcia wlan card) Jean Tourrilhes
2003-07-14 16:52   ` Russell King
2003-07-14 17:00     ` Jean Tourrilhes
2003-07-15 13:20     ` Sven Dowideit
2003-07-15 14:55       ` Russell King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1058100731.778.5.camel@localhost \
    --to=svenud@ozemail.com.au \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).