From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Anthony Brock <Anthony_Brock@ous.edu>
Subject: Re: [uml-devel] New messages at boot with 2.6.7 kernel
Date: Fri, 20 Aug 2004 13:30:54 +0200 [thread overview]
Message-ID: <200408201330.54086.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <s107d727.063@ORANGE.OUS.EDU>
Alle 01:40, giovedì 29 luglio 2004, Anthony Brock ha scritto:
> I've started seeing the following message with a newly built kernel at
> startup of SuSE 9.1 and Debian Woody images. While the kernel appears to be
> functioning as expected, the messages are new. I did configure this kernel
> from scratch, so it's possible that I made a significant change to cause
> these.
They come because you enabled CONFIG_DEBUG_SPINLOCK, and show a bug standing
since 2.5.70 at least. Anyway it causes actual problems just with SMP (which
does not work under UML), so for now don't worry; I already noticed this
problem and I'm going to fix it.
Bye
--
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
prev parent reply other threads:[~2004-08-20 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s107d727.063@ORANGE.OUS.EDU>
2004-07-29 4:08 ` [uml-devel] New messages at boot with 2.6.7 kernel Jeff Dike
2004-08-20 11:30 ` BlaisorBlade [this message]
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=200408201330.54086.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=Anthony_Brock@ous.edu \
--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