From: Andrew Morton <akpm@osdl.org>
To: Marco Perosa <marco.perosa@poste.it>
Cc: linux-kernel@vger.kernel.org, Neil Horman <nhorman@redhat.com>
Subject: Re: 2.6.13-mm1 - MAKEDEV - /proc/devices
Date: Thu, 1 Sep 2005 15:22:37 -0700 [thread overview]
Message-ID: <20050901152237.23f62e71.akpm@osdl.org> (raw)
In-Reply-To: <20050901204555.10b32a42.marco.perosa@poste.it>
Marco Perosa <marco.perosa@poste.it> wrote:
>
> Hi there,
> I've just tried the 2.6.13-mm1 kernel,
Thanks for doing that.
> and at the new boot i've noticed a strange stop in the init sequence.
> Not a freeze, the system will shutdown with ctrl+alt+canc (even though it give a timeout on /dev/initctl).
> After some tests i've figured out that the problem is in the init script /etc/init.d/makedev.
> In fact if i run a "MAKEDEV something" in the /dev directory, i obtain the same problem.
> When this happens, /proc/devices becomes also inacessible, and it's impossible to exec any other program that requires a new shell.
> ps shows them ('MAKEDEV something' and 'cat /proc/devices') as D+.
>
> It all works fine removing the makedev script from the init sequence, i use udev so it's not a problem at all.
> Anyway, it should be good to figure out where's the problem, so, in the hoping that it will be useful, I enclose the config of my kernel and the kernel trace (the process is #2786).
>
This:
Sep 1 20:14:30 localhost kernel: MAKEDEV D F56A0000 0 2786 2758 (NOTLB)
Sep 1 20:14:30 localhost kernel: f5553ea8 f54f8c50 c0671a20 f56a0000 c18dfa80 00000000 f5553ea4 c014cc2e
Sep 1 20:14:30 localhost kernel: c18df080 f56a0000 0000006b 0003d741 62301160 00000078 f54f8c50 f54f8d78
Sep 1 20:14:30 localhost kernel: f5552000 c0566020 00000246 f5553ee4 c04dc9d4 c0566028 f54f8c50 00000001
Sep 1 20:14:30 localhost kernel: Call Trace:
Sep 1 20:14:30 localhost kernel: [__down+132/320] __down+0x84/0x140
Sep 1 20:14:30 localhost kernel: [__sched_text_start+10/16] __down_failed+0xa/0x10
Sep 1 20:14:30 localhost kernel: [.text.lock.char_dev+11/121] .text.lock.char_dev+0xb/0x79
Sep 1 20:14:30 localhost kernel: [devinfo_start+103/176] devinfo_start+0x67/0xb0
Sep 1 20:14:30 localhost kernel: [traverse+112/432] traverse+0x70/0x1b0
Sep 1 20:14:30 localhost kernel: [seq_lseek+168/288] seq_lseek+0xa8/0x120
Sep 1 20:14:30 localhost kernel: [vfs_llseek+74/80] vfs_llseek+0x4a/0x50
Sep 1 20:14:30 localhost kernel: [sys_llseek+83/176] sys_llseek+0x53/0xb0
Sep 1 20:14:30 localhost kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Sep 1 20:14:30 localhost kernel: ---------------------------
Sep 1 20:14:30 localhost kernel: | preempt count: 00000002 ]
Sep 1 20:14:30 localhost kernel: | 2 level deep critical section nesting:
Sep 1 20:14:30 localhost kernel: ----------------------------------------
I'd assume that convert-proc-devices-to-use-seq_file-interface.patch got
confused and failed to release chrdevs_lock. That
(info->cur_record >= info->num_records)
in devinfo_stop() looks fishy.
Over to you, Neil...
prev parent reply other threads:[~2005-09-01 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 18:45 Marco Perosa
2005-09-01 22:22 ` Andrew Morton [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=20050901152237.23f62e71.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.perosa@poste.it \
--cc=nhorman@redhat.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
all inboxes | Powered by JetHome®