From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Bernard Pidoux <pidoux@ccr.jussieu.fr>
Cc: "Mike McCarthy, W1NR" <lists@w1nr.net>,
'Douglas Cole' <doug.n7bfs@gmail.com>,
linux-hams@vger.kernel.org
Subject: Re: AX25 patches and how it affects the end user
Date: Wed, 18 Jan 2006 01:08:43 +0000 [thread overview]
Message-ID: <20060118010843.GA3312@linux-mips.org> (raw)
In-Reply-To: <43CD2275.8050602@ccr.jussieu.fr>
On Tue, Jan 17, 2006 at 05:59:33PM +0100, Bernard Pidoux wrote:
> After applying mkiss patch to kernel 2.6.15.1 I compiled it for a 3 GHz
> Xeon P4 configuring it for SMP and multithread plus lock options.
>
> The SMP kernel seems very sensitive to AX25 configuration errors and it
> locks up quite soon in that case when loading applications.
>
> However when ax25 is carefully initialized, mkiss, kissattach, ax25ipd
> and ROSE/FPAC switch software suite) are running without problem.
>
> But there is still a spinlock lockup when shutting down the system.
>
> Here is a copy of the sequence I made by hand (subject to errors) :
Thanks. Btw, in some cases digital cameras have served well to catch
messages from screens without types - just make sure the images aren't
larger than necessary to be readable.
> Spinlock lockup on CPU#0, kissattach / 5048, f8d68714
> EIP <c01e3ba5>
> rose_remove_neigh + 0x30/0xb0 [rose]
> rose_rt_device_down + 0xeb / 0x120 [rose]
> rose_device_event + 0x42/0x50 [rose]
> notifier_call_chain + 0x2/0x50 [rose]
> dev_close + 0x7b/0xb0
> unregister_netdevice + 0x19e/0x250
> unregister_netdev+0x16/0x1d
> mkiss_close + 0x4a /0xa0 [mkiss]
> release_dev....
> tty_release ...
>
> Hope this can help.
> Please suggest any more test to be done.
I think the ROSE routing code is beyond recovery. The current data
structures requires extensive locking code that is easily prone to
deadlocks like this. It also is slow - fortunately nobody is using ROSE
on highspeed links ...
Anyway, the problem is pretty obvious in your traceback and I'll cook a
patch for you to test.
73,
Ralf
next prev parent reply other threads:[~2006-01-18 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:45 AX25 patches and how it affects the end user Douglas Cole
2006-01-11 22:14 ` Mike McCarthy, W1NR
2006-01-12 0:55 ` Douglas Cole
2006-01-13 21:09 ` Ralf Baechle DL5RB
2006-01-17 16:59 ` Bernard Pidoux
2006-01-18 1:08 ` Ralf Baechle DL5RB [this message]
2006-01-18 8:38 ` ROSE lockup fix Ralf Baechle DL5RB
2006-01-19 16:44 ` Bernard Pidoux
2006-02-09 16:25 ` Bernard Pidoux
2006-01-18 12:26 ` AX25 patches and how it affects the end user Chuck Hast
2006-01-18 21:52 ` Ralf Baechle DL5RB
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=20060118010843.GA3312@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=doug.n7bfs@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=lists@w1nr.net \
--cc=pidoux@ccr.jussieu.fr \
/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).