[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510812060816h4401c78bj6d656d0d5721024@mail.gmail.com>
Date: Sat, 6 Dec 2008 17:16:06 +0100
From: "Kay Sievers" <kay.sievers@...y.org>
To: "Evgeniy Polyakov" <zbr@...emap.net>
Cc: "Alan Cox" <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Runaway loop with the current git.
On Sat, Dec 6, 2008 at 17:09, Evgeniy Polyakov <zbr@...emap.net> wrote:
> On Sat, Dec 06, 2008 at 03:10:33AM +0100, Kay Sievers (kay.sievers@...y.org) wrote:
>> Can you add something like:
>> +++ b/kernel/kmod.c
>> @@ -108,6 +108,7 @@ int request_module(const char *fmt, ...)
>> return -ENOMEM;
>> }
>>
>> + printk("XXX call modprobe %s %s[%u]\n", module_name,
>> current->comm, task_pid_nr(current));
>>
>> It may show which process is looking for /dev/console and causes
>> modprobe to run, and maybe we get an idea what's going on. It may at
>> least show if it's a /dev/console problem.
>
> Its a modprobe with different pids tries to load char-major-5 and
> char-major-5-1 in the infinite loop.
So the loop is probably a modprobe itself that tries to access
/dev/console. Is there a different argument for the very first
modprobe which is called? Which may be the one that triggers the loop.
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists