panic after entering blank line at mountroot prompt
I recently ran my FreeBSD installation in a virtual machine, and when I booted on real hardware I'd forgotten to update /etc/fstab. I saw the rootmount prompt and tried to clear away the USB probe messages by pressing enter. It appears there's a problem with the mountroot code though because instead of another line, I got a panic: "failed to (re-)mount root". Should the mountroot parser be failing if it doesn't find a valid root to mount on the first line? -- Bruce Cran ___ 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: panic after entering blank line at mountroot prompt
On 30.10.2010 12:48, Bruce Cran wrote: > mountroot code though because instead of another line, I got a panic: > "failed to (re-)mount root". Should the mountroot parser be failing if > it doesn't find a valid root to mount on the first line? Yes. This is default config for CURRENT. -- WBR, Andrey V. Elsukov ___ 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"
panic: invalid PDPE on recend amd64
Hi, Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE This is on: Copyright (c) 1992-2010 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-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 root@:/usr/obj/usr/src/sys/kernel i386 CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f2 Family = 6 Model = f Stepping = 2 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x2010 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2087346176 (1990 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed ___ 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: panic: invalid PDPE on recend amd64
on 30/10/2010 17:43 Paul B Mahol said the following: > Hi, > > Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE > > This is on: > > Copyright (c) 1992-2010 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-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 > root@:/usr/obj/usr/src/sys/kernel i386 amd64 or i386? > CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz 686-class > CPU) > Origin = "GenuineIntel" Id = 0x6f2 Family = 6 Model = f Stepping = 2 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x2010 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 2147483648 (2048 MB) > avail memory = 2087346176 (1990 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 1 > ioapic0 irqs 0-23 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: reservation of 0, a (3) failed It seems that the panic happens at the stage where you should be able to enter ddb and obtain a backtrace at the very least, after adding DDB option to your kernel. -- Andriy Gapon ___ 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: panic: invalid PDPE on recend amd64
On 10/30/10, Andriy Gapon wrote: > on 30/10/2010 17:43 Paul B Mahol said the following: >> Hi, >> >> Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE >> >> This is on: >> >> Copyright (c) 1992-2010 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-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 >> root@:/usr/obj/usr/src/sys/kernel i386 > > amd64 or i386? That is working i386 kernel, I can send bt of amd64 kernel as picture. > >> CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz >> 686-class CPU) >> Origin = "GenuineIntel" Id = 0x6f2 Family = 6 Model = f Stepping = 2 >> >> Features=0xbfebfbff >> >> Features2=0xe3bd >> AMD Features=0x2010 >> AMD Features2=0x1 >> TSC: P-state invariant >> real memory = 2147483648 (2048 MB) >> avail memory = 2087346176 (1990 MB) >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> FreeBSD/SMP: 1 package(s) x 2 core(s) >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> ioapic0: Changing APIC ID to 1 >> ioapic0 irqs 0-23 on motherboard >> acpi0: on motherboard >> acpi0: Power Button (fixed) >> acpi0: reservation of 0, a (3) failed > > It seems that the panic happens at the stage where you should be able to > enter > ddb and obtain a backtrace at the very least, after adding DDB option to > your > kernel. ___ 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: panic: invalid PDPE on recend amd64
on 30/10/2010 18:00 Paul B Mahol said the following: > On 10/30/10, Andriy Gapon wrote: >> on 30/10/2010 17:43 Paul B Mahol said the following: >>> Hi, >>> >>> Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE >>> >>> This is on: >>> >>> Copyright (c) 1992-2010 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-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 >>> root@:/usr/obj/usr/src/sys/kernel i386 >> >> amd64 or i386? Oh, right. Yes, that would be helpful. Thank you. -- Andriy Gapon ___ 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: panic: invalid PDPE on recend amd64
On 10/30/10, Paul B Mahol wrote: > On 10/30/10, Andriy Gapon wrote: >> on 30/10/2010 17:43 Paul B Mahol said the following: >>> Hi, >>> >>> Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE >>> >>> This is on: >>> >>> Copyright (c) 1992-2010 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-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 >>> root@:/usr/obj/usr/src/sys/kernel i386 >> >> amd64 or i386? > > That is working i386 kernel, I can send bt of amd64 kernel as picture. >> >>> CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz >>> 686-class CPU) >>> Origin = "GenuineIntel" Id = 0x6f2 Family = 6 Model = f Stepping = >>> 2 >>> >>> Features=0xbfebfbff >>> >>> Features2=0xe3bd >>> AMD Features=0x2010 >>> AMD Features2=0x1 >>> TSC: P-state invariant >>> real memory = 2147483648 (2048 MB) >>> avail memory = 2087346176 (1990 MB) >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>> cpu0 (BSP): APIC ID: 0 >>> cpu1 (AP): APIC ID: 1 >>> ioapic0: Changing APIC ID to 1 >>> ioapic0 irqs 0-23 on motherboard >>> acpi0: on motherboard >>> acpi0: Power Button (fixed) >>> acpi0: reservation of 0, a (3) failed >> >> It seems that the panic happens at the stage where you should be able to >> enter >> ddb and obtain a backtrace at the very least, after adding DDB option to >> your >> kernel. panic: pmap_demote_DMAP: Invalid PDPE cpuid=0 KDB: enter: panic: [ thread pid 0 tid .. Stopped at .. db> bt Tracing pid 0 .. kdb_enter() .. panic() .. pmap_demote_DMAP() .. amd64_mrinit() .. mem_modevent() .. module_register_init() .. mi_startup() .. If I remove mem module from loader.conf kernel boots fine. If I kldload mem after boot, panic happens. ___ 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"
calcru: runtime went backwards
I haven't seen much of this since 5.x days. Anyone else see calcru messages lately ? -DR NFS# uname -a FreeBSD NFS.Lesmilde.com 9.0-CURRENT FreeBSD 9.0-CURRENT #2: Fri Oct 29 01:07:40 CDT 2010 r...@nfs.lesmilde.com:/usr/obj/usr/src/sys/GENERIC amd64 NFS# tail -25 /var/log/messages Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 91464 usec to 40935 usec for pid 2709 (csh) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4334 usec to 1927 usec for pid 2134 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4814 usec to 2140 usec for pid 2133 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4752 usec to 2113 usec for pid 2132 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 5322 usec to 2366 usec for pid 2131 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 5183 usec to 2304 usec for pid 2130 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4495 usec to 1998 usec for pid 2129 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4501 usec to 2001 usec for pid 2128 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 15315 usec to 6809 usec for pid 2127 (login) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 32057357 usec to 28943929 usec for pid 2063 (cron) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1381 usec to 613 usec for pid 2015 (rsync) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1606 usec to 936 usec for pid 1940 (smbd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 20818 usec to 9600 usec for pid 1895 (smbd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 18992 usec to 8440 usec for pid 1760 (cupsd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 3378 usec to 1501 usec for pid 1720 (mountd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1458 usec to 648 usec for pid 1681 (nfsuserd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 568 usec to 308 usec for pid 1335 (devd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 214373 usec to 95273 usec for pid 1335 (devd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 965 usec to 428 usec for pid 132 (adjkerntz) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 191 usec to 84 usec for pid 15 (vmdaemon) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 74 usec to 33 usec for pid 7 (sctp_iterator) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 984227 usec to 748883 usec for pid 4 (g_down) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1281130 usec to 979529 usec for pid 3 (g_up) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 10320 usec to 4890 usec for pid 1 (init) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 6244341 usec to 2848133 usec for pid 1 (init) NFS# ___ 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: calcru: runtime went backwards
On Saturday 30 October 2010 20:19:04 David Rhodus wrote: > I haven't seen much of this since 5.x days. Anyone else see calcru > messages lately ? > > -DR > > NFS# uname -a > FreeBSD NFS.Lesmilde.com 9.0-CURRENT FreeBSD 9.0-CURRENT #2: Fri Oct > 29 01:07:40 CDT 2010 > r...@nfs.lesmilde.com:/usr/obj/usr/src/sys/GENERIC amd64 > NFS# tail -25 /var/log/messages > Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 91464 > usec to 40935 usec for pid 2709 (csh) It seems to occur if certain CPU power features are enabled in the BIOS - EIST or C1E? I also saw it today when I connected to the virtual VGA console on my Xen VPS. -- Bruce Cran ___ 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: panic: invalid PDPE on recend amd64
Please boot your i386 kernel and send me the output from "memcontrol list". Alan ___ 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"
issue with "options DDB"
hi there, with "options DDB" in my kernel conf i run into the following issue with my kernel modules: link_elf_lookup_symbol: missing symbol hash table KLD file snd_hda.ko is missing dependencies KLD file sound.ko is missing dependencies KLD file nvidia.ko is missing dependencies KLD file linux.ko is missing dependencies KLD file ng_ubt.ko is missing dependencies KLD file ng_hci.ko is missing dependencies KLD file ng_bluetooth.ko is missing dependencies KLD file netgraph.ko is missing dependencies link_elf_lookup_symbol: missing symbol hash table removing the option solves the issue. any advice? cheers. alex ps: i'm running HEAD (r214542; amd64). -- a13x ___ 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"
panic: loading if_bfe after boot
Hi, Loading if_bfe module after boot hangs machine, it works/attach fine from loader. Tell me if you need bt. ___ 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: panic: loading if_bfe after boot
On Sat, Oct 30, 2010 at 5:40 PM, Paul B Mahol wrote: > Hi, > > Loading if_bfe module after boot hangs machine, it works/attach fine > from loader. > > Tell me if you need bt. Yes, I want to see the back trace. ___ 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"
