Re: Help with panic: vm_fault
N.J. Thomas [EMAIL PROTECTED] writes: * Brad Marsh [EMAIL PROTECTED] [2006-01-12 11:09:29 -0800]: or singly, not in pairs... This should never be the case. If your memory is acceptable one module at a time, why wouldn't the system accept two? Capacitive loading, for one reason. Not common, but I've certainly seen it (particularly with lower-end machines a couple or so years back). And since different brands of memory modules will have different capacitances (and there may be some variation even among identical units), it may not be easy to reproduce. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help with panic: vm_fault
Howdy, I just added RAM to my computer, and upon boot I get a panic. I'm enclosing the debug session script output, but first a bit of background... The computer has two slots for DIMMs, and was using both before, with generic 256MB sticks. I removed both of those and put in two 512MB sticks of Kingston PC2700 RAM - and that's when I got the panic. Test 1 - switch the positions of the sticks (swap slots). Same result. Test 2 - Remove one stick. Successful boot. Test 3 - Put that same stick in the other slot. Successful boot. Tests 4, 5 - Repeat tests 2 and 3 with the other stick. Successful boots, both. Test 6 - One 512MB stick and one old 26MB stick. Successful boot. Test 7 - Swap slots. Successful boot. Tests 8, 9, 10, 11 - various combinations of sticks and slots. Successful boots, all. Also, I added a swap file so that I'd have a bit over 3GB swap space. I'm including swapinfo output at the bottom... So my comclusion is that FreeBSD is having trouble booting with 2 512MB RAM sticks. The BIOS recognizes the RAM ok (see the debug out put, below). Help? Thank you... *** Script started on Thu Jan 12 08:25:18 2006 %kgdb kernel.debug.0 vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] ... This GDB was configured as i386-marcel-freebsd. Unread portion of the kernel message buffer: Copyright (c) 1992-2005 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 6.0-RELEASE #0: Wed Jan 11 11:05:20 PST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DEBUG Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2806.38-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x441dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,b14 real memory = 1040121856 (991 MB) avail memory = 1013084160 (966 MB) ACPI APIC Table: AWARD AWRDACPI ioapic0 Version 1.4 irqs 0-23 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: AWARD AWRDACPI on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 10 on acpi0 pci_link1: ACPI PCI Link LNKB irq 0 on acpi0 pci_link2: ACPI PCI Link LNKC irq 11 on acpi0 pci_link3: ACPI PCI Link LNKD irq 5 on acpi0 pci_link4: ACPI PCI Link LNKE irq 11 on acpi0 pci_link5: ACPI PCI Link LNKF irq 6 on acpi0 pci_link6: ACPI PCI Link LNKG irq 0 on acpi0 pci_link7: ACPI PCI Link LNKH irq 9 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x480-0x48f,0x1000-0x10bf,0x10c0-0x10ff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 661 host to AGP bridge mem 0xe800-0xebff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 962/963 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f at device 2.5 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pcm0: SiS 7012 port 0xe000-0xe0ff,0xe100-0xe17f irq 18 at device 2.7 on pci0 pcm0: [GIANT-LOCKED] pcm0: Avance Logic ALC650 AC97 Codec ohci0: SiS 5571 USB controller mem 0xec10-0xec100fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: SiS 5571 USB controller mem 0xec101000-0xec101fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xec102000-0xec102fff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: EHCI (generic) USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered rl0: RealTek 8139 10/100BaseTX port 0xe200-0xe2ff mem 0xec103000-0xec1030ff irq 18 at device 15.0 on pci0 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:30:1b:3e:a4:06 pci0: serial
Re: Help with panic: vm_fault
Hi Your conclusion is wrong. I'm using 2 512MB sticks of ram without problem... Brad Marsh wrote: Howdy, I just added RAM to my computer, and upon boot I get a panic. I'm enclosing the debug session script output, but first a bit of background... The computer has two slots for DIMMs, and was using both before, with generic 256MB sticks. I removed both of those and put in two 512MB sticks of Kingston PC2700 RAM - and that's when I got the panic. Test 1 - switch the positions of the sticks (swap slots). Same result. Test 2 - Remove one stick. Successful boot. Test 3 - Put that same stick in the other slot. Successful boot. Tests 4, 5 - Repeat tests 2 and 3 with the other stick. Successful boots, both. Test 6 - One 512MB stick and one old 26MB stick. Successful boot. Test 7 - Swap slots. Successful boot. Tests 8, 9, 10, 11 - various combinations of sticks and slots. Successful boots, all. Also, I added a swap file so that I'd have a bit over 3GB swap space. I'm including swapinfo output at the bottom... So my comclusion is that FreeBSD is having trouble booting with 2 512MB RAM sticks. The BIOS recognizes the RAM ok (see the debug out put, below). Help? Thank you... *** Script started on Thu Jan 12 08:25:18 2006 %kgdb kernel.debug.0 vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] ... This GDB was configured as i386-marcel-freebsd. Unread portion of the kernel message buffer: Copyright (c) 1992-2005 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 6.0-RELEASE #0: Wed Jan 11 11:05:20 PST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DEBUG Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.80GHz (2806.38-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x441dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,b14 real memory = 1040121856 (991 MB) avail memory = 1013084160 (966 MB) ACPI APIC Table: AWARD AWRDACPI ioapic0 Version 1.4 irqs 0-23 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: AWARD AWRDACPI on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA irq 10 on acpi0 pci_link1: ACPI PCI Link LNKB irq 0 on acpi0 pci_link2: ACPI PCI Link LNKC irq 11 on acpi0 pci_link3: ACPI PCI Link LNKD irq 5 on acpi0 pci_link4: ACPI PCI Link LNKE irq 11 on acpi0 pci_link5: ACPI PCI Link LNKF irq 6 on acpi0 pci_link6: ACPI PCI Link LNKG irq 0 on acpi0 pci_link7: ACPI PCI Link LNKH irq 9 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x480-0x48f,0x1000-0x10bf,0x10c0-0x10ff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 661 host to AGP bridge mem 0xe800-0xebff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 962/963 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f at device 2.5 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pcm0: SiS 7012 port 0xe000-0xe0ff,0xe100-0xe17f irq 18 at device 2.7 on pci0 pcm0: [GIANT-LOCKED] pcm0: Avance Logic ALC650 AC97 Codec ohci0: SiS 5571 USB controller mem 0xec10-0xec100fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: SiS 5571 USB controller mem 0xec101000-0xec101fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: SiS 5571 USB controller on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xec102000-0xec102fff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: EHCI (generic) USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered rl0: RealTek 8139 10/100BaseTX port 0xe200-0xe2ff mem 0xec103000-0xec1030ff irq 18 at device 15.0 on pci0 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0:
Re: Help with panic: vm_fault
* Brad Marsh [EMAIL PROTECTED] [2006-01-12 09:33:37 -0800]: I removed both of those and put in two 512MB sticks of Kingston PC2700 RAM - and that's when I got the panic. [...] So my comclusion is that FreeBSD is having trouble booting with 2 512MB RAM sticks. The BIOS recognizes the RAM ok Before you do anything else, I strongly recommend you put in both of the new memory modules in and run memtest86+. Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with panic: vm_fault
OK...in agreement, I've read that memory modules will sometimes work in pairs, not individually, or singly, not in pairs... Thanks! P.S. Juraj, you're right. I'm sure FreeBSD can handle more than 1GB RAM - it's just my system. I was hoping someone could look at the debug info and say something helpful like it's for sure your memory module hardware!. :^) --- N.J. Thomas [EMAIL PROTECTED] wrote: So my comclusion is that FreeBSD is having trouble booting with 2 512MB RAM sticks. The BIOS recognizes the RAM ok Before you do anything else, I strongly recommend you put in both of the new memory modules in and run memtest86+. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with panic: vm_fault
* Brad Marsh [EMAIL PROTECTED] [2006-01-12 11:09:29 -0800]: OK...in agreement, I've read that memory modules will sometimes work in pairs, not individually Older memory/systems used to only take memory that worked in pairs, newer ones shouldn't have that problem. In the worst case, it may accept a single module, but maybe not run as fast as it would with a pair. But my memory-fu isn't up to date, and perhaps someone could correct me. or singly, not in pairs... This should never be the case. If your memory is acceptable one module at a time, why wouldn't the system accept two? Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with panic: vm_fault
Thanks for the help...I booted the GENERIC kernel, and it allowed me to log in as root, but as soon as I started to to anything (I think I did cd) it panicked. I'm going to run the memtest86 and see if it says anything. If you think it would be useful, I could do more debugging on the new vmcore file. Thanks again! --- Brad Marsh [EMAIL PROTECTED] wrote: Date: Thu, 12 Jan 2006 14:58:23 -0800 (PST) From: Brad Marsh [EMAIL PROTECTED] Subject: Re: Help with panic: vm_fault To: Mark Tinguely [EMAIL PROTECTED] Does the Mainboard say that it can handle this amount of RAM? The manual for the motherboard says I can use up to two 1GB modules. (And I used to have two 256MB modules, so I know it can handle two at a time. Also, right now I'm using one 512 and one 256.) Do you have 2 video cards, for example a built into the mainboard but disabled? Just the built-in video adapter. Is this a GENERIC kernel or has it been modified? I see the compile directory is DEBUG, so I am guessing it could be a custom kernel. Yeah, I customized it first thing. Then after all this trouble I built a debug kernel and put the two modules in again so I'd have the debug info. #17 0xc062b6bf in Xint0x80_syscall () at ../../../i386/i386/exception.s:200 #18 0x0033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) q Level 17 is wrong, because that is not a caller of pmap_change_wiring(). Maybe the stack frame got corrupted and the strange VA is another side effect of the corruption. ...if this is not a GENERIC kernel, could you try boo[t]ing say the install CD to eliminate options in the kernel? Great idea. I kept the original GENERIC kernel around just for this purpose. Back in a while... Thanks! P.S. I've been working toward testing with memtest86, but this machine doesn't have a floppy, the USB floppy isn't working (strangely enough - it used to), and I don't have any CDs at this office that the burner can use! I'm having a lovely day. :^) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
