From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at sched.c:564! (2.4.20, 2.4.21-pre5-ac3)
Date: Wed, 26 Mar 2003 11:34:37 -0800 [thread overview]
Message-ID: <20030326193437.GI24689@kroah.com> (raw)
In-Reply-To: <20030326192520.GH2695@spackhandychoptubes.co.uk>
On Wed, Mar 26, 2003 at 07:25:20PM +0000, Chris Sykes wrote:
>
> I seem to have worked around it for now. I've jumpered the hardware
> to stop it from echoing what you transmit back locally and all seems
> OK now.
Good.
> > Can you test 2.5 to see if this is fixed there for you or not?
>
> I can test it yes, but 2.5 may be a bit too unstable for our
> production use ATM.
I understand.
> 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.
thanks,
greg k-h
next prev parent reply other threads:[~2003-03-26 19:24 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 [this message]
2003-03-27 11:16 ` Chris Sykes
2003-03-27 12:12 ` Stephan von Krawczynski
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=20030326193437.GI24689@kroah.com \
--to=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.