RE: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
re: device atpic yup, I added that manually in the older stuff, but its getting added by default in 9 build as part of the default stuff meow. re: device.hints in /boot ? neg, I will try that right nao. -Original Message- From: adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] On Behalf Of Adrian Chadd Sent: Wednesday, August 31, 2011 6:26 PM To: Mike Tancsa Cc: Edgar Martinez; freebsd-current@freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) This the key here: atrtc0: at port 0x70 irq 8 on isa0 Event timer RTC frequency 32768 Hz quality 0 Edgar, are you missing a device entry for the RTC? Do you have device.hints in /boot ? GENERIC.hints:hint.atrtc.0.at=isa GENERIC.hints:hint.atrtc.0.port=0x70 GENERIC.hints:hint.atrtc.0.irq=8 And do you have device atpic? That seems to be what compiles in atrtc. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
I was missing the hints..problem solved..thanks! -Original Message- From: adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] On Behalf Of Adrian Chadd Sent: Wednesday, August 31, 2011 6:26 PM To: Mike Tancsa Cc: Edgar Martinez; freebsd-current@freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) This the key here: atrtc0: at port 0x70 irq 8 on isa0 Event timer RTC frequency 32768 Hz quality 0 Edgar, are you missing a device entry for the RTC? Do you have device.hints in /boot ? GENERIC.hints:hint.atrtc.0.at=isa GENERIC.hints:hint.atrtc.0.port=0x70 GENERIC.hints:hint.atrtc.0.irq=8 And do you have device atpic? That seems to be what compiles in atrtc. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
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? Adrian On 31 August 2011 22:33, Edgar Martinez emarti...@kbcnetworks.com wrote: GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-BETA2 #0: Wed Aug 31 06:47:57 PDT 2011 root@chuckles.local:/usr/obj/usr/src/sys/MESH i386 WARNING: DIAGNOSTIC option enabled, expect reduced performance. CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x5a2 Family = 5 Model = a Stepping = 2 Features=0x88a93dFPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX AMD Features=0xc040MMX+,3DNow!+,3DNow! real memory = 268435456 (256 MB) avail memory = 223870976 (213 MB) pnpbios: Bad PnP BIOS data checksum wlan: mac acl policy registered K6-family MTRR support enabled (2 registers) cryptosoft0: software crypto on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 Geode LX: PC Engines ALIX.3 v0.99h tinyBIOS V1.4a (C)1997-2007 glxsb0: AMD Geode LX Security Block (AES-128-CBC, RNG) mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0 vr0: VIA VT6105M Rhine III 10/100BaseTX port 0x1000-0x10ff mem 0xe000-0xe0ff irq 10 at device 9.0 on pci0 vr0: Quirks: 0x2 vr0: Revision: 0x96 miibus0: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:0d:b9:19:57:e4 pci0: network, ethernet at device 12.0 (no driver attached) isab0: PCI-ISA bridge port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD CS5536 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, USB at device 15.4 (no driver attached) pci0: serial bus, USB at device 15.5 (no driver attached) cpu0 on motherboard pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xe-0xea7ff pnpid ORM on isa0 uart0: 16550 or compatible at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 uart0: console (38400,n,8,1) uart1: 16550 or compatible at port 0x2f8-0x2ff irq 3 on isa0 panic: No usable event timer found! KDB: stack backtrace: X_db_sym_numargs(c07205cd) at 0xc044c705 = X_db_sym_numargs+0x135 kdb_backtrace(c2820d38,1,fff,c2820d40,c06d0d6a,...) at 0xc056e498 = kdb_backtrace+0x28 panic(c0746b08,c074bfe8,fff,c2820d48,c06d6378,...) at 0xc05460e2 = panic+0xa2 cpu_initclocks_bsp(c2820d60,c050834b,c078f8b4,c0718b46,0,...) at 0xc06d0d6a = cpu_initclocks_bsp+0xfa cpu_initclocks(c078f8b4,c0718b46,0,0,c2820d78,...) at 0xc06d6378 = cpu_initclocks+0x8 hardclock_sync(0,281ec00,281e000,2825000,0,...) at 0xc050834b = hardclock_sync+0x3b mi_startup() at 0xc0506229 = mi_startup+0xa9 btext() at 0xc043f7e5 = btext+0x95 KDB: enter: panic [ thread pid 0 tid 10 ] Stopped at 0xc056e2a4 = kdb_enter+0x34: movl $0,0xc079f874 = kdb_why db ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
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,fff,c2820d40,c070257a,...) at 0xc05a9c98 = kdb_backtrace+0x28 panic(c077df08,c078251c,fff,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 10 ] Stopped at 0xc05a9aa4 = kdb_enter+0x34:movl$0,0xc07d93b4 = kdb_why Is still the result.. -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 10:53 AM To: Adrian Chadd Cc: Edgar Martinez; freebsd-current@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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
On 8/31/2011 3:25 PM, Edgar Martinez wrote: Nope..I rebuilt with both options..and just one at a time.. Strange, My kernel is not so different from GENERIC. I added it to the bottom of http://www.tancsa.com/beta2.html Perhaps its a different Alix box than mine that is causing the issue ? I tried with http://www.pcengines.ch/alix6f2.htm and http://www.pcengines.ch/alix3d2.htm ---Mike 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,fff,c2820d40,c070257a,...) at 0xc05a9c98 = kdb_backtrace+0x28 panic(c077df08,c078251c,fff,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 10 ] Stopped at 0xc05a9aa4 = kdb_enter+0x34:movl$0,0xc07d93b4 = kdb_why Is still the result.. -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 10:53 AM To: Adrian Chadd Cc: Edgar Martinez; freebsd-current@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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
On 8/31/2011 3:57 PM, Edgar Martinez wrote: Latest ALIX firmware? .99h? I'm using the below board... http://pcengines.ch/alix2d2.htm Thats pretty well the same board as me, except I dont have the 2 mini-pci slots. Mine comes up as Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007 vs Geode LX: PC Engines ALIX.3 v0.99h tinyBIOS V1.4a (C)1997-2007 Perhaps engage the PCEngine's folks to see what the difference is and if they know what might be up. ---Mike -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 12:57 PM To: Edgar Martinez Cc: Adrian Chadd; freebsd-current@freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) On 8/31/2011 3:25 PM, Edgar Martinez wrote: Nope..I rebuilt with both options..and just one at a time.. Strange, My kernel is not so different from GENERIC. I added it to the bottom of http://www.tancsa.com/beta2.html Perhaps its a different Alix box than mine that is causing the issue ? I tried with http://www.pcengines.ch/alix6f2.htm and http://www.pcengines.ch/alix3d2.htm ---Mike 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,fff,c2820d40,c070257a,...) at 0xc05a9c98 = kdb_backtrace+0x28 panic(c077df08,c078251c,fff,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 10 ] Stopped at 0xc05a9aa4 = kdb_enter+0x34:movl$0,0xc07d93b4 = kdb_why Is still the result.. -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 10:53 AM To: Adrian Chadd Cc: Edgar Martinez; freebsd-current@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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
(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@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,fff,c2820d40,c070257a,...) at 0xc05a9c98 =
kdb_backtrace+0x28
panic(c077df08,c078251c,fff,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 10 ]
Stopped at 0xc05a9aa4 = kdb_enter+0x34:movl$0,0xc07d93b4 = kdb_why
Is still the result..
-Original Message-
From: Mike Tancsa [mailto:m...@sentex.net]
Sent: Wednesday, August 31, 2011 10:53 AM
To: Adrian Chadd
Cc: Edgar Martinez; freebsd-current@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, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
Latest ALIX firmware? .99h? I'm using the below board... http://pcengines.ch/alix2d2.htm -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 12:57 PM To: Edgar Martinez Cc: Adrian Chadd; freebsd-current@freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) On 8/31/2011 3:25 PM, Edgar Martinez wrote: Nope..I rebuilt with both options..and just one at a time.. Strange, My kernel is not so different from GENERIC. I added it to the bottom of http://www.tancsa.com/beta2.html Perhaps its a different Alix box than mine that is causing the issue ? I tried with http://www.pcengines.ch/alix6f2.htm and http://www.pcengines.ch/alix3d2.htm ---Mike 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,fff,c2820d40,c070257a,...) at 0xc05a9c98 = kdb_backtrace+0x28 panic(c077df08,c078251c,fff,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 10 ] Stopped at 0xc05a9aa4 = kdb_enter+0x34:movl$0,0xc07d93b4 = kdb_why Is still the result.. -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 10:53 AM To: Adrian Chadd Cc: Edgar Martinez; freebsd-current@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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
I have a debug kernel built..anything I can do in the meantime? I imagine Pascal will be sleeping right about now. -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 1:12 PM To: Edgar Martinez Cc: Adrian Chadd; freebsd-current@freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) On 8/31/2011 3:57 PM, Edgar Martinez wrote: Latest ALIX firmware? .99h? I'm using the below board... http://pcengines.ch/alix2d2.htm Thats pretty well the same board as me, except I dont have the 2 mini-pci slots. Mine comes up as Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007 vs Geode LX: PC Engines ALIX.3 v0.99h tinyBIOS V1.4a (C)1997-2007 Perhaps engage the PCEngine's folks to see what the difference is and if they know what might be up. ---Mike -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 12:57 PM To: Edgar Martinez Cc: Adrian Chadd; freebsd-current@freebsd.org Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX) On 8/31/2011 3:25 PM, Edgar Martinez wrote: Nope..I rebuilt with both options..and just one at a time.. Strange, My kernel is not so different from GENERIC. I added it to the bottom of http://www.tancsa.com/beta2.html Perhaps its a different Alix box than mine that is causing the issue ? I tried with http://www.pcengines.ch/alix6f2.htm and http://www.pcengines.ch/alix3d2.htm ---Mike 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,fff,c2820d40,c070257a,...) at 0xc05a9c98 = kdb_backtrace+0x28 panic(c077df08,c078251c,fff,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 10 ] Stopped at 0xc05a9aa4 = kdb_enter+0x34:movl$0,0xc07d93b4 = kdb_why Is still the result.. -Original Message- From: Mike Tancsa [mailto:m...@sentex.net] Sent: Wednesday, August 31, 2011 10:53 AM To: Adrian Chadd Cc: Edgar Martinez; freebsd-current@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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on ALIX)
This the key here: atrtc0: at port 0x70 irq 8 on isa0 Event timer RTC frequency 32768 Hz quality 0 Edgar, are you missing a device entry for the RTC? Do you have device.hints in /boot ? GENERIC.hints:hint.atrtc.0.at=isa GENERIC.hints:hint.atrtc.0.port=0x70 GENERIC.hints:hint.atrtc.0.irq=8 And do you have device atpic? That seems to be what compiles in atrtc. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
