On Fri, Feb 04, 2005 at 10:29:30PM +0100, Kurt Schreiner wrote:
> sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST373307LW, 0007> disk fixed
> sd0: 70007 MB, 49855 cyl, 4 head, 718 sec, 512 bytes/sect x 143374744 sectors
> sd0: sync (6.25ns offset 63), 16-bit (320.000MB/s) transfers, tagged queueing
> sd1 at scsibus1 target 0 lun 0: <SEAGATE, ST373307LW, 0007> disk fixed
> sd1: 70007 MB, 49855 cyl, 4 head, 718 sec, 512 bytes/sect x 143374744 sectors
> sd1: sync (6.25ns offset 63), 16-bit (320.000MB/s) transfers, tagged queueing
> sd0(ahd0:0:0:0): adapter resource shortage
> sd0(ahd0:0:0:0): adapter resource shortage
> sd0(ahd0:0:0:0): adapter resource shortage
> sd0(ahd0:0:0:0): adapter resource shortage
> sd0(ahd0:0:0:0): adapter resource shortage
> findroot: unable to read block 4294967296
> sd1(ahd1:0:0:0): adapter resource shortage
> sd1(ahd1:0:0:0): adapter resource shortage
> sd1(ahd1:0:0:0): adapter resource shortage
> sd1(ahd1:0:0:0): adapter resource shortage
> sd1(ahd1:0:0:0): adapter resource shortage
> findroot: unable to read block 4294967296
> 
> There was a thread on similar problems w/ ahc on i386/alpha/sgi some time
> (2001?) ago.
> This doesn't seem to be a real problem (AFAICS) as the machine runs fine
> w/o any complaints (just build a new "world" and kernel), it's only spewing
> this messages during boot...
> 
> If I can do anything to help getting rid of this anoyance, just let me
> know.

It appears that there is a bug in the higher level code somewhere that
was introduced recently. It's passing bogus parameters to SCSI drivers.
See Nicolas Joly's message on current-users today.

- Frank