(gdb) list *0xc05a9aa4 0xc05a9aa4 is in kdb_enter (/usr/src/sys/kern/subr_kdb.c:421). 416 if (kdb_dbbe != NULL && kdb_active == 0) { 417 if (msg != NULL) 418 printf("KDB: enter: %s\n", msg); 419 kdb_why = why; 420 breakpoint(); 421 kdb_why = KDB_WHY_UNSET; 422 } 423 } 424 425 /* (gdb) -----Original Message----- From: Edgar Martinez Sent: Wednesday, August 31, 2011 12:25 PM To: 'Mike Tancsa'; Adrian Chadd Cc: freebsd-current_at_freebsd.org Subject: RE: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) Nope..I rebuilt with both options..and just one at a time.. panic: No usable event timer found! KDB: stack backtrace: X_db_sym_numargs(c0758a2d) at 0xc0471f85 = X_db_sym_numargs+0x135 kdb_backtrace(c2820d38,1,fffffff,c2820d40,c070257a,...) at 0xc05a9c98 = kdb_backtrace+0x28 panic(c077df08,c078251c,fffffff,c2820d48,c0708b88,...) at 0xc0581322 = panic+0xa2 cpu_initclocks_bsp(c2820d60,c054358b,c07c8f14,c0750d2a,0,...) at 0xc070257a = cpu_initclocks_bsp+0xfa cpu_initclocks(c07c8f14,c0750d2a,0,0,c2820d78,...) at 0xc0708b88 = cpu_initclocks+0x8 hardclock_sync(0,281ec00,281e000,2825000,0,...) at 0xc054358b = hardclock_sync+0x3b mi_startup() at 0xc0541469 = mi_startup+0xa9 btext() at 0xc0447665 = btext+0x95 KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at 0xc05a9aa4 = kdb_enter+0x34: movl $0,0xc07d93b4 = kdb_why Is still the result.. -----Original Message----- From: Mike Tancsa [mailto:mike_at_sentex.net] Sent: Wednesday, August 31, 2011 10:53 AM To: Adrian Chadd Cc: Edgar Martinez; freebsd-current_at_freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) On 8/31/2011 12:27 PM, Adrian Chadd wrote: > Just to clarify for Edgar, > > His 9.0 build isn't finding any valid timers; hence why the thing > panics upon boot. > > Since I've got a few Alix boards I'd like to use for 11n testing, i'd > like to know how to make this work. > Does anyone know the relevant magic to see which timers are available, > and force enable something that'll work? Strange, I had just tried with a Soekris not long ago and it was happy with Beta1 and 2.... csuping... updating... and it still works. dmesg.txt at http://www.tancsa.com/beta2.html What if you add option CPU_GEODE option CPU_SOEKRIS to the kernel ? I think actually only one is needed, but I forget which one. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike_at_sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/Received on Wed Aug 31 2011 - 17:50:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:17 UTC