From: Steven Walter <srwalter@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] in __switch_to with 2.4.0-prerelease
Date: Tue, 2 Jan 2001 20:06:43 -0600 [thread overview]
Message-ID: <20010102200643.A360@hapablap.dyn.dhs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
This oops occurred just a few minutes ago under no particular load.
There were actually two oopsen, but I've included only the first as I've
heard that successive oops really aren't helpful. Nonetheless, if
anyone's interested in seeing it, I have it captured.
These oops were processed by syslog, if that's a problem. Not sure
if its repeatable. This is these are the first and only oops I've had
with -prerelease, otherwise it has been very stable.
The system is 500MHz K6/2, 64MB RAM.
--
-Steven
"Voters decide nothing. Vote counters decide everything."
-Joseph Stalin
[-- Attachment #2: oops --]
[-- Type: text/plain, Size: 743 bytes --]
printing eip:
c01076c9
Oops: 0002
CPU: 0
EIP: 0010:[__switch_to+33/180]
EFLAGS: 00010886
eax: c2e9c260 ebx: 614fa060 ecx: c2cbe2c0 edx: c347a000
esi: c2e9bfff edi: c347a000 ebp: c2e9df1c esp: c347bed4
ds: 0018 es: 0018 ss: 0018
Process panel (pid: 2016, stackpage=c347b000)
Stack: c2e9c000 c2cbe1c0 c2e9c000 c2e9df1c c2e9c260 c0111fd0 c347bf1c c347a000
c2cbe2c0 c347bf30 010b626a 081b99c0 c07d8000 c1164720 c2cbe2c0 00000002
00000000 c0261540 c347bf44 c0111d4a c347bf30 00000000 c0762aa0 c0268734
Call Trace: [schedule+604/908] [schedule_timeout+114/144] [process_timeout+0/72] [do_poll+184/216] [sys_poll+470/724] [system_call+51/64]
Code: 00 0c 08 60 00 00 00 b0 89 ca 08 60 4f 73 08 60 4f 73 08 74
next reply other threads:[~2001-01-03 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 2:06 Steven Walter [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-03 11:50 [OOPS] in __switch_to with 2.4.0-prerelease Manfred
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=20010102200643.A360@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--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