On 09/11/2017 06:45 AM, Petr Mladek wrote:
>> Except for the second printk line: If you boot with rdinit=/bin/hush
>> then the first time you mount -t devtmpfs /dev /dev after boot (with
>> CONFIG_DEVTMPFS_MOUNT already having mounted it), you get the 0 return
>> value but the last printk() doesn't
On (09/11/17 13:45), Petr Mladek wrote:
[..]
> > Except for the second printk line: If you boot with rdinit=/bin/hush
> > then the first time you mount -t devtmpfs /dev /dev after boot (with
> > CONFIG_DEVTMPFS_MOUNT already having mounted it), you get the 0 return
> > value but the last printk() d
On Sun 2017-09-10 18:43:24, Rob Landley wrote:
> On 05/25/2017 01:13 AM, Michael Ellerman wrote:
> > Hi Rob,
> >
> > This is breaking a bunch of my powerpc boxes, for the exact same
> > reason, they use a config that has DEVTMPFS_MOUNT=y and that trips
> > up the initramfs.
>
> I've continued to
Taking another stab at this old issue from last merge window...
> Rob Landley writes:
>> On 05/23/2017 03:01 AM, Yury Norov wrote:
>>> On Mon, May 22, 2017 at 09:07:54PM -0500, Rob Landley wrote:
Your userspace mounted a tmpfs over /dev when it couldn't mount a second
identical instance
The previous email was rejected by LKML. So resend again.
On Thu, May 25, 2017 at 09:39:32PM +0800, Leo Yan wrote:
> Hi Rob, Yury,
>
> On Mon, May 22, 2017 at 8:05 PM, Yury Norov
> wrote:
>
> > Hi Rob,
> >
> > I found that next-20170522 fails to boot on arm64 machine with the
> > following log:
Hi Rob,
This is breaking a bunch of my powerpc boxes, for the exact same reason,
they use a config that has DEVTMPFS_MOUNT=y and that trips up the
initramfs.
Rob Landley writes:
> On 05/23/2017 03:01 AM, Yury Norov wrote:
>> On Mon, May 22, 2017 at 09:07:54PM -0500, Rob Landley wrote:
>>> Your u
On 05/23/2017 06:08 PM, Yury Norov wrote:
>> It was 2 years ago, but AFAIR I took the Ubuntu image here:
>> http://cdimage.ubuntu.com/ubuntu-base/releases/14.04.1/release/ubuntu-base-14.04.1-core-arm64.tar.gz
Have you applied updates since then? (Maybe they fixed their init script
since 2 years ag
> It was 2 years ago, but AFAIR I took the Ubuntu image here:
> http://cdimage.ubuntu.com/ubuntu-base/releases/14.04.1/release/ubuntu-base-14.04.1-core-arm64.tar.gz
>
> Kernel config is attached. I build the kernel with simple 'make'.
>
> Yury
Sorry, config is here.
config.tar.gz
Description:
On Tue, May 23, 2017 at 12:40:04PM -0500, Rob Landley wrote:
> On 05/23/2017 03:01 AM, Yury Norov wrote:
> > On Mon, May 22, 2017 at 09:07:54PM -0500, Rob Landley wrote:
> >> Your userspace mounted a tmpfs over /dev when it couldn't mount a second
> >> identical instance of devtmpfs over itself. If
On 05/23/2017 03:01 AM, Yury Norov wrote:
> On Mon, May 22, 2017 at 09:07:54PM -0500, Rob Landley wrote:
>> Your userspace mounted a tmpfs over /dev when it couldn't mount a second
>> identical instance of devtmpfs over itself. If you had a static /dev in
>> initramfs but didn't configure _in_ devt
On Mon, May 22, 2017 at 09:07:54PM -0500, Rob Landley wrote:
> On 05/22/2017 07:05 AM, Yury Norov wrote:
> > Hi Rob,
> >
> > I found that next-20170522 fails to boot on arm64 machine with the
> > following log:
>
> I don't know anything about your kernel config (is CONFIG_DEVTMPFS_MOUNT
> enable
On 05/22/2017 07:05 AM, Yury Norov wrote:
> Hi Rob,
>
> I found that next-20170522 fails to boot on arm64 machine with the
> following log:
I don't know anything about your kernel config (is CONFIG_DEVTMPFS_MOUNT
enabled or disabled?) or what userspace you're booting with, but it
seems I can gue
Hi Rob,
I found that next-20170522 fails to boot on arm64 machine with the
following log:
[...]
[4.179509] Freeing unused kernel memory: 1088K
Loading, please wait...
mount: mounting udev on /dev failed: Device or resource busy
W: devtmpfs not available, falling back to tmpfs for /dev
Couldn't ge
13 matches
Mail list logo