Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!wuarchive!udel!mmdf
From: archer%segin4.segin.fr@relay.prime.com (Vincent Archer)
Newsgroups: comp.os.minix
Subject: Problems with ST 1.5.10/3's fd0
Message-ID: <35536@nigel.ee.udel.edu>
Date: 6 Nov 90 07:43:32 GMT
Sender: mmdf@ee.udel.edu
Lines: 34

To be quick here's the problem:

* If I access the drive using sd0/dd0, there's no problem. Everything works
  fine.

* Using a disk that I just read thru dd0 (and that has a correct boot sector
  too - I checked that), and trying to open fd0 (major/minor 2/16):

  - I get an EINVAL error at the open time.
  - I've got five seconds to leave the room, because the kernel's blowing up
    :-)

    >	Kernel panic: trap via vector 11
    >
    >	Push RESET button

    :-(

* Sometimes (don't know how), I'm able to open the disk. Then to read the
  disk's content. But I'm not happy yet, because, guess what happens...
  Gotcha, a kernel panic!


From stmain.c, I know that this is a SIGEMT event (obsolete? It's just brand
new :-), but that the processor is in SUPERVISOR mode (i.e. in the kernel).

Any bright ideas?

_________
 |\___/|	Vincent Archer
 | \ / |	Email: archer%segin4.segin.fr@relay.prime.com
 | /|\ |
 |// \\|
-+-----+-	"Time is running fast..."