From owner-freebsd-bugs Mon Feb 3 15:30:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27867 for bugs-outgoing; Mon, 3 Feb 1997 15:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA27861; Mon, 3 Feb 1997 15:30:02 -0800 (PST) Date: Mon, 3 Feb 1997 15:30:02 -0800 (PST) Message-Id: <199702032330.PAA27861@freefall.freebsd.org> To: freebsd-bugs Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: kern/2649: accessing floppy using wrong major number causes crash at next access Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2649; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: javaman@halcyon.com Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/2649: accessing floppy using wrong major number causes crash at next access Date: Tue, 4 Feb 1997 00:26:13 +0100 As javaman@halcyon.com wrote: > Accessing the floppy using the wrong /dev/fdX.XXXX will cause a crash > at the next access. I was using mtools at the time, but I have repeated (Btw. that's the minor number, not the major number. Nevermind.) > Fatal Trap 9: general protection fault while in kernel mode > instruction pointer = 0x8:0xf010def1 > stack pointer = 0x10: 0xefbffd64 > frame pointer = 0x10: 0xefbffd8c > code segment = base 0x0, limit 0xfffff, type 0x1b > processor eflags = interrupt enabled, resume, IOPL=0 > int mask = net tty bio > panic: general protection fault I've never seen this, and be assured, i also use mtools every now and then... Again, do a nm /kernel | sort | more and extract the region around 0xf010def1. What makes me wonder is the GP fault. This is something concerning the dreaded segment registers... maybe Bruce's got an idea offhand. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)