public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: kernel panic -- finding proper config diff
Date: Thu, 22 Oct 2009 16:31:10 -0700	[thread overview]
Message-ID: <hbqpvq$2qm$1@ger.gmane.org> (raw)
In-Reply-To: <a0811460910211125m28d1c14ct7a0d4ebe5d131cf3@mail.gmail.com>

On 10/21/2009 11:25 AM, Maxim Wexler wrote:
> Hi group,
> 
> Did linux#make menuconfig followed by linux# make && make
> modules_install on the .2.6.30-gentoo-r7 sources. And copied over the
> new kernel and rebooted.
> 
> The kernel panicked. The relevant messages are:
> 
> <...>
> VFS: Mounted root (ext2 filesystem) readonly on device 8:1,
> Freeing unused kernel memory: 276k freed
> Warning: unable to open an initial console

That warning is interesting.  This is from the kernel sources:
 if (sys_open((const char __user *) "/dev/console", O_RDWR, 0) < 0)
     printk(KERN_WARNING "Warning: unable to open an initial console.\n");

In the dark ages, before udev, /dev/console had to be created in the bare
/dev directory (i.e. before anything is mounted on /dev) to prevent this
sort of error.  I thought it had been solved, but maybe I'm wrong about
that.

Of course, I'm not sure I don't get the same warning, but if I do it
flashes by so quickly I can't read it.

The message clearly states that / is mounted readonly, but that test for
/dev/console is asking for read/write. Maybe that's why the test fails,
dunno.  And I don't know if that warning is important.

Nowadays udev uses a tmpfs in RAM to populate /dev with devices, but
at the point your kernel panics, that tmpfs doesn't exist yet, so you
are stuck with the /dev directory on / including its readonly status,
I'm assuming.

Anyone else know?




  parent reply	other threads:[~2009-10-22 23:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 18:25 [gentoo-user] kernel panic -- finding proper config diff Maxim Wexler
2009-10-21 18:56 ` [gentoo-user] " Maxim Wexler
2009-10-21 19:07 ` Jonathan Callen
2009-10-21 19:13   ` Alan McKinnon
2009-10-21 20:22     ` Maxim Wexler
2009-10-21 20:35       ` Albert Hopkins
2009-10-21 20:45   ` Maxim Wexler
2009-10-22  1:19     ` walt
2009-10-22  3:28       ` Maxim Wexler
2009-10-22  3:37         ` William Kenworthy
2009-10-22  3:45           ` Maxim Wexler
2009-10-22 14:18         ` Neil Bothwick
2009-10-22 18:17           ` Maxim Wexler
2009-10-22 18:29             ` Neil Bothwick
2009-10-22 18:36             ` Maxim Wexler
2009-10-22 18:53               ` Alan McKinnon
2009-10-22 20:43                 ` Maxim Wexler
2009-10-22 19:31               ` Neil Bothwick
2009-10-22 18:50             ` Alan McKinnon
2009-10-24 10:41               ` Stroller
2009-10-22  1:48     ` Maxim Wexler
2009-10-22 23:31 ` walt [this message]
2009-10-23  0:31   ` Neil Bothwick
2009-10-23 16:02   ` walt
2009-10-23 21:57     ` Maxim Wexler
2009-10-23 22:54       ` walt
2009-10-24  1:33         ` Richard Marza
2009-10-24  4:05           ` Maxim Wexler
2009-10-24  7:44             ` Neil Bothwick
2009-10-24  7:44       ` Neil Bothwick
2009-10-26  4:52         ` Maxim Wexler
2009-10-26  9:10           ` Neil Bothwick
2009-10-29  4:38             ` waltdnes
2009-10-29  5:45               ` Maxim Wexler
2009-10-29  5:42             ` Maxim Wexler
2009-10-23  0:56 ` Jonathan Callen

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='hbqpvq$2qm$1@ger.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.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