the vinum module looks to have been the problem..
not ethat you had stack elements at 0xc101exxx
vinum starts at 0c1011000,
On Mon, 18 Oct 1999, Michael Reifenberger wrote:
> On Mon, 18 Oct 1999, Bernd Walter wrote:
> ...
> > What kind of modules were you running?
> (nullum)(root)# kldstat
> Id Refs Address Size Name
> 1 7 0xc0100000 1eb518 kernel
> 2 1 0xc02ec000 cdbc bktr.ko
> 3 1 0xc1011000 c3000 vinum.ko
> 4 1 0xc1111000 6000 procfs.ko
> 5 1 0xc1118000 8000 if_xl.ko
> 6 1 0xc1121000 7000 miibus.ko
> 7 1 0xc131e000 4c000 nfs.ko
> > Are these in sync with the kernel?
> Yes.
>
> Configuration hasnt changed for weeks.
>
> boottext is attached.
>
> Softupdates is on on all FS. (Wasn't a problem so far)
> (nullum)(root)# mount
> /dev/da0s1a on / (ufs, local, soft-updates, writes: sync 5 async 274)
> /dev/da0s1d on /usr (ufs, NFS exported, local, soft-updates, writes: sync 172
> async 5230)
> /dev/vinum/data on /mnt/data (ufs, NFS exported, local, soft-updates, writes:
> sync 2 async 0)
> /dev/vinum/oracle on /oracle (ufs, NFS exported, local, soft-updates, writes:
> sync 2 async 0)
> /dev/vinum/sapdaten on /oracle/NIL/sapdaten (ufs, local, soft-updates, writes:
> sync 2 async 0)
> /dev/vinum/sapmnt on /sapmnt (ufs, local, soft-updates, writes: sync 2 async 0)
> /dev/vinum/usr_sap on /usr/sap (ufs, NFS exported, local, soft-updates, writes:
> sync 2 async 0)
> procfs on /proc (procfs, local)
>
> Bye!
> ----
> Michael Reifenberger
> Plaut Software GmbH, R/3 Basis
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message