Re: scsi freezing problem with NetBSD current

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

It turns out that the freeze was due to a cable plugged into the serial port 
(null modem to my PC).  Removing this allows the 1.6.1 and 4.0 HEAD 
netbsd-ATARITT kernels to boot just fine.  I didn't have to touch my nvram. 
I updated the PR by responding to the mail.

The other bug report on the sysinst.fs failure is here:
http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=39850

..however I must have accidently typed just "dross" instead of my full 
email address because I never got the automated mail and I see my e-mail 
address is incorrectly reported in the PR as dross%netbsd.org.@localhost  David, if 
you have access to correct this, please do, otherwise maybe it's best for me 
to just file a different PR.

In any case, I do have some new info...  I can't even load a known-good 
1.6.1 sysinst.fs from floppy with the 4.0 HEAD kernel.  It just loads 3 dots 
worth of data and freezes.  I'm using 'md2a' as the floppy device to load 
from, which has always worked in the past.

David Ross
dross%pobox.com@localhost


----- Original Message ----- 
From: "David Brownlee" <abs%absd.org@localhost>
To: <dross%pobox.com@localhost>
Cc: <abs%NetBSD.org@localhost>; <tjamaloo%gmail.com@localhost>; 
<port-atari%netbsd.org@localhost>
Sent: Sunday, November 02, 2008 3:15 AM
Subject: Re: scsi freezing problem with NetBSD current


> From: David Ross <dross%pobox.com@localhost>
>
> > Hmm, I just went back to try the 1.6.1 netbsd-ATARITT kernel and I see
> the
> > same garbled video issue.  (Again, no issue with the netbsd-BOOT kernel).
> > This used to work for sure...  I think I need to go reset my nvram, I'm
> not
> > sure what else could have caused this.
>
> Can you take a copy of you nvram contents before resetting - if it turns
> out to be the issue it would be good to have NetBSD handle it.
>
> > Also, there doesn't seem to be a way to delete a PR.  If anyone has the
> > power to delete port-atari/39849, please do, or at least add a comment
> that
> > it now seems to be an issue that's not netbsd version dependent but
> rather
> > dependent on some local machine configuration.  It's still a bug that
> this
> > would happen under any circumstances.
>
> You can reply to the original PR ack email and it will be appended to the
> PR.