LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Folkert van Heusden" <folkert@vanheusden.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.26] kobject_add_internal failed for 2:0 with -EEXIST / unable to handle kernel NULL pointer dereference in sysfs_create_link
Date: Wed, 29 Oct 2008 15:49:05 +0100	[thread overview]
Message-ID: <ac3eb2510810290749o2dd062b5m7b966d2d25b69714@mail.gmail.com> (raw)
In-Reply-To: <20081029132704.GS11214@vanheusden.com>

On Wed, Oct 29, 2008 at 14:27, Folkert van Heusden
<folkert@vanheusden.com> wrote:
>> >> > While running my http://vanheusden.com/pyk/ script (which randomly
>> >> > inserts and removes modules) I triggered the folllowing oops in a 2.6.26
>> >> > kernel on an IBM xSeries 260. This oops (in fact no oops at all) did not
>> >> > get triggered in a 2.6.18 kernel on that system.
>> >> >
>> >> > [   42.507375] FDC 0 is a National Semiconductor PC87306
>> >> > [   42.509057] kobject_add_internal failed for 2:0 with -EEXIST, don't try to register things with the same name in the same directory.
>> >> > [   42.509291] Pid: 5301, comm: modprobe Not tainted 2.6.26-1-amd64 #1
>> >> > [   42.509431]
>> >> > [   42.509433] Call Trace:
>> >> > [   42.509685]  [<ffffffff8031b031>] kobject_add_internal+0x13f/0x17e
> ...
>> >> > [   42.511519]  [<ffffffff8027d23b>] bdi_register+0x57/0xb4
>> >>
>> >> Looks like bdi sees two devices with the same devnum, or didn't
>> >> cleanup an old entry. What does: ls -l "/sys/class/bdi/" print?
>> >
>> > The following:
>> > folkert@debiantesthw:~$ ls -l /sys/class/bdi/
>> > drwxr-xr-x 3 root root 0 2008-10-28 18:32 2:0
>> > drwxr-xr-x 3 root root 0 2008-10-28 18:32 2:1
>>
>> Oh, you are running the old sysfs layout without symlinks. Care to
>> tell where the "device" link in these directories points to?
>
> None exist:
> folkert@debiantesthw:~$ ls -la /sys/class/bdi/*/device
> ls: cannot access /sys/class/bdi/*/device: No such file or directory

Ah, sorry. Seems the bdi stuff never got to pass the usual parent
device with the device registration, to let the bdi device show up at
the right place in the device tree.

Let's see what current devices on your box have the major 2:
  find /sys -name dev | xargs grep '^2:'

Thanks,
Kay

  reply	other threads:[~2008-10-29 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 15:11 Folkert van Heusden
2008-10-28 23:07 ` Kay Sievers
2008-10-29  9:40   ` Folkert van Heusden
2008-10-29 10:01     ` Bryan Wu
2008-10-29 12:28       ` Kay Sievers
2008-10-29 12:25     ` Kay Sievers
2008-10-29 13:27       ` Folkert van Heusden
2008-10-29 14:49         ` Kay Sievers [this message]
2008-10-29 15:25           ` Folkert van Heusden
2008-10-29 21:51             ` Kay Sievers
2008-10-30 10:55               ` Folkert van Heusden
2008-10-30 23:06                 ` Kay Sievers
2008-10-30 23:23                   ` Kay Sievers
2008-10-31  1:13                     ` Kay Sievers
2008-10-31  9:28                     ` Peter Zijlstra
2008-11-03 11:53                       ` Kay Sievers
2008-11-03 11:55                         ` Peter Zijlstra

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=ac3eb2510810290749o2dd062b5m7b966d2d25b69714@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [2.6.26] kobject_add_internal failed for 2:0 with -EEXIST / unable to handle kernel NULL pointer dereference in sysfs_create_link' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).