Date: Sat, 05 Jun 1999 07:27:07 -0400 (EDT) From: John Baldwin <jobaldwi@vt.edu> To: Alexander Langer <alex@cichlids.com> Cc: Ken Lui <klui@cup44ux.cup.hp.com>, stable@FreeBSD.ORG, Ken Lui <klui@cup.hp.com>, Dag-Erling Smorgrav <des@flood.ping.uio.no>, Oscar Bonilla <obonilla@fisicc-ufm.edu> Subject: Re: Spontaneous reboot while CPU usage is high Message-ID: <199906051127.HAA28994@smtp1.erols.com> In-Reply-To: <19990605111755.B554@cichlids.cichlids.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05-Jun-99 Alexander Langer wrote: > Thus spake Oscar Bonilla (obonilla@fisicc-ufm.edu): > >> > What chipset is on your motherboard? VIA? >> is there a problem with VIA chipsets? I was about to buy a new computer and >> I think it has a VIA chipset... > > I have a K6-2-300 on a VIA Super Sockel 7 Board (DFI), and when I've > been in X some weeks ago, I had such a reboot, when opening a Netscape > window, too. > Maybe it's really a VIA Problem. I have the following: CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> real memory = 67108864 (65536K bytes) avail memory = 62124032 (60668K bytes) ... chip0: <VIA 82C597 (Apollo VP3) system controller> rev 0x04 on pci0.0.0 chip1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI bridge> rev 0x00 on pci0.1.0 chip2: <VIA 82C586 PCI-ISA bridge> rev 0x41 on pci0.7.0 ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1 chip3: <VIA 82C586B ACPI interface> rev 0x10 on pci0.7.3 and I have never had a reboot. I have hit the limit of my swap when running too many things (especially X, Netscape, the Gimp, and AOL's TiK, which has a memory leak) and watched X curl up and die because it got killed due to the lack of swap, but that is normal behavior, as the alternative is to lock up. I also have the following CPU-specific options in my kernel: # CPU options options "NO_F00F_HACK" #not a iPentium options CPU_WT_ALLOC #enable write-back allocation options NO_MEMORY_HOLE It probably won't make a difference, but it might. If it does, then that would help narrow down the bug. > Alex --- John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906051127.HAA28994>