When compiling a kernel with MAXMEM set to (128*1024) or (256*1024), an error message occurs during boot of the system: /kernel: de0 <Digital 21041 Ethernet> 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
State Changed From-To: open->feedback Can you please verify this is still valid? The de driver has been updated.
State Changed From-To: feedback->closed Originator confirms closure.