On Sat, Apr 2, 2022 at 1:27 PM Jonathan Chen <[email protected]> wrote:
> Hi, > > I recently updated 13/stable (stable/13-n250195-26e8bb3a4e1), and I'm > now seeing the following messages on boot: > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > Root mount waiting for: CAM > ahcich5: AHCI reset: device not ready after 31000ms (tfd = 0000ff7f) > (aprobe3:ahcich5:0:15:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00 > 00 00 00 00 > (aprobe3:ahcich5:0:15:0): CAM status: ATA Status Error > (aprobe3:ahcich5:0:15:0): ATA status: f7 (BSY DRDY DF SERV CORR IDX > ERR), error: ff (ICRC UNC MC IDNF MCR ABRT NM ILI) > (aprobe3:ahcich5:0:15:0): RES: f7 ff ff ff ff ff ff ff ff ff ff > (aprobe3:ahcich5:0:15:0): Error 5, Retries exhausted > (aprobe0:ahcich5:0:0:0): NOP FLUSHQUEUE. ACB: 00 00 00 00 00 00 00 00 > 00 00 00 00 > (aprobe0:ahcich5:0:0:0): CAM status: ATA Status Error > (aprobe0:ahcich5:0:0:0): ATA status: f7 (BSY DRDY DF SERV CORR IDX > ERR), error: ff (ICRC UNC MC IDNF MCR ABRT NM ILI) > (aprobe0:ahcich5:0:0:0): RES: f7 ff ff ff ff ff ff ff ff ff ff > (aprobe0:ahcich5:0:0:0): Error 5, Retries exhausted > > The system boots up fine after this. > > Is this a regression, or an indication that my hardware is failing? > If this was after a power on, maybe it indicates your drive on channel 5 of the ahci controller took too long to spin up? If this was a normal reboot, then it may suggest trouble the drive is having. Or this is a new bug that I've not seen a similar failure before like this... If you reboot your old kernel, do you see this too? Warner
