From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755826AbZC1KWh (ORCPT ); Sat, 28 Mar 2009 06:22:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753340AbZC1KWZ (ORCPT ); Sat, 28 Mar 2009 06:22:25 -0400 Received: from mail-ew0-f165.google.com ([209.85.219.165]:63355 "EHLO mail-ew0-f165.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753224AbZC1KWX (ORCPT ); Sat, 28 Mar 2009 06:22:23 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=HPkjQOgRv/breakqwq6HEfIhD2LcifOphJJQmZ8uHtddliedfLVBP0I/fSEObcESn9 TCLlK+JtWOj19W23Kt6X/2d5SEGBSUKHvnTlJt63fvcjEFycT0DGjrW61VyKzhhpj0k7 3Bmmhh1XBHdPETJx+a+Xesw8I5MBw+KyLv2Jk= Message-ID: <49CDFA60.9080403@gmail.com> Date: Sat, 28 Mar 2009 12:22:24 +0200 From: Niel Lambrechts User-Agent: Thunderbird 2.0.0.21 (X11/20090310) MIME-Version: 1.0 To: Arjan van de Ven CC: "linux.kernel" , James Bottomley , Pavel Machek , "Rafael J. Wysocki" , Linux IDE mailing list , Jeff Garzik Subject: Re: 2.6.29 regression: ATA bus errors on resume References: <49CD24BC.8040303@devnull.org> <20090327153044.3234722d@infradead.org> In-Reply-To: <20090327153044.3234722d@infradead.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/28/2009 12:30 AM, Arjan van de Ven wrote: > On Fri, 27 Mar 2009 21:10:52 +0200 > Niel Lambrechts wrote: > > >> I'm seeing some dubious looking ATA messages even on 2.6.28.9-pae, >> although with all the 2.6.28 variants I used s2disk/resume has always >> worked. I was wondering if these "errors" perhaps play more of a role >> in 2.6.29, perhaps due to the async. changes that was mentioned? >> > > unless you actively enabled this via a kernel command line option there > are no async changes in 2.6.29 in terms of behavior. > > > The only non-default option I had was 'modeset=1'. From Jeff's earlier comment I understood the probing behaviour changed. The fundamental difference is that in 2.6.29 everything initially seems okay, but then there is a ata1.00: exception Emask 0x10 SAct 0x3f SErr 0x50000 action0xe frozen ata1.00: irq_stat 0x00400008, PHY RDY changed There's nothing frozen it 2.6.28. Should I log a kernel bug, what's the best way forward and is there anything more I can do to help? cheers Niel