netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Niranjan <niranjan_cs2905@yahoo.com>
Cc: netdev@oss.sgi.com
Subject: Re: kernel bug at sched.c:564! + linux kernel 2.4.25
Date: Mon, 26 Jul 2004 16:06:13 -0500	[thread overview]
Message-ID: <20040726210613.GR5414@waste.org> (raw)
In-Reply-To: <20040724223310.68910.qmail@web53004.mail.yahoo.com>

On Sat, Jul 24, 2004 at 03:33:10PM -0700, Niranjan wrote:
> Hi,
> I am working on Linux Kernel 2.4.25. I am trying to
> add cryptoapi (cryptoapi-0.1.0) support to wireless
> lan driver (linux-wlan-ng-0.2.1.pre14) of prism-based
> cards. Cardctl version is 3.1.31.
> When I am using "null" as a encryption cipher to check
> the coding sequence, everything is working fine. But
> when I change it to any other cipher for e.g.
> "blowfish" or "rc5", it is giving kernel panic. I have
> included Ksymoops extract from the kernel Ooops
> reports below.
> Can anyone please help me in what can be possible
> error by looking at the log ? 
> I will greatly appreciate any help in this matter.

The cryptoapi currently decides to sleep at various points internally
when digesting a block which is probably what you're seeing.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2004-07-26 21:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 22:33 kernel bug at sched.c:564! + linux kernel 2.4.25 Niranjan
2004-07-26 21:06 ` Matt Mackall [this message]
2004-07-27 18:02   ` Vladimir Kondratiev
2004-07-27 18:39     ` James Morris
2004-07-27 18:50       ` Vladimir Kondratiev
2004-07-27 18:57         ` James Morris
2004-07-28 15:55           ` Niranjan
2004-07-28 16:10             ` James Morris
2004-07-28 16:30               ` Niranjan
2004-07-27 22:23         ` Niranjan

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=20040726210613.GR5414@waste.org \
    --to=mpm@selenic.com \
    --cc=netdev@oss.sgi.com \
    --cc=niranjan_cs2905@yahoo.com \
    /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).