Rik van Riel wrote:
> On Thu, 15 Feb 2001, Martin Rode wrote:
>
> > My last bug report did not seem to attract to much attention.
>
> > For now we have switched back to 2.2.18 which stays up for about
> > a week before it crashes because of the VM too.
>
My last bug report did not seem to attract to much attention. But I'm
back and I have a even longer oops list. Last night our system crashed
(again). (Again) right after arkeia had started the nightly backup. But
this time the kernel oopses went through syslog. Here they are ran
through ksymoo
Manfred Spraul wrote:
> Martin Rode wrote:
> >
> > >
> > > Run this oops message through ksymoops please. It will make debugging
> > > it alot easier.
> > >
> > >
> >
> > Since I did not compile the kernel myself, ksym
Re-ran ksymoops:
; Martin
kernel BUG at sched.c:714!
invalid operand:
CPU: 0
EIP: 0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 001b ebx ecx df4f6000 edx 0001
esi: 001cffe3 edi db5eede0 ebp dc0e9f40 esp dc0e9ef0
stack: c01f26f3 c01f2856
>
> Run this oops message through ksymoops please. It will make debugging
> it alot easier.
>
>
Since I did not compile the kernel myself, ksymoops is not too happy with
what is has to analyse the dump. I tried compile the Mandrake kernel myself
but there seems to be something unmatched.
After upgrading to kernel 2.4.1 my box locked hard after starting the
regular arkeia backup. I had previously problems with MM on kernel
2.2.18 and > 2.2.19pre2. My report a few days ago is still unanswered.
I would be glad if someone would be comment this time.
Here's the typed crash dump
We are seeing problems on our K7 600Mhz, 256MB box. After about one week
uptime we certainly run into
vm_trying_to_free_unused pages.
With > 2.2.19pre2 the hylafax daemon would not even start without
causing a kernel oops. I was not able to capture these oopses, but they
definitely were about
7 matches
Mail list logo
