On Wed, Jan 10, 2007 at 09:14:21AM +0100, Jarek Dylag wrote:
> Hi
>
> >> There is nothing new in kernel log after changes, oops in attachement.
> >
> >very strange ... you constantly omit the kernel
> >lines from the oops traces, could you verify that
> >you actually booted the modified kernel?
>
> I sended all information i can find in server logs (from netconsole).
> Yes, i'm sure it is modified kernel.
>
> >could you also upload the vmlinux (not vmlinuz)
> >file somewhere where I could access it?
>
> Vmlinux file, oops and my config file are available at:
>
> http://195.149.230.90/vmlinux
> http://195.149.230.90/vmlinux.bz2
> http://195.149.230.90/.config
> http://195.149.230.90/oops.txt
okay, I think we need some more information, especially
the following would be of interest:
# gcc --version
# as --version
and the result of this inisde your kernel build tree:
(make sure that config and tools are the same as for
the oops you reported!!)
# make fs/proc/array.s
simply provide the resulting fs/proc/array.s
TIA,
Herbert
PS: does the issue go away if you do not compile with
the CONFIG_CC_OPTIMIZE_FOR_SIZE=y (which probably doesn't
make any sense on you arch, as it just slows down execution)
> Jarek Dylag
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Sat Jan 20 20:05:02 2007