mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Regression - Re: 2.6.28-rc2: runaway loop modprobe char-major-5-1
Date: Fri, 21 Nov 2008 23:56:38 +0200 (EET)	[thread overview]
Message-ID: <Pine.SOC.4.64.0811212351200.16409@math.ut.ee> (raw)
In-Reply-To: <49071A84.3080706@trash.net>

> > request_module: runaway loop modprobe char-major-5-1
> > 
> > and then hangs.
> > 
> > char-major-5-1 seems to mean ttyS0.
> 
> I'm seeing the same problem on a Debian unstable system using
> initramfs and dm-crypt, but it seems to be caused by userspace
> changes, using an old initramfs image with just the new modules
> added manually works fine (well, breaks elsewhere).

I have done some eveninfs testing, taking apart and putting together my 
own initramfs. It looks like this is a kernel bug, not userspace - the 
hang happens after initramfs is unpacked and after VFS and quotas are 
installed, and after "msgmni has been set to 627" message but before BSG 
loading message and before io scheduler initialization. And log before 
init is executed from initramfs (and no modprobe is executed either, as 
my wrapper does not run).

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.

Seems like a kernel regression to me.

-- 
Meelis Roos (mroos@linux.ee)

  parent reply	other threads:[~2008-11-21 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 10:15 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   ` Meelis Roos [this message]
2008-11-24 13:31     ` Regression - " Patrick McHardy
2008-11-24 15:05       ` Kay Sievers
2008-11-25 11:12         ` Patrick McHardy

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=Pine.SOC.4.64.0811212351200.16409@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=kaber@trash.net \
    --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®