Date: Sat, 06 Sep 2003 20:01:18 +0200 From: Idar Tollefsen <idart@performancedesign.no> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-alpha@freebsd.org Subject: Re: atapicam causes fatal kernel trap Message-ID: <3F5A20ED.C5DE017E@performancedesign.no> References: <3F568ED4.5095458F@performancedesign.no> <16215.32222.610240.127909@grasshopper.cs.duke.edu> <16215.39766.415180.759716@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin wrote: >>> Can you rebuild your kernel with ddb? Add >>> options DDB >>> to your kernel config file, re-run config, rebuild and reboot into >>> the new kernel. >> ../../alpha/alpha/dec_eb164.c:92: undefined reference to `siogdbattach' >> ../../alpha/alpha/dec_eb164.c:113: undefined reference to `comconsole' >> ../../alpha/alpha/dec_eb164.c:114: undefined reference to `siocnattach' > You need to have an sio device in the kernel. Aha ;) Should have guessed that from the undefined references themselves... OK... here's the output: [snip] IPsec: Initialized Security Association Processing. ata1-slave: ATAPI identify retries exceeded ad0: 9787MB <QUANTUM FIREBALL EX10.2A> [19885/16/63] at ata0-master WDMA2 fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0xfffffe780073520c a1 = 0x1 a2 = 0x0 pc = 0xfffffc000036b974 ra = 0xfffffc000036b940 curproc = 0xfffffc000061d308 pid = 0, comm = swapper ddbprinttrap from 0xfffffc000036b974 ddbprinttrap(0xfffffr780073520c, 0x1, 0x0, 0x2) panic: trap panic stop at Debugger+0x2c: ldq ra,0(sp) <0xfffffc00006a98d0> <ra=0xfffffc0000513320,sp=0xfffffc00006a98d0> db> trace Debugger() at Debugger+0x2c panic() at panic+0x100 trap() at trap+0x600 XentMM() at XentMM+0x2c --- memory management fault (from ipl 4) --- atapi_action() at atapi_action+0x194 xpt_action() at xpt_action+0x4dc xpt_bus_register() at xpt_bus_register+0x1ec atapi_cam_attach_bus() at atapi_cam_attach_bus+0x130 ata_boot_attach() at ata_boot_attach+0x284 run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks+0x30 mi_startup() at mi_startup+0xf4 locorestart() at locorestart+0x68 --- root of call graph --- >> On a somewhat unrelated note; could someone explain to me why it builds, >> and installs, all kernel modules? For instance, it builds and installs >> USB modules, even tough I don't want USB support...? It's not a major >> problem, I have place for them, but when rebuilding kernels like this it >> just wastes time. > edit /etc/make.conf and set MODULES_OVERRIDE to a list of modules > you are interested in. Or just 'make kernel' Thanks, nice to know. - IT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F5A20ED.C5DE017E>