On Sun, 16 Jun 2002 19:21:10 +0200
Bernd Walter <ticso(at)cicely5.cicely.de> wrote:
> Das geht mit DDB_BREAK_TO_DEBUGGER und CTRL-ALT-ESC auf der Console.
> Der DDB, den du ja schon drin hast sollte dann einen Prompt liefern,
> auf welchem du dann mit panic einen solchen incl. Crashdump auslöst.
Sorry, aber wo steht das? ;)
Nungut, hatte gerade beim erneuten make -j4 world wieder n absturz, und
nun auch n dump...
root(at)nudel olivleh1> cd /
root(at)nudel /> gdb -k kernel /var/crash/vmcore.0
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
SMP 2 cpus
IdlePTD at phsyical address 0x0038d000
initial pcb at physical address 0x002f2060
panicstr: from debugger
panic messages:
--- Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0xbfefa600 fault code = supervisor read, page not present instruction pointer = 0x8:0xc027723b stack pointer = 0x10:0xcdd4cecc frame pointer = 0x10:0xcdd4cedc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 36476 (tsort) interrupt mask = net bio cam <- SMP: XXX panic: from debugger mp_lock = 00000004; cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 syncing disks... 163 12 2 2 2 2 2 2 2 7 done Uptime: 35m5s dumping to dev #da/0x20001, offset 294912 dump 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 9 7 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 1 7 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc017b756 in dumpsys () (kgdb) bt #0 0xc017b756 in dumpsys () #1 0xc017b527 in boot () #2 0xc017b999 in panic () #3 0xc0135bc5 in db_panic () #4 0xc0135b65 in db_command () #5 0xc0135c2a in db_command_loop () #6 0xc0137d67 in db_trap () #7 0xc02653cd in kdb_trap () #8 0xc0278bdc in trap () #9 0xc026568c in Debugger () #10 0xc02621f2 in scgetc () #11 0xc025ea79 in sckbdevent () #12 0xc0256452 in atkbd_intr () #13 0xc0284b90 in atkbd_isa_intr () #14 0xc02732b4 in stop_cpus () #15 0xc0265395 in kdb_trap () #16 0xc02792c2 in trap_fatal () #17 0xc0278f59 in trap_pfault () #18 0xc0278ab3 in trap () #19 0xc027723b in pmap_remove_pages () #20 0xc01735b7 in exit1 () #21 0xc0173394 in exit1 () #22 0xc0279645 in syscall2 () #23 0xc026632b in Xint0x80_syscall () Cannot access memory at address 0xbfbff89c. Kann ich jetzt davon ausgehen das es doch am ram liegt? Leider hab ich das alte compile dir vom kernel nicht mehr... Gruesse, Oliver -- :======> Oliver Lehmann <======: clear perl code is better than :====> lehmann(at)ans-netz.de <====: unclear awk code; but NOTHING :===> http://www.pofo.de/ <===: comes close to unclear perl code :=> http://wishlist.pofo.de/ <=: (taken from comp.lang.awk FAQ) To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org with "unsubscribe de-bsd-questions" in the body of the messageReceived on Sun 16 Jun 2002 - 19:41:31 CEST