archive mirror
 help / color / mirror / Atom feed
From: "Jeremy T. Bouse" <>
Subject: Re: PROBLEM: Problem with wireless PCMCIA card insertion on 2.6.0-test2
Date: Mon, 4 Aug 2003 11:12:21 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On Mon, Aug 04, 2003 at 07:01:33PM +0100, Russell King wrote:
> On Mon, Aug 04, 2003 at 10:18:59AM -0700, Jeremy T. Bouse wrote:
> > [1.]
> > Problem with Wireless PCMCIA card insertion.
> PCMCIA or CardBus?
	My bad it is a CardBus bridge using the yenta socket
> > [5.]
> > Jul 28 18:02:10 vaio kernel: airo:  Probing for PCI adapters
> > Jul 28 18:02:10 vaio kernel: kobject_register failed for airo (-17)
> This looks like an error in airo.  For starters, it doesn't unregister
> its PCI driver structure when the module removed, so when it is
> inserted the next time, you get this complaint.
> (You can only have one driver called "airo" registered with the device
> model.)
	I am currently compiling -test2-bk4 to test it out and see if
there is any change... I did notice a patch to airo.c in it... I'll
advise if there is any change good or bad... 
> Oops, it seems to be scheduling from timer context.  That's pretty bad.
> I guess this is the culpret:
> static u16 issuecommand(struct airo_info *ai, Cmd *pCmd, Resp *pRsp) {
> ...
>                 if (!in_interrupt() && (max_tries & 255) == 0)
>                         schedule();
> ...
> }
	This must be active only if CONFIG_PREEMPT is set as the atomic
errors did seem to cease after recompiling with CONFIG_PREEMPT not being

	Jeremy T. Bouse

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-04 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 17:18 PROBLEM: Problem with wireless PCMCIA card insertion on 2.6.0-test2 Jeremy T. Bouse
2003-08-04 18:01 ` Russell King
2003-08-04 18:12   ` Jeremy T. Bouse [this message]
2003-08-04 22:05   ` Jeremy T. Bouse

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:

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

  git send-email \ \ \ \ \

* 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).