Re: problem with linux 2.2.15pre4 + Rik's VM fix

From: Kevin Fenzi (kevin@scrye.com)
Date: Thu Jan 27 2000 - 00:39:26 EST


I just booted into 2.2.15pre4 + Rik's vm fix...

Could this vm problem be related a problem I have been seeing for a
while sporadically:

2.2.14 after about 2 weeks I got a slocate process stuck in
       wait_on_buffer (disk wait).

2.2.14pre4 after about 2 days I got the same thing.

When it's in that state, everything is ok on the machine, but anything
that calls a "sync" never comes back. It goes into the same
wait_on_buffer and disk wait state and can't be killed. ;(

Could this be slocate holding some kind of buffer lock?

Anyhow, here are the results of

sed -ne '/gfp called/{ s/.* /EIP: [</; s/!/>]/p; }' < foo | ksymoops -m /boot/System.map-2.2.15pre4-rik

ksymoops 2.3.3 on i686 2.2.15pre4. Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.2.15pre4/ (default)
     -m /boot/System.map-2.2.15pre4-rik (specified)

EIP: [<c011e595>]
Using defaults from ksymoops -t elf32-i386 -a i386
EIP: [<c011e0f9>]
EIP: [<c011e0f9>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e0f9>]
EIP: [<c011e595>]
...lots of the same...
EIP: [<c011e595>]
EIP: [<c011e595>]
EIP: [<c011e595>]
Warning (Oops_read): Code line not seen, dumping what data is available

>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e0f9 <do_wp_page+19/200> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
...lots of the same...
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====
>>EIP; c011e595 <do_anonymous_page+2d/80> <=====

Most of the early ones happened during the boot.

I now have my slocate set to run under strace tonight so I can see
where it is locking up...if anyone has any ideas why it's happening or
has seen the same thing, I would love to hear it.

kevin

-- 
Kevin Fenzi
MTS, tummy.com, ltd.
http://www.tummy.com/  KRUD - Kevin's Red Hat Uber Distribution

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:17 EST