Re: Self baked kernel panics

[Ede Wolf <listac%nebelschwaden.de@localhost>]

Ok, heres the panic again from generic:

<snip>
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...

CPU 0: fatal kernel trap:

CPU 0    trap entry = 0x4 (unaligned access fault)
CPU 0    a0         = 0xfffffe000c589a66
CPU 0    a1         = 0x2c
CPU 0    a2         = 0x1f
CPU 0    pc         = 0xfffffc00004ea978
CPU 0    ra         = 0xfffffc00004ea890
CPU 0    pv         = 0xfffffc0000a697c0
CPU 0    curlwp    = 0xfffffc000fbe9ba0
CPU 0        pid = 3, comm = scsibus1

panic: trap
Stopped in pid 3.1 (scsibus1) at        netbsd:cpu_Debugger+0x14:       or      
z
ero,s6,sp


And now for the backtrace:


db> bt
cpu_Debugger() at netbsd:cpu_Debugger+0x14
panic() at netbsd:panic+0x18c
trap() at netbsd:trap+0x990
XentUna() at netbsd:XentUna+0x20
--- unaligned access fault (from ipl 4) ---
isp_start() at netbsd:isp_start+0x440
ispcmd() at netbsd:ispcmd+0x560
isprequest() at netbsd:isprequest+0x7c
scsipi_run_queue() at netbsd:scsipi_run_queue+0x230
scsipi_execute_xs() at netbsd:scsipi_execute_xs+0x410
scsipi_command() at netbsd:scsipi_command+0xa0
scsipi_inquire() at netbsd:scsipi_inquire+0xb0
scsi_probe_device() at netbsd:scsi_probe_device+0x258
scsi_probe_bus() at netbsd:scsi_probe_bus+0x1b8
scsibus_config() at netbsd:scsibus_config+0x108
scsipi_completion_thread() at netbsd:scsipi_completion_thread+0x4c
exception_return() at netbsd:exception_return
--- root of call graph ---


Will do the recompile without -mcpu tomorrow, I am too tired today


Am Donnerstag, 7. Februar 2008 schrieben Sie:
> On Thu, Feb 07, 2008 at 01:26:44PM +0100, Ede Wolf wrote:
> > However, I am not really sure what you mean by the 4.0 sources? I got
> > mine from CVS and thought that those are 4.0...
> >
> > Initial:
> > cvs checkout -r netbsd-4 -P src
> >
> > update:
> > cvs -t update -Pd
>
> This is the head of the netbsd-4 branch, which has a few modifications
> already applied after the 4.0 release. Maybe it is easier to try a GENERIC
> kernel build from your source (to make sure it fails the same way). If it
> does, it also has DDB included. When it enters that (the "db> " prompt),
> type "bt" and report the output please.
>
> Martin