Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!pipex!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.bugs Subject: Re: ptdi 4f324a6a Message-ID: <C653DM.9q@veda.is> Date: 27 Apr 93 11:17:31 GMT References: <C6299E.1Gw@veda.is> Organization: Veda Systems, Iceland Lines: 28 I wrote: >After building the 0.1.2.3 kernel, if any of the new devices are configured >in, I get the message "ptdi 4f324a6a" and the machine crashes after pressing >a key. Sometimes it just crashes without doing the ptdi diagnosis. Utter garbage! This was happening because the kernel size was approaching 640k. The kernel still loaded but fell flat on its face because of memory tightness. >The 4th serial port is hopeless at irq2, this conflicts with the ethernet >card at irq9 and crashes immediately. Utter garbage! I just built a kernel with some features disabled and the 4th serial port enabled on irq2 (It gets found at irq9, like the ethernet). It seems to work now, so previously it was failing entirely due to memory tightness. How come the ethernet and serial port can share an interrupt without any conflict, when 2 serial ports can't even do this right? Why should the kernel run into problems when it is almost 640k in size? It still fits in 640k after all (text, data, bss). Is there a stack that gets clobbered just below the 640k boundary? Please someone tell me how to get a kernel to work that is loaded at 0x00100000. -- Adam D. (adam@veda.is)