From owner-freebsd-smp Tue Mar 3 22:15:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02116 for freebsd-smp-outgoing; Tue, 3 Mar 1998 22:15:25 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02108; Tue, 3 Mar 1998 22:15:22 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id WAA00443; Tue, 3 Mar 1998 22:15:20 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Tue, 3 Mar 1998 22:15:20 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG cc: smp@FreeBSD.ORG Subject: Current SMP kernel panics on booting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There were some smp file changes today and i built a new a kernel. It drops into debugger when booting at the place where it used to say CPU1 launched here is what i get: mp_lock=00000002; cpuid=0; lapic.id=00000000 instruction pointer = 0x8 : 0x0f012f89e stack pointer = 0x10 : 0xf02a9f90 frame pointer = 0x10 : 0xf02a9f94 code segment = base 0x0 limit 0fffff, type 0x1b = DPL0, pres 1, def321, gran1 processor flags = interrupt enabled, IOPL = 0 current process = 0 (swapper) interrupt mask = <-- SMP:XXX kernel : type 29 trap, code = 0 stopped at _mbinit + 0xe movl $0,_mclfree For the past couple of days it seems like the system has been unstable frequent lock ups.A kernel from last thursday works fine. Manfred ============================== || mantar@netcom.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 07:45:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23488 for freebsd-smp-outgoing; Wed, 4 Mar 1998 07:45:22 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23474 for ; Wed, 4 Mar 1998 07:45:18 -0800 (PST) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id QAA24636; Wed, 4 Mar 1998 16:44:47 +0100 (MET) Message-Id: <199803041544.QAA24636@pat.idi.ntnu.no> To: root@mantar.slip.netcom.com Cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: Your message of "Tue, 3 Mar 1998 22:15:20 -0800 (PST)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 04 Mar 1998 16:44:46 +0100 From: Tor Egge Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > There were some smp file changes today and i built a new > a kernel. It drops into debugger when booting at the place where it used > to say CPU1 launched > here is what i get: > > mp_lock=00000002; cpuid=0; lapic.id=00000000 > instruction pointer = 0x8 : 0x0f012f89e > stack pointer = 0x10 : 0xf02a9f90 > frame pointer = 0x10 : 0xf02a9f94 > code segment = base 0x0 limit 0fffff, type 0x1b > = DPL0, pres 1, def321, gran1 > processor flags = interrupt enabled, IOPL = 0 > current process = 0 (swapper) > interrupt mask = <-- SMP:XXX > kernel : type 29 trap, code = 0 > stopped at _mbinit + 0xe movl $0,_mclfree This probably means that the CPU got an interrupt for which it had no reasonable interrupt handler. All vectors initially points to rsvd, which gives a T_RESERVED (29) trap. This looks like the result of an incomplete kernel rebuild. The config program no longer removes the old kernel compile directory by default. I suggest a complete kernel rebuild, i.e. make clean && make depend && make The message shown by the kernel is not very informative. Vectors 32..254 should probably initially point to a different handler. On systems where APIC_IO is defined, that handler could examine the ISR register in the local apic. A more informative message could be then be printed (e.g. unexpected interrupt (vector 0x50) recieved.) in the panic message. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 10:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19444 for freebsd-smp-outgoing; Wed, 4 Mar 1998 10:33:36 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA19417 for ; Wed, 4 Mar 1998 10:33:25 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-24-b-160.dialup.umn.edu by mhub3.tc.umn.edu; Wed, 4 Mar 98 12:33:16 -0600 Date: Wed, 4 Mar 1998 12:30:15 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: Tor Egge cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: <199803041544.QAA24636@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 4 Mar 1998, Tor Egge wrote: > > here is what i get: > > > > mp_lock=00000002; cpuid=0; lapic.id=00000000 > > instruction pointer = 0x8 : 0x0f012f89e > > stack pointer = 0x10 : 0xf02a9f90 > > frame pointer = 0x10 : 0xf02a9f94 > > code segment = base 0x0 limit 0fffff, type 0x1b > > = DPL0, pres 1, def321, gran1 > > processor flags = interrupt enabled, IOPL = 0 > > current process = 0 (swapper) > > interrupt mask = <-- SMP:XXX > > kernel : type 29 trap, code = 0 > > stopped at _mbinit + 0xe movl $0,_mclfree > > This probably means that the CPU got an interrupt for which it had no > reasonable interrupt handler. All vectors initially points to rsvd, > which gives a T_RESERVED (29) trap. > > This looks like the result of an incomplete kernel rebuild. The > config program no longer removes the old kernel compile directory by > default. > > I suggest a complete kernel rebuild, i.e. > > make clean && make depend && make I've done that (usually the first thing I do if I get a panic on a new kernel), but I have the same panic. The mb is a tyan tomcatII. As a guess, mbinit happens right after the 8254 intr is enabled. Could the clock interrupt forwarding could be causing the problem. Any way to shut that down? Is it all ifdef'd by BETTER_CLOCK? dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 11:45:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09082 for freebsd-smp-outgoing; Wed, 4 Mar 1998 11:45:40 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09008 for ; Wed, 4 Mar 1998 11:45:29 -0800 (PST) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id UAA07342; Wed, 4 Mar 1998 20:45:22 +0100 (MET) Message-Id: <199803041945.UAA07342@pat.idi.ntnu.no> To: adkin003@tc.umn.edu Cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: Your message of "Wed, 4 Mar 1998 12:30:15 -0600 (CST)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 04 Mar 1998 20:45:21 +0100 From: Tor Egge Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've done that (usually the first thing I do if I get a panic on a new > kernel), but I have the same panic. The mb is a tyan tomcatII. As a > guess, mbinit happens right after the 8254 intr is enabled. Could the > clock interrupt forwarding could be causing the problem. Any way to shut > that down? Is it all ifdef'd by BETTER_CLOCK? I suspect this has nothing to do with interrupt forwarding, but with the 8254 clock being routed via a different pin on the IO apic. Try the following patch: Index: sys/i386/isa/intr_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/intr_machdep.c,v retrieving revision 1.9 diff -u -r1.9 intr_machdep.c --- intr_machdep.c 1998/03/03 22:56:29 1.9 +++ intr_machdep.c 1998/03/04 19:24:38 @@ -466,6 +466,11 @@ * Reprogram the vector in the IO APIC. */ select = (intr * 2) + IOAPIC_REDTBL0; + + /* Handle 8254 being routed via pin 2 on the IO APIC */ + if (intr == 0 && (mask8254 == (1 << 2))) + select = (2 * 2) + IOAPIC_REDTBL0; + value = io_apic_read(0, select) & ~IOART_INTVEC; io_apic_write(0, select, value | vector); #else or comment out the definition of APIC_INTR_HIGHPRI_CLOCK in sys/i386/include/smptests.h. On my SMP systems I get the message APIC_IO: routing 8254 via 8259 on pin 0 during boot. If you get APIC_IO: routing 8254 via pin 2 during boot, this is probably related to the problem. I would like feedback on what works and what doesn't on this. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 14:55:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12663 for freebsd-smp-outgoing; Wed, 4 Mar 1998 14:55:01 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12594 for ; Wed, 4 Mar 1998 14:54:47 -0800 (PST) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id XAA14015; Wed, 4 Mar 1998 23:54:41 +0100 (MET) Message-Id: <199803042254.XAA14015@pat.idi.ntnu.no> To: adkin003@tc.umn.edu Cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: Your message of "Wed, 4 Mar 1998 12:30:15 -0600 (CST)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 04 Mar 1998 23:54:40 +0100 From: Tor Egge Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've done that (usually the first thing I do if I get a panic on a new > kernel), but I have the same panic. The mb is a tyan tomcatII. ^^^^^^^^^^^^^ mptable output for Tyan Tomcat II shows that IO APIC pin 0 is configured for ExtInt. But the mptable output also shows that this is a Dual Pentium motherboard. Please try a kernel with the NO_F00F_HACK option. f00f_hack() is broken, since it causes further calls to setidt() to have very little effect. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 16:17:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01842 for freebsd-smp-outgoing; Wed, 4 Mar 1998 16:17:56 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mhub2.tc.umn.edu (0@mhub2.tc.umn.edu [128.101.131.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA01807 for ; Wed, 4 Mar 1998 16:17:40 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-18-c-176.dialup.umn.edu by mhub2.tc.umn.edu; Wed, 4 Mar 98 18:17:28 -0600 Date: Wed, 4 Mar 1998 18:14:27 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: Tor Egge cc: David A Adkins , smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: <199803042254.XAA14015@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 4 Mar 1998, Tor Egge wrote: > Date: Wed, 04 Mar 1998 23:54:40 +0100 > From: Tor Egge > To: David A Adkins > Cc: smp@FreeBSD.ORG > Subject: Re: Current SMP kernel panics on booting > > > I've done that (usually the first thing I do if I get a panic on a new > > kernel), but I have the same panic. The mb is a tyan tomcatII. > ^^^^^^^^^^^^^ > > mptable output for Tyan Tomcat II > shows that IO APIC > pin 0 is configured for ExtInt. > > But the mptable output also shows that this is a Dual Pentium motherboard. > > Please try a kernel with the NO_F00F_HACK option. f00f_hack() is > broken, since it causes further calls to setidt() to have very little > effect. > > - Tor Egge > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > > Hi, Looks like removing f00f_hack() took care of it. Thanks dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 18:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24733 for freebsd-smp-outgoing; Wed, 4 Mar 1998 18:09:30 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24710 for ; Wed, 4 Mar 1998 18:09:28 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id SAA01312; Wed, 4 Mar 1998 18:09:15 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Wed, 4 Mar 1998 18:09:15 -0800 (PST) From: Manfred Antar To: Tor Egge cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: <199803041544.QAA24636@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 4 Mar 1998, Tor Egge wrote: > > There were some smp file changes today and i built a new > > a kernel. It drops into debugger when booting at the place where it used > > to say CPU1 launched > > here is what i get: > > > > mp_lock=00000002; cpuid=0; lapic.id=00000000 > > instruction pointer = 0x8 : 0x0f012f89e > > stack pointer = 0x10 : 0xf02a9f90 > > frame pointer = 0x10 : 0xf02a9f94 > > code segment = base 0x0 limit 0fffff, type 0x1b > > = DPL0, pres 1, def321, gran1 > > processor flags = interrupt enabled, IOPL = 0 > > current process = 0 (swapper) > > interrupt mask = <-- SMP:XXX > > kernel : type 29 trap, code = 0 > > stopped at _mbinit + 0xe movl $0,_mclfree > > This probably means that the CPU got an interrupt for which it had no > reasonable interrupt handler. All vectors initially points to rsvd, > which gives a T_RESERVED (29) trap. > > This looks like the result of an incomplete kernel rebuild. The > config program no longer removes the old kernel compile directory by > default. > > I suggest a complete kernel rebuild, i.e. > > make clean && make depend && make > > > The message shown by the kernel is not very informative. Vectors > 32..254 should probably initially point to a different handler. On > systems where APIC_IO is defined, that handler could examine the ISR > register in the local apic. A more informative message could be then > be printed (e.g. unexpected interrupt (vector 0x50) recieved.) in the > panic message. > > - Tor Egge > I tried that and it didn't work. I'm not too sharp on using the debugger I wish I could be of more help. I just did a fresh make world and suped the new smptest.h file no problems now Thanks Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Mar 4 21:18:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02015 for freebsd-smp-outgoing; Wed, 4 Mar 1998 21:18:17 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01992 for ; Wed, 4 Mar 1998 21:18:13 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA02534; Thu, 5 Mar 1998 16:14:43 +1100 Date: Thu, 5 Mar 1998 16:14:43 +1100 From: Bruce Evans Message-Id: <199803050514.QAA02534@godzilla.zeta.org.au> To: adkin003@tc.umn.edu, Tor.Egge@idi.ntnu.no Subject: Re: Current SMP kernel panics on booting Cc: smp@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Please try a kernel with the NO_F00F_HACK option. f00f_hack() is >broken, since it causes further calls to setidt() to have very little >effect. Here are my (very old :-() fixes for this. I think you only want the first hunk. Only one page is necessary for the buggy version and for a version that maps the page read-write in setidt(), so I'm saving some space and preparing for a better setidt() by only allocating one. The other changes are mostly style fixes. This should all be done differently, perhaps by allocating a page or two of physical memory earlier as in NetBSD. It would have been better to allocate one idt without padding in the text section and mapping it read/write in setidt(), but the 4MB page breaks the read-onlyness of the text section. Bruce diff -c2 machdep.c~ machdep.c *** machdep.c~ Tue Mar 3 12:58:07 1998 --- machdep.c Tue Mar 3 12:58:10 1998 *************** *** 1056,1061 **** int selec; { ! struct gate_descriptor *ip = idt + idx; ip->gd_looffset = (int)func; ip->gd_selector = selec; --- 1119,1129 ---- int selec; { ! struct gate_descriptor *ip; + #if defined(I586_CPU) && !defined(NO_F00F_HACK) + ip = (t_idt != NULL ? t_idt : idt) + idx; + #else + ip = idt + idx; + #endif ip->gd_looffset = (int)func; ip->gd_selector = selec; *************** *** 1560,1593 **** #if defined(I586_CPU) && !defined(NO_F00F_HACK) ! static void f00f_hack(void *unused); ! SYSINIT(f00f_hack, SI_SUB_INTRINSIC, SI_ORDER_FIRST, f00f_hack, NULL); static void ! f00f_hack(void *unused) { struct region_descriptor r_idt; vm_offset_t tmp; - int i; if (!has_f00f_bug) return; ! ! printf("Intel Pentium F00F detected, installing workaround\n"); ! ! r_idt.rd_limit = sizeof(idt) - 1; ! tmp = kmem_alloc(kernel_map, PAGE_SIZE * 2); if (tmp == 0) panic("kmem_alloc returned 0"); ! if (((unsigned int)tmp & (PAGE_SIZE-1)) != 0) ! panic("kmem_alloc returned non-page-aligned memory"); ! /* Put the first seven entries in the lower page */ ! t_idt = (struct gate_descriptor*)(tmp + PAGE_SIZE - (7*8)); bcopy(idt, t_idt, sizeof(idt)); ! r_idt.rd_base = (int)t_idt; ! lidt(&r_idt); ! if (vm_map_protect(kernel_map, tmp, tmp + PAGE_SIZE, ! VM_PROT_READ, FALSE) != KERN_SUCCESS) panic("vm_map_protect failed"); ! return; } #endif /* defined(I586_CPU) && !NO_F00F_HACK */ --- 1623,1662 ---- #if defined(I586_CPU) && !defined(NO_F00F_HACK) ! static void f00f_hack __P((void *unused)); ! SYSINIT(f00f_hack, SI_SUB_INTRINSIC, SI_ORDER_FIRST, f00f_hack, NULL) static void ! f00f_hack(unused) ! void *unused; ! { struct region_descriptor r_idt; vm_offset_t tmp; if (!has_f00f_bug) return; ! printf("Intel Pentium detected, installing workaround for F00F bug\n"); ! #if 0 tmp = kmem_alloc(kernel_map, PAGE_SIZE * 2); + #else + tmp = kmem_alloc(kernel_map, PAGE_SIZE * 1); + #endif if (tmp == 0) panic("kmem_alloc returned 0"); ! ! /* Put the problematic entry (#6) at the end of the lower page. */ ! t_idt = (struct gate_descriptor *) ! #if 0 ! (tmp + PAGE_SIZE - 7 * sizeof(struct gate_descriptor)); ! #else ! tmp; ! #endif ! bcopy(idt, t_idt, sizeof(idt)); ! if (vm_map_protect(kernel_map, tmp, tmp + PAGE_SIZE, VM_PROT_READ, ! FALSE) != KERN_SUCCESS) panic("vm_map_protect failed"); ! r_idt.rd_limit = sizeof(idt) - 1; ! r_idt.rd_base = (unsigned)t_idt; ! lidt(&r_idt); } #endif /* defined(I586_CPU) && !NO_F00F_HACK */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Mar 5 13:14:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20421 for freebsd-smp-outgoing; Thu, 5 Mar 1998 13:14:16 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20411; Thu, 5 Mar 1998 13:14:11 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id QAA13018; Thu, 5 Mar 1998 16:10:24 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Thu, 5 Mar 1998 16:10:23 -0500 (EST) From: Daniel Berlin To: freebsd-smp@FreeBSD.ORG cc: smp@FreeBSD.ORG Subject: hmmmm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having problems getting SMP to work on my P6DLS from SuperMicro. I was looking over list archives and i noticed that someone way back in january had posted about having problems with the P6DLF, which is of the same family. In fact, they were having the same problem. Even though it may be a bios problem, no idea yet, i think i know what it is related to. If i sit there and wait long enough, it starts getting errors on the adaptec controller. It continually times out until the kernel gives up, decides it can't mount root, and panics. I think the adaptec is getting pissed off because it's interrupt was reassigned. or, the apic isn't routing it properly. It works fine without SMP. Is their anyway to disable rerouting of just that interrupt? I'll try a new bios version, and see if it helps also, when i reboot it says it's on cpu #1, and it should be on cpu 0 (about 8 times). --Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Mar 5 14:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28358 for freebsd-smp-outgoing; Thu, 5 Mar 1998 14:10:37 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28318; Thu, 5 Mar 1998 14:10:14 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id RAA00195; Thu, 5 Mar 1998 17:06:20 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Thu, 5 Mar 1998 17:06:19 -0500 (EST) From: Daniel Berlin To: smp@FreeBSD.ORG cc: freebsd-smp@FreeBSD.ORG Subject: AH HAH Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org the problem with the supermicro boards indeed the adaptec controller It's the bios version. all the supermicro bioses but one contain version 1.24 all the ones (newer and older) with 1.24 fail. the one with 1.25 (which isn't the newest or the oldest) works perfectly. --Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Mar 6 14:04:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01125 for freebsd-smp-outgoing; Fri, 6 Mar 1998 14:04:29 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01117 for ; Fri, 6 Mar 1998 14:04:15 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <16397-22914>; Fri, 6 Mar 1998 23:04:03 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id WAA02610 for ; Fri, 6 Mar 1998 22:56:06 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id WAA18839 for smp@freebsd.org; Fri, 6 Mar 1998 22:55:20 +0100 (MET) Message-Id: <199803062155.WAA18839@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Fri, 6 Mar 98 22:55:17 +0100 To: smp@FreeBSD.ORG Subject: Error compiling today's kernel Reply-To: ben@stuyts.nl Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FYI: While compiling a kernel I got this during linking: loading kernel mp_machdep.o: Undefined symbol `_Xforward_irq' referenced from text segment *** Error code 1 Stop. Any ideas? This was cvsupped a few moments ago. Best regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Mar 6 14:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07222 for freebsd-smp-outgoing; Fri, 6 Mar 1998 14:54:34 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from silver.sdsmt.edu (root@silver.sdsmt.edu [151.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07217 for ; Fri, 6 Mar 1998 14:54:31 -0800 (PST) (envelope-from sbauer@taz.sdsmt.edu) Received: from garfield.sdsmt.edu (bugs.sdsmt.edu [151.159.3.11]) by silver.sdsmt.edu (8.8.8/8.8.6) with ESMTP id PAA41540 for ; Fri, 6 Mar 1998 15:54:23 -0700 Received: by bugs.sdsmt.edu with Internet Mail Service (5.5.1960.3) id ; Fri, 6 Mar 1998 15:54:23 -0700 Message-ID: From: "Bauer, Steven J." To: "'freebsd-smp@freebsd.org'" Subject: problems with networking code on a SMP 2 processor Date: Fri, 6 Mar 1998 15:54:18 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! The system was rebuilt using the sources that were cvsup as of 3-4-98. What happens is this: When running in smp mode, and two network cards active and a moderate level of data flowing between the cards, the network quits working -- no forwarding, not access to anywhere. The network drivers will then start reporting timeout errors. If I try to ping a host that is on the same network, I cannot reach it, yet if I ping one of the interfaces on the freebsd machine from the freebsd machine, I get a response. If I then try shutting down the interfaces, I get this error when I shut the last interface down: Fatal trap12: page fault while in kernel mode mp_lock=00000002; cpuid=0;lapic.id=01000000 fault virtual address=0x80430 fault code= supervisor read, page not present instruction pointer =0x8:0xf0148d1f framepointer = 0x10:0xf3f68db4 code segment = base 0x0, limit 0xfffff, type0x1b = DPL 0,pres 1,def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 196 (ifconfig) interrupt mask = net <- SMP:XXX kernel: type 12 trap, code=0 stopped at _rtrequest+0x7f movl 0x14(%edx), %eax The results of show trace where as follows: _rtrequest _in_ifadownkill _rn_walktree _in_ifadown _rip_ctlinput _pfctlinput _if_down _ifioctl _soo_ioctl _ioctl _syscall _Xsyscall --- syscall 0x36, eip=0x25a65, esp 0xefbfdc54, ebp=0xefbfdc70 --- The machine is currently running gated 3.5.8 for a routing daemon. This same problem happens if I use routed as a routing daemon. If I use static routes instead of a routing daemon, I have not been able to cause the machine to quit forwarding packets. Also, if I run the machine in uniprocessor mode, everything works fine. The network cards that I have used include a 4 port network card, Adaptec 6944a, which is base on the DEC 21140-ac chipset (using only two ports), and the SMC 9432. At both times, the cards were running at 100Mbp/s Full Duplex. >From my testing that I have done, it appears that somewere in the routing code there is a problem with the data not being protected from the effects of 2 cpus working on it at once. Does this sound right? Is there a different place I should be looking for this bug at? Thanks for your help! Steve Bauer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Mar 7 17:32:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10954 for freebsd-smp-outgoing; Sat, 7 Mar 1998 17:32:34 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10946 for ; Sat, 7 Mar 1998 17:32:31 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id TAA00395 for ; Sat, 7 Mar 1998 19:32:30 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803080132.TAA00395@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: ccsanady@iastate.edu To: freebsd-smp@FreeBSD.ORG Subject: SMP completely unuseable/w my GA-586DX anymore.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Mar 1998 19:32:30 -0600 From: Chris Csanady Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have really hoped that this problem would go away before too long, but it hasn't. I have had consistent lockups over the past 2 months, and can no longer even complete a make world. As the lock ups only seem to occur in X though, I have not been able to gather any info on what went wrong. Is anyone out there succesfully using a Giga-byte 586DX anymore? It had previously been working great for a long time with SMP. I have also tried a kernel without the F00F hack, as well as one built today with the fixes as well, to no avail. If anyone has any suggestions, it would really be appreciated. It is painful to have to run on a single 133 all the time. :( Following is my dmesg, mptable output, and config file.. Chris Csanady Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sat Mar 7 17:38:54 CST 1998 ccsanady@friley585.res.iastate.edu:/usr/src/sys/compile/xSMP Timecounter "i8254" frequency 1193182 Hz cost 2625 ns CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 63000576 (61524K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vga0: rev 0x01 int a irq 18 on pci0.10.0 ahc0: rev 0x00 int a irq 19 on pci0.12.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1002MB (2053880 512 byte sectors) ahc0: target 1 Tagged Queuing Device sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 3090MB (6328861 512 byte sectors) ahc0: target 2 Tagged Queuing Device sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 3090MB (6328861 512 byte sectors) cd0 at scbus0 target 6 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM can't get the size Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*UTP*] address 00:20:af:75:70:bc npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround APIC_IO: routing 8254 via 8259 on pin 0 ccd0-3: Concatenated disk drivers SMP: AP CPU #1 Launched! Start pid=2 Start pid=3 Start pid=4 =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f0c80 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0xf4 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f0c94 signature: 'PCMP' base table length: 292 version: 1.1 checksum: 0x31 OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 28 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 5 2 1 0x07bf 1 0x11 AP, usable 5 2 1 0x07bf -- Bus: Bus ID Type 0 ISA 1 PCI -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0 2 0 INT conforms conforms 0 1 2 1 INT conforms conforms 0 0 2 2 INT conforms conforms 0 3 2 3 INT conforms conforms 0 4 2 4 INT conforms conforms 0 5 2 5 INT conforms conforms 0 6 2 6 INT conforms conforms 0 7 2 7 INT conforms conforms 0 8 2 8 INT conforms conforms 0 9 2 9 INT conforms conforms 0 10 2 10 INT conforms conforms 0 11 2 11 INT conforms conforms 0 12 2 12 INT conforms conforms 0 13 2 13 INT conforms conforms 0 14 2 14 INT conforms conforms 0 15 2 15 INT active-lo level 1 8:A 2 16 INT active-lo level 1 9:A 2 17 INT active-lo level 1 10:A 2 18 INT active-lo level 1 12:A 2 19 SMI conforms conforms 0 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 0 0 255 0 NMI active-hi edge 0 0 255 1 ------------------------------------------------------------------------------- # 1 "CONFIG" machine "i386" cpu "I586_CPU" ident xSMP maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network File System options MSDOSFS #MS DOS File System options "CD9660" #ISO 9660 filesystem options PROCFS #Process filesystem options COMPAT_LINUX options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO #options DDB options DIAGNOSTIC options KTRACE #options SOFTUPDATES options SC_HISTORY_SIZE=200 # number of history buffer lines config kernel root on sd1 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 controller ahc0 controller scbus0 device sd0 device cd0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmint r device ep0 at isa? port 0x300 net irq 10 vector epintr pseudo-device loop pseudo-device ether pseudo-device pty 64 #pseudo-device tun 1 #pseudo-device gzip #pseudo-device snp 3 pseudo-device vn pseudo-device ccd 4 pseudo-device bpfilter 4 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Mar 7 18:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13223 for freebsd-smp-outgoing; Sat, 7 Mar 1998 18:14:08 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13217 for ; Sat, 7 Mar 1998 18:14:06 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA00292; Sat, 7 Mar 1998 21:14:02 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803080214.VAA00292@dyson.iquest.net> Subject: Re: SMP completely unuseable/w my GA-586DX anymore.. In-Reply-To: <199803080132.TAA00395@friley585.res.iastate.edu> from Chris Csanady at "Mar 7, 98 07:32:30 pm" To: ccsanady@iastate.edu Date: Sat, 7 Mar 1998 21:14:02 -0500 (EST) Cc: freebsd-smp@FreeBSD.ORG 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-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Csanady said: > > I have really hoped that this problem would go away before too > long, but it hasn't. I have had consistent lockups over the > past 2 months, and can no longer even complete a make world. > As the lock ups only seem to occur in X though, I have not been > able to gather any info on what went wrong. Is anyone out there > succesfully using a Giga-byte 586DX anymore? It had previously > been working great for a long time with SMP. > Have you tried it after my recent (todays) mods? -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Mar 7 22:36:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13561 for freebsd-smp-outgoing; Sat, 7 Mar 1998 22:36:20 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13539; Sat, 7 Mar 1998 22:36:15 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id WAA00192; Sat, 7 Mar 1998 22:36:11 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sat, 7 Mar 1998 22:36:11 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG cc: smp@FreeBSD.ORG Subject: current vm changes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been getting a few messages like this from a kernel built tonite vm_fault: pager input (probably hardware) error, PID 28996 failure Mar 7 22:27:22 mantar /kernel: pid 28996 (in.cfingerd), uid 32767: exited on signal 11 spec_getpages: I/O read failure: (code=0) vm_fault: pager input (probably hardware) error, PID 29047 failure Mar 7 22:28:29 mantar /kernel: pid 29047 (make), uid 0: exited on signal 11 (core dumped) I'm doing a make -j -k world in the backround on a dual pentium machine confiured for smp. never seen this before. Manfred ============================== || mantar@netcom.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Mar 7 23:00:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15661 for freebsd-smp-outgoing; Sat, 7 Mar 1998 23:00:39 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15646; Sat, 7 Mar 1998 23:00:34 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA02274; Sun, 8 Mar 1998 02:00:27 -0500 (EST) (envelope-from toor) Message-Id: <199803080700.CAA02274@dyson.iquest.net> Subject: Re: current vm changes In-Reply-To: from Manfred Antar at "Mar 7, 98 10:36:11 pm" To: root@mantar.slip.netcom.com (Manfred Antar) Date: Sun, 8 Mar 1998 02:00:27 -0500 (EST) Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG 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-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Manfred Antar said: > I've been getting a few messages like this from a kernel built > tonite > vm_fault: pager input (probably hardware) error, PID 28996 failure > Mar 7 22:27:22 mantar /kernel: pid 28996 (in.cfingerd), uid 32767: exited > on signal 11 > spec_getpages: I/O read failure: (code=0) > vm_fault: pager input (probably hardware) error, PID 29047 failure > Mar 7 22:28:29 mantar /kernel: pid 29047 (make), uid 0: exited on signal > 11 (core dumped) > I am working on it, should have better diagnostics, and possible fix in an hour or so. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Mar 7 23:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17928 for freebsd-smp-outgoing; Sat, 7 Mar 1998 23:24:47 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17858; Sat, 7 Mar 1998 23:24:38 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id XAA10057; Sat, 7 Mar 1998 23:24:34 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sat, 7 Mar 1998 23:24:33 -0800 (PST) From: Manfred Antar To: "John S. Dyson" cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: current vm changes In-Reply-To: <199803080700.CAA02274@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 8 Mar 1998, John S. Dyson wrote: > Manfred Antar said: > > I've been getting a few messages like this from a kernel built > > tonite > > vm_fault: pager input (probably hardware) error, PID 28996 failure > > Mar 7 22:27:22 mantar /kernel: pid 28996 (in.cfingerd), uid 32767: exited > > on signal 11 > > spec_getpages: I/O read failure: (code=0) > > vm_fault: pager input (probably hardware) error, PID 29047 failure > > Mar 7 22:28:29 mantar /kernel: pid 29047 (make), uid 0: exited on signal > > 11 (core dumped) > > > I am working on it, should have better diagnostics, and possible fix in > an hour or so. > All in all my machine seems to be working better. I have not been able to do a full make world without it locking up for about a week.And it's just about completed one now. Thanks much Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message