From owner-freebsd-current Sun Nov 19 10:40:40 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA16519 for current-outgoing; Sun, 19 Nov 1995 10:40:40 -0800 Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA16514 for ; Sun, 19 Nov 1995 10:40:35 -0800 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id UAA14646 for ; Sun, 19 Nov 1995 20:40:23 +0200 Received: (news@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id UAA00383; Sun, 19 Nov 1995 20:40:31 +0200 To: clinet-list-freebsd-current@clinet.fi Path: cs.hut.fi!hsu From: hsu@cs.hut.fi (Heikki Suonsivu) Newsgroups: clinet.list.freebsd-current Subject: Re: Total lookup under -CURRENT (me too) Date: 19 Nov 1995 18:40:26 GMT Organization: Helsinki University of Technology, Finland Lines: 92 Message-ID: References: <199511191312.OAA00303@keltia.freenix.fr>, <199511191510.HAA11190@MediaCity.com> <48nn6q$sb6$1@haywire.DIALix.COM> NNTP-Posting-Host: shadows.cs.hut.fi In-reply-to: peter@haywire.dialix.com's message of 19 Nov 1995 19:02:00 +0200 Sender: owner-current@FreeBSD.ORG Precedence: bulk In article <48nn6q$sb6$1@haywire.DIALix.COM> peter@haywire.dialix.com (Peter Wemm) writes: brian@MediaCity.com (Brian Litzinger) writes: >> Hello, hate to bear bad news but I've got two total lock-ups in the last >> I don't have a dump as the system lock up without a panic. I'll add DDB and >> see if there is any difference. >Just thought I'd let you know I experience similar behavior. I'm afraid I've got to add a 'me too'... I hadn't been recording it, metoo I've not been able to get a crash dump. dmesg is always reset each time. Unfortunately the machine is remote and unattended. I had though of hooking up a serial console that I could monitor from one of the machines next to it, but the machine doesn't have any serial ports.... So, we have a machine that silently reboots with no way of knowing what is causing it... I get lockup almost every time the kernel puffs this out: messages.0:Nov 11 04:43:24 katiska /kernel: nfsd send error 55 *LOCKUP* messages.0:Nov 11 06:56:43 katiska /kernel: in_rtqtimo: adjusted rtq_reallyold t o 710 messages.0:Nov 11 09:19:14 katiska /kernel: nfs send error 55 for server hauki.c linet.fi:/m/hauki/customer messages.0:Nov 11 09:19:16 katiska /kernel: nfs send error 55 for server hauki.c linet.fi:/m/hauki/bc messages.0:Nov 11 09:19:16 katiska /kernel: nfsd send error 55 messages.0:Nov 11 09:26:10 katiska /kernel: nfs send error 55 for server hauki.c linet.fi:/m/hauki/bc messages.0:Nov 11 09:39:56 katiska /kernel: nfs server hauki.clinet.fi:/m/hauki/ bc: not responding messages.0:Nov 11 09:40:07 katiska /kernel: nfs server hauki.clinet.fi:/var: not responding messages.0:Nov 11 09:40:35 katiska /kernel: nfs server hauki.clinet.fi:/m/hauki/ customer: not responding messages.0:Nov 11 09:42:45 katiska /kernel: nfs server hauki.clinet.fi:/var: is alive again messages.0:Nov 11 09:42:48 katiska /kernel: nfs server hauki.clinet.fi:/m/hauki/ bc: is alive again messages.0:Nov 11 09:42:49 katiska /kernel: nfs server hauki.clinet.fi:/m/hauki/ customer: is alive again messages.0:Nov 11 10:27:15 katiska /kernel: nfs send error 55 for server hauki.c linet.fi:/m/hauki/customer *LOCKUP* nfsd(s) getting killed from a 1.1.5.1 server seems to be a way to exhibit this. I haven't gotten any dumps since last -current upgrade, the systems always lock up or panic but leave no dump. Systems without lots of nfs mounts and access seem much more stable. 2.2-current kernel is from mid-november. Other fancy things, in addition to various SCSI problems every now and then: messages.1:Nov 4 09:18:35 katiska /kernel: Data modified on freelist: word 12 o f object 0xf17fc100 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 09:32:39 katiska /kernel: Data modified on freelist: word 12 o f object 0xf16fd400 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 09:33:01 katiska /kernel: Data modified on freelist: word 12 o f object 0xf191a100 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 09:48:00 katiska /kernel: Data modified on freelist: word 12 o f object 0xf17c8400 size 132 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 10:54:41 katiska /kernel: Data modified on freelist: word 12 o f object 0xf17a1300 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 11:16:54 katiska /kernel: Data modified on freelist: word 12 o f object 0xf15cb700 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 11:23:30 katiska /kernel: Data modified on freelist: word 12 o f object 0xf15a0400 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 11:48:13 katiska /kernel: ed0: warning - receiver ring buffer overrun messages.1:Nov 4 13:10:17 katiska /kernel: Data modified on freelist: word 12 o f object 0xf1746e00 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 13:21:08 katiska /kernel: Data modified on freelist: word 12 o f object 0xf1b0c700 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 13:32:00 katiska /kernel: Data modified on freelist: word 12 o f object 0xf1878000 size 256 previous type NFS node (0xc6 != 0xdeadc0de) messages.1:Nov 4 14:14:21 katiska /kernel: Data modified on freelist: word 12 o f object 0xf15ce100 size 132 previous type NFS node (0xc6 != 0xdeadc0de) These don't seem to be (directly) harmful, though, as the system usually does not crash right after these. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN