All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: spinlock in ROSE module with kernel 2.6.17
Date: Wed, 05 Jul 2006 16:59:52 +0200	[thread overview]
Message-ID: <44ABD3E8.6040305@ccr.jussieu.fr> (raw)
In-Reply-To: <20060604231859.GA20158@linux-mips.org>

Hi Ralf,

I amnot sure this message go through, so I send it again.

I installed linux kernel 2.6.17.1 (now -3) on my ROSE-FPAC switch box 
and got systematically spinlocks within a few minutes, that did not came 
out with previous 2.6.16.23 and your patched applied.

After enabling compilation of sysrq for spinlocks and allowing sysrq
options (see linux/Documentation/sysrq.txt) I found that rose module was
involved.

Here is a summary of the screen dump obtained using console level 5 and
't' key action :

            softlockup_tick
            update_process_times
            timer_interrupt
            handle_IRQ_event
            __do_IRQ
            do_IRQ
            common_interrupt
            delay_tsc
            delay_tsc
            _raw_spin_lock
            _spin_lock_bh
<c8a25646> rose_get_neigh   +0x16 /0xa0  [rose]
<c8a25c2c> rose_route_frame +0x41c/0x580 [rose]
<c89d3bfe> ax25_check_iframes_acked +0x5e/0x70 [ax25]
<c89d55e1> ax25_std_frame_in +0x741/0x7e0 [ax25]
            ax25_find_cb
            ax25_kiss_rcv
            autoremove_wake_function

Since spinlock address is always lock: c8a2b3a4
I guess that the problem is in rose_route_frame ?

EIP is at delay_tsc + 0x16/0x20

What other report can I provide in order to help ?

73 de Bernard, f6bvp

http://f6bvp.org
http://rose.fpac.free.fr/MINI-HOWTO/
http://rose.fpac.free.fr/MINI-HOWTO-FR/



      parent reply	other threads:[~2006-07-05 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 19:48 Listen on a consol Chuck Hast
2006-06-03 21:11 ` bud Thompson
2006-06-03 21:44   ` Chuck Hast
2006-06-04  1:57     ` Bob Nielsen
2006-06-04 23:07       ` Jim Bayer
2006-06-04 23:18 ` Ralf Baechle DL5RB
2006-06-29 11:09   ` spinlock in kernel 2.6.17.1 Bernard Pidoux
2006-07-05 14:59   ` Bernard Pidoux [this message]

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=44ABD3E8.6040305@ccr.jussieu.fr \
    --to=pidoux@ccr.jussieu.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=ralf@linux-mips.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.