From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.6-test1, PCMCIA cards require two insertions
Date: Mon, 4 Aug 2003 07:50:26 -0800 [thread overview]
Message-ID: <20030804155026.GB10269@iarc.uaf.edu> (raw)
In-Reply-To: <20030802173352.A1895@flint.arm.linux.org.uk>
Russell,
Earlier I reported:
> On Fri, Jul 25, 2003 at 01:02:42PM -0800, Christopher Swingley wrote:
> > I'm running 2.6.0-test1 on an SiS based laptop with all the PCMCIA
> > network and serial drivers built into the kernel. When the system boots
> > with a PCMCIA cardbus card in place, the card doesn't show up. I unplug
> > the card and plug it back in, and then the kernel "sees" it and it
> > works. If I unplug it again, I have to go through a plug - unplug -
> > plug cycle before it recognizes it. As if it only recognizes the card
> > on even numbered insertion events.
Still behaves the same way with a stock 2.6.0-test2. I applied the
patch you included to 2.6.0-test2. Same strange dual-insertion behavior
was noted.
Also, I have another laptop, Intel based, that doesn't show this
behavior. So it's something to do with this one.
> Hmm, weird - I'm not seeing that behaviour here. Can you report back
> with kernel messages with the following patch applied please?
Here's what happens on the console. If you want kern.log, let me know
and I'll send that along. I don't see anything different between them.
After the laptop finishes booting, the PCMCIA network card (tulip
driver) is not running.
I remove the card:
parse_events: socket df5cd82c thread df60e060 events 00000080
socket df5cd82c status 00001c00
I insert the card:
parse_events: socket df5cd82c thread df60e060 events 00000080
socket df5cd82c status 00001c80
socket_insert: skt df5cd82c
socket_setup: skt df5cd82c status 00001c80
socket_reset: skt df5cd82c
Linux Tulip driver version 1.1.13 (May 11, 2002)
<rest of tulip driver stuff snipped>
I remove the card:
parse_events: socket df5cd82c thread df60e060 events 00000080
socket df5cd82c status 00001c00
socket_remove: skt df5cd82c
socket_shutdown: skt df5cd82c status 00001c80
I insert the card:
(nothing at all)
I remove the card:
parse_events: socket df5cd82c thread df60e060 events 00000080
socket df5cd82c status 00001c00
I insert the card:
parse_events: socket df5cd82c thread df60e060 events 00000080
socket df5cd82c status 00001c80
socket_insert: skt df5cd82c
socket_setup: skt df5cd82c status 00001c80
socket_reset: skt df5cd82c
Linux Tulip driver version 1.1.13 (May 11, 2002)
<rest of tulip driver stuff snipped>
Chris
--
Christopher S. Swingley email: cswingle@iarc.uaf.edu
IARC -- Frontier Program Please use encryption. GPG key at:
University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle/
prev parent reply other threads:[~2003-08-04 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 21:02 Christopher Swingley
2003-07-25 21:24 ` Bart Trojanowski
2003-08-02 16:33 ` Russell King
2003-08-04 15:50 ` Christopher Swingley [this message]
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=20030804155026.GB10269@iarc.uaf.edu \
--to=cswingle@iarc.uaf.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®