Am 12.09.2013 20:00, schrieb Salvo Tomaselli:
> partitions, also because there is no /dev/sda.
> Kernel: Linux 3.11.0a (SMP w/4 CPU cores)
Can you attach the output of
# grep DEVTMPFS "/boot/config-$(uname -r)"
and
# grep devtmpfs /proc/filesystems
thanks
signature.asc
Description: OpenPGP d
Salvo,
I see you are using Linux 3.11.0a; is that an experimental kernel?
I have just dist-upgraded to the latest unstable and I do *not* see this
failure. I am using linux-image-3.10-3-amd64 (3.10.11-1). Everything
Maintainer, please consider downgrading the severity of this report as
apt-l
In data venerdì 13 settembre 2013 07.08.19, hai scritto:
> I see you are using Linux 3.11.0a; is that an experimental kernel?
Nope it's stable. -rc* kernels are experimental.
kernel.org calls it: "Latest Stable Kernel"
Anyway I've tried with 3.10.10 and even 3.9 and I had the same exact issue.
-
> # grep DEVTMPFS "/boot/config-$(uname -r)"
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
> # grep devtmpfs /proc/filesystems
nodev devtmpfs
And tmpfs fs work perfectly with the older version of udev.
--
Salvo Tomaselli
http://ltworf.github.io/ltworf/
signature.asc
Description: Th
Am 12.09.2013 20:00, schrieb Salvo Tomaselli:
> Package: udev
> Version: 204-3
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
> after the upgrade of udev, my system won't boot properly.
>
> It will only mount the root partition from /dev/root, but not the other
Am 13.09.2013 18:25, schrieb Salvo Tomaselli:
> # CONFIG_DEVTMPFS_MOUNT is not set
Are you using an initramfs with your custom kernel which mounts the
devtmpfs?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Hi,
thanks for the information so far.
Am 13.09.2013 18:25, schrieb Salvo Tomaselli:
>> Please try to boot with a default Debian kernel and test if that works.
> 3.10-3-amd64 works
>
> # CONFIG_AUTOFS4_FS is not set
Are you booting with systemd or sysvinit?
I now you've been using systemd in th
> Are you using an initramfs with your custom kernel which mounts the
> devtmpfs?
No, or at least, dmesg doesn't mention decompressing it.
--
Salvo Tomaselli
http://ltworf.github.io/ltworf/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
Am 13.09.2013 18:47, schrieb Salvo Tomaselli:
>> Are you using an initramfs with your custom kernel which mounts the
>> devtmpfs?
> No, or at least, dmesg doesn't mention decompressing it.
Ok, then this looks like the same bug as #722580 after all :-)
Recompiling your kernel with CONFIG_DEVTMPFS_M
Am 13.09.2013 19:05, schrieb Michael Biebl:
> Am 13.09.2013 18:47, schrieb Salvo Tomaselli:
>>> Are you using an initramfs with your custom kernel which mounts the
>>> devtmpfs?
>> No, or at least, dmesg doesn't mention decompressing it.
>
> Ok, then this looks like the same bug as #722580 after a
/etc/init.d/udev has a bug which breaks it here:
$dev_mount_options is empty (not set at all) which makes
mount -n -o $dev_mount_options -t tmpfs tmpfs /dev
fail in mount_tmpfs().
I think
dev_mount_options='mode=0755'
if [ "$tmpfs_size" ]; then
dev_mount_options="size=${tmpfs_size},${dev_mo
Hello,
yes it fixes the problem.
Maybe this change can be documented somewhere, for the other people who don't
use prebuilt kernels.
> Did you have the chance to verify that using CONFIG_DEVTMPFS_MOUNT=y
> fixes the problem you're having?
--
Salvo Tomaselli
http://ltworf.github.io/ltworf/
s
12 matches
Mail list logo
