From owner-freebsd-stable Mon Dec 29 10:26:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23100 for stable-outgoing; Mon, 29 Dec 1997 10:26:03 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23077 for ; Mon, 29 Dec 1997 10:25:42 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id TAA15038 for freebsd-stable@freebsd.org; Mon, 29 Dec 1997 19:06:12 +0100 (CET) (envelope-from olli) Message-Id: <199712291806.TAA15038@dorifer.heim3.tu-clausthal.de> Subject: Errors with DEC 21040 NIC in 2.2-stable To: freebsd-stable@freebsd.org Date: Mon, 29 Dec 1997 19:06:12 +0100 (CET) Reply-To: freebsd-stable@freebsd.org From: oliver.fromme@heim3.tu-clausthal.de (Oliver Fromme) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I recently upgraded a dedicated FreeBSD box with a DEC 21040- based network card from 2.1.7.1-RLEASE to 2.2-971223-SNAP. It was running with 2.1.7.1 about one year without problems. Since the upgrade to 2.2-971223, I get the following syslog messages every now and then: Dec 29 18:18:19 dorifer /kernel: de0: receive: 00:e0:f7:8a:8d:41: alignment error Dec 29 18:25:37 dorifer /kernel: de0: receive: 00:00:e8:0d:8d:6f: bad crc As far as I can tell, nothing else has changed (same network card, mainboard, CPU, RAM). Is this a problem with the "de" driver? Or is this just normal, and the 2.1.7.1 driver just didn't report it? Or did my network card break at the same time I upgraded to 2.2-971223? Please tell me if I should provide any additional information. Regards Oliver PS: The errors don't seem to affect data integrity, therefore I think the affected packets are retransmitted. PPS: No need to cc replies to me; I'm reading the list via a news gateway. -- Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) From owner-freebsd-stable Mon Dec 29 16:19:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA27761 for stable-outgoing; Mon, 29 Dec 1997 16:19:44 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from safe.boh.com (firewall.boh.com [205.172.19.170]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA27727 for ; Mon, 29 Dec 1997 16:19:21 -0800 (PST) (envelope-from aneilson@usa.net) Received: from firewall.safe.boh.com ([10.1.25.11]) by firewall.safe.boh.com with SMTP id <15233>; Mon, 29 Dec 1997 14:20:51 -1000 Message-Id: <1.5.4.16.19971229142006.3907849e@pop.netaddress.com> X-Sender: aneilson@pop.netaddress.com X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-stable@freebsd.org From: "Arthur W. Neilson III" Subject: fatal trap 12 Date: Mon, 29 Dec 1997 14:20:45 -1000 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk been getting quite a few kernel panics w/2.2.5-stable since i installed it Saturday. I get trap type 12 consistently, supervisor write error, page not present. I'm not sure what's wrong, if it's a hardware problem or what. Anyone have a clue? (obiously not me !!! :^( __ / ) _/_ It is a capital mistake to theorise before one has data. /--/ __ / Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III Bank of Hawaii Tech support aneilson@usa.net From owner-freebsd-stable Mon Dec 29 17:00:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01464 for stable-outgoing; Mon, 29 Dec 1997 17:00:17 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from roguetrader.com (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01433 for ; Mon, 29 Dec 1997 17:00:09 -0800 (PST) (envelope-from root@roguetrader.com) Received: (from root@localhost) by roguetrader.com (8.8.5/8.8.5) id SAA14053; Mon, 29 Dec 1997 18:00:10 -0700 (MST) Date: Mon, 29 Dec 1997 18:00:10 -0700 (MST) Message-Id: <199712300100.SAA14053@roguetrader.com> Subject: ERRATA NOTICE: FreeBSD 2.2.5-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.5-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/ERRATA.TXT The last update was sent: Tue Dec 23 10:30:32 1997 This update is sent: Mon Dec 29 18:00:09 1997 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o A bug in XF86Setup causes it to fail to create a symbolic link from /usr/X11R6/bin/X to the right X server for your hardware if a link does not already exist. When you type startx the following error is displayed: xinit: No such file or directory (errno 2): no server "X" found in PATH Fix: Execute the following commands (as root) and re-run XF86Setup. # cd /usr/X11R6/bin # ln -s XF86_VGA16 X If XF86Setup asks you if you want to use the existing XF86Config for defaults choose no. When it asks you if you want to create an 'X' link to the server choose yes. From owner-freebsd-stable Mon Dec 29 19:12:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA11728 for stable-outgoing; Mon, 29 Dec 1997 19:12:38 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from thelab.hub.org (slip-33.acadiau.ca [131.162.2.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA11709 for ; Mon, 29 Dec 1997 19:12:31 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with ESMTP id XAA18887 for ; Mon, 29 Dec 1997 23:12:22 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 29 Dec 1997 23:12:22 -0400 (AST) From: The Hermit Hacker To: freebsd-stable@freebsd.org Subject: Nov 21st stable kernel panicking... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I had my -stable machine reboot twice today, and figured that I'd check in and see if maybe this was a known problem...my first thought is the land attack stuff, or FOOF, and I'm just too behind on my kernel :( I've downloaded the newest kernel, and will be upgrading tomorrow, but if its not related...? Here's what GDB is showing me: (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 #1 0xf010ec72 in panic (fmt=0xf017b90f "page fault") at ../../kern/kern_shutdown.c:390 #2 0xf017c476 in trap_fatal (frame=0xefbffe3c) at ../../i386/i386/trap.c:742 #3 0xf017bf64 in trap_pfault (frame=0xefbffe3c, usermode=0) at ../../i386/i386/trap.c:653 #4 0xf017bc3f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -265854700, tf_esi = 2176, tf_ebp = -272630144, tf_isp = -272630172, tf_ebx = 2359525, tf_edx = 1664, tf_ecx = 17520, tf_eax = 246723, tf_trapno = 12, tf_err = 2, tf_eip = -267237996, tf_cs = 8, tf_eflags = 66195, tf_esp = 1460, tf_ss = 17520}) at ../../i386/i386/trap.c:311 #5 0xf0124594 in sbreserve (sb=0x2400e5, cc=17520) at ../../kern/uipc_socket2.c:410 #6 0xf014697e in tcp_mss (tp=0xf0276114, offer=1460) at ../../netinet/tcp_input.c:2097 #7 0xf01465b1 in tcp_dooptions (tp=0xf0276114, cp=0xf1094852 "\002\004\005´", cnt=0, ti=0xf109482a, to=0xefbfff50) at ../../netinet/tcp_input.c:1825 #8 0xf01451d1 in tcp_input (m=0xf1094800, iphlen=20) at ../../netinet/tcp_input.c:485 #9 0xf0141b14 in ip_input (m=0xf1094800) at ../../netinet/ip_input.c:570 #10 0xf0141b8c in ipintr () at ../../netinet/ip_input.c:591 #11 0xf0174de9 in swi_net_next () #12 0xefbfdfdc in ?? () #13 0xefbfdfdc in ?? () #14 0x2442b in ?? () #15 0x24548 in ?? () #16 0x233b0 in ?? () #17 0x1934 in ?? () #18 0x19fd3 in ?? () #19 0x1095 in ?? () (kgdb) down 4 #5 0xf0124594 in sbreserve (sb=0x2400e5, cc=17520) at ../../kern/uipc_socket2.c:410 410 return (0); (kgdb) list 405 struct sockbuf *sb; 406 u_long cc; 407 { 408 409 if (cc > sb_max * MCLBYTES / (MSIZE + MCLBYTES)) 410 return (0); 411 sb->sb_hiwat = cc; 412 sb->sb_mbmax = min(cc * sb_efficiency, sb_max); 413 if (sb->sb_lowat > sb->sb_hiwat) 414 sb->sb_lowat = sb->sb_hiwat; Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-stable Tue Dec 30 06:59:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27412 for stable-outgoing; Tue, 30 Dec 1997 06:59:33 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from bsd.dialup.bestweb.net (geniusj@bsd.dialup.bestweb.net [209.94.111.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27406 for ; Tue, 30 Dec 1997 06:59:29 -0800 (PST) (envelope-from geniusj@bsd.dialup.bestweb.net) Received: (from geniusj@localhost) by bsd.dialup.bestweb.net (8.8.8/8.8.3) id EAA15015; Tue, 30 Dec 1997 04:59:41 -0500 (EST) Date: Tue, 30 Dec 1997 04:59:40 -0500 (EST) From: Wut!? To: The Hermit Hacker cc: freebsd-stable@FreeBSD.ORG Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id GAA27407 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hrmm.. Did you update your whole etc. dir when you did a CVSUP or whatever you did.. I used to have those problems and when I got the updated RC and rc.conf etc, mine worked fine. I don't know, give it a try :) On Mon, 29 Dec 1997, The Hermit Hacker wrote: > > Hi... > > I had my -stable machine reboot twice today, and figured that I'd > check in and see if maybe this was a known problem...my first thought > is the land attack stuff, or FOOF, and I'm just too behind on my kernel :( > > I've downloaded the newest kernel, and will be upgrading tomorrow, but > if its not related...? > > Here's what GDB is showing me: > > (kgdb) where > #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 > #1 0xf010ec72 in panic (fmt=0xf017b90f "page fault") > at ../../kern/kern_shutdown.c:390 > #2 0xf017c476 in trap_fatal (frame=0xefbffe3c) at ../../i386/i386/trap.c:742 > #3 0xf017bf64 in trap_pfault (frame=0xefbffe3c, usermode=0) > at ../../i386/i386/trap.c:653 > #4 0xf017bc3f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -265854700, > tf_esi = 2176, tf_ebp = -272630144, tf_isp = -272630172, > tf_ebx = 2359525, tf_edx = 1664, tf_ecx = 17520, tf_eax = 246723, > tf_trapno = 12, tf_err = 2, tf_eip = -267237996, tf_cs = 8, > tf_eflags = 66195, tf_esp = 1460, tf_ss = 17520}) > at ../../i386/i386/trap.c:311 > #5 0xf0124594 in sbreserve (sb=0x2400e5, cc=17520) > at ../../kern/uipc_socket2.c:410 > #6 0xf014697e in tcp_mss (tp=0xf0276114, offer=1460) > at ../../netinet/tcp_input.c:2097 > #7 0xf01465b1 in tcp_dooptions (tp=0xf0276114, cp=0xf1094852 "\002\004\005´", > cnt=0, ti=0xf109482a, to=0xefbfff50) at ../../netinet/tcp_input.c:1825 > #8 0xf01451d1 in tcp_input (m=0xf1094800, iphlen=20) > at ../../netinet/tcp_input.c:485 > #9 0xf0141b14 in ip_input (m=0xf1094800) at ../../netinet/ip_input.c:570 > #10 0xf0141b8c in ipintr () at ../../netinet/ip_input.c:591 > #11 0xf0174de9 in swi_net_next () > #12 0xefbfdfdc in ?? () > #13 0xefbfdfdc in ?? () > #14 0x2442b in ?? () > #15 0x24548 in ?? () > #16 0x233b0 in ?? () > #17 0x1934 in ?? () > #18 0x19fd3 in ?? () > #19 0x1095 in ?? () > (kgdb) down 4 > #5 0xf0124594 in sbreserve (sb=0x2400e5, cc=17520) > at ../../kern/uipc_socket2.c:410 > 410 return (0); > (kgdb) list > 405 struct sockbuf *sb; > 406 u_long cc; > 407 { > 408 > 409 if (cc > sb_max * MCLBYTES / (MSIZE + MCLBYTES)) > 410 return (0); > 411 sb->sb_hiwat = cc; > 412 sb->sb_mbmax = min(cc * sb_efficiency, sb_max); > 413 if (sb->sb_lowat > sb->sb_hiwat) > 414 sb->sb_lowat = sb->sb_hiwat; > > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > From owner-freebsd-stable Tue Dec 30 07:37:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00216 for stable-outgoing; Tue, 30 Dec 1997 07:37:15 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from adsight.com (adsight.com [207.86.2.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00205 for ; Tue, 30 Dec 1997 07:37:11 -0800 (PST) (envelope-from webadmin@adsight.com) Received: from localhost (webadmin@localhost) by adsight.com (8.8.7/8.8.7) with SMTP id KAA11222 for ; Tue, 30 Dec 1997 10:37:17 -0500 (EST) Date: Tue, 30 Dec 1997 10:37:08 -0500 (EST) From: Sam Magee To: freebsd-stable@FreeBSD.ORG Subject: Re: Errors with DEC 21040 NIC in 2.2-stable In-Reply-To: <199712291806.TAA15038@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi, > > I recently upgraded a dedicated FreeBSD box with a DEC 21040- > based network card from 2.1.7.1-RLEASE to 2.2-971223-SNAP. > > It was running with 2.1.7.1 about one year without problems. > Since the upgrade to 2.2-971223, I get the following syslog > messages every now and then: > > Dec 29 18:18:19 dorifer /kernel: de0: receive: 00:e0:f7:8a:8d:41: alignment error > Dec 29 18:25:37 dorifer /kernel: de0: receive: 00:00:e8:0d:8d:6f: bad crc > > As far as I can tell, nothing else has changed (same network > card, mainboard, CPU, RAM). Is this a problem with the "de" > driver? Or is this just normal, and the 2.1.7.1 driver just > didn't report it? Or did my network card break at the same > time I upgraded to 2.2-971223? Please tell me if I should > provide any additional information. > > Regards > Oliver > > PS: The errors don't seem to affect data integrity, therefore > I think the affected packets are retransmitted. > > PPS: No need to cc replies to me; I'm reading the list via a > news gateway. > > -- > Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > I once got messages like that from a de card, and it turned out to be some other machine on my local network that wasn't working well. Track down those mac addresses and that will help isolate where the problem is from. Sam From owner-freebsd-stable Tue Dec 30 07:58:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01745 for stable-outgoing; Tue, 30 Dec 1997 07:58:25 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01734 for ; Tue, 30 Dec 1997 07:58:23 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.5/8.7.5) with SMTP id KAA01661; Tue, 30 Dec 1997 10:58:10 -0500 (EST) Date: Tue, 30 Dec 1997 10:58:10 -0500 (EST) From: The Hermit Hacker To: Wut!? cc: freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, Wut!? wrote: > Hrmm.. Did you update your whole etc. dir when you did a CVSUP or > whatever you did.. I used to have those problems and when I got the > updated RC and rc.conf etc, mine worked fine. I don't know, give it a try :) This could very well be where I screwed up :( I just rebuild and installed a new kernel...am doing a make world right now to go alone with it. Does anyone have a "clean" method of updating /etc, or do you just go through one file at a time and decide what needs to be updated and what doesn't? :( From owner-freebsd-stable Tue Dec 30 10:04:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11043 for stable-outgoing; Tue, 30 Dec 1997 10:04:57 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA11035 for ; Tue, 30 Dec 1997 10:04:52 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xn61s-0003wY-00; Tue, 30 Dec 1997 10:04:37 -0800 Date: Tue, 30 Dec 1997 10:04:35 -0800 (PST) From: Tom To: The Hermit Hacker cc: Wut!? , freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, The Hermit Hacker wrote: > On Tue, 30 Dec 1997, Wut!? wrote: > > > Hrmm.. Did you update your whole etc. dir when you did a CVSUP or > > whatever you did.. I used to have those problems and when I got the > > updated RC and rc.conf etc, mine worked fine. I don't know, give it a try :) > > This could very well be where I screwed up :( I just rebuild and > installed a new kernel...am doing a make world right now to go alone with > it. Does anyone have a "clean" method of updating /etc, or do you just go > through one file at a time and decide what needs to be updated and what > doesn't? :( Do an entire make world is important, updating /etc/ isn't. After all, the /etc/rc* stuff is just shell scripts. I have 2.2.5 boxes running with /etc/rc* from 2.1. However these shell scripts don't work so well, if bins that mess with the kernel aren't updated. Tom From owner-freebsd-stable Tue Dec 30 10:22:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13042 for stable-outgoing; Tue, 30 Dec 1997 10:22:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13032 for ; Tue, 30 Dec 1997 10:21:58 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.5/8.7.5) with SMTP id NAA12724; Tue, 30 Dec 1997 13:21:48 -0500 (EST) Date: Tue, 30 Dec 1997 13:21:47 -0500 (EST) From: The Hermit Hacker To: Tom cc: freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, Tom wrote: > > On Tue, 30 Dec 1997, The Hermit Hacker wrote: > > > On Tue, 30 Dec 1997, Wut!? wrote: > > > > > Hrmm.. Did you update your whole etc. dir when you did a CVSUP or > > > whatever you did.. I used to have those problems and when I got the > > > updated RC and rc.conf etc, mine worked fine. I don't know, give it a try :) > > > > This could very well be where I screwed up :( I just rebuild and > > installed a new kernel...am doing a make world right now to go alone with > > it. Does anyone have a "clean" method of updating /etc, or do you just go > > through one file at a time and decide what needs to be updated and what > > doesn't? :( > > Do an entire make world is important, updating /etc/ isn't. After all, > the /etc/rc* stuff is just shell scripts. I have 2.2.5 boxes running with > /etc/rc* from 2.1. However these shell scripts don't work so well, if > bins that mess with the kernel aren't updated. Except that right now, I can't even get through a 'make world' without it crashing :( The only thing that I can think of is that it has something to do with my re-arranging (ccd) my news spool, but then I wouldn't have expected to get an error in sockets, I wouldn't think... would I? I got another crash after upgrading the kernel, this time looking like the following. I would suspect swap space, based on it being in the vm_ code, except that I haven't added or removed any swap space in several months: # gdb -k kernel.Dec30 vmcore.10 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 1b8000 current pcb at 19f018 panic: vm_object_deallocate: object deallocated too many times #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 266 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 #1 0xf010eca2 in panic ( fmt=0xf016cb93 "vm_object_deallocate: object deallocated too many times") at ../../kern/kern_shutdown.c:390 #2 0xf016cbfd in vm_object_deallocate (object=0xf1e2f580) at ../../vm/vm_object.c:264 #3 0xf016b154 in vm_map_entry_delete (map=0xf101af00, entry=0xf17f5340) at ../../vm/vm_map.c:1885 #4 0xf016b2d0 in vm_map_delete (map=0xf_map_delete (map=0xf101af00, start=40918 91712, end=4091899904) at ../../vm/vm_map.c:1986 #5 0xf012779e in bfreekva (bp=0xf368785c) at ../../kern/vfs_bio.c:194 #6 0xf01280a0 in brelse (bp=0xf368785c) at ../../kern/vfs_bio.c:603 #7 0xf0128988 in getnewbuf (slpflag=0, slptimeo=0, size=1024, maxsize=8192) at ../../kern/vfs_bio.c:1000 #8 0xf0128d25 in getblk (vp=0xf1d77800, blkno=0, size=1024, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:1197 #9 0xf015a7bd in ffs_balloc (ip=0xf184df00, bn=0, size=6, cred=0xf1e60080, bpp=0xefbffecc, flags=1) at ../../ufs/ffs/ffs_balloc.c:149 #10 0xf015db1d in ffs_write (ap=0xefbffef4) at ../../ufs/ufs/ufs_readwrite.c:260 #11 0xf0131fdb in vn_write (fp=0xf1efd700, uio=0xefbfff38, cred=0xf1e60080) at vnode_if.h:283 #12 0xf0115ce6 in write (p=0xf16aa400, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/sys_generic.c:263 #13 0xf017c8f3 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 3, tf_esi = -272638568, tf_ebp = -272638732, tf_isp = -27232, tf_isp = -27262 9788, tf_ebx = 6, tf_edx = 6, tf_ecx = 7, tf_eax = 4, tf_trapno = 7, tf_err = 7, tf_eip = 268975457, tf_cs = 31, tf_eflags = 662, tf_esp = -272640824, tf_ss = 39}) at ../../i386/i386/trap.c:914 #14 0x10083d61 in ?? () Cannot access memory at address 0xefbfdcf8. (kgdb) quit From owner-freebsd-stable Tue Dec 30 10:25:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13400 for stable-outgoing; Tue, 30 Dec 1997 10:25:37 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA13382 for ; Tue, 30 Dec 1997 10:25:30 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xn6M3-00057z-00; Tue, 30 Dec 1997 10:25:27 -0800 Date: Tue, 30 Dec 1997 10:25:25 -0800 (PST) From: Tom To: The Hermit Hacker cc: freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, The Hermit Hacker wrote: > I got another crash after upgrading the kernel, this time looking > like the following. I would suspect swap space, based on it being in the > vm_ code, except that I haven't added or removed any swap space in several > months: There were some VM bugs fixed shortly after 2.2.5.... Can you try a "make buildworld" on another machine, then "installworld" it on the troubled machine? I do this around here, as I have a half-dozen machines to upgrade, but it also has advantange of being quite a bit faster. An "installworld" only takes 30 minutes over ethernet. Tom From owner-freebsd-stable Tue Dec 30 10:29:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13728 for stable-outgoing; Tue, 30 Dec 1997 10:29:25 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13715 for ; Tue, 30 Dec 1997 10:29:21 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.5/8.7.5) with SMTP id NAA16144; Tue, 30 Dec 1997 13:29:18 -0500 (EST) Date: Tue, 30 Dec 1997 13:29:15 -0500 (EST) From: The Hermit Hacker To: Tom cc: freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, Tom wrote: > > On Tue, 30 Dec 1997, The Hermit Hacker wrote: > > > I got another crash after upgrading the kernel, this time looking > > like the following. I would suspect swap space, based on it being in the > > vm_ code, except that I haven't added or removed any swap space in several > > months: > > There were some VM bugs fixed shortly after 2.2.5.... > > Can you try a "make buildworld" on another machine, then "installworld" > it on the troubled machine? I do this around here, as I have a half-dozen > machines to upgrade, but it also has advantange of being quite a bit > faster. An "installworld" only takes 30 minutes over ethernet. Only have the one FreeBSD machine...:( I'm going to do the 'make world' manually and see if I can get it upgraded that way :( Its painful, but being 2500k away from the machine doesn't give much in the way of options :( From owner-freebsd-stable Tue Dec 30 11:21:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA17254 for stable-outgoing; Tue, 30 Dec 1997 11:21:06 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA17241 for ; Tue, 30 Dec 1997 11:20:59 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id UAA01361 for freebsd-stable@FreeBSD.ORG; Tue, 30 Dec 1997 20:20:43 +0100 (CET) (envelope-from olli) Date: Tue, 30 Dec 1997 20:20:43 +0100 (CET) From: Oliver Fromme Message-Id: <199712301920.UAA01361@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Errors with DEC 21040 NIC in 2.2-stable Newsgroups: list.freebsd-stable Organization: Administration Heim 3 Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It was running with 2.1.7.1 about one year without problems. > > Since the upgrade to 2.2-971223, I get the following syslog > > messages every now and then: > > > > Dec 29 18:18:19 dorifer /kernel: de0: receive: 00:e0:f7:8a:8d:41: alignment error > > Dec 29 18:25:37 dorifer /kernel: de0: receive: 00:00:e8:0d:8d:6f: bad crc > > I once got messages like that from a de card, and it turned out > to be some other machine on my local network that wasn't working > well. Track down those mac addresses and that will help isolate > where the problem is from. It occurs with all kinds of different MAC addresses, including the router's and my own private boxes', so that doesn't really help. And besides -- If there was a machine causing that trouble, the ethernet hubs should filter the bad packets out (at least the manual of the hubs says so). Regards Oliver -- Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) From owner-freebsd-stable Tue Dec 30 12:10:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21589 for stable-outgoing; Tue, 30 Dec 1997 12:10:21 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA21583 for ; Tue, 30 Dec 1997 12:10:16 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xn7zM-0004Tp-00; Tue, 30 Dec 1997 13:10:08 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA29978; Tue, 30 Dec 1997 13:10:26 -0700 (MST) Message-Id: <199712302010.NAA29978@harmony.village.org> To: Tom Subject: Re: Nov 21st stable kernel panicking... Cc: The Hermit Hacker , Wut!? , freebsd-stable@freebsd.org In-reply-to: Your message of "Tue, 30 Dec 1997 10:04:35 PST." References: Date: Tue, 30 Dec 1997 13:10:26 -0700 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Tom writes: : Do an entire make world is important, updating /etc/ isn't. After all, : the /etc/rc* stuff is just shell scripts. I have 2.2.5 boxes running with : /etc/rc* from 2.1. However these shell scripts don't work so well, if : bins that mess with the kernel aren't updated. Just as an aside, I have (or had until very recently) a -current system that used the 2.0.5R rc scripts. Worked just fine. Fear of the unknown kept me from upgrading, and the "don't fix what ain't broken" mantra. After getting some rc.conf expereinces under my belt, and seeing how easy it was to do, I changed my mind and upgraded after the next make world. There are those in the -core team that tell of systems they have had since patchkit days that still have the same rc scripts..... Warner From owner-freebsd-stable Wed Dec 31 11:33:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19517 for stable-outgoing; Wed, 31 Dec 1997 11:33:34 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from alpha.pair.com (pair.com [209.68.1.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA19506 for ; Wed, 31 Dec 1997 11:33:30 -0800 (PST) (envelope-from sigma@pair.com) Received: (from sigma@localhost) by alpha.pair.com (8.8.8/8.6.12) id OAA25587 for freebsd-stable@freebsd.org; Wed, 31 Dec 1997 14:33:20 -0500 (EST) From: Kevin Martin Message-Id: <199712311933.OAA25587@alpha.pair.com> X-Envelope-To: freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: from Tom at "Dec 30, 97 10:25:25 am" To: freebsd-stable@freebsd.org Date: Wed, 31 Dec 1997 14:33:20 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I got another crash after upgrading the kernel, this time looking > > like the following. I would suspect swap space, based on it being in the > > vm_ code, except that I haven't added or removed any swap space in several > > months: > > There were some VM bugs fixed shortly after 2.2.5.... Like kern/4844 and/or kern/5117? Do these particular bugs seem to be resolved in the 2.2.5-stable branch? I see that the bugs are still open in GNATS, so I'm concerned. Thanks, Kevin Martin sigma@pair.com From owner-freebsd-stable Wed Dec 31 22:59:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA24517 for stable-outgoing; Wed, 31 Dec 1997 22:59:56 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from radford.i-plus.net (root@NS.i-Plus.net [208.24.67.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA24509 for ; Wed, 31 Dec 1997 22:59:53 -0800 (PST) (envelope-from rewt@i-Plus.net) Received: from b.nu (old@b.nu [208.24.67.58]) by radford.i-plus.net (8.8.8/8.8.5) with SMTP id BAA08948 for ; Thu, 1 Jan 1998 01:59:42 -0500 (EST) Message-ID: <00d601bd1683$d0f9ca80$3a4318d0@b.nu> From: "Troy Settle" To: "(ML) FreeBSD Stable" Subject: syscons bug Date: Thu, 1 Jan 1998 02:06:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk A few weeks ago, I posted a request for help with a 2.2.5-STABLE (mid to late Nov) problem involving a bug in the syscons driver that caused a reboot when switching vtys. Someone (one of the developers?) from Japan, I belive, asked me to apply a couple patches to revert syscons.c and syscons.h back to 2.2.5-RELEASE to see where the bug appeared. It took a while, but I finally found the time to try those patches, and it took both of them before I got a stable syscons driver. Just wanted to let the person know (I lost your email, sorry). Thanks for the fix, I hope this info helps you out. --Troy From owner-freebsd-stable Wed Dec 31 23:43:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA26985 for stable-outgoing; Wed, 31 Dec 1997 23:43:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from gold.csl.sri.com (gold.csl.sri.com [130.107.4.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA26980 for ; Wed, 31 Dec 1997 23:43:45 -0800 (PST) (envelope-from narana@gold.csl.sri.com) Received: (from narana@localhost) by gold.csl.sri.com (8.8.5/8.8.5) id XAA19747 for freebsd-stable@freebsd.org; Wed, 31 Dec 1997 23:06:21 -0800 From: Narana Kannappan Message-Id: <199801010706.XAA19747@gold.csl.sri.com> Subject: custom kernel To: freebsd-stable@freebsd.org Date: Wed, 31 Dec 1997 23:06:21 -75200 (PST) Content-Type: text Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have a TOSHIBA 24X atapi cd-rom drive. The current customized kernel takes a long time (20 seconds) trying to probe for this device during boot time. Al the other steps during boot up are quite fast. I was wondering if there are any specific lines that I could change in my config file to make this probing faster. I am running 2.2.5-STABLE and here are somem more details: 1) dmesg gives the foll wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4119MB (8436960 sectors), 8928 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, ovlap, d ma, iordy wcd0: 4133/4134Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tra y wcd0: 120mm data disc loaded, unlocked 2) the relevant lines in my config file are options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM Thanks, Narana.