From owner-freebsd-bugs Sat Sep 20 10:40:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17739 for bugs-outgoing; Sat, 20 Sep 1997 10:40:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17699; Sat, 20 Sep 1997 10:40:01 -0700 (PDT) Resent-Date: Sat, 20 Sep 1997 10:40:01 -0700 (PDT) Resent-Message-Id: <199709201740.KAA17699@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, beckmann@nacamar.net Received: from ns.nacamar.net (ns.nacamar.net [194.162.162.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA17633 for ; Sat, 20 Sep 1997 10:38:59 -0700 (PDT) Received: (from petzi@localhost) by ns.nacamar.net (8.8.6/8.8.5) id TAA02243; Sat, 20 Sep 1997 19:38:51 +0200 (MET DST) Message-Id: <199709201738.TAA02243@ns.nacamar.net> Date: Sat, 20 Sep 1997 19:38:51 +0200 (MET DST) From: petzi@nacamar.net Reply-To: beckmann@nacamar.net To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: kern/4589: de0: abnormal interrupt: receive process stopped Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Number: 4589 >Category: kern >Synopsis: de driver error message during boot >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Sep 20 10:40:00 PDT 1997 >Last-Modified: >Originator: Michael Beckmann >Organization: Nacamar >Release: FreeBSD 2.2-970918-RELENG i386 >Environment: Recent versions of 2.2-RELENG PCI Ethernet card driven by de driver >Description: When compiling a kernel with MAXMEM set to (128*1024) or (256*1024), an error message occurs during boot of the system: /kernel: de0 rev 17 int a irq 10 on pci0:9 /kernel: de0: 21041 [10Mb/s] pass 1.1 /kernel: de0: address 00:00:c0:94:e7:f8 /kernel: de0: enabling 10baseT port /kernel: de0: abnormal interrupt: receive process stopped This message does not occur when the kernel was compiled without the MAXMEM option. >How-To-Repeat: Problem occurs in various tested hardware confugurations. Ethernet cards used were various revisions of SMC EtherPower 10 Combo Typical kernel config file to reproduce the problem: # $Id: GENERIC,v 1.77.2.10 1997/06/06 12:24:17 jkh Exp $ machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident BLAH maxusers 128 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device #options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "MAXMEM=(128*1024)" config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 controller scbus0 device sd0 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 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 de0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device vn 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf 2 >Fix: >Audit-Trail: >Unformatted: