public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Ian Duggan <ian@ianduggan.net>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18 Preempt Freezeups
Date: 14 Mar 2002 20:54:09 -0500	[thread overview]
Message-ID: <1016157250.4599.62.camel@phantasy> (raw)
In-Reply-To: <3C9153A7.292C320@ianduggan.net>
In-Reply-To: <3C9153A7.292C320@ianduggan.net>

On Thu, 2002-03-14 at 20:51, Ian Duggan wrote:

> Stock 2.4.17+preempt+lock-break+mki-adapter+win4lin
> 
> 	- Problem extremely intermittent, maybe once a day.
> 
> 
> Stock 2.4.18+preempt+mki-adapter+win4lin
> 
> 	- Very frequent, and also repeatable every time I
> 		try to start win4lin.

Pretty clear it is win4line.  Is it SMP-safe?

Is there another kernel module you load for win4lin?  Binary?  It needs
to be made preempt (and SMP) -safe.

	Robert Love



  reply	other threads:[~2002-03-15  1:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  1:51 2.4.18 Preempt Freezeups Ian Duggan
2002-03-15  1:54 ` Robert Love [this message]
2002-03-15  8:36   ` Ian Duggan
2002-03-15 14:25     ` Robert Love
2002-03-15 16:11       ` Mikael Pettersson
2002-03-15 19:11         ` Robert Love
2002-03-16  0:40           ` yodaiken
2002-03-16  1:46             ` Mike Fedyk
2002-03-16  3:12               ` yodaiken
2002-03-17  0:33             ` Daniel Phillips
2002-03-17  1:13               ` yodaiken
2002-03-17  1:14                 ` Daniel Phillips
2002-03-17  1:54                   ` yodaiken
2002-03-17  2:08                     ` Daniel Phillips
2002-03-17 21:17                     ` Davide Libenzi
2002-03-15 14:30     ` Alan Cox
2002-03-15 21:36       ` Ian Duggan
2002-03-15  2:11 ` Alan Cox
2002-03-15  8:38   ` Ian Duggan
2002-03-15  8:51     ` David S. Miller
2002-03-15 14:28     ` Alan Cox
2002-03-16 23:51       ` Daniel Phillips
2002-03-17  3:31         ` Alan Cox
2002-03-17 12:59           ` Dave Jones
2002-03-15  8:43   ` Daniel Phillips

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=1016157250.4599.62.camel@phantasy \
    --to=rml@tech9.net \
    --cc=ian@ianduggan.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox