> I haven't seen vm_object_collapse(), but I didn't know to type
> 'trace' until your message.  
> 
> Same type of behaviour from GENERICSBC when I was incorrectly newfs'ing
> /dev/sd2c instead of /dev/sd2g.  Don't know about with xhfs.

Hmmm...I could see how the SCSI subsystem just might panic if you tried 
to newfs the interface to the entire disk...it might be messy... ;-)

> >About the only thing that might be useful from this point is for you to 
> >type up the printout from the debugger that occurs when you type 'trace' 
> >at the 'db>' prompt.
.
> ok, here are some more details:
> dinah-moe-dan (105)-% more /var/log/messages
> Apr  2 20:42:45 dinah-moe /netbsd: NetBSD 1.2.1 (GENERIC) #0: Mon Mar 17 18:10:55 PST 1997
> Apr  2 20:42:45 dinah-moe /netbsd:     scottr@red:/usr/src/sys/arch/mac68k/compile/GENERIC
> Apr  2 20:42:45 dinah-moe /netbsd: Apple Macintosh IIci  (68030)
> Apr  2 20:42:45 dinah-moe /netbsd: adb: extended mouse <LT01> 3-button 400 dpi mouse at 15

Logitech mouse, huh?  How well does it work?

> Apr  2 20:42:45 dinah-moe /netbsd: mainbus0 (root)
> Apr  2 20:42:45 dinah-moe /netbsd: obio0 at mainbus0
> Apr  2 20:42:45 dinah-moe /netbsd: adb0 at obio0 (ADB event device)
> Apr  2 20:42:45 dinah-moe /netbsd: asc0 at obio0 Apple sound chip.
> Apr  2 20:42:45 dinah-moe /netbsd: sd0 at scsibus0 targ 0 lun 0: <QUANTUM, LP80S  980809404, 3.3> SC
> SI2 0/direct fixed
> Apr  2 20:42:45 dinah-moe /netbsd: sd0: 80MB, 921 cyl, 4 head, 44 sec, 512 bytes/sec
> Apr  2 20:42:45 dinah-moe /netbsd: sd1 at scsibus0 targ 1 lun 0: <QUANTUM, FIREBALL1080S, 1Q09> SCSI
> 2 0/direct fixed
> Apr  2 20:42:45 dinah-moe /netbsd: sd1: 1042MB, 3835 cyl, 4 head, 139 sec, 512 bytes/sec
> Apr  2 20:42:45 dinah-moe /netbsd: sd2 at scsibus0 targ 3 lun 0: <SEAGATE, ST325N, \004\021\021> SCS
> I1 0/direct fixed
> Apr  2 20:42:45 dinah-moe /netbsd: sd2: 20MB, 654 cyl, 2 head, 32 sec, 512 bytes/sec
> Apr  2 20:42:45 dinah-moe /netbsd: probe(ncrscsi0:3:1): illegal request, data = 00 00 00 00 db 6d b6
>  db 6d b6 db 6d b6 db
> 
> NOTE,  the probe(ncrsci0:3:7) errors started when I added that 20M drive (woohoo, 2% increase
> in disk space).  I get similar errors on that drive during boot with sbc, but even with
> these error messages, the drive seems to work right....

It may just be that the 20MB drive is so old that it has some problems or 
doesn't implement the SCSI spec quite right (of course I'm kinda grasping 
at straws here...)

> Apr  2 20:55:55 dinah-moe /netbsd: sd0: mode sense (4) returned 
> nonsense; using fictitious geometry

Hmmm...I usually don't get these at all...

> dinah-moe-dan (105)-% /sbin/disklabel /dev/sd0a
> # /dev/sd0a:
> type: SCSI
> disk: SCSI disk
> label: fictitious
> flags:
> bytes/sector: 512
> sectors/track: 32
> tracks/cylinder: 64
> sectors/cylinder: 2048
> cylinders: 80
> total sectors: 164139
> rpm: 3600
> interleave: 1
> trackskew: 0
> cylinderskew: 0
> headswitch: 0           # milliseconds
> track-to-track seek: 0  # milliseconds
> drivedata: 0 
> 
> 2 partitions:
> #        size   offset    fstype   [fsize bsize   cpg]
>   a:   156270       96       HFS                        # (Cyl.    0*- 76*)
>   b:     7773   156366   unknown                        # (Cyl.   76*- 80*)
> disklabel: boot block size 0
> disklabel: super block size 0
> disklabel: warning, unused partition c: size 164139 offset 0
> 
> This drive is my 80mb mac only drive.  Under netbsd 1.1, I could access it
> via xhfs (although I seem to remember using /dev/sd0c).
> Now, when I run xfhs, I can open /dev/sd0a see my top level directory (mac),
> immediately close /dev/sd0a and then when I exit xhfs, I get
> 
> panic: kernel jump to zero
> Stopped at _Debugger + 0x6: unlk a6
> db> trace
> _Debugger (20eec,2e18,866edc,0,866f08) +6
> _panic (2e18,0,0,0,0) + 34
> _jmp0panic() + 12
> db> cont

Yeah, it would be real helpful if you typed 'trace' here instead of 
'cont' and we can see exactly where the problem is occuring...

> Syncing disks... 4 3 done
> NetBSD/mac68k does not trust itself to update the RTC on shutdown
> dumping to dev 409, offset 8
> dump 79 78 77 76 area improper
> (reboots hardware)
> 
> thanks for the reply Colin.  BTW, what does 'ender' mean?

The name Ender is from _Ender's_Game_ by Orson Scott Card.  If you like 
scifi, you should read it; it's really good.

Later.

-- 
Colin Wood                                      ender@is.rice.edu
Consultant                                        Rice University
Information Technology Services                       Houston, TX