linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: "Mike McCarthy, W1NR" <mike@w1nr.net>, linux-hams@vger.kernel.org
Subject: Re: 2.6.15 ax25 system lockup with kissattach
Date: Sun, 08 Jan 2006 01:09:50 +0100	[thread overview]
Message-ID: <43C0584E.6060109@ccr.jussieu.fr> (raw)
In-Reply-To: <20060107004231.GB12765@linux-mips.org>

Hi Ralf,

Without your patch, running Mandriva Linux 2006 with 2.6.15 kernel on a 
Pentium IV Xeon would freeze immediately when loading mkiss driver.

After the patch was applied and mkiss module compiled and driver 
installed, there is no more problem here.

However, the kernel was compiled with no forced preemption model and 
without SMP option. I will do it soon an report if any change.

Thank you for the nice job you are doing on AX25 stuff.

73 de Bernard, f6bvp

http://f6bvp.free
http://f6bvp.org (mirror)

-----------

Ralf Baechle DL5RB a écrit :
> On Thu, Jan 05, 2006 at 06:26:43PM -0500, Mike McCarthy, W1NR wrote:
> 
> 
>>That's all folks.  System locked up hard.  Caps lock and scroll lock lights
>>flashing.  System needs a hard reset.
>>
>>2.6.14-5 appears to be fine.  Tried recompiled tools and libraries as well.
>>Others report similar problems on Debian systems with 2.6.15 kernel as well.
> 
> 
> Can you try below patch?  It fixes a locking bug which was affecting only
> preemptable or SMP kernels until the recent rewrite of the locking code.
> 
> 73 de DL5RB op Ralf
> 
> --
> Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
> 
>  drivers/net/hamradio/mkiss.c |    1 +
>  1 files changed, 1 insertion(+)
> 
> Index: net.git/drivers/net/hamradio/mkiss.c
> ===================================================================
> --- net.git.orig/drivers/net/hamradio/mkiss.c
> +++ net.git/drivers/net/hamradio/mkiss.c
> @@ -515,6 +515,7 @@ static void ax_encaps(struct net_device 
>  			count = kiss_esc(p, (unsigned char *)ax->xbuff, len);
>  		}
>    	}
> +	spin_unlock_bh(&ax->buflock);
>  
>  	set_bit(TTY_DO_WRITE_WAKEUP, &ax->tty->flags);
>  	actual = ax->tty->driver->write(ax->tty, ax->xbuff, count);
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2006-01-08  0:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 23:26 2.6.15 ax25 system lockup with kissattach Mike McCarthy, W1NR
2006-01-06 12:26 ` Ralf Baechle DL5RB
2006-01-07  0:42 ` Ralf Baechle DL5RB
2006-01-07 12:50   ` Markus Roch
2006-01-07 17:55     ` Mike McCarthy, W1NR
2006-01-14 17:03     ` Linux FPAC MINI-HOWTO bernard f6bvp
2006-01-07 22:45   ` 2.6.15 ax25 system lockup with kissattach Bob Nielsen
2006-01-08  0:09   ` Bernard Pidoux [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-11 15:09 Bob Brose N0QBJ

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=43C0584E.6060109@ccr.jussieu.fr \
    --to=pidoux@ccr.jussieu.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=mike@w1nr.net \
    --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 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).