[Bug 237261] Boot stuck in endless ATAPI_IDENTIFY attempts
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Apr 21 08:13:19 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237261
Andriy Gapon <avg at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs at FreeBSD.org |scsi at FreeBSD.org
--- Comment #6 from Andriy Gapon <avg at FreeBSD.org> ---
(In reply to Mikhail Teterin from comment #5)
Thank you!
So, we can see that the old stack also sees the phantom device, tries to
identify it and fails. But I guess that that happens rather quickly (?) and,
certainly, there are no endless retries. That seems to be the main difference
between the old code and the new one.
I would try to draw attention of CAM experts like Scott Long or Alexander Motin
or Kenneth Merry to this bug. I'll re-assign this bug to scsi@ as well.
Here are the relevant bits from the log:
ata1: <ATA channel 1> on atapci0
ata1: reset tp1 mask=03 ostat0=50 ostat1=00
ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: reset tp2 stat0=00 stat1=00 devices=0x30000
ata1: Identifying devices: 00030000
ata1: New devices: 00030000
ata1: reiniting channel ..
ata1: reset tp1 mask=03 ostat0=00 ostat1=00
ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: reset tp2 stat0=00 stat1=00 devices=0x30000
ata1: reinit done ..
unknown: FAILURE - ATAPI_IDENTIFY timed out LBA=0
ata1: reiniting channel ..
ata1: reset tp1 mask=03 ostat0=00 ostat1=00
ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: reset tp2 stat0=00 stat1=00 devices=0x30000
ata1: reinit done ..
unknown: FAILURE - ATAPI_IDENTIFY timed out LBA=0
And then success for the real device:
ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire
acd0: setting UDMA33
acd0: <UJDA755 DVD/CDRW/1.00> CDRW drive at ata1 as master
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-scsi
mailing list