All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Chris Sykes <chris@sigsegv.plus.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at sched.c:564! (2.4.20, 2.4.21-pre5-ac3)
Date: Thu, 27 Mar 2003 13:12:14 +0100	[thread overview]
Message-ID: <20030327131214.1dae4005.skraw@ithnet.com> (raw)
In-Reply-To: <20030327111600.GI2695@spackhandychoptubes.co.uk>

Hello all,

I just wanted to hint that this very same BUG message appears on channel
bundling of ISDN, too. Greg, can you give a short description for this race
please, as I would like to find it in the ISDN-code, maybe your ideas help...

Thanks,
Stephan


On Thu, 27 Mar 2003 11:16:00 +0000
Chris Sykes <chris@sigsegv.plus.com> wrote:

> On Wed, Mar 26, 2003 at 11:34:37AM -0800, Greg KH wrote:
> > > Anyway I'll test out a 2.5 kernel when I'm back in the office
> > > tomorrow, I can devote some time to tracking down the problem if you
> > > can give me some pointers on where to start.  I'd like to be able to
> > > feel confident that this will work reliably under 2.4, otherwise I
> > > guess I need to look for alternate solutions.
> > 
> > The problem is in the race on close() in the usb-serial.c code.  In 2.5
> > that logic has been rewritten to (hopefully) get rid of the race.  That
> > is what will need to be backported, once people test that this fixes the
> > issue.
> 
> OK.  2.5.66 compiled and booted.
> 
> I've jumpered the hardware back to how it was originally when I
> experienced the problem.
> I've been working happily for about 10 mins with:
> 
> while /bin/true; do
>         for i in *; do
>                 cat $i >/dev/ttyUSB0
>         done
> done
> 
> No Oopsen or errors in dmesg as yet. (Before I was getting many errors
> about 0 size writes).
> 
> I can keep working under 2.5.66 for now to see if I experience any
> problems, but it would appear that the race is gone in 2.5.66
> (CONFIG_PREEMPT=y)
> 
> If you'd like me to try any patches against 2.4 just let me know.
> 
> Thanks again,
> 
> -- 
> 
> (o-  Chris Sykes  -- GPG Key: http://www.sigsegv.plus.com/key.txt
> //\       "Don't worry. Everything is getting nicely out of control ..."
> V_/_                          Douglas Adams - The Salmon of Doubt
> 
> 


-- 
MfG,
Stephan von Krawczynski
ith Kommunikationstechnik GmbH

  reply	other threads:[~2003-03-27 12:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 16:25 kernel BUG at sched.c:564! (2.4.20, 2.4.21-pre5-ac3) Chris Sykes
2003-03-26 18:52 ` Greg KH
2003-03-26 19:25   ` Chris Sykes
2003-03-26 19:34     ` Greg KH
2003-03-27 11:16       ` Chris Sykes
2003-03-27 12:12         ` Stephan von Krawczynski [this message]
2003-03-27 12:35           ` Patrick McHardy
2003-03-27 15:52             ` Stephan von Krawczynski
2003-03-27 17:45             ` Greg KH
2003-03-27 17:51               ` Patrick McHardy
2003-03-27 17:58                 ` Greg KH
2003-03-27 17:46         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 16:19 Chris Sykes

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=20030327131214.1dae4005.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=chris@sigsegv.plus.com \
    --cc=greg@kroah.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.