From: Stuffed Crust <pizza@shaftnet.org>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] 2.4.19rc2aa1 in page_cache_read
Date: Wed, 24 Jul 2002 20:59:15 -0400 [thread overview]
Message-ID: <20020725005915.GA24308@shaftnet.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3841 bytes --]
I was having VM oopsen with 2.4.19rc1aa1, so I upgraded to 2.4.19rc2aa1
to see if things were any better. Apparently they aren't.
System uptime of about 60 hours. P3-1G, 512M RAM. Pretty standard
system. This time it wasn't postgresql that got whacked, it was scp.
I'm probably going to fall back to 2.4.19rc3 soon. This is a production
machine, so I can't reboot it that often... The -aa kernel does
bring a number of benefits (and I'm hoping to not have to pull the bits
I want out; I hate rediffing things..)
Here's the ksymoops dump. NULL dereference in the middle of
page_cache_read.
ksymoops 2.4.4 on i686 2.4.19-rc2aa1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.19-rc2aa1/ (default)
-m /boot/System.map-2.4.19-rc2aa1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Unable to handle kernel NULL pointer dereference at virtual address
00000017
80126817
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<80126817>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 0000000f ebx: 89b6a728 ecx: 00000011 edx: 973c2000
esi: 00009bc2 edi: 00009c3c ebp: 9fe95cf4 esp: 973c3eb8
ds: 0018 es: 0018 ss: 0018
Process scp (pid: 5900, stackpage=973c3000)
Stack: 96de9ae0 0000007a 00009bc2 96de9ae0 00009b43 80126ed7 0000007f 00000080
00027e50 814656c4 00000001 96de9ae0 89b6a728 80127135 00000001 96de9ae0
89b6a680 814656c4 00001000 00000001 00000000 00000000 00009b43 89b6a680
Call Trace: [<80126ed7>] [<80127135>] [<8012772c>] [<80127630>] [<80134056>]
[<80113abe>] [<801087a3>]
Code: 39 58 08 75 f4 39 78 0c 75 ef 85 c0 75 59 8b 43 2c 31 d2 89
>>EIP; 80126817 <page_cache_read+67/e0> <=====
Trace; 80126ed7 <generic_file_readahead+127/160>
Trace; 80127135 <__do_generic_file_read+1e5/4b0>
Trace; 8012772c <generic_file_read+8c/180>
Trace; 80127630 <file_read_actor+0/70>
Trace; 80134056 <sys_read+96/f0>
Trace; 80113abe <schedule+1ee/210>
Trace; 801087a3 <system_call+33/38>
Code; 80126817 <page_cache_read+67/e0>
00000000 <_EIP>:
Code; 80126817 <page_cache_read+67/e0> <=====
0: 39 58 08 cmp %ebx,0x8(%eax) <=====
Code; 8012681a <page_cache_read+6a/e0>
3: 75 f4 jne fffffff9 <_EIP+0xfffffff9> 80126810 <page_cache_read+60/e0>
Code; 8012681c <page_cache_read+6c/e0>
5: 39 78 0c cmp %edi,0xc(%eax)
Code; 8012681f <page_cache_read+6f/e0>
8: 75 ef jne fffffff9 <_EIP+0xfffffff9> 80126810 <page_cache_read+60/e0>
Code; 80126821 <page_cache_read+71/e0>
a: 85 c0 test %eax,%eax
Code; 80126823 <page_cache_read+73/e0>
c: 75 59 jne 67 <_EIP+0x67> 8012687e <page_cache_read+ce/e0>
Code; 80126825 <page_cache_read+75/e0>
e: 8b 43 2c mov 0x2c(%ebx),%eax
Code; 80126828 <page_cache_read+78/e0>
11: 31 d2 xor %edx,%edx
Code; 8012682a <page_cache_read+7a/e0>
13: 89 00 mov %eax,(%eax)
1 warning issued. Results may not be reliable.
- Pizza
--
Solomon Peachy pizza@f*cktheusers.org
I'm not broke, but I'm badly bent. ICQ #1318344
Patience comes to those who wait. Melbourne, FL
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2002-07-25 0:57 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=20020725005915.GA24308@shaftnet.org \
--to=pizza@shaftnet.org \
--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