From: Pawel Sikora <pluto@agmk.net>
To: linux-kernel@vger.kernel.org
Subject: [2.6.11.12] oops in scheduler_tick
Date: Mon, 6 Jun 2005 08:05:38 +0200 [thread overview]
Message-ID: <200506060805.38799.pluto@agmk.net> (raw)
Oops: 0002 [#1]
Modules linked in:
CPU: 0
EIP: 0060:[<c0112e1f>] Not tainted VLI
EFLAGS: 00010013 (2.6.11.11-2.1)
EIP is at scheduler_tick+0x3a/0x233
eax: 00000000 ebx: d0063500 ecx: 00000000 edx: 000f41fb
esi: 00000000 edi: 00000000 ebp: d0137eb0 esp: d0137e9c
ds: 007b es: 007b ss: 0068
Process (pid: 24947, threadinfo=d0136000 task=d0063500)
Stack:
d0137f14 d0137f14 d0137f14 00000000 00000000 d0137ec4
c0106ebf 00000000 c02a7000 00000000 d0137eec c01292ed
00000000 00000000 d0137f14 d0137f14 00000000 c031ea80
00000000 c02a7000 d0137f04 c01293a7 d0137f14 d0063500
Call Trace:
[<c0103fdd>] show_stack+0x78/0x83
[<c01040f3>] show_registers+0xf1/0x15d
[<c0104290>] die+0xac/0x120
[<c01113aa>] do_page_fault+0x44a/0x5d9
[<c0103c1f>] error_code+0x4f/0x60
[<c0106ebf>] timer_interrupt+0x47/0xeb
[<c01292ed>] handle_IRQ_event+0x26/0x56
[<c01293a7>] __do_IRQ+0x8a/0xc7
[<c0104fec>] do_IRQ+0x1c/0x28
[<c0103b2a>] common_interrupt+0x1a/0x20
[<c0117d80>] do_wait+0x75/0x364
[<c01180fb>] sys_wait4+0x28/0x2d
[<c0118113>] sys_waitpid+0x13/0x15
[<c0102ac7>] syscall_call+0x7/0xb
Code:
8b 18 e8 02 85 ff ff a3 34 27 36 c0 89 15 38 27 36 c0 3b 1d 40
27 36 c0 0f 84 fe 01 00 00 a1 48 27 36 c0 39 43 28 74 0d 8b 43
04 <0f> ba 68 08 03 e9 e7 01 00 00 8b 43 18 89 45 f0 83 f8 63 7f 43
^^^^^^^^^^^^^
btsl $0x3,0x8(%eax)
^^^^^^^^^^^^
set_bit(...) inlined form of set_tsk_need_resched(p)
<0>Kernel panic - not syncing: Fatal exception in interrupt
--
The only thing necessary for the triumph of evil
is for good men to do nothing.
- Edmund Burke
next reply other threads:[~2005-06-06 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 6:05 Pawel Sikora [this message]
2005-06-06 12:40 ` [2.6.11.12] oops in scheduler_tick Mikulas Patocka
2005-06-06 19:58 ` [2.6.11.11] " Pawel Sikora
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=200506060805.38799.pluto@agmk.net \
--to=pluto@agmk.net \
--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