Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
I have had odd behavior like you are describing with cheap motherboards. I ran all of the memory tests etc, and everything passed with flying colors. Despite passing all of the tests I could throw at the hardware, windows 2000 was very unstable. We ultimately ended up replacing the board. On Thu, 17 Mar 2005 17:59:13 +, Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Mar 16, 2005 at 07:29:43PM -0800, Jean Lagarde wrote: Thanks to all who replied. So it seems the consensus is a likely hardware issue, and I am leaning that way as well now. I will try the suggestion about disabling ACPI however. To address some of the other comments, that exact CPU-mobo-memory configuration worked fine running Win2000 for many years, so I doubt it is the problem per se. Doesn't rule out bugs in the ACPI support of your motherboard. Some low-quality motherboards only implement an approximation to the ACPI spec to a level that gets windows to run. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
On Wed, Mar 16, 2005 at 07:29:43PM -0800, Jean Lagarde wrote: Thanks to all who replied. So it seems the consensus is a likely hardware issue, and I am leaning that way as well now. I will try the suggestion about disabling ACPI however. To address some of the other comments, that exact CPU-mobo-memory configuration worked fine running Win2000 for many years, so I doubt it is the problem per se. Doesn't rule out bugs in the ACPI support of your motherboard. Some low-quality motherboards only implement an approximation to the ACPI spec to a level that gets windows to run. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
I would have to agree that it is a HW issue. The RAM itself may be ok, but may have issues with other HW components in your system. --Nick On Tue, 15 Mar 2005 19:10:27 -0800, Jean Lagarde [EMAIL PROTECTED] wrote: I have been troubleshooting reboots over the last weekend, I think I might have enough clues now to get some useful hints from an expert. FreeBSD 5.3-release (see dmesg below for details) The problem seems to be with trying to run with 1.5GB vice 512MB of RAM. The system has not had problems so far when I only leave the 512MB stick in. When I add the 1GB stick the system will reboot at specific times, for example, while trying to launch KDE3 or trying to make OpenOffice (always reboots at Extracting for openoffice-1.1.2-1). I do not see any panic in the messages log, the system just silently reboots. I initially installed FreeBSD with only the 512MB stick in. The memory itself seems fine; memtest86 detects no errors. At boot time all the memory is detected: real memory = 1610547200 (1535 MB) avail memory = 1568432128 (1495 MB) Running memtest all only seems to find 512MB to use. It evidently makes no assumption about how much memory is there, starting by trying to malloc 4GB and reducing the amount gradually until it finally successfully mallocs 512 MB and eventually manages to lock 413 MB (failed due to insufficient resources above that). The tests on the 413 MB do pass. I have rebuilt the kernel with VM_KMEM_SIZE_MAX=419430400 as suggested in the FAQ. No change. Would setting MAXMEM to 1572864 help? I am not sure since the correct amount is reported by FreeBSD at boot, and right now trying to make the kernel with that option seems to be another case that reboots the machine (i.e. the make process itself reboots the machine) so I have not tried it yet (guess I would have to remove the 1GB stick to make the new kernel and then put it back to try it out). Thank you for any help. dmesg FreeBSD 5.3-RELEASE #1: Sun Mar 13 20:01:36 PST 2005 x:/usr/src/sys/i386/compile/KERNEL_JEAN Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.20GHz (2205.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1610547200 (1535 MB) avail memory = 1568432128 (1495 MB) mptable_probe: MP Config Table has bad signature: .\M^K\M-@ npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: SOYO AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (3 Cx states) on acpi0 acpi_tz0: Thermal Zone on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x1080-0x10ff,0x1000-0x107f,0x480-0x48f,0xcf8 -0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 645 host to AGP bridge mem 0xe000-0xe3ff at device 0.0 on pc i0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 ohci0: SiS 5571 USB controller mem 0xe700-0xe7000fff irq 5 at device 2.2 o n pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support 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 0xe7001000-0xe7001fff irq 12 at device 2.3 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support 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 atapci0: SiS 961 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6 ,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 sis0: SiS 900 10/100BaseTX port 0xe000-0xe0ff mem 0xe7002000-0xe7002fff irq 11 at device 3.0 on pci0 miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:50:2c:04:6c:0b pci0: display, VGA at device 10.0 (no driver attached) pci0: multimedia, audio at device 14.0 (no driver attached) sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles,
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
Jean Lagarde wrote: I have been troubleshooting reboots over the last weekend, I think I might have enough clues now to get some useful hints from an expert. FreeBSD 5.3-release (see dmesg below for details) The problem seems to be with trying to run with 1.5GB vice 512MB of RAM. The system has not had problems so far when I only leave the 512MB stick in. When I add the 1GB stick the system will reboot at specific times, for example, while trying to launch KDE3 or trying to make OpenOffice (always reboots at Extracting for openoffice-1.1.2-1). I do not see any panic in the messages log, the system just silently reboots. I initially installed FreeBSD with only the 512MB stick in. The memory itself seems fine; memtest86 detects no errors. I too have a similar problem. I have 7 identical systems. all with identical MoBo's SCSI hard drives and RAM. One machine reboots frequently with 5.3 where with 4.9 it never rebooted. 6 machines are fine. 1 reboots. I changed memory sticks. (which incidentally always pass an extensive memory test). I even changed the power supply on the computer. The last thing I am going to change is the MoBo. Perhaps it has some timing issue discovered only with 5.3. Luckily when I needed 7 MoBos, I purchased 8 and have a spare. This is mystery, because as I said, 4.9 worked fine on this machine. regards, Jim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
On Wed, Mar 16, 2005 at 12:45:07PM -0800, Jim Pazarena wrote: I too have a similar problem. I have 7 identical systems. all with identical MoBo's SCSI hard drives and RAM. One machine reboots frequently with 5.3 where with 4.9 it never rebooted. 6 machines are fine. 1 reboots. I changed memory sticks. (which incidentally always pass an extensive memory test). I even changed the power supply on the computer. The last thing I am going to change is the MoBo. Perhaps it has some timing issue discovered only with 5.3. Luckily when I needed 7 MoBos, I purchased 8 and have a spare. This is mystery, because as I said, 4.9 worked fine on this machine. As you noted, 5.3 uses the hardware differently. For example, it uses ACPI, which is sometimes buggy as implemented by the mobo manufacturer. Try looking for an updated BIOS, disabling ACPI in the freebsd boot screen, etc. Also make sure you're truly seeing a spontaneous reboot and not a panic. Sometimes users are confused about the difference (when FreeBSD panics it tells you as such on the console). Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
On Wednesday 16 March 2005 03:10, Jean Lagarde wrote: I have been troubleshooting reboots over the last weekend, I think I might have enough clues now to get some useful hints from an expert. FreeBSD 5.3-release (see dmesg below for details) The problem seems to be with trying to run with 1.5GB vice 512MB of RAM. The system has not had problems so far when I only leave the 512MB stick in. When I add the 1GB stick the system will reboot at specific times, for example, while trying to launch KDE3 or trying to make OpenOffice (always reboots at Extracting for openoffice-1.1.2-1). I do not see any panic in the messages log, the system just silently reboots. Have you checked your motherboard's manual for allowed memory combinations? I was thinking of making the same upgrade, but I looked through the table of supported configurations and I noticed that for DDR 400 memory, I should only have 1 double-sided stick. As I understand it, most DDR400 memory at 0.5 and 1GB is currently double-sided. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
Thanks to all who replied. So it seems the consensus is a likely hardware issue, and I am leaning that way as well now. I will try the suggestion about disabling ACPI however. To address some of the other comments, that exact CPU-mobo-memory configuration worked fine running Win2000 for many years, so I doubt it is the problem per se. Also, I did try the 1GB stick alone yesterday and it had similar symptoms as for 1.5 GB. I do know where to look for a panic message and there is none. About my running Win2000 on this hardware before, I would initially have thought that this made a hardware problem improbable, but I used to run the computer continually and I guess it's not impossible that there was a hardware degradation that was mitigated by the system staying warm all the time. The system was mothballed for a few months before my FreeBSD install, so the prolonged period at room temperature may have allowed some motherboard degradation to get worse. I was led to form that hypothesis because I noticed yesterday that there seems to be a relation with temperature: I ran burnP6 and crashme concurrently (both ran without problem with any memory configuration but I realize that neither of these two utilities necessarily stress the system in the way I need) and since they ran fine with the 1.5 GB in I tried to start KDE again (leaving the stress applications running) and it did bring everything up without rebooting. I stopped the system and let it cool down and KDE made the system reboot as before after a restart. I guess my next step will be to install chm or something like that to monitor the temperatures as the system runs, but anyway, it seems this is likely not a FreeBSD problem anymore, so I thank you all again for the suggestions and will continue troubleshooting the hardware. My immediate guess is either the CPU or motherboard. Oh yeah, I still wonder thought why memtest all only seemed to find 512MB of RAM, but I think it is a side issue at this time. Cheers, Jean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
I have been troubleshooting reboots over the last weekend, I think I might have enough clues now to get some useful hints from an expert. FreeBSD 5.3-release (see dmesg below for details) The problem seems to be with trying to run with 1.5GB vice 512MB of RAM. The system has not had problems so far when I only leave the 512MB stick in. When I add the 1GB stick the system will reboot at specific times, for example, while trying to launch KDE3 or trying to make OpenOffice (always reboots at Extracting for openoffice-1.1.2-1). I do not see any panic in the messages log, the system just silently reboots. I initially installed FreeBSD with only the 512MB stick in. The memory itself seems fine; memtest86 detects no errors. At boot time all the memory is detected: real memory = 1610547200 (1535 MB) avail memory = 1568432128 (1495 MB) Running memtest all only seems to find 512MB to use. It evidently makes no assumption about how much memory is there, starting by trying to malloc 4GB and reducing the amount gradually until it finally successfully mallocs 512 MB and eventually manages to lock 413 MB (failed due to insufficient resources above that). The tests on the 413 MB do pass. I have rebuilt the kernel with VM_KMEM_SIZE_MAX=419430400 as suggested in the FAQ. No change. Would setting MAXMEM to 1572864 help? I am not sure since the correct amount is reported by FreeBSD at boot, and right now trying to make the kernel with that option seems to be another case that reboots the machine (i.e. the make process itself reboots the machine) so I have not tried it yet (guess I would have to remove the 1GB stick to make the new kernel and then put it back to try it out). Thank you for any help. dmesg FreeBSD 5.3-RELEASE #1: Sun Mar 13 20:01:36 PST 2005 x:/usr/src/sys/i386/compile/KERNEL_JEAN Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.20GHz (2205.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1610547200 (1535 MB) avail memory = 1568432128 (1495 MB) mptable_probe: MP Config Table has bad signature: .\M^K\M-@ npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: SOYO AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (3 Cx states) on acpi0 acpi_tz0: Thermal Zone on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x1080-0x10ff,0x1000-0x107f,0x480-0x48f,0xcf8 -0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: SiS 645 host to AGP bridge mem 0xe000-0xe3ff at device 0.0 on pc i0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 ohci0: SiS 5571 USB controller mem 0xe700-0xe7000fff irq 5 at device 2.2 o n pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support 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 0xe7001000-0xe7001fff irq 12 at device 2.3 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support 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 atapci0: SiS 961 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6 ,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 sis0: SiS 900 10/100BaseTX port 0xe000-0xe0ff mem 0xe7002000-0xe7002fff irq 11 at device 3.0 on pci0 miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:50:2c:04:6c:0b pci0: display, VGA at device 10.0 (no driver attached) pci0: multimedia, audio at device 14.0 (no driver attached) sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2205013308 Hz quality 800 Timecounters tick every 10.000 msec ad0: 39216MB QUANTUM FIREBALLP AS40.0/A1Y.1300 [79677/16/63] at
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
On Tue, Mar 15, 2005 at 07:10:27PM -0800, Jean Lagarde wrote: I have been troubleshooting reboots over the last weekend, I think I might have enough clues now to get some useful hints from an expert. FreeBSD 5.3-release (see dmesg below for details) The problem seems to be with trying to run with 1.5GB vice 512MB of RAM. The system has not had problems so far when I only leave the 512MB stick in. When I add the 1GB stick the system will reboot at specific times, for example, while trying to launch KDE3 or trying to make OpenOffice (always reboots at Extracting for openoffice-1.1.2-1). I do not see any panic in the messages log, the system just silently reboots. Spontaneous reboots means that it's almost certain that your RAM is bad or you have some other hardware failure. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic)
On 03/15/05 22:10:27, Jean Lagarde wrote: I have been troubleshooting reboots over the last weekend, I think I might have enough clues now to get some useful hints from an expert. FreeBSD 5.3-release (see dmesg below for details) The problem seems to be with trying to run with 1.5GB vice 512MB of RAM. The system has not had problems so far when I only leave the 512MB stick in. When I add the 1GB stick the system will reboot at specific times, for example, while trying to launch KDE3 or trying to make OpenOffice (always reboots at Extracting for openoffice-1.1.2-1). I do not see any panic in the messages log, the system just silently reboots. I initially installed FreeBSD with only the 512MB stick in. The memory itself seems fine; memtest86 detects no errors. At boot time all the memory is detected: real memory = 1610547200 (1535 MB) avail memory = 1568432128 (1495 MB) Running memtest all only seems to find 512MB to use. It evidently makes no assumption about how much memory is there, starting by trying to malloc 4GB and reducing the amount gradually until it finally successfully mallocs 512 MB and eventually manages to lock 413 MB (failed due to insufficient resources above that). The tests on the 413 MB do pass. I have rebuilt the kernel with VM_KMEM_SIZE_MAX=419430400 as suggested in the FAQ. No change. Would setting MAXMEM to 1572864 help? I am not sure since the correct amount is reported by FreeBSD at boot, and right now trying to make the kernel with that option seems to be another case that reboots the machine (i.e. the make process itself reboots the machine) so I have not tried it yet (guess I would have to remove the 1GB stick to make the new kernel and then put it back to try it out). Thank you for any help. What happens with just the gig stcik? What happens when you switch the slots the sticks are in? Are the sticks the sam brand? Are the brands/brand supported? http://www.sis.com/support/support_memory_3.htm Are you overclocking? intersresting read on the sis memory controller http://www.lostcircuits.com/motherboard/asus_p4s333/ I also find it hard to believe you have a bad mptable. Maybe you could check for a new bios? It is kind of funny if sis used the ms acpi tools and not intels for an intel system. I say this because I have never heard of problems from the intel acpi tools, and ms is the only other set I know of. dmesg FreeBSD 5.3-RELEASE #1: Sun Mar 13 20:01:36 PST 2005 x:/usr/src/sys/i386/compile/KERNEL_JEAN Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.20GHz (2205.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1610547200 (1535 MB) avail memory = 1568432128 (1495 MB) mptable_probe: MP Config Table has bad signature: .\M^K\M-@ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
