udev 146-5 and ppc64 kernel

[Stephane Louise-2]

Hi,

My quad-G5 is not updatable anymore (on Debian-testing) because udev
fails to install.

Here is the message :

marie:/home/luigi# LANG=C apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
   udev
The following packages will be upgraded:
   udev
1 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
36 not fully installed or removed.
Need to get 0B/459kB of archives.
After this operation, 500kB of additional disk space will be used.
Do you want to continue [Y/n]?
Preconfiguring packages ...
(Reading database ... 229052 files and directories currently installed.)
Preparing to replace udev 0.141-2 (using .../udev_146-5_powerpc.deb) ...
Since release 146, udev requires support for the following features in
the running kernel:

- inotify(2)       (CONFIG_INOTIFY_USER)
- signalfd(2)      (CONFIG_SIGNALFD)

Please upgrade your kernel before or while upgrading udev.

dpkg: error processing /var/cache/apt/archives/udev_146-5_powerpc.deb
(--unpack):
  subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
  /var/cache/apt/archives/udev_146-5_powerpc.deb

Nonetheless both inotify and signalfd seems to be activated in the
running kernel:

marie:/home/luigi# grep -i inotify /boot/config-2.6.30-2-powerpc64
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
marie:/home/luigi# grep -i signalfd /boot/config-2.6.30-2-powerpc64
CONFIG_SIGNALFD=y


and of course:

marie:/home/luigi# uname -a
Linux marie 2.6.30-2-powerpc64 #1 SMP Sun Oct 4 09:29:28 UTC 2009 ppc64
GNU/Linux

Moreover it worth noting that even /proc shows that at least inotify
seems to be activated:

marie:/home/luigi# ls -ld /proc/sys/fs/inotify
dr-xr-xr-x 0 root root 0 oct 19 10:23 /proc/sys/fs/inotify
marie:/home/luigi# ls -l /proc/sys/fs/inotify
total 0
-rw-r--r-- 1 root root 0 oct 21 21:13 max_queued_events
-rw-r--r-- 1 root root 0 oct 21 21:13 max_user_instances
-rw-r--r-- 1 root root 0 oct 21 21:13 max_user_watches

I don't know how to check for signalfd.

Another Debian user may have been hit by this (but no follow up that I
am aware of):

http://forums.debian.net/viewtopic.php?f=5&t=46128&start=0

So I guess I am not the only one but the bug doesn't seems to be
reported (yet):
http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=src&data=udev&pend-exc=fixed&pend-exc=done

Any idea that I may be missing before filling a bug report?

mata ne
--
Luigi


--
To UNSUBSCRIBE, email to debian-powerpc-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Julien BLACHE]

Stephane Louise <luigi+online@...> wrote:

Hi,

> marie:/home/luigi# grep -i inotify /boot/config-2.6.30-2-powerpc64
> CONFIG_INOTIFY=y
> CONFIG_INOTIFY_USER=y
> marie:/home/luigi# grep -i signalfd /boot/config-2.6.30-2-powerpc64
> CONFIG_SIGNALFD=y

udev's preinst checks for those features by looking for
sys_inotify_init and sys_signalfd in /proc/kallsyms.

Look at the preinst script and check your system; you should find
pretty quickly what's wrong with your system/config or udev.

JB.

--
 Julien BLACHE - Debian & GNU/Linux Developer - <jblache@...>
 
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169


--
To UNSUBSCRIBE, email to debian-powerpc-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Paul Mackerras]

Julien BLACHE writes:

> Stephane Louise <luigi+online@...> wrote:
>
> Hi,
>
> > marie:/home/luigi# grep -i inotify /boot/config-2.6.30-2-powerpc64
> > CONFIG_INOTIFY=y
> > CONFIG_INOTIFY_USER=y
> > marie:/home/luigi# grep -i signalfd /boot/config-2.6.30-2-powerpc64
> > CONFIG_SIGNALFD=y
>
> udev's preinst checks for those features by looking for
> sys_inotify_init and sys_signalfd in /proc/kallsyms.
>
> Look at the preinst script and check your system; you should find
> pretty quickly what's wrong with your system/config or udev.

The symbols in /proc/kallsyms are .sys_inotify_init and .sys_signalfd,
not sys_inotify_init and sys_signalfd, so the preinst script thinks
they're not there.  I kludged around it by doing "sudo touch
/etc/udev/kernel-upgrade", but a better way would be to fix the
regexps in the preinst script.

The "." at the start of the symbol names is an ABI thing; ".foo"
refers to the start of the text for function foo, "foo" refers to the
procedure descriptor for foo.

Paul.


--
To UNSUBSCRIBE, email to debian-powerpc-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Julien BLACHE]

Paul Mackerras <paulus@...> wrote:

Hi,

>> udev's preinst checks for those features by looking for
>> sys_inotify_init and sys_signalfd in /proc/kallsyms.

> The symbols in /proc/kallsyms are .sys_inotify_init and .sys_signalfd,
> not sys_inotify_init and sys_signalfd, so the preinst script thinks
> they're not there.  I kludged around it by doing "sudo touch

That's what I had in mind, thanks for the confirmation. Too bad my PB
G4 is kind of dead (of old age) now :(

JB.

--
 Julien BLACHE <jblache@...>  |  Debian, because code matters more
 Debian & GNU/Linux Developer        |       <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169


--
To UNSUBSCRIBE, email to debian-powerpc-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...