Re: port-atari/39965: "lock error" panic on install with Atari TT030

["David Ross" <dross%pobox.com@localhost>]

Wow, we're up to three Davids now, this might get confusing.  =)

Ok, so here are the answers to David Brownlee's questions b) and c) earlier 
in the bug report.

b)  Same as before but install via CD-ROM.  I used the 11/20 ATARITT HEAD 
built kernel.  No networking set up.
Result: not exactly the same panic but consistent with the "lock error" 
panic in terms of when it occurred.

Screenshot:
http://i38.tinypic.com/2s7if0k.jpg

c)  Same as b) but with BOOTX kernel.  No networking set up.
Result: mostly the same as b)...  Different panic but consistent with the 
"lock error" panic in terms of when it occurred.

Screenshots:
http://i33.tinypic.com/2enx6zb.jpg
http://i37.tinypic.com/okwraw.jpg
http://i37.tinypic.com/281vpyg.jpg

Sorry about the fuzzyness of the second shot.  Most of it is duplicative 
with the third shot which is much sharper.

David (Holland), if there's a better place to upload the screenshots so you 
don't feel compelled to transcribe them, please let me know!  =)

David Ross
dross%pobox.com@localhost


----- Original Message ----- 
From: "David Holland" <dholland-bugs%netbsd.org@localhost>
To: <dross%pobox.com@localhost>; <gnats-bugs%netbsd.org@localhost>
Cc: <port-atari-maintainer%netbsd.org@localhost>; <gnats-admin%netbsd.org@localhost>; 
<netbsd-bugs%netbsd.org@localhost>
Sent: Thursday, November 27, 2008 3:31 PM
Subject: Re: port-atari/39965: "lock error" panic on install with Atari 
TT030


> On Thu, Nov 20, 2008 at 06:10:00AM +0000, dross%pobox.com@localhost wrote:
> > Screen shots:
> > http://i38.tinypic.com/2j5aqf.jpg
> > http://i38.tinypic.com/ml791x.jpg
> > http://i37.tinypic.com/9746de.jpg
>
> Transcription for posterity, just in case.
>
> It doesn't look machine-specific to me, unless the root cause is e.g.
> a problem with the locking primitives.
>
>  --------
>
>   :
>   :
> local: base.tgz remote: base.tgz
> 227 Entering Passive Mode (204,152,190,13,217,124)
> panic: lock error
> Stopped in pid 54.1 (ftp) at    netbsd:cpu_Debugger+0x6:   unlk  a6
> db> tr
> cpu_Debugger(2c26c0,0,1a566c,287d72c,287d738) + 6
> panic(2596eb,170a000,2c26c0,0,287d750) + 172
> lockdebug_abort(2c26c0,2718f0,24556f,245527) + 6c
> mutex_abort(2c26c0,24556f) + 28
> mutex_spin_enter(?)
> mutex_enter(2c26c0,287d79c,202568,414cf4,0) + ba
> brelse(414cf4,0,310ccc4) + a
> biodone2(414cf4) + ae
> biodone(414cf4,30b44d4,fccba0,30b4408,4000,0) + 92
> sddone(405ec0,0) + 78
> scsipi_complete(405ec0) + 162
> scsipi_done(405ec0) + 18c
> run_main(2861860) + b72
> ncr_ctrl_intr(2861860,287d8b4,251a,2000,fffffffb) + ba
> scsi_ctrl(2000) + 48
> nfp2_5380(?)
> brelsel(41508c,0,2c26c0,287d8e4,203018) + 10
> brelse(41508c,0,310dbc4) + 18
> bdwrite(41508c,5c1bcc) + 92
> ffs_alloccg(310f3f4,2c,0,3f34b0,4000) + 25c
> ffs_hashalloc(310f3f4,2c,0,3f34b0,4000,0,45b12) + 30
> ffs_alloc(310f3f4,0,f,0,3f34b0,4000,0,1709ec0,287db28,310f3f4,0,f,3,0,31bcc) 
> + 142
> ffs_balloc_ufs1(310cb44,0,3c00,3a20,1709ec0,0,0) + fc8
> ffs_balloc(310cb44,0,3c000,3a20,1709ec0,0,0) + a2
> ufs_gop_alloc(310cb44,0,3c00,0,3a20,0,1709ec0,310cb44,310cb44) + 88
> ufs_balloc_range(310cb44,0,3c000,0,3a20,1709ec0,0) + 1f6
> ffs_write(287de40,260920,310cb44,287deb8,10) + 912
> VOP_WRITE(310cb44,287db8,10,1709ec0,310cb44,20002) + 32
> vn_write(3101d50,3101d50,287deb8,1709ec0,1) + 96
> dofilewrite(5,3101d50,4228000,7a20,3101d50,1,287df78) + 64
> sys_write(170a000,287df38,287df78,0,9f) + 4c
> syscall_plain(4,170a000,287dfb4,4228000,7a20) + c2
> syscall(4) + 78
> trap0() + e
> db>
>
> --
> David A. Holland
> dholland%netbsd.org@localhost