Date: Thu, 26 Aug 1999 14:17:42 +0300 (EEST) From: Adrian Penisoara <ady@warpnet.ro> To: Alan Cox <alc@cs.rice.edu> Cc: Juergen Lock <nox@jelal.kn-bremen.de>, scrappy@hub.org, freebsd-stable@FreeBSD.ORG, alc@FreeBSD.ORG Subject: Re: 3.2-STABLE hangs after several hours ... Message-ID: <Pine.BSF.4.10.9908261355110.5037-200000@ady.warpnet.ro> In-Reply-To: <19990824153116.P39490@nonpc.cs.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Hi,
On Tue, 24 Aug 1999, Alan Cox wrote:
> > > >In case anyone is looking at this, with as little info as there is here,
> > > >the last kernel updated was July 13th, so its between then and now that
> > > >the "bug" appears to have been introduced...
> > >
> > > I also went to update my kernel yesterday and stumbled across what
> > > appears to be the same problems as yours, hanging processes until the
> > > entire system becomes unusable... And here is what i came up with:
> >
> > It seems that I've been bitten by the same bug (the machine suddenly
> > freezes after some 2-3 hours); I'm checking out right now the submitted
> > patch and I'll let you know (probably tomorrow) how it works for me...
> >
>
> Please check if you have a process hung in "objtrm". Juergen did.
I haven't the kernel debugger compiled in (as this is a production
machine); anyone care to point me out some documentatin suited to my
situation (kernel debugging on production machines) ?
> If so, this is the same bug reported in the "mSQL getting stuck
> in objtrm state" thread, and it has nothing to do with the changes
> below. (See my earlier message on this subject to the -STABLE list.)
I checked out the previous threads and my situation appears to be similar
to those described in the "On freezes in 3.2-stable" thread, although I
have only 128Mb of RAM and UP kernel; see the attached dmesg output for
more details...
Let me tell you how it worked for me:
* I had an uptime of more than 13 hours with Juergen's patch, but that's
not so conclusive, as these freezes tend to be somewhat random
* When I saw your commit I reverted the patch, cvsupped and rebuilt the
kernel; the machine hung up some 7-8 hours later ...
I really don't know what to blame, kernel bug or faulty hardware; one
thing I can be sure about is that the machine has been rock stable until
I've started to track -STABLE from 3.1-RELEASE somtime around 6th August.
I'll apply Juergen's patch again and come back to you with details.
>
> Alan
>
Thanks,
Ady (@freebsd.ady.ro)
[-- Attachment #2 --]
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.2-STABLE #0: Wed Aug 25 16:03:59 EEST 1999
ady@ady.warpnet.ro:/usr/src/sys/compile/ADY
Timecounter "i8254" frequency 1193356 Hz
Timecounter "TSC" frequency 300725536 Hz
CPU: AMD-K6tm w/ multimedia extensions (300.73-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x570 Stepping = 0
Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
AMD Features=0x400<<b10>>
real memory = 134217728 (131072K bytes)
avail memory = 127729664 (124736K bytes)
Preloaded elf kernel "kernel" at 0xc02a8000.
Probing for devices on PCI bus 0:
chip0: <Intel 82439TX System Controller (MTXC)> rev 0x01 on pci0.0.0
chip1: <Intel 82371AB PCI to ISA bridge> rev 0x01 on pci0.7.0
chip2: <Intel 82371AB Power management controller> rev 0x01 on pci0.7.3
rl0: <RealTek 8139 10/100BaseTX> rev 0x10 int a irq 11 on pci0.9.0
rl0: Ethernet address: 00:20:18:8a:9e:1f
rl0: autoneg complete, link status good (half-duplex, 100Mbps)
cy0: <Cyclades Cyclom-Y Serial Adapter> rev 0x01 int a irq 10 on pci0.11.0
ed1: <NE2000 PCI Ethernet (RealTek 8029)> rev 0x00 int a irq 12 on pci0.13.0
ed1: address 00:00:21:45:df:7b, type NE2000 (16 bit)
ahc0: <Adaptec 2940A Ultra SCSI adapter> rev 0x01 int a irq 15 on pci0.15.0
ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
Probing for PnP devices:
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 at 0x340-0x35f irq 5 on isa
ed0: address 00:00:21:62:9b:5b, type NE2000 (16 bit)
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
ppc0 at 0x378 irq 7 flags 0x40 on isa
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
plip0: <PLIP network interface> on ppbus 0
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 1000 packets/entry
changing root device to da0s1a
da0 at ahc0 bus 0 target 1 lun 0
da0: <QUANTUM FIREBALL SE8.4S PJ0A> Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 8191MB (16777215 512 byte sectors: 64H 32S/T 8191C)
WARNING: / was not properly dismounted
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
cy0: 1 more silo overflow (total 1)
cy7: 1 more silo overflow (total 1)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9908261355110.5037-200000>