public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Riffard <laurent.riffard@free.fr>
To: ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com
Cc: Andrew Morton <akpm@osdl.org>,
	andrew.j.wade@gmail.com, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>
Subject: Re: Kubuntu's udev broken with 2.6.18-rc2-mm1
Date: Sun, 30 Jul 2006 16:01:43 +0200	[thread overview]
Message-ID: <44CCBBC7.3070801@free.fr> (raw)
In-Reply-To: <200607281033.06111.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com>

Le 28.07.2006 16:33, Andrew James Wade a écrit :
> On Thursday 27 July 2006 16:12, Greg KH wrote:
>> On Thu, Jul 27, 2006 at 12:56:55PM -0700, Andrew Morton wrote:
>>> On Fri, 28 Jul 2006 15:46:08 -0400
>>> Andrew James Wade <andrew.j.wade@gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> Some change between -rc1-mm2 and -rc2-mm1 broke Kubuntu's udev
>>>> (079-0ubuntu34). In particular /dev/mem went missing, and /dev/null had
>>>> bogus permissions (crw-------). I've kludged around the problem by
>>>> populating /lib/udev/devices from a good /dev, but I'm assuming the
>>>> breakage was unintentional.
>>>>
>>> /dev/null damage is due to a combination of vdso-hash-style-fix.patch and
>>> doing the kernel build as root (don't do that).
>>>
>>> I don't know what happened to /dev/mem.
>> Me either.  Look in /sys/class/mem/  Is it full of symlinks or real
>> directories?
> 
> Symlinks.
> 
>> If symlinks, your version of udev should be able to handle it properly,
>> but might have a bug somehow.
>>
>> Try running udevmonitor and echo a "1" to /sys/class/mem/mem/uevent and
>> see if udev creates the device properly or not.
> 
> udevmonitor prints the received event from the kernel [UEVENT]
> and the event which udev sends out after rule processing [UDEV]
> 
> UEVENT[1154093169.330045] add@/devices/mem
> UDEV  [1154093169.331914] add@/devices/mem
> 
> The device node was not created.
> 
> udev.log for 2.6.18-rc1-mm2 (which does work) has these lines:
> 
> UEVENT[1154105360.092631] add@/class/mem/mem
> ACTION=add
> DEVPATH=/class/mem/mem
> SUBSYSTEM=mem
> SEQNUM=589
> MAJOR=1
> MINOR=1
> 
> ...
> 
> UDEV  [1154105363.575086] add@/class/mem/mem
> UDEV_LOG=3
> ACTION=add
> DEVPATH=/class/mem/mem
> SUBSYSTEM=mem
> SEQNUM=589
> MAJOR=1
> MINOR=1
> UDEVD_EVENT=1
> DEVNAME=/dev/mem
> 
> The Changelog for udev v081 has:
> "prepare moving of /sys/class devices to /sys/devices"
> Is this related? 
> 
> Thanks,
> Andrew Wade

gregkh-driver-mem-devices.patch seems to be the culprit.

With this patch, /sys/class/mem/ looks like this:

/sys/class/mem/
|-- full -> ../../devices/full
|-- kmem -> ../../devices/kmem
|-- kmsg -> ../../devices/kmsg
|-- mem -> ../../devices/mem
|-- null -> ../../devices/null
|-- port -> ../../devices/port
|-- random -> ../../devices/random
|-- urandom -> ../../devices/urandom
`-- zero -> ../../devices/zero

9 directories, 0 files

And /sys/class/mem/*/ look like this:

/sys/class/mem/full/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/kmem/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/kmsg/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/mem/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/null/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/port/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/random/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/urandom/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent
/sys/class/mem/zero/
|-- dev
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../class/mem
`-- uevent

18 directories, 36 files

In this situation, udev (version 096 here) is unable to create these
device files (/dev/full, /dev/kmem, /dev/kmsg, etc.). /dev/null does
exist (with wrong permissions) because it has been created by the
initrd script.

In order to get back the device files, I have to run the following
command:
# for f in /sys/class/mem/*/uevent; do echo 1 > $f; done

After gregkh-driver-mem-devices.patch been reverted, all is working
fine and /sys/class/mem/ looks like this:

/sys/class/mem/
|-- full
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- kmem
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- kmsg
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- mem
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- null
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- port
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- random
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
|-- urandom
|   |-- dev
|   |-- subsystem -> ../../../class/mem
|   `-- uevent
`-- zero
    |-- dev
    |-- subsystem -> ../../../class/mem
    `-- uevent

18 directories, 18 files

~~
laurent

  reply	other threads:[~2006-07-30 14:01 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  8:56 2.6.18-rc2-mm1 Andrew Morton
2006-07-27 10:27 ` [PATCH] Require mmap handler for a.out executables (was Re: 2.6.18-rc2-mm1) Eugene Teo
2006-07-27 11:40 ` [patch -mm] s390: remove s390 touch_nmi_watchdog() define Heiko Carstens
2006-07-27 12:26 ` 2.6.18-rc2-mm1 Frederik Deweerdt
2006-07-27 12:39   ` [patch] fix "efi_init_e820_map undefined" warning Frederik Deweerdt
2006-07-27 13:12 ` Should cpuset ABBA deadlock fix be in 2.6.18-rc2-mmx? Paul Jackson
2006-07-27 18:22   ` Andrew Morton
2006-07-27 19:32     ` Paul Jackson
2006-07-27 13:32 ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-27 18:59   ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-29 12:15     ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-29 12:17       ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-28  8:17   ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-28  8:34     ` 2.6.18-rc2-mm1 Andrew Morton
2006-07-28 18:49       ` 2.6.18-rc2-mm1 Matt Helsley
2006-07-28 19:53         ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-28 20:39           ` 2.6.18-rc2-mm1 Matt Helsley
2006-07-28 21:34             ` 2.6.18-rc2-mm1 Andrew Morton
2006-07-29  2:04             ` 2.6.18-rc2-mm1 Valdis.Kletnieks
2006-07-29 22:34             ` 2.6.18-rc2-mm1 Shailabh Nagar
2006-07-29 23:38               ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-28 17:57     ` 2.6.18-rc2-mm1 Matt Helsley
2006-07-27 14:04 ` 2.6.18-rc2-mm1 Andy Whitcroft
2006-07-27 14:48   ` 2.6.18-rc2-mm1 Andy Whitcroft
2006-07-27 15:37 ` [PATCH] highmem: fixed ip27-memory.c build error Yoichi Yuasa
2006-07-27 18:16 ` [-mm patch] arch/i386/pci/mmconfig.c: fixes Adrian Bunk
2006-07-28  8:09 ` 2.6.18-rc2-mm1 Reuben Farrelly
2006-07-28  8:35 ` [mm-patch] bluetooth: use GFP_ATOMIC in *_sock_create's sk_alloc Frederik Deweerdt
2006-07-28  9:00   ` Marcel Holtmann
2006-07-28 12:36     ` Frederik Deweerdt
2006-07-28  9:17   ` Masatake YAMATO
2006-07-28 12:32     ` Frederik Deweerdt
2006-07-28 13:12       ` Masatake YAMATO
2006-07-28 16:15         ` [01/04 mm-patch, rfc] Add lightweight rwlock (was Re: [mm-patch] bluetooth: use GFP_ATOMIC in *_sock_create's sk_alloc) Frederik Deweerdt
2006-07-28 16:23           ` [02/04 " Frederik Deweerdt
2006-07-28 16:28             ` [03/04 mm-patch, rfc] Add lightweight rwlock to net/dccp/ccid.c " Frederik Deweerdt
2006-07-28 16:33               ` [04/04 mm-patch, rfc] Add lightweight rwlock to net/bluetooth/af_bluetooth.c " Frederik Deweerdt
2006-07-31  7:06           ` [01/04 mm-patch, rfc] Add lightweight rwlock Masatake YAMATO
2006-08-01  9:06             ` Frederik Deweerdt
2006-07-28  8:56 ` 2.6.18-rc2-mm1 Michal Piotrowski
2006-07-28  9:23   ` 2.6.18-rc2-mm1 Andrew Morton
2006-07-28 15:53 ` [PATCH] 2.6.18-rc2-mm1 i386 add_memory_region undefined Valdis.Kletnieks
2006-07-28 18:20 ` 2.6.18-rc2-mm1 - hard lockups on Dell C840 Valdis.Kletnieks
2006-07-28 18:44 ` 2.6.18-rc2-mm1 timer int 0 doesn't work Paul Fulghum
2006-07-28 21:48   ` Andrew Morton
2006-07-28 22:10     ` Paul Fulghum
2006-07-28 23:38     ` Andi Kleen
2006-07-29  0:15       ` Paul Fulghum
2006-07-29  1:16         ` Paul Fulghum
2006-07-29  1:24           ` Andrew Morton
2006-07-29  2:37             ` Paul Fulghum
2006-07-29  2:58             ` Eric W. Biederman
2006-07-29  4:03             ` Ingo Molnar
2006-07-30 23:00               ` Steven Rostedt
2006-07-29  2:36           ` Andi Kleen
2006-07-29 15:33       ` Paul Fulghum
2006-07-29 19:50         ` Eric W. Biederman
2006-07-29 22:05           ` Paul Fulghum
2006-07-31  5:31             ` Andi Kleen
2006-07-31 13:32               ` Paul Fulghum
2006-07-28 19:46 ` Kubuntu's udev broken with 2.6.18-rc2-mm1 Andrew James Wade
2006-07-27 19:56   ` Andrew Morton
2006-07-27 20:12     ` Greg KH
2006-07-28 14:33       ` Andrew James Wade
2006-07-30 14:01         ` Laurent Riffard [this message]
2006-07-31  0:03           ` Greg KH
2006-07-31  2:27             ` Andrew James Wade
2006-07-31  3:37               ` Greg KH
2006-07-31  4:22                 ` Andrew Morton
2006-07-31  4:35                   ` Greg KH
2006-07-31  4:50                     ` Andrew Morton
2006-07-31  5:15                       ` Greg KH
2006-07-31  6:00                         ` Andrew Morton
2006-07-31  7:54                           ` bert hubert
2006-07-31  8:30                             ` Jesper Juhl
2006-07-31 11:14                           ` Alan Cox
2006-07-31  8:10                 ` Laurent Riffard
2006-08-01  3:01                 ` Andrew James Wade
2006-07-27 21:28     ` Valdis.Kletnieks
2006-07-29 17:48 ` [-mm patch] security/selinux/hooks.c: make 4 functions static Adrian Bunk
2006-07-30  0:37   ` James Morris
2006-07-29 17:58 ` swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1] Jiri Slaby
2006-07-29 18:59   ` Rafael J. Wysocki
2006-07-29 23:06     ` Jiri Slaby
2006-07-29 23:10       ` Rafael J. Wysocki
2006-07-29 23:59         ` Jiri Slaby
2006-07-30  0:03         ` Jiri Slaby
2006-07-29 23:22       ` Pavel Machek
2006-07-29 23:58         ` Jiri Slaby
2006-07-30  0:06           ` Pavel Machek
2006-07-30  7:31             ` Rafael J. Wysocki
2006-07-30  8:08               ` Jiri Slaby
2006-07-30  9:28                 ` Rafael J. Wysocki
2006-07-30 10:54                   ` Jiri Slaby
2006-07-30 11:08                     ` Pavel Machek
2006-07-30 11:34                     ` Rafael J. Wysocki
2006-07-31 13:59                       ` [Alsa-devel] " Takashi Iwai
2006-07-31 14:03                         ` Pavel Machek
2006-07-30 11:36           ` James Courtier-Dutton
2006-07-30 11:35 ` 2.6.18-rc2-mm1 fails to reboot properly on Dell Latitude CPiA Christian Trefzer
2006-07-31  4:42 ` 2.6.18-rc2-mm1 Reuben Farrelly
2006-07-31  4:57   ` 2.6.18-rc2-mm1 Andrew Morton
2006-07-31  5:25     ` 2.6.18-rc2-mm1 Andi Kleen
2006-08-03 15:59 ` [2.6 patch] DVB_CORE must select I2C Adrian Bunk
2006-08-03 16:10   ` [v4l-dvb-maintainer] " Manu Abraham
2006-08-03 16:30   ` Trent Piepho
2006-08-03 19:13     ` Mauro Carvalho Chehab

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=44CCBBC7.3070801@free.fr \
    --to=laurent.riffard@free.fr \
    --cc=ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com \
    --cc=akpm@osdl.org \
    --cc=andrew.j.wade@gmail.com \
    --cc=greg@kroah.com \
    --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