DragonFly bugs List (threaded) for 2007-05
DragonFly BSD
DragonFly bugs List (threaded) for 2007-05
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: kernel panic


From: Joe Talbott <josepht@xxxxxxxxxx>
Date: Thu, 10 May 2007 21:12:03 -0400
Mail-followup-to: Matthew Dillon <dillon@apollo.backplane.com>, bugs@crater.dragonflybsd.org

On Thu, May 10, 2007 at 05:17:42PM -0700, Matthew Dillon wrote:
> 
> :I updated to the latest HEAD as of yesterday (2007-05-09) after the
> :INET6 fix.  
> :
> :...
> :I got the following kernel panic:
> :
> :Fatal trap 19: non-maskable interrupt trap while in kernel mode
> :mp_lock = 00000000; cpuid = 0; lapic.id = 00000000
> :instruction pointer     = 0x8:0xc02f6a1e
> :stack pointer           = 0x10:0xcade4a44
> :frame pointer           = 0x10:0xcade4a68
> :...
> :processor eflags        = interrupt enabled, IOPL = 0
> :current process         = 729 (ifconfig)
> :current thread          = pri 6 
> : <- SMP: XXX
> :
> :It looks like the stack was corrupted but I was able to get this:
> :
> :(kgdb) bt
> :#0  0x00000000 in ?? ()
> :(kgdb) info locals 
> :No symbol table info available.
> :(kgdb) x 0xc02f6a1e
> :0xc02f6a1e <agp_intel_flush_tlb+35>:    0x81028b90
> :
> :I can upload the kernel and vmcore files if absolutely necessary but
> :the vmcore file is 1.6GB uncompressed so if I don't need to I will
> :save the bandwidth.
> :
> :Perhaps unrelated, but just in case.  I got this out of the kernel
> :buffer:
> :
> :[diagnostic] cache_lock: blocked on 0xdc583e28 "utils"
> :
> :I have also had a cvs process hang in the "vnode" state.  I was unable
> :to attach the process with gdb (this just seemed to hang) or get any
> :output from ktrace.
> :
> :Thanks,
> :Joe Talbott
> 
>     NMI traps during device operation usually indicate a bus parity
>     failure during DMA.  This often occurs when shared memory on
>     the device itself is not properly initialized by the device driver
>     and then accessed.
> 
>     What interface were you ifconfig'ing when the crash occured?
>     And is it repeatable?

The strange thing is I was rebooting my laptop (via icewm) when this
occurred.  The interface is re(4) according to the kernel buffer output
which follows.  

Joe

Here is some kernel buffer output:

<118>Shutting down daemon processes:
<118>.
<118>Stopping cron.
<118>Shutting down local daemons:
<118>.
<118>Terminated
<118>.
<118>Dec 15 16:53:11 neptune syslogd: exiting on signal 15
<118>Enter full pathname of shell or RETURN for /bin/sh: 
<118># 
<118>u
<118>m
<118>o
<118>u
<118>n
<118>t
<118> 
<118>/
<118>u
<118>s
<118 
<118 
<118>u
<118>s
<118>r
<118> 
<118>/
<118>h
<118>o
<118>m
<118>e
<118>
<118># 
<118>i
<118>f
<118>c
<118>o
<118>n
<118>f
<118>i
<118>g
<118> 
<118>r
<118>e
<118>0
<118> 
<118>2
<118>0
<118>9
<118>.
<118>1
<118>4
<118>5
<118>.
<118>6
<118>6
<118>.
<118>3
<118>2
<118>



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]