Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:681 comp.os.386bsd.questions:2203 Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!nigel.msen.com!math.fu-berlin.de!informatik.tu-muenchen.de!regent!gjung From: gjung@guug.de (Guenter Jung) Subject: Re: [386bsd] can't mount cdrom after PK-0.2.3 Message-ID: <gjung.736593150@guug.de> Summary: wrong pointer to "isofs_mount" in "vfssw" Keywords: cdrom 386bsd patchkit-0.2.3 Sender: news@regent.e-technik.tu-muenchen.de (News System.) Organization: Technical University of Munich, Germany Date: Wed, 5 May 1993 09:12:30 GMT Lines: 14 I wrote: > I have installed patchkit-0.2.3 and now I can't mount my cdrom anymore. > ... OK, I have investigated the problem a little further. The reason for "isofs_mount" getting the wrong parameters is that the pointer to "isofs_mount" in "vfssw" is wrong. It seams that this pointer is incremented somewhere. When I have patch10002 (npx-5.0) installed it is incremented twice leading to a wrong stackframe, when I don't have patch10002 installed it is incremented once leading to a kernel-panic. Since the pointer to "isofs_mount" is right just before "npxattach" and wrong after it, the problem seams to be somewhere in "npxattach" Guenter Jung gjung@guug.de