All of lore.kernel.org
 help / color / mirror / Atom feed
From: gshan <gshan@alcatel-lucent.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bugs in __schedule()
Date: Tue, 26 Jun 2007 16:18:28 +0800	[thread overview]
Message-ID: <4680CBD4.2040702@alcatel-lucent.com> (raw)
In-Reply-To: <b6fcc0a0706260114o59b489a7o7dd7e4ce2e621852@mail.gmail.com>

The code is written by myself. 2 questions:

1) tasklet couldn't sleep?
2) It is because the tasklet take a semaphore?

Thanks,
Gavin

Alexey Dobriyan wrote:
> On 6/26/07, gshan <gshan@alcatel-lucent.com> wrote:
>> Anybody has suggestions on this crash?
>
> talk to whoever supplied the following into your kernel:
>
>> [c02dc4dc] __schedule+0x654/0x788
>>  [c02dc6f4] schedule+0x4c/0xe4
>>  [c02dbe24] __compat_down+0xc8/0x12c
>>  [c0226b60] mv_sw_read_reg+0x178/0x17c
>
> this
>
>>  [c02296fc] mvSwIntrTasklet+0x128/0x744
>
> and this.
>
>>  [c0020afc] tasklet_action+0x7c/0xec
>>  [c00204f4] ___do_softirq+0x80/0x11c
>>  [c00205cc] __do_softirq+0x3c/0x6c
>>  [c00206a4] do_softirq+0x60/0x68
>>  [c00207a8] irq_exit+0x6c/0x94
>>  [c0005e1c] do_IRQ+0x88/0xa4
>>  [c0004b70] ret_from_except+0x0/0x18
>>  [c000680c] __delay+0xc/0x14
>>  [c0226598] mv_sw_read_smi_reg+0x84/0x1ac


  reply	other threads:[~2007-06-26  8:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26  7:57 bugs in __schedule() gshan
2007-06-26  8:14 ` Alexey Dobriyan
2007-06-26  8:18   ` gshan [this message]
2007-06-26  8:18 ` Satyam Sharma
2007-06-26  8:20   ` gshan
2007-06-26  8:25     ` Satyam Sharma
2007-06-26  8:36       ` gshan
2007-06-26  8:50         ` Satyam Sharma
2007-06-26  8:55           ` gshan
2007-06-26  9:08             ` Satyam Sharma
2007-06-26  9:13               ` gshan

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=4680CBD4.2040702@alcatel-lucent.com \
    --to=gshan@alcatel-lucent.com \
    --cc=adobriyan@gmail.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.