From: Paolo Giarrusso <blaisorblade_personal@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Carlo Wood <carlo@alinoe.com>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] ubd_kern.c: spin_lock already locked by drivers/block/ll_rw_blk.c
Date: Thu, 19 Aug 2004 20:57:37 +0200 [thread overview]
Message-ID: <200408192057.37295.blaisorblade_personal@yahoo.it> (raw)
In-Reply-To: <20030611091956.GA32752@alinoe.com>
Alle 11:19, mercoledì 11 giugno 2003, Carlo Wood ha scritto:
> Running 2.5.69 as uml, I get the following during boot:
>
> ...
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> /dev/ubd/disc0:arch/um/drivers/ubd_kern.c:383:
> spin_lock(arch/um/drivers/ubd_kern.c:a01b6940) already locked by
> drivers/block/ll_rw_blk.c/1002 drivers/block/ll_rw_blk.c:1004:
> spin_unlock(arch/um/drivers/ubd_kern.c:a01b6940) not locked unknown
> partition table
> /dev/ubd/disc1:arch/um/drivers/ubd_kern.c:383:
> spin_lock(arch/um/drivers/ubd_kern.c:a01b6940) already locked by
> drivers/block/ll_rw_blk.c/1002 drivers/block/ll_rw_blk.c:1004:
> spin_unlock(arch/um/drivers/ubd_kern.c:a01b6940) not locked unknown
> partition table
> arch/um/drivers/ubd_kern.c:383:
> spin_lock(arch/um/drivers/ubd_kern.c:a01b6940) already locked by
> drivers/block/ll_rw_blk.c/1002 drivers/block/ll_rw_blk.c:1004:
> spin_unlock(arch/um/drivers/ubd_kern.c:a01b6940) not locked
> arch/um/drivers/ubd_kern.c:383:
> spin_lock(arch/um/drivers/ubd_kern.c:a01b6940) already locked by
> drivers/block/ll_rw_blk.c/1002 drivers/block/ll_rw_blk.c:1004:
> spin_unlock(arch/um/drivers/ubd_kern.c:a01b6940) not locked
> arch/um/drivers/ubd_kern.c:383:
> spin_lock(arch/um/drivers/ubd_kern.c:a01b6940) already locked by
> drivers/block/ll_rw_blk.c/1002 drivers/block/ll_rw_blk.c:1004:
> spin_unlock(arch/um/drivers/ubd_kern.c:a01b6940) not locked VFS: Mounted
> root (ext2 filesystem) readonly.
> ...
>
> This is with kernel debugging on, of course.
>
> Because it mentions files in arch/um/*, it must be a problem
> with the uml.
In fact, yes, it's a UML problem. I'm going to solve this. No, I'm not crazy,
the problem is still here (the line numbers are different, but probably is
the same). As a side note, to get this you need CONFIG_SMP=n and
CONFIG_DEBUG_SPINLOCK=y. If you enable CONFIG_SMP, you actually don't get the
debug messages, only the deadlock. Also, to get *this* messages you need to
be using synchronous mode. I recommend *NOT* enabling
CONFIG_BLK_DEV_UBD_SYNC, but using instead the ubd=sync option (which is the
same thing, but selectable at runtime).
**And no, using the 's' ubd0s=... is not the same thing; the second just means
"use O_SYNC", while the first means "always use O_SYNC, and also don't start
the ubd I/O thread".
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
parent reply other threads:[~2004-08-20 10:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030611091956.GA32752@alinoe.com>]
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=200408192057.37295.blaisorblade_personal@yahoo.it \
--to=blaisorblade_personal@yahoo.it \
--cc=carlo@alinoe.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@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