[ipxe-devel] SCSI 0x7ced5188 tag 18ae0008 status 02 overrun +4294967288 sense 70 key

Heinrich Schuchardt xypron.glpk at gmx.de
Sat Aug 26 13:42:40 UTC 2017


On 08/25/2017 11:11 PM, Michael Brown wrote:
> On 25/08/17 20:17, Heinrich Schuchardt wrote:
>> I have finally succeeded to get the network running when starting iPXE
>> from U-Boot. So we will be able to use iPXE on Raspberry Pi class
>> devices.
> 
> Awesome!
> 
>> SCSI 0x7ced5188 tag 18ae0004 status 02 overrun +4294967288 sense 70 key
>> 00 additional 2000
>> SCSI 0x7ced5188 tag 18ae0004 closed: Input/output error
>> (http://ipxe.org/1d704098)
> 
> That error message is bizarre, and looks like some kind of build system
> error.  The code generating it is:
> 
>     if ( response->overrun > 0 ) {
>         overrun = response->overrun;
>         DBGC ( scsidev, " overrun +%zd", overrun );
>     } ...
> 
> response->overrun is an ssize_t, which should be a signed 32-bit integer
> on the 32-bit ARM build.  It should be impossible to end up with
> "overrun +4294967288", since 4294967288=0xfffffff8, which should not
> pass the "> 0" test for a signed 32-bit number.
> 
> Could you check that your compiler is generating sensible code?  For
> example, apply the attached patch and then check the assembly code
> generated for scsicmd_wtf():
> 
>   make -j 16 bin-arm32-efi/scsi.s
>   grep -A20 wtf bin-arm32-efi/scsi.s
> 
> 
> Could you also capture the network traffic for the failed iSCSI
> connection attempt with wireshark, and send the .pcap file?
> 
> Thanks,
> 
> Michael

Hello Michael,

the problem was that I did not specify the LUN and iPXE tried to read
from LUN 0 which is the controller. With the LUN specified as 1 I
reached "Registered SAN device 0x80".

Sorry for the noise.

Best regards

Heinrich



More information about the ipxe-devel mailing list