I think this happens when I try to mount a LVM block device which has
not yet been initialised with vgchange.
I remember seeing this bug in older kernels too, and if it is the same
issue it was 100% reproducible.
This is the linuxppc_2_4_devel tree rsynced yesterday from mvista.com.
I know the Sys
On Sun, Jun 30, Marco d'Itri wrote:
> >>NIP; c0110e7c<=
>
> >>GPR1; dcae9d00 <_end+1c857584/20db4884>
> >>GPR2; dcae8000 <_end+1c855884/20db4884>
> >>GPR3; ddf66bc0 <_end+1dcd/20db4884>
> >>GPR4; dcae9d28 <_end+1c8575ac/20db4884>
> >>GPR5; dcae9d28 <_end+1c8575ac/20db4884>
> >>GPR6; d
On Jul 02, Olaf Hering <[EMAIL PROTECTED]> wrote:
>Can you paste your config, I see the same. All cdrom drivers are
>modules, do you have a similar config?
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_EXPERIMENTAL=y
CONFIG_ADVANCED_OPTIONS=y
CONFIG_MODULES=y
CONFIG_MODVERSIO
3 matches
Mail list logo