linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Damon LaCrosse <arid@inbox.ru>
Cc: user-mode-linux-user@lists.sourceforge.net,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Is this a known printk bug?
Date: Wed, 25 Oct 2006 11:59:53 -0400	[thread overview]
Message-ID: <20061025155953.GB4996@ccure.user-mode-linux.org> (raw)
In-Reply-To: <87bqo2ou4z.fsf@inbox.ru>

On Tue, Oct 24, 2006 at 01:01:00PM +0200, Damon LaCrosse wrote:
> 
> On certain situations where printk are embedded in spinlock protected regions
> (i.e. "spin_lock(); for () { printk(); } spin_unlock(); }") I often 
> experience uml lockups like this one:

Yeah, known bug.  We are using spinlocks improperly in the console subsystem.

				Jeff

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2006-10-25 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 11:01 [uml-devel] Is this a known printk bug? Damon LaCrosse
2006-10-25 15:59 ` Jeff Dike [this message]
2006-10-26  0:07   ` Blaisorblade

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=20061025155953.GB4996@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=arid@inbox.ru \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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