From: "Martin J. Bligh" <fletch@aracnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Adding a printk in start_secondary breaks 2.4.10, not 2.4.9 ??
Date: Fri, 28 Sep 2001 10:50:05 -0700 [thread overview]
Message-ID: <946825303.1001674205@[10.10.1.2]> (raw)
In-Reply-To: <E15n1Rz-0007lt-00@the-village.bc.nu>
> The console locking changes have I suspect broken your bandaid. I guess
> this time you need to fix it properly. Garbled panics normally occur when
> both cpus panic in parallel. That really wants some kind of timed spinlock
> to try and dump them one after the other
Humpf. You mean I've got to get rid of my disgusting hack? Sigh ... OK. ;-)
FWIW, I still think that means that the console locking changes are broken
-
adding a printk shouldn't panic the kernel. I'll go look at the console
locking
changes (*and* fix my disgusting hack ;-) )
M.
next prev parent reply other threads:[~2001-09-28 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 17:23 Martin J. Bligh
2001-09-28 17:29 ` Alan Cox
2001-09-28 17:50 ` Martin J. Bligh [this message]
2001-09-28 18:09 ` Alan Cox
2001-09-28 18:37 ` Martin J. Bligh
2001-09-28 18:43 ` Alan Cox
2001-09-30 5:49 ` Martin J. Bligh
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='946825303.1001674205@[10.10.1.2]' \
--to=fletch@aracnet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®