From: Christoph Rohland <cr@sap.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Oops in 2.4.7 final
Date: 21 Jul 2001 16:37:42 +0200 [thread overview]
Message-ID: <m3k81273gp.fsf@linux.local> (raw)
Hi,
I did my shm stress test the first time since weeks on my 8way/8GB
today. After the usual load of
__alloc_pages: 0-order allocation failed.
It got the following oops:
Unable to handle kernel paging request at virtual address 7061732e
printing eip:
7061732e
*pde = 00000000
Oops: 0000
CPU: 6
EIP: 0010:[<7061732e>]
EFLAGS: 00010246
eax: 7061732e ebx: c0633bc0 ecx: 00000001 edx: c0666840
esi: c0633bc0 edi: 00000008 ebp: f75d7400 esp: f6d29cc0
ds: 0018 es: 0018 ss: 0018
Process screen (pid: 630, stackpage=f6d29000)
Stack: c0131e84 c0666840 00000001 f75d74ac c0633bc0 c01b3880 c0633bc0 00000001
00000008 c060d000 c060d000 f75d7400 c01b3bff f75d7400 00000001 00000000
00000001 00000001 00000008 00000001 f75d7400 00000000 ccd47200 f75d7400
Trace; c0131e84 <bounce_end_io_write+14/c0>
Trace; c01b3880 <__scsi_end_request+a4/164>
Trace; c01b3bff <scsi_io_completion+1d3/3c0>
Trace; c01b8921 <ncr_complete+4f9/510>
Trace; c01c4176 <rw_intr+1f6/204>
Trace; c01b290d <scsi_old_done+3d/5c8>
Trace; c01b2e7c <scsi_old_done+5ac/5c8>
Trace; c01bd567 <sym53c8xx_intr+87/9c>
Trace; c01084e6 <handle_IRQ_event+4e/78>
Trace; c01086d9 <do_IRQ+99/e4>
Trace; c0106dfc <ret_from_intr+0/7>
Trace; c0220018 <stext_lock+4994/7efc>
Trace; c021d662 <stext_lock+1fde/7efc>
Trace; c012c031 <page_launder+395/930>
Trace; c012c949 <do_try_to_free_pages+1d/58>
Trace; c012cab2 <try_to_free_pages+22/2c>
Trace; c012d6e4 <__alloc_pages+1e0/28c>
Trace; c012d500 <_alloc_pages+18/1c>
Trace; c012d79a <__get_free_pages+a/18>
Trace; c0143b73 <__pollwait+33/94>
Trace; c017b9d4 <normal_poll+28/124>
Trace; c0178573 <tty_poll+8b/98>
Trace; c0143ddb <do_select+14b/234>
Trace; c0144322 <sys_select+436/598>
Trace; c0106d7b <system_call+33/38>
Code: Bad EIP value.
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
Greetings
Christoph
reply other threads:[~2001-07-21 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3k81273gp.fsf@linux.local \
--to=cr@sap.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