From owner-freebsd-bugs Fri Jul 21 01:18:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id BAA15113 for bugs-outgoing; Fri, 21 Jul 1995 01:18:09 -0700 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id BAA15107 for ; Fri, 21 Jul 1995 01:18:05 -0700 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from omega.physik.fu-berlin.de (130.133.3.51) with smtp id ; Fri, 21 Jul 95 10:17 MEST Received: by omega.physik.fu-berlin.de; id AA25956; Fri, 21 Jul 1995 10:17:53 +0200 From: Thomas Graichen Message-Id: <9507210817.AA25956@omega.physik.fu-berlin.de> Subject: 3 ways to crash FreeBSD (2.0.5 and 950412-SNAP) To: bugs@freebsd.org Date: Fri, 21 Jul 1995 10:17:53 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4107 Sender: bugs-owner@freebsd.org Precedence: bulk hello - here are my 3 ways to crash FreeBSD: * simply hit ctrl-alt-del while booting multiple times -> at the probes of the floppies and/or the wd drives the system stops with a panic (i'va also managed it to panic the system TWICE at once) - this is total reproducable - if it is'nt for you - please send me a mail and i'll give you any more information you need (this happens on 950412-SNAP and 2.0.5 RELEASE) * simply do the following as root at the console: modload -u -o /tmp/saver_mod -e saver_init -q /lkm/${saver}_saver_mod.o modload -u -o /tmp/saver_mod -e saver_init -q /lkm/${saver}_saver_mod.o (this will giva an error) modunload -n star_saver this is also total reproducable on 950412-SNAP and 2.0.5 RELEASE and leads also to a kernel panic * the last is a problem i have since the early january SNAP's - this is what i've written some times before to jordan: the system crashes then i log in (but couriously not if somebody else or root does this) via xdm - /var/log/messages says Feb 9 10:49:44 julia /vmunix: Error in getattr: 70 Feb 9 10:49:45 julia /vmunix: Feb 9 10:49:45 julia /vmunix: Feb 9 10:49:45 julia /vmunix: Fatal trap 12: page fault while in kernel mode Feb 9 10:49:45 julia /vmunix: fault virtual address = 0x40 Feb 9 10:49:45 julia /vmunix: fault code = supervisor read, page not present Feb 9 10:49:45 julia /vmunix: instruction pointer = 0x8:0xf0125b1b Feb 9 10:49:45 julia /vmunix: code segment = base 0x0, limit 0xffff f, type 0x1b Feb 9 10:49:45 julia /vmunix: = DPL 0, pres 1, def32 1, gran1 Feb 9 10:49:45 julia /vmunix: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 9 10:49:45 julia /vmunix: current process = 122 (xdm) Feb 9 10:49:45 julia /vmunix: interrupt mask = Feb 9 10:49:46 julia /vmunix: panic: page fault Feb 9 10:49:46 julia /vmunix: Feb 9 10:49:46 julia /vmunix: syncing disks... 28 28 25 21 16 10 1 done its absolutely reproducable: reboot - xdm is started - i try to login - the xdm login window disappears - i here the disk writing the coredump - but the problem did'nt appear if somebody else logs in (who has his homedirectory on another machine - but both dec alpha's osf/1 3.0 - we are mounting the homedirs via amd with nfs) - my nfs-homedir-server says: Feb 9 10:45:48 sirius vmunix: NFS server: stale file handle fs(8,2054) file 116839 gen 792314558 Feb 9 10:45:48 sirius vmunix: getattr, client address = 130.133.3.235, errno 22 it only happens sometimes - but if - it will happen at any try to login after the system has rebooted after that panic - loging in as root and doing a "su - myusername" then logout and login as me works then - if you need any more information - please send a mail to me (by the way - we have some problems with our net - because our net-segment is too long - but this should max. result in an but not in an kernel panic!) * and one last thing: we mount all our homedir's via amd - which mounts them if they are needed (user logs in) and tries to unmount them automatic if they are no longer used - but FreeBSD seems to loose the directories from time to time - that means the directory will be mounted again and again (this way i sometimes get 20 times the same dir mounted) - and after each of these overmountings i get an "getting cwd failed" from my tcsh (because the directory is new ... mounted) - do you have any ideas ? to all the points above - i'll try to give you all the information you need and as far as i can all the help i may give you - thanks in advance - t _______________________________________________________||_____________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| ___________________________||____email: graichen@omega.physik.fu-berlin.de____