Re: panic: page fault (apparently caused by mount_mfs)
Yep! The patch seems to have fixed the problem! :-)
Thanks Luoqi!!
Bob
On Mon, May 17, 1999 at 11:42:21PM -0400, Luoqi Chen wrote:
> > I have been making world each time after cvsupping so I would expect the
> > mfs kld module to be getting rebuilt and it appears to be up-to-date:
> >
> > -r-xr-xr-x 1 root wheel 12778 May 17 13:34 /modules/mfs.ko
> >
> > Also, both my custom kernel config file and the GENERIC config file
> > include "options MFS" so mfs should not be getting loaded, right?
> >
> > Thanks,
> > Bob
> >
> > >
> > > -lq
> >
> > --
> > Bob Willcox The man who follows the crowd will usually get no
> > b...@luke.pmr.comfurther than the crowd. The man who walks alone is
> > Austin, TX likely to find himself in places no one has ever
> > been.-- Alan Ashley-Pitt
> >
> Would you try this patch?
>
> Index: kern_conf.c
> ===
> RCS file: /home/ncvs/src/sys/kern/kern_conf.c,v
> retrieving revision 1.39
> diff -u -r1.39 kern_conf.c
> --- kern_conf.c 1999/05/12 13:06:34 1.39
> +++ kern_conf.c 1999/05/18 03:27:36
> @@ -182,7 +182,7 @@
> uintptr_t i = (uintptr_t)x;
>
> #ifdef DEVT_FASCIST
> - return(253 - ((i >> 8) & 0xff));
> + return(255 - ((i >> 8) & 0xff));
> #else
> return((i >> 8) & 0xff);
> #endif
> @@ -200,7 +200,7 @@
> makedev(int x, int y)
> {
> #ifdef DEVT_FASCIST
> -return ((dev_t) (((253 - x) << 8) | y));
> +return ((dev_t) (((255 - x) << 8) | y));
> #else
> return ((dev_t) ((x << 8) | y));
> #endif
--
Bob Willcox The man who follows the crowd will usually get no
b...@luke.pmr.comfurther than the crowd. The man who walks alone is
Austin, TX likely to find himself in places no one has ever
been.-- Alan Ashley-Pitt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 04:34:50PM -0400, Luoqi Chen wrote: > > Hi, > > > > I have been getting a panic lately with every -current kernel that I > > have built for the past week or so (-current cvsupped daily). Even the > > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > > filesystem is attempted. If I boot an old kernel from 5/11 or remove > > the fstab entry for the mfs file system the system boots up okay. My > > fstab entry for this is: > > > > /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 > > > > and the panic messages are: > > > > Fatal trap 12: pagefault while in kernel mode > > fault virtual address = 0x9d334e68 > > fault code = Supervisor read, page not present > > instruction pointer = 0x8:0xc0185cb0 > > stack pointer = 0x10:0xc98ad84 > > frame pointer = 0x10:0xc98adb0 > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags= interrupt enabled, resume, IOPL = 0 > > current process = 40 (mount_mfs) > > interrupt mask = > > trap number = 12 > > panic: page fault > > > > > > Any ideas on what may be wrong? > > > > Thanks, > > Bob > > > > -- > > Bob Willcox The man who follows the crowd will usually get no > > b...@luke.pmr.comfurther than the crowd. The man who walks alone is > > Austin, TX likely to find himself in places no one has ever > > been.-- Alan Ashley-Pitt > > > How about recompile mfs kld module and try again? I have been making world each time after cvsupping so I would expect the mfs kld module to be getting rebuilt and it appears to be up-to-date: -r-xr-xr-x 1 root wheel 12778 May 17 13:34 /modules/mfs.ko Also, both my custom kernel config file and the GENERIC config file include "options MFS" so mfs should not be getting loaded, right? Thanks, Bob > > -lq -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 01:47:59PM -0700, Matthew Jacob wrote: > > > > > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > > > > > swap/tmpmfs rw,-s=200 0 > > > > > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > > > some trouble? > > > > Unfortunately, changing from /dev/da0s1b to swap didn't help. I also > > tried it without the nosuid option but it still panics. > > > > Hmm. Is MFS a module as Luoqi keeps mentioning? How much real memory do > you have? I believe it is in the kernel (the GENERIC kernel includes it as well as my customized kernel config file). This system has 256MB. > > > See- it's been working fine for me! Yep. I am going to try re-checking out all of the current sources and see if that helps. Perhaps something is hosed with my source tree. Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
> > > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > > > swap/tmpmfs rw,-s=200 0 > > > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > > some trouble? > > Unfortunately, changing from /dev/da0s1b to swap didn't help. I also > tried it without the nosuid option but it still panics. > Hmm. Is MFS a module as Luoqi keeps mentioning? How much real memory do you have? See- it's been working fine for me! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 01:03:50PM -0700, Matthew Jacob wrote: > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > swap/tmpmfs rw,-s=200 0 > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > some trouble? Unfortunately, changing from /dev/da0s1b to swap didn't help. I also tried it without the nosuid option but it still panics. Bob > > > On Mon, 17 May 1999, Bob Willcox wrote: > > > Hi, > > > > I have been getting a panic lately with every -current kernel that I > > have built for the past week or so (-current cvsupped daily). Even the > > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > > filesystem is attempted. If I boot an old kernel from 5/11 or remove > > the fstab entry for the mfs file system the system boots up okay. My > > fstab entry for this is: > > > > /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 > > > > and the panic messages are: > > > > Fatal trap 12: pagefault while in kernel mode > > fault virtual address = 0x9d334e68 > > fault code = Supervisor read, page not present > > instruction pointer = 0x8:0xc0185cb0 > > stack pointer = 0x10:0xc98ad84 > > frame pointer = 0x10:0xc98adb0 > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags= interrupt enabled, resume, IOPL = 0 > > current process = 40 (mount_mfs) > > interrupt mask = > > trap number = 12 > > panic: page fault > > > > > > Any ideas on what may be wrong? > > > > Thanks, > > Bob > > > > -- > > Bob Willcox The man who follows the crowd will usually get no > > b...@luke.pmr.comfurther than the crowd. The man who walks alone is > > Austin, TX likely to find himself in places no one has ever > > been.-- Alan Ashley-Pitt > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > with "unsubscribe freebsd-current" in the body of the message > > -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
> Hi, > > I have been getting a panic lately with every -current kernel that I > have built for the past week or so (-current cvsupped daily). Even the > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > filesystem is attempted. If I boot an old kernel from 5/11 or remove > the fstab entry for the mfs file system the system boots up okay. My > fstab entry for this is: > > /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 > > and the panic messages are: > > Fatal trap 12: pagefault while in kernel mode > fault virtual address = 0x9d334e68 > fault code= Supervisor read, page not present > instruction pointer = 0x8:0xc0185cb0 > stack pointer = 0x10:0xc98ad84 > frame pointer = 0x10:0xc98adb0 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 40 (mount_mfs) > interrupt mask= > trap number = 12 > panic: page fault > > > Any ideas on what may be wrong? > > Thanks, > Bob > > -- > Bob Willcox The man who follows the crowd will usually get no > b...@luke.pmr.comfurther than the crowd. The man who walks alone is > Austin, TX likely to find himself in places no one has ever > been.-- Alan Ashley-Pitt > How about recompile mfs kld module and try again? -lq To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 01:03:50PM -0700, Matthew Jacob wrote: > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > swap/tmpmfs rw,-s=200 0 > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > some trouble? Don't know, but I will change it and see what happens. Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
I use mfs a lot and have had no trouble whatsoever. I'm using: swap/tmpmfs rw,-s=200 0 Do you suppose that the usage of /dev/da0s1b directly is what's causing some trouble? On Mon, 17 May 1999, Bob Willcox wrote: > Hi, > > I have been getting a panic lately with every -current kernel that I > have built for the past week or so (-current cvsupped daily). Even the > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > filesystem is attempted. If I boot an old kernel from 5/11 or remove > the fstab entry for the mfs file system the system boots up okay. My > fstab entry for this is: > > /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 > > and the panic messages are: > > Fatal trap 12: pagefault while in kernel mode > fault virtual address = 0x9d334e68 > fault code= Supervisor read, page not present > instruction pointer = 0x8:0xc0185cb0 > stack pointer = 0x10:0xc98ad84 > frame pointer = 0x10:0xc98adb0 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 40 (mount_mfs) > interrupt mask= > trap number = 12 > panic: page fault > > > Any ideas on what may be wrong? > > Thanks, > Bob > > -- > Bob Willcox The man who follows the crowd will usually get no > b...@luke.pmr.comfurther than the crowd. The man who walks alone is > Austin, TX likely to find himself in places no one has ever > been.-- Alan Ashley-Pitt > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
