Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752132AbbHGK3h (ORCPT ); Fri, 7 Aug 2015 06:29:37 -0400 Received: from trent.utfs.org ([94.185.90.103]:60500 "EHLO trent.utfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751069AbbHGK3f (ORCPT ); Fri, 7 Aug 2015 06:29:35 -0400 Date: Fri, 7 Aug 2015 03:29:31 -0700 (PDT) From: Christian Kujau To: linuxppc-dev@ozlabs.org cc: linux-kernel@vger.kernel.org Subject: 4.1-rc6: ATA link is slow to respond, please be patient Message-ID: User-Agent: Alpine 2.20.8 (DEB 77 2015-05-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-AV-Checked: ClamAV using ClamSMTP (127.0.0.1 (trent) at Fri Aug 7 12:29:31 2015 +0200 (CEST)) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2668 Lines: 65 Hi, this PowerBook G4 was running 3.16 for a while but now I wanted to upgrade to latest mainline. However, during bootup the following happens: =============================== [ 2.237102] ata1: PATA max UDMA/100 irq 39 [ 2.401708] ata1.00: ATA-8: SAMSUNG HM061GC, LR100-10, max UDMA/100 [ 2.401764] ata1.00: 117231408 sectors, multi 16: LBA48 [ 2.417633] ata1.00: configured for UDMA/100 [ 44.918102] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 44.920452] ata1.00: failed command: READ DMA [ 44.922725] ata1.00: cmd c8/00:88:64:c2:12/00:00:00:00:00/e0 tag 0 dma 69632 in [ 44.927257] ata1.00: status: { DRDY } [ 49.971784] ata1.00: qc timeout (cmd 0xec) [ 49.976529] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 49.978908] ata1.00: revalidation failed (errno=-5) [ 55.019662] ata1: link is slow to respond, please be patient (ready=0) [ 60.007677] ata1: device not ready (errno=-16), forcing hardreset [ 60.012670] ata1: soft resetting link [ 60.193638] ata1.00: configured for UDMA/100 [ 60.196158] ata1.00: device reported invalid CHS sector 0 [ 60.198610] ata1: EH complete =============================== This happens only once, but systemd thinks there's a hard problem and will drop to a recovery shell. I can start sshd and login remotely and then the system appears to be running just fine. This happened in 4.2.0-rc5 so I went back a few versions and found that 4.1-rc5 was OK (the error does not show up and the system boots just fine) and 4.1-rc6 is not. Unfortunately a git-bisect between these two versions went completly off the charts, I don't know what happened here: ================================== first bad commit: 0fa372b6c95013af1334b3d5c9b5f03a70ecedab is the first bad commit commit 0fa372b6c95013af1334b3d5c9b5f03a70ecedab Author: Takashi Iwai Date: Wed May 27 16:17:19 2015 +0200 ALSA: hda - Fix noise on AMD radeon 290x controller ================================== I don't have this driver (or ALSA) even selected. I can reproduce this error pretty reliably and I'd like to attempt another git-bisect run when I'm more awake. But maybe somebody recognizes this error and has a hint where this could come from? dmesg & .config: http://nerdbynature.de/bits/v4.1-rc6/ Thanks, Christian. -- BOFH excuse #225: It's those computer people in X {city of world}. They keep stuffing things up. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/