In message <4478.927463...@axl.noc.iafrica.com>, Sheldon Hearn writes:
>
>
>On Sun, 23 May 1999 11:32:27 +0200, Poul-Henning Kamp wrote:
>
>> Can somebody please try if this fixes MFS ?
>
>Do you want your patch applied alongside Luoqi Chen's patch to
>kern_conf.c from last week? I've been able to
On Sun, 23 May 1999 11:32:27 +0200, Poul-Henning Kamp wrote:
> Can somebody please try if this fixes MFS ?
Do you want your patch applied alongside Luoqi Chen's patch to
kern_conf.c from last week? I've been able to mount_mfs without problems
since then.
Ciao,
Sheldon/
To Unsubscribe: send m
Can somebody please try if this fixes MFS ?
Poul-Henning
Index: ufs/mfs/mfs_vfsops.c
===
RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vfsops.c,v
retrieving revision 1.63
diff -u -r1.63 mfs_vfsops.c
--- mfs_vfsops.c1999/05/14 20:
On Wed, 19 May 1999 17:40:50 +1000, Bruce Evans wrote:
> so you must be using the old wd driver. The old wd_driver's d_dump
> only returns ENXIO when the drive doesn't exist or has never been
> opened or is not labeled.
I'm using the "old" wd driver (controller wdc in CURRENT). The disk is
lab
>> >dumping to dev (0, 131089), offset 524288
>> >dump device bad
>>
>> The dev_t changes obfuscated it by printing it in %d format instead of
>> as part of the dev number in [0x]%x format.
>
>So you reckon that whatever problem is making it imp[ossible for me to
>take dumps, it was present before
On Wed, 19 May 1999 12:04:54 +1000, Bruce Evans wrote:
> >dumping to dev (0, 131089), offset 524288
> >dump device bad
>
> The dev_t changes obfuscated it by printing it in %d format instead of
> as part of the dev number in [0x]%x format.
So you reckon that whatever problem is making it imp[o
>I think I know why a lot of people _aren't_ seeing this panic: it
>doesn't show up if you #undef DEVT_FASCIST in kern/kern_conf.c .
#undef DEVT_FASICIST weakens tthe error detection.
>I found this by accident because I can't get a crash dump using the wd
>driver. I get
>
>dumping to dev (0, 131
On Tue, 18 May 1999 08:53:49 +0200, Sheldon Hearn wrote:
> I remade world and kernel (config -g -r) with yesterday's HEAD and still
> get a panic mounting MFS. My kernel config includes MFS but not
> MFS_ROOT.
>
> Shout if you want a trace. I haven't provided one here, since I'll need
> to copy
On Mon, 17 May 1999 13:02:29 -0400, Luoqi Chen wrote:
> Are you sure you have the latest -current? I committed a fix Friday
> night.
Hi Luoqi,
I remade world and kernel (config -g -r) with yesterday's HEAD and still
get a panic mounting MFS. My kernel config includes MFS but not
MFS_ROOT.
Sho
On Mon, May 17, 1999 at 03:37:36PM -0400, Luoqi Chen wrote:
> If you don't have `options MFS' in your config file, you will need to
> recompile the mfs kld module.
I know, I did that this evening (did a make world/kernel rebuild around 8pm
CEST):
-r-xr-xr-x 1 root wheel 12874 May 17 21:20 mfs
> On Mon, May 17, 1999 at 01:02:29PM -0400, Luoqi Chen wrote:
> > Are you sure you have the latest -current? I committed a fix Friday night.
>
> I'm quite positive, because I experimented with a fresh -current/kernel
> yesterday. Changing NUMCDEV from 256 to 255 in kern_conf.c fixes the problem
>
On Mon, May 17, 1999 at 01:02:29PM -0400, Luoqi Chen wrote:
> Are you sure you have the latest -current? I committed a fix Friday night.
I'm quite positive, because I experimented with a fresh -current/kernel
yesterday. Changing NUMCDEV from 256 to 255 in kern_conf.c fixes the problem
though. I'm
> With todays -current, mounting /tmp using
> swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0
> yields a
>
Are you sure you have the latest -current? I committed a fix Friday night.
-lq
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Sun, May 16, 1999 at 01:36:44PM -0700, Doug White wrote:
> I've been getting this for a week now. :( Luoqui Chen suggested bumping
> NUMCDEV in src/sys/kern/kern_conf.c to 255 to get around it, and a couple
> of people had success, including myself.
I'll do that then. Thanks!
Groetjes,
--
J
On Sun, 16 May 1999, Jos Backus wrote:
> With todays -current, mounting /tmp using
> swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0
> yields a
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address= 0x9d203590
I've been getting this for a week now. :( Luoqui Chen suggested b
15 matches
Mail list logo