Gregor Suhr writes:
> Richard Gooch wrote:
>
> >Gregor Suhr writes:
> >
> >>
> >>Trace; c0105000 <_stext+0/0>
> >>Trace; c010525e <init+e/140>
> >>Trace; c0105000 <_stext+0/0>
> >>Trace; c0105726 <kernel_thread+26/30>
> >>Trace; c0105250 <init+0/140>
> >>
> >
> >No mention of devfs in the traceback. It doesn't look like a devfs
> >problem.
> >
> OK
However, on seeing your other message, I take that back. See my other
reply.
> >>mtab" and "/etc/devfs: devfs_register(mp3): could not append to parent,
> >>err: -17
> >>lvmtab.d" succesdevfs: devfs_register(appdata): could not append to
> >>parent, err: -17
> >>sfully created
> >>devfs: devfs_register(oracle): could not append to parent, err: -17
> >>
> >
> >These devfs-related messages are due to configuration problems
> >(i.e. boot scripts untarring a pile of crap into devfs), but they are
> >unlikely to be the cause of your Oops.
> >
> The linuxrc script of the initrd include:
>
> #!/bin/sh
> /bin/mount /proc
> /sbin/vgscan
> /sbin/vgchange -a y
> /bin/umount /proc
>
> But it is using a mountd devfs without runnig devfsd.
> I used this inird (without any change or rebuild) since 2.4 without any
> problem, so something in the kernel must been changed.
Yes, something in the kernel has changed. New devfs core, which
doesn't work with broken drivers, and generates warning messages for
bad configurations. But those are warnings, and broken configurations
should continue to work (in 2.4, in 2.5 they won't). The problem you
are having is unrelated to a broken configuration. See other message.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:25 EST