All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Jones <cretin@gentoo.org>
To: linux-kernel@vger.kernel.org
Cc: linux-pcmcia@lists.infradead.org
Subject: Re: [2.6.0-test1] yenta_socket.c:yenta_get_status returns bad value compared to 2.4
Date: 27 Jul 2003 10:46:22 +0100	[thread overview]
Message-ID: <1059299182.3383.18.camel@localhost> (raw)
In-Reply-To: <1059244318.3400.17.camel@localhost>

OSDL wrote:
> 
> Which is interesting in itself. It's entirely possible that we should 
> just ignore the 16-bit status when it comes to the SS_POWERON logic. 
> 
> 
> Does the card actually _work_ when you do your hack? Or does it just 
> stop the hang? 
> 
It just stopped the hang, which caused me to think I was onto something.

I will continue my debugging and take this to the pcmcia list,

so far with printk's and early returns I have got the following:

The ds_ioctl's are triggering the hang,

ioctl calls to DS_ADJUST_RESOURCE_INFO and DS_GET_STATUS work fine (all
others are quoted out and are not called before the hang )

But the first call to DS_VALIDATE_CIS causes the machine to hang.
I have tracked down the hang to 

pcmcia_get_first_tuple called from
pcmcia_validate_cis called from
ds_ioctl

in cistpl.c

Will narrow it down some more today.

PS. the card is:
Netgear 802.11b wireless PC card 16-bit PCMCIA MA401
( which works fine with 2.4.21 )

For you pcmcia ppl:
http://www.ussg.iu.edu/hypermail/linux/kernel/0307.3/0166.html
( hardware details )
http://www.ussg.iu.edu/hypermail/linux/kernel/0307.3/0690.html
( my misdiagnosis )

Any tips, known problem?

Stefan


  parent reply	other threads:[~2003-07-27  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 18:31 [2.6.0-test1] yenta_socket.c:yenta_get_status returns bad value compared to 2.4 Stefan Jones
2003-07-26 19:17 ` OSDL
2003-07-27  9:46 ` Stefan Jones [this message]
2003-08-02 17:08 ` Russell King
2003-08-03 11:07   ` Stefan Jones
2003-08-03 12:50     ` Russell King
2003-08-03 13:34       ` Stefan Jones

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=1059299182.3383.18.camel@localhost \
    --to=cretin@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.