From: Patrick McHardy <kaber@trash.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Regression - Re: 2.6.28-rc2: runaway loop modprobe char-major-5-1
Date: Tue, 25 Nov 2008 12:12:52 +0100 [thread overview]
Message-ID: <492BDDB4.90304@trash.net> (raw)
In-Reply-To: <ac3eb2510811240705q2133b4e5w6ac0ab6b41ccaa69@mail.gmail.com>
Kay Sievers wrote:
> On Mon, Nov 24, 2008 at 14:31, Patrick McHardy <kaber@trash.net> wrote:
>> Meelis Roos wrote:
>>> Rerepeating, same userspace generats fine initramfs for 2.6.27 and the
>>> initramfs contents are the same except modules tree that is for different
>>> version.
>>>
>>> It happens on 2 of my computers, both have custom config (serial compiled
>>> in, not modular). The hang happens before ttyS driver initialization.
>> char-major-5-1 is /dev/console here.
>>
>>> Seems like a kernel regression to me.
>> It does, I changed some configuration options from =m to =y and
>> it started working again. Unfortunately I'm unable to find the
>> exact option that fixed it since I don't have the previous
>> configuration anymore and random attempts to trigger the problem
>> again failed.
>
> Maybe you just miss /dev/console in initramfs? That would trigger the
> kernel forked modprobe with that major/minor.
>
> Some device nodes must be created or included in initramfs before any
> action is taken.
No, the image is fine. As I said, changing the config fixed the problem.
prev parent reply other threads:[~2008-11-25 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 10:15 2.6.28-rc2: runaway loop modprobe char-major-5-1 Meelis Roos
2008-10-28 13:58 ` Patrick McHardy
2008-10-28 14:50 ` Meelis Roos
2008-10-29 20:27 ` Meelis Roos
2008-11-21 21:56 ` Regression - " Meelis Roos
2008-11-24 13:31 ` Patrick McHardy
2008-11-24 15:05 ` Kay Sievers
2008-11-25 11:12 ` Patrick McHardy [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=492BDDB4.90304@trash.net \
--to=kaber@trash.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.