From: Brian Gerst <bgerst@didntduck.org>
To: Martin Rode <Martin.Rode@programmfabrik.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG in sched.c, Kernel 2.4.1?
Date: Tue, 13 Feb 2001 09:30:09 -0500 [thread overview]
Message-ID: <3A8944F1.93C252EB@didntduck.org> (raw)
In-Reply-To: <3A8942FA.484BE2FC@programmfabrik.de>
Martin Rode wrote:
>
> 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:
>
> st0: Block limits 1 - 16777215 bytes.
> Scheduling an interrupt
> kernel BUG at sched.c:714!
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c0113781>]
> EFLAGS: 00010282
> eax: 0000001b ebx 00000000 ecx df4f6000 edx 00000001
> esi: 001cffe3 edi db5eede0 ebp dc0e9f40 esp dc0e9ef0
> ds 0018 es 0018 ss 0018
> process o3flow (pid 13180 stackpage dc0e9000)
> stack: c01f26f3 c01f2856 000002ca db5eed80 dc0e8000 db5eede0 dc0e9f18
> dc0e8000 000033ba 00000000 00000000 000000e7 0000001c 0000001c
> fffffff3 dc0e8000 00000800 00000000 dc0e8000 dc0e9f68 c0139c44
> d488bf80 00000000
>
> call trace: [<cc0139c44>] [<c0139d1c>] [<c0130af6>] [<c0108e93>]
>
> code: 0f 0b 8d 65 bc 5b 5e 5f 89 ec 5d c3 8d 76 00 55 89 e5 83 ec
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
Run this oops message through ksymoops please. It will make debugging
it alot easier.
--
Brian Gerst
next prev parent reply other threads:[~2001-02-13 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 14:21 BUG in sched.c, Kernel 2.4.1? Martin Rode
2001-02-13 14:30 ` Brian Gerst [this message]
2001-02-13 15:24 ` Martin Rode
2001-02-13 15:49 ` Manfred Spraul
2001-02-13 18:59 ` Martin Rode
[not found] ` <3A8956E9.402D0136@didntduck.org>
2001-02-13 17:19 ` Martin Rode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A8944F1.93C252EB@didntduck.org \
--to=bgerst@didntduck.org \
--cc=Martin.Rode@programmfabrik.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox