Date: Fri, 7 May 1999 14:39:43 -0700 (PDT) From: Cliff Skolnick <cliff@steam.com> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Strange reboot saga Message-ID: <Pine.BSF.4.10.9905071429260.505-100000@lazlo.internal.steam.com> In-Reply-To: <3.0.5.32.19990507162332.017e16f0@staff.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
My deadlock problems started with a cvsup a little over a week ago, and many others also noted that the problem started in april. Before that, my 3.1 system was rock solid. It's either a VM problem or a CAM problem by how the system responds to pings for a bit, but no disk acces can be done. No console messages, the machine is a server and not running X. Perhaps something bad got checked in in April, this weekend I'm going to spend some time looking a what actually changed that month. I'm also a little alarmed about how many people are rationalizing this and attacking the posters of lockup problems. Many posters have stated that there sysem was stable with 2.2 or an earlier version of 3.1, please don't discount that. This is -stable, not -advocacy. QUESTION FOR THE GURUS I'd love to get a system snapshot or something while the kernel is still running. Is there a way to do this once the disk system is out to lunch? Hints? Cliff On Fri, 7 May 1999, Mike Tancsa wrote: > At 08:52 PM 5/7/99 +0100, Greg Quinlan wrote: > >Compare !! > > > ># uname -r; uptime > >2.2.5-RELEASE > > 8:56PM up 65 days, 6:52, 1 user, load averages: 0.02, 0.01, 0.00 > > > ># uname -r; uptime > >3.1-RELEASE > > 8:57PM up 4:15, 4 users, load averages: 0.16, 0.12, 0.11 > > It doesnt really mean that much though... here is an SMP system, > FreeBSD 3.1-STABLE #0: Fri Feb 19 11:21:12 EST 1999 > uptime > 4:19PM up 77 days, 3:52, 3 users, load averages: 0.01, 0.06, 0.24 > > > It takes 250K web hits a day, and about 10K worth of email messages... > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xf029d000. > Probing for devices on PCI bus 0: > chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0 > chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0 > chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.4.0 > chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.4.3 > fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 19 on > pci0.9.0 > fxp0: Ethernet address 00:90:27:25:bf:8f > ahc0: <Adaptec 2940 Ultra2 SCSI adapter> rev 0x00 int a irq 18 on pci0.10.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > fxp1: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 17 on > pci0.11.0 > fxp1: Ethernet address 00:90:27:0f:50:f3 > > ---Mike > ------------------------------------------------------------------------ > Mike Tancsa, tel 01.519.651.3400 > Network Administrator, mike@sentex.net > Sentex Communications www.sentex.net > Cambridge, Ontario Canada > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Cliff Skolnick Steam Tunnel Operations cliff@steam.com http://www.steam.com/ 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?Pine.BSF.4.10.9905071429260.505-100000>