Subject: Re: another kernel panic
To: Chuck Silvers <chuq@chuq.com>
From: Albert Zick <al@datazap.net>
List: netbsd-help
Date: 01/21/2005 03:59:53
Hi,

For right now, I have installed 1.6 on my server (I really need to get it 
back to the colo). I do have another box that is just like it and I will 
probably be putting 2.0 on it to try to reproduce this problem. I should 
be able to get a crash dump for you then.

Thanks for all your help,
Al



On Sat, 15 Jan 2005, Chuck Silvers wrote:

> if this happens again, could you try to get a crash dump?
> from ddb, do "reboot 0x104".
>
> -Chuck
>
>
> On Wed, Jan 12, 2005 at 05:22:57PM +0000, Albert Zick wrote:
>> Hi,
>>
>> Yes, more bad news.
>>
>> My 2000 with a 2060 card and 128 megs of ram has kernel panic'd again. I
>> am using the latest 2.0 source from about 10 days ago. Before it kernel
>> panic'd, it showed some strange behavior.
>>
>> from top:
>>
>> 3 root     -18    0     0K  123M pgdaemon  49:15 20.95% 20.95%
>> [pagedaemon]
>>
>> The kernel has grown to 123 megs in size.
>>
>>
>> I killed all the processes that I had running expect for mysqld, which I
>> could not kill even with kill -9.  Then I tried to reboot and it
>> crashed. Any suggestions would be appreciated.
>>
>> Here is the output from the crash and tr:
>>
>>
>> agnus# reboot
>> Jan 12 00:15:51 agnus syslogd: Exiting on signal 15
>> uvm_fault(0x215dd0, oxo, 0, ox1) -) 0xe
>>   type 8, code [mmu,,ssv]: 1050200
>> trap type 8, code = 1050200, v = 24
>> pid = 8733, lid = 1, pc = 000E0A9A, ps = 2700, sfc = 1, dfc = 1
>> Registers:
>>              0        1        2        3        4        5
>> dreg: 00000008 00000001 00004700 00000000 00000000 00000000
>> areg: 00000000 0711B260 00002A24 000029D4 00002970 00000000
>>         6        7
>>  00000000 00000000
>>  0654DE3C 0DFFF81C
>>
>> Kernel stack (0654DCCC):
>> 54DCCC: 001C310C 0654DDE8 00000080 0654DD64 001C361E 00000008 01050200
>> 00000024
>> 54DCEC: 0654DDE8 00004700 00000000 00000000 00000000 00000000 00000000
>> 066D9410
>> 54DD0C: 00000000 0000000E 00000000 00000001 00000000 00000000 00000000
>> 00000001
>> 54DD2C: 00000000 00000000 00000008 00000000 00000000 00000000 064EB960
>> 00215DD0
>> 54DD4C: 00000000 00000001 064EB960 06995654 00000000 00000000 0654DDD4
>> 001C3C18
>> 54DD6C: 00000000 01050200 00000024 0654DDE8 064EDC80 00000000 00000000
>> 00000000
>> 54DD8C: 002D8530 FFFFFFFF 00000000 00000000 00000001 00000000 00000000
>> 00000000
>> 54DDAC: 00000000 00000000 00000000 00000008 00000000 00000000 00000000
>> 0019FB3E
>> 54DDCC: 06995654 064EDC80 0654DE3C 00002058 00000008 0654DE3C 0DFFF81C
>> 00000000
>> 54DDEC: 00000001 00004700 00000000 00000000 00000000 00000000 00000000
>> 00000000
>> 54DE0C: 0711B260 00002A24 000029D4 00002970 00000000 0654DE3C 0DFFF81C
>> 00000000
>> 54DE2C: 2700000E 0A9A4008 00000024 01050200 0654DE78 000ED3BC 00000000
>> 00000000
>> 54DE4C: 00000004 00002A24 000029D4 00002970 00000000 0654DE3C 0DFFF81C
>> 00000000
>> 54DE6C: 00000000 00000000 00000000 0654DEA8 000EC38A 0711B190 0654DEC8
>> 0000001
>> 54DE8C: 00000023 00000000 00000009 00000001 00000100 064E06D8 0711B190
>> 0654DF08
>> 54DEAC: 000EC220 06995654 0654DEC8 00000000 00000001 FFFFFFFF 0654DEF4
>> 00000000
>> panic: MMU fault
>> Stppoed in pid 8733.1 (reboot) at       0x1826ac:       un1k    a6
>> db> tr
>> ?(654dcd8,100,654dcd8,1c3136,1ed630) at 1826ac
>> ?(1ed630,654dd64,1c361e,8,1050200) at 10536a
>> ?(8,1050200,24,654dde8) at1c3130
>> ?(8,1050200,24,654dde8,64edc80,0,0) at 1c3618
>> ?(8,1050200,24) at 1c3c12
>> ?(0) at 2052
>> ?(711b190,654dec8,1) at ed3b6
>> ?(6995654,654dec8,0,1) at ec386
>> ?(64edc80,654df30,654df28) at ec21a
>> ?(25,64edc80,654dfb4) at 184d42
>> ?(25) at 184b50
>> ?() at 2222
>> db>
>