From: Chris Boot <bootc@bootc.net>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiser4 lockups (no oops)
Date: Thu, 20 Oct 2005 23:05:59 +0100 [thread overview]
Message-ID: <435814C7.8050807@bootc.net> (raw)
In-Reply-To: <17240.1485.704010.417090@gargle.gargle.HOWL>
Nikita Danilov wrote:
> Chris Boot writes:
> > Nikita Danilov wrote:
> >
> > >Chris Boot writes:
> > >
> > >[...]
> > >
> > > > Oh! Hehe, now I get you. However, I'm using metalog for logging, and
> > > > modprobe loop doesn't give any output. What's interesting is that serial
> > > > console logging dies long before metalog is started, just after my swap
> > > > is added in fact. I'm using Gentoo.
> > > >
> > > > Any ideas?
> > >
> > >What
> > >
> > >cat /proc/sys/kernel/printk
> > >
> > >shows after a boot?
> > >
> > > >
> > > > Cheers,
> > > > Chris
> > >
> > >Nikita.
> > >
> > >
> > Hi there,
> >
> > It shows:
> >
> > arcadia ~ # cat /proc/sys/kernel/printk
> > 1 4 1 7
>
> That's why nothing is printed on the console. Try
>
> echo 8 4 4 8 > /proc/sys/kernel/printk
Cheers! That did the trick.
Chris
--
Chris Boot
bootc@bootc.net
http://www.bootc.net/
next prev parent reply other threads:[~2005-10-20 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 17:08 Reiser4 lockups (no oops) Chris Boot
2005-10-20 13:18 ` Jens Axboe
2005-10-20 15:34 ` Chris Boot
2005-10-20 16:21 ` Jens Axboe
2005-10-20 16:27 ` Chris Boot
2005-10-20 17:52 ` Nikita Danilov
2005-10-20 18:44 ` Chris Boot
2005-10-20 21:02 ` Nikita Danilov
2005-10-20 22:05 ` Chris Boot [this message]
2005-10-20 18:37 ` Mattia Dongili
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=435814C7.8050807@bootc.net \
--to=bootc@bootc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@clusterfs.com \
/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