All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: spin_unlock hang, and IRC question
Date: Thu, 22 Aug 2002 23:02:40 -0700	[thread overview]
Message-ID: <3D65D000.60004@candelatech.com> (raw)

Hello!

First, anyone know why I get this when trying to log onto #kernel IRC
channel?

  greear sets mode +i greear
--- You have been killed by mid.eu.linuxnet.org (Username))
--- Closing Link: dhcp101-dsl-usw4.w-link.net greear (Killed by mid.eu.linuxnet.org (Bad Username))
--- Disconnected (Remote host closed socket).


Now, for the real question:  I'm making pktgen threaded.  It works great on
a single processor (compiled for single processor).  But, it hangs quickly
when used on an SMP (Athlon 2Ghz-equiv) machine.

I put in print statements (I would love to hear other ideas for how to debug)
and it seems that the system hangs trying to unlock a spin lock.  Specifically,
I see the first printout, but not the second:


inline static void pg_unlock(struct pktgen_thread_info* pg_thread, char* msg) {
         if (debug > 1) {
                 printk("before pg_unlock thread, thread: %x  msg: %s\n",
                        pg_thread, msg);
         }
         spin_unlock(&(pg_thread->pg_threadlock));
         if (debug > 1) {
                 printk("after pg_unlock thread, thread: %x  msg: %s\n",
                        pg_thread, msg);
         }
}


Any ideas for how to go about debugging this will be greatly appreciated!

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



                 reply	other threads:[~2002-08-23  5:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3D65D000.60004@candelatech.com \
    --to=greearb@candelatech.com \
    --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 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.